Frequently Asked Questions for Microsoft JDBC Driver for SQL Server
This article provides answers to frequently asked questions about the Microsoft JDBC Driver for SQL Server.
See our documentation for more details.
Questions and Answers
1. Question: Which versions of SQL Server and Java does the driver support?
Answer: See the support matrix page for details.
2. Question: What should I know when upgrading my driver?
Answer: The Microsoft JDBC Driver for SQL Server supports both JDBC 3.0 and JDBC 4.0 specifications and includes two JAR class libraries in the installation package for each specification: sqljdbc.jar and sqljdbc4.jar, respectively.
See System Requirements for the JDBC Driver for more details.
In addition, review What’s New in the JDBC Driver for details on changes included in that release.
3. Question: Do I need to make any code changes in my application to use the latest driver with my existing SQL Server version?
Answer: In general, we design the driver to be backward compatible so that you do not need to change your existing applications when upgrading the driver. In the event that a new driver version introduces a breaking change, the What’s New in the JDBC Driver section will provide clear details on the change and the impact to existing applications. In addition, you can review the release notes included with the driver for a list of bugs fixed in that release and known issues.
4. Question: How much does the driver cost?
Answer: The Microsoft JDBC Driver for SQL Server is available at no additional charge.
5. Question: Can I redistribute the driver?
Answer: The driver is freely redistributable under a separate Redistribution License that requires registration. To register or for more information, see our Redistribution Page.
6. Question: Can I use the driver to access Microsoft SQL Server from a Linux computer?
Answer: Yes! You can use the driver to access SQL Server from Linux, Unix, and other non-Windows platforms. See our support matrix for more details.
7. Question: Does the driver support Secure Sockets Layer (SSL) encryption?
Answer: Starting with version 1.2, the driver supports Secure Sockets Layer (SSL) encryption. For more information, see Using SSL Encryption.
8. Question: Which authentication types are supported by the Microsoft JDBC Driver for SQL Server?
Answer: The table below lists available authentication options. Note that pure Java Kerberos authentication is available starting with the 4.0 release of the driver.
9. Question: Does the driver support Internet Protocol version 6 (IPv6) addresses?
Answer: Yes, the driver supports the use of IPv6 addresses with the connection properties collection and with the serverName connection string property. For more information, see Building the Connection URL.
10. Question: What is adaptive buffering?
Answer: Adaptive buffering is introduced starting with Microsoft SQL Server 2005 JDBC Driver version 1.2, and is designed to retrieve any kind of large-value data without the overhead of server cursors. The adaptive buffering feature of the Microsoft SQL Server JDBC Driver provides a connection string property, responseBuffering, which can be set to "adaptive" or "full". Starting with the JDBC Driver version 2.0, the default behavior of the driver is "adaptive". In other words, in order to get the adaptive buffering behavior, your application does not have to request the adaptive behavior explicitly. In the version 1.2 release, however, the buffering mode was "full" by default and the application had to request the adaptive buffering mode explicitly. For more information, see Using Adaptive Buffering topic and the blog What is adaptive response buffering and why should I use it?.
11. Question: Does the driver support connection pooling?
Answer: The driver provides support for Java Platform, Enterprise Edition 5 (Java EE 5) connection pooling. The driver implements the JDBC 3.0 required interfaces to enable the driver to participate in any connection-pooling implementation that is provided by middleware application server vendors. The driver participates in pooled connections in these environments. For more information, see Using Connection Pooling. The driver does not provide its own pooling implementation, but rather it relies on third-party Java application servers.
12. Question: Is support available for the driver?
Answer: Several support options are available. You may post your question to our forums which are monitored by Microsoft, MVP’s, and the community. You may also contact Microsoft Customer Support. We may ask you to reproduce the issue outside any third-party application servers. If the issue cannot be reproduced outside the hosting Java container environment, you will need to involve the related third-party so that we can continue to assist you.We may also ask you to reproduce your issue on an operating system such as Windows so we can best assist you.
13. Question: Is the driver certified for use with any third-party application servers?
Answer: The driver has been tested against various application servers including IBM WebSphere and SAP Netweaver.
14. Question: How do I enable tracing?
Answer: The driver supports the use of tracing (or logging) to help resolve issues and problems with the JDBC Driver when it is used in your application. To enable the use of client-side JAR tracing, the JDBC Driver uses the logging APIs in java.util.logging. For more information, see Tracing Driver Operation. For server-side XA tracing, see Data Access Tracing in SQL Server.
15. Question: Where can I download older versions of the driver such as the SQL Server 2000 JDBC driver, 2005 driver, 1.0, 1.1, or 1.2 driver?
Answer: These driver versions are not available for download as they are no longer supported. We are continually improving our Java connectivity support. As such we highly recommend you work with the latest version of our JDBC driver.
16. Question: I am using JRE 1.4. Which driver is compatible with JRE 1.4?
Answer: For customers who are using SAP products and require JRE 1.4 support, you may contact SAP Service Marketplace to obtain the 1.2 Microsoft JDBC driver.
17. Question: Can the driver communicate using FIPS validated algorithms?
Answer: The Microsoft JDBC Driver does not contain any cryptographic algorithms. If a customer leverages operating system, application, and JVM algorithms that are deemed acceptable by Federal Information Processing Standards (FIPS) and configures the driver to use those algorithms then the driver will use only the designated algorithms for communication.
For more information about support for this driver and the support matrix, see our Support Matrix.