What's New in the JDBC Driver
Support for JDK 8
Support for Java Development Kit (JDK) version 8.0 in addition to JDK 7.0, 6.0, and 5.0.
JDBC 4.1 and 4.2 compliance
The bulk copy feature is used to quickly copy large amounts of data into tables or views in SQL Server databases. For details see Using Bulk Copy with the JDBC Driver.
XA transaction rollback option
Added new timeout options for existing automatic rollback of unprepared transactions. For detail see Understanding XA Transactions.
Information about Connecting to an Azure SQL Database
There is now a topic with information about connecting to an Azure SQL database. See Connecting to a Windows Azure SQL Database for more information.
Support for High Availability, Disaster Recovery
Support for high-availability, disaster recovery connections to AlwaysOn Availability Groups in SQL Server 2012. See JDBC Driver Support for High Availability, Disaster Recovery for more information.
Using Kerberos Integrated Authentication to Connect to SQL Server
Support for type 4 Kerberos integrated authentication for applications to connect to SQL Server database. For more information, see Using Kerberos Integrated Authentication to Connect to SQL Server. (Type 2 Kerberos integrated authentication is available in Microsoft JDBC Driver for SQL Server versions prior to 4.0.)
Accessing Diagnostic Information in the Extended Events Log
You can access information in the server's extended events log to understand connection failures. For more information, see Accessing Diagnostic Information in the Extended Events Log.
Additional Support for Sparse Columns
If your application already accesses data in a table that uses sparse columns, you should see an increase in performance. You can get information about columns (including sparse column information) with getColumns Method (SQLServerDatabaseMetaData). For more information about SQL Server sparse columns, see Using Sparse Columns.
The isSparseColumnSet method is added to the SQLServerResultSetMetaData class to indicate if a column in a result set is a sparse column set.
Prior to Microsoft JDBC Driver 4.0 for SQL Server, the JDBC driver received a format identifier from the application but did not pass that value to the database server. Instead, the JDBC driver passed a format identifier of 0 to the database server.
Beginning in Microsoft JDBC Driver 4.0 for SQL Server, the JDBC driver will pass the format identifier from the application to the database server. To get the updated behavior, make sure the sqljdbc_xa.dll on the server is updated. For more information on copying an updated version of sqljdbc_xa.dll to the server, see Understanding XA Transactions.