SQL SERVER - Drivers for PHP, JDBC, ODBC and OLE DB settings A driver is software that allows your computer to communicate with hardware, devices or other software. Without drivers, the software or hardware you connect to your computer will not work properly.

Here is the list of the drivers which are available for SQL Server to connect from multiple applications and programming language.

Microsoft JDBC Driver 4.0 for SQL Server
The JDBC driver can access many of the features including database mirroring; the xml, user-defined, and large-value data types; and it supports the new “snapshot” transaction isolation.

Microsoft Drivers for PHP for SQL Server
The Microsoft Drivers for PHP for SQL Server API includes support for Windows Authentication, transactions, parameter binding, streaming, metadata access, and error handling.

Microsoft ODBC Driver for SQL Server
The Microsoft ODBC Driver for SQL Server is comprised of an ODBC driver for Windows and an ODBC driver for Linux.

Microsoft OLE DB Provider for DB2 Version 4.0
The Data Provider takes advantage of Microsoft SQL Server data access architecture together with a Microsoft network client for DB2 that functions as a Distributed Relational Database Architecture (DRDA) application requester. The Data Provider converts the Microsoft Component Object Model (COM) OLE DB commands and data types to DRDA protocol code points and data formats.

Reference: Pinal Dave (https://blog.sqlauthority.com)

SQL Download
Previous Post
SQL SERVER – Weekly Series – Memory Lane – #037
Next Post
SQL – What ACID stands in the Database? – Contest to Win 24 Amazon Gift Cards and Joes 2 Pros 2012 Kit

Related Posts

1 Comment. Leave new

  • Answer1:
    A database guarantees the following four properties to ensure database reliability, as follows:
    Atomicity: (DO-or-DIE)
    A database follows the all or nothing rule, i.e., the database considers all transaction operations as one whole unit or atom. Thus, when a database processes a transaction, it is either fully completed or not executed at all.
    In above example if any one of statement becomes fails in the TRY block then engine has to revert back to initial stage (i.e. NONE of the statements will be considered); whereas ALL statements will be committed in the case of no error.

    Consistency: Ensures that only valid data following all rules and constraints is written in the database. When a transaction results in invalid data, the database reverts to its previous state, which abides by all customary rules and constraints.
    Example: To maintain data integrity throughout the database this rule will be useful. Here SQL engine checks for all constraints to maintain consistent data. In the above example if there occurs any constraint (foreign key, unique key, check constrains) violation entire transaction will be rolled back to original state.

    Isolation: Ensures that transactions are securely and independently processed at the same time without interference, but it does not ensure the order of transactions. i.e. Two database transactions happening at same time should not affect each other and has consistent view of database. This is achieved by using isolation levels in database.
    For example, user A withdraws $100 and user B withdraws $250 from user Z’s account, which has a balance of $1000. Since both A and B draw from Z’s account, one of the users is required to wait until the other user transaction is completed, avoiding inconsistent data. If B is required to wait, then B must wait until A’s transaction is completed, and Z’s account balance changes to $900. Now, B can withdraw $250 from this $900 balance.

    Durability: Data has to be persisted successfully in database once transaction completed successfully and it has to be saved from power outage or other threats. This is achieved by saving data related to transaction in more than one places along with database.
    In the above(isolation) example, user B may withdraw $100 only after user A’s transaction is completed and is updated in the database. If the system fails before A’s transaction is logged in the database, A cannot withdraw any money, and Z’s account returns to its previous consistent state.

    NuoDB installation file is of size 153 MB for Windows Platform.


Leave a Reply