Microsoft JDBC Driver for SQL Server Team Blog

The Microsoft JDBC Driver now supports JRE 7

dpblogs — Fri, 19 Oct 2012 17:48:00 GMT

Greetings Developer Community,

The Microsoft JDBC Driver 4.0 for SQL Server now supports JRE 7. If you have applications running against JRE 6 (or 5) and roll them forward to execute against JRE7, the Microsoft JDBC driver is now fully supported.

It's important to note that:

This is valid only for the latest Microsoft JDBC Driver 4.0 for SQL Server;
This change requires no driver refresh, which means that if you already have the Microsoft JDBC Driver 4.0 for SQL Server deployed, you are good to go;
The driver does not support the JDK 7, which means that, if you recompile your application against Java7, you will experience compilation errors. This announcement is only for runtime execution.

Thanks

Luiz Santos

Sr. Program Manager

How Would You Use Table Valued Parameters (TVP)?

dpblogs — Tue, 03 Apr 2012 20:09:48 GMT

Many of you have asked for Table Valued Parameters (TVP) support in the Microsoft JDBC Driver for SQL Server. We have added TVP support to our roadmap and are gathering requirements (we don’t have an availability date yet).

We would like to hear more details about how you would use TVP’s and how TVP’s will benefit your organization. Many of you have told us that you currently pass structured data to SQL Server/SQL Azure using XML but we would like more
specifics.

Can you share snippets or samples of your existing code that you would like to retool to use TVP’s? Can you provide more details on how TVP’s will help you or your organization?

You can email us or comment on this blog.

Thanks,

Shamitha Reddy

Program Manager – Microsoft JDBC Driver for SQL Server

For technical support, please use our forums.

Microsoft JDBC Driver 4.0 for SQL Server Released!

dpblogs — Tue, 06 Mar 2012 22:31:00 GMT

Dear SQL Server Developer Community,

I am pleased to report that the Microsoft JDBC Driver 4.0 for SQL Server is now released. Thank you for all your great feedback on our three community technology previews (CTP). Our 4.0 release contains some great features which I would like to highlight.

Pure Java Kerberos

Customers using non-Windows platforms now have the option of using Kerberos for authentication. The table below summarizes available authentication options.

Platform	Authentication
Non-Windows	Pure Java Kerberos
Non-Windows	SQL Server
Windows	Pure Java Kerberos
Windows	SQL Server
Windows	Kerberos with NTLM backup
Windows	NTLM

We have several customers who have tested Kerberos via our CTP driver, some using Linux in a cross-realm environment.

Always On

The Microsoft JDBC Driver 4.0 for SQL Server supports AlwaysOn high availability and disaster recovery. Customers have the option to use AlwaysOn instead of database mirroring.
Some key features include

Ability to specify whether an application is connecting to an AlwaysOn Availability Group Cluster (multi subnet failover)
Ability to specify application intent as read only vs. read/write

Correlated Tracing with XEvents

SQL Server 2012 introduces a user interface for XEvents and users can choose to track driver related actions within XEvents. Simply set appropriate parameters for logging, create an XEvents session and the Microsoft JDBC Driver 4.0 for SQL
Server will send tracing information to XEvents to enable troubleshooting and monitoring. The correlation information will be available in all XEvent targets including in memory, the XEvents ring buffer, log files, and the viewer in management studio.

FormatID change in XA Transactions

Based on customer and partner feedback, we made a change to the way the FormatID field is handled in XA transactions. The Microsoft JDBC Driver 4.0 for SQL Server will now use the provided formatID field in all XA transactions.

Other features

Other features include UTF-16 support, enhanced SQL Azure support, support for sparse columns,and bug fixes.

Documentation, Feedback and Download

You can find documentation on the driver at our MSDN documentation page, obtain technical support via our forums or Microsoft Customer Support, report bugs via the SQL Server Connect Site, and (most importantly!) download the new driver here.

Thank you for your support and we look forward to your feedback.

Shamitha Reddy

Program Manager - Microsoft JDBC Driver for SQL Server

Hotfix Available for Date Issue When Using JRE 1.7

dpblogs — Fri, 20 Jan 2012 21:34:00 GMT

Dear SQL Server developers and users:

Thank you for your ongoing support of the Microsoft JDBC Driver for SQL Server. Some of you reported problems with dates when using JRE 1.7.

The Microsoft JDBC Driver for SQL Server currently supports JRE 1.5 & JRE 1.6, however we have made modifications to return correct date values regardless of the JRE version. This modification is available in the production version of the Microsoft JDBC Driver 4.0 for SQL Server. The Microsoft JDBC Driver 4.0 for SQL Server
is supported on JRE 1.5 and JRE 1.6, and support for JRE 1.7 is on our roadmap.

In addition, the driver modification is also available for SQL Server 2000 customers as a hotfix in the 3.0 version of our driver. Please review the hotfix article to determine if the fix is applicable to you and if so, click the link to download the hotfix (applicable for all platforms).

As always we are interested in your feedback. You may report bugs and issues via our forums. If you encounter Java bugs you may report those to Java.

Thank you,
Shamitha Reddy
Program Manager Microsoft JDBC Driver for SQL Server

For technical support, please use our forums.

Patch Available for SQL Server and Java 6 update 30

dpblogs — Thu, 19 Jan 2012 16:37:00 GMT

Dear SQL Server developers and users:

Thank you for your ongoing support of the Microsoft JDBC Driver for SQL Server. We have an update on the connection issues some of you experienced when using Java 6 update 29 and above.

Java 6 update 29 (6u29) introduced a change to how data is sent to databases to counteract the so-called BEAST vulnerability. Shortly after the release of 6u29, we began to receive reports of users experiencing connection failures or hangs when using the Microsoft JDBC Driver for SQL Server to connect to SQL Server.

Oracle has released Java 6 update 30 (6u30) which behaves differently from JRE 6u29. Microsoft recommends that our customers use JRE 6u30 (and above) instead of JRE 6u29. In addition, Microsoft is releasing an interoperability enhancement that will enable SQL Server to process data from Oracle JRE 6u30 and up.

This interoperability enhancement is available in the following SQL Server versions.

This enhancement is independent of your JDBC Driver version; Microsoft recommends that customers upgrade their SQL Server installation based on the list above prior to upgrading their Java version.

Please keep in mind that other JVM vendors may introduce this BEAST related change in the future. Before upgrading your JVM version, Microsoft suggests you determine if the new JVM version contains this change and update your SQL Server installation accordingly.

You can obtain the relevant SQL Server cumulative update by clicking the link in the Knowledge base article for that cumulative update or contacting Microsoft Customer Support.

Customers who are running older versions of SQL Server have the following options available to them.

Upgrade to a SQL Server version that contains our enhancement
Use Oracle Java 6 update 27 or lower (or another JVM version that does not contain the BEAST change)
Disable the BEAST change in the JVM (consult your JVM vendor for details)
Prefer RC4 cipher suites via Windows Schannel

For additional details see Knowledge Base article 2653857.

We look forward to your feedback on this enhancement.

Thank you,

Shamitha Reddy

Program Manager Microsoft

For technical support, please use our forums or contact Microsoft Customer Support.

Using SQL Azure and the Microsoft JDBC Driver?

dpblogs — Thu, 12 Jan 2012 20:42:00 GMT

Dear SQL Server developers and users:

Are you using the Microsoft JDBC Driver for SQL Server to access SQL Azure?

If so, we would like to talk to you about your experience. Please contact us via the following (http://blogs.msdn.com/b/jdbcteam/contact.aspx) if you would like to provide us with more information.

Thank you for your ongoing support of the Microsoft JDBC Driver for SQL Server,

Shamitha Reddy

Program Manager Microsoft JDBC Driver for SQL Server

Available Today: Preview Release of the SQL Server [C/C++] ODBC Driver for Linux

dpblogs — Tue, 29 Nov 2011 22:27:00 GMT

This has been re-posted from the SQL Server Team Blog.

In our continued commitment to interoperability, we are very excited to announce the availability of a preview release of the SQL Server ODBC Driver for Linux! This release will allow native developers to access Microsoft SQL Server from Linux operating systems. To assist our customers with native applications on multi-platform we have ported our existing, reliable and enterprise-class ODBC for Windows driver (a.k.a. SQL Server Native Client, or SNAC) to the Linux platform. Download the driver today here!

In this release, the SQL Server ODBC Driver for Linux will be a 64-bit driver for Red Hat Enterprise Linux 5. We will support SQL Server 2008 R2 and SQL Server 2012 with this release of the driver. Notable driver features (in addition to what you would expect in an ODBC driver) include support for the Kerberos authentication protocol, SSL and client-side UTF-8 encoding. This release also brings proven and effective tools and the BCP and SQLCMD utilities to the Linux world.

This SQL Server ODBC Driver for Linux provides a Microsoft-supported solution for C and C++ applications that target SQL Server. It also provides a mechanism for applications and runtimes that leverage ODBC to access SQL Server from Linux platforms. For customers who want to move from Sybase to SQL Server, the SQL Server ODBC Driver for Linux allows C and C++ code to continue running in Linux environments. For additional information on the first release of Microsoft ODBC Driver for Linux please refer to our ODBC Driver on Linux Documentation.

This release marks a big milestone in Microsoft’s continued commitment to interoperability and our alignment with ODBC as the preferred way to access SQL Server. Download the driver today; please provide your feedback and ask us questions via our forums; or post a comment via Microsoft Connect. We look forward to hearing from you.

Thanks,

Shekhar Joshi
Senior Program Manager
Microsoft SQL Server ODBC Driver For Linux

Supported Java Versions - January 2012

dpblogs — Mon, 07 Nov 2011 21:38:00 GMT

Dear SQL Server developers and users:

Thank you for your ongoing support of the Microsoft JDBC Driver for SQL Server.

We have recently had some questions regarding which versions of Java are supported by the Microsoft JDBC Driver for SQL Server. We support Java 5.0 and Java 6.0 currently. We are looking forward to adding support for Java 7.0 in the future as well. Look for updates on this blog and our website.

In addition, there are known connection failure issues with Java 6 update 29, Java 6 update 30, and above. We are rolling out SQL Server patches for this issue, see this blog post for details.

There is also a known date issue with JRE 1.7, our 4.0 driver (production release) contains a fix for this issue. In addition, our 3.0 driver also corrects this issue via a hotfix.

The Microsoft JDBC Driver does not yet support Java 7.0, if you wish to do some early non production testing of Java 7.0 with our driver, you may report Java bugs & issues to Java and Microsoft bugs & issues via our forums.

Thank you,
Shamitha Reddy
Program Manager Microsoft JDBC Driver for SQL Server

For technical support, please use our forums.

Announcing Microsoft SQL Server ODBC Driver for Linux

dpblogs — Thu, 13 Oct 2011 17:10:00 GMT

Greetings Developer community:

We heard yesterday and today at the PASS conference about the exciting new areas that we are investing in to bring the power of SQL Server to our customers.

Many of our developers who rely on native connectivity to SQL Server primarily use ODBC for their connectivity needs. We have been supporting ODBC as a part of the SQL Native Access Client (SNAC) libraries. In our continued commitment to interoperability, today we also announced that we will be releasing the Microsoft SQL Server ODBC Driver for Linux. We will be releasing the first community technology preview (CTP) around mid-November and it will be available along with SQL Server 2012 when it is released. Please look for the announcement on our SQL Connectivity home page and SQL Server blog page.

We will be showcasing the Microsoft SQL Server ODBC Driver for Linux along with our Java and PHP solutions for SQL Server and Azure at PASS conference session:

“[AD-211-M] Developing Multi-Platform Applications for Microsoft SQL Server and Azure” on Thursday October 13th at 5:00PM at Washington State Convention Center Room #4C4.

Also, if you have any questions or feedback on our multi-platform strategy as well as the entire gamut of support we provide to application developers, I encourage you to attend the PASS Panel Discussion with the SQL Connectivity Leadership team.

“[AD-101-M] SQL Connectivity Leadership Unplugged” on Friday, October 14, 2011, 2:30 PM - 3:45 PM at Washington State Convention Centre Room# 612 where I will host a panel along with the rest of the leadership team that drives the strategy for our application platform.

Thanks,
Raghu Ram
Principal Group Program Manager
SQL Server

Microsoft JDBC Driver 4.0 for SQL Server CTP3 is Released!!!

dpblogs — Wed, 12 Oct 2011 00:05:23 GMT

Dear SQL Server developers and users:

Thank you for providing great feedback on our first two Community Technology Previews (CTPs) of Microsoft JDBC Driver 4.0 for SQL Server. I am very pleased to announce the availability of our third CTP. This CTP expands on our support for SQL Server AlwaysOn in Denali by adding read only routing functionality on the client side.

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.

Thank you,
Shamitha Reddy, Program Manager Microsoft

TVP or Bulk Copy?

dpblogs — Thu, 22 Sep 2011 22:53:00 GMT

SQL Server developer community thanks for all your input to date for our roadmap. I am the new Program Manager for Microsoft JDBC Driver for SQL Server and would like input while planning our next release.

In the past, we have had requests for both Table-Valued Parameters (TVP) as well as bulk copy API. We would like to understand which of these two is most important to your organization.

Please vote for the feature you would most like to see added to our JDBC driver.

To vote for TVP http://mssqlconn.uservoice.com/forums/113295-feature-feedback/suggestions/2269687-table-valued-parameters-tvp-support-in-jdbc

To vote for Bulk Copy API http://mssqlconn.uservoice.com/forums/113295-feature-feedback/suggestions/2269691-bulk-copy-api-support-in-jdbc

This data will help us to determine the priority of these two items for our roadmap. Also, please provide the specific scenarios in which you would like to use the feature via our blog or while voting in the User Voice forum.

Shamitha Reddy
Program Manager - Microsoft

Update January 2012

Thank you all for your feedback. Based on your votes and comments, we have added TVP to our roadmap. Bulk copy is still on our to do list as well.

Update March 2012
For those of you who are interested in TVP, please provide us with more details on how you would use this feature. You can email us or comment on the following blog post.

Annual SQL Connectivity Customer Survey Deadline Extended

dpblogs — Thu, 08 Sep 2011 01:18:00 GMT

Thank you very much for an overwhelming response on our survey. Feedback is continuing to pour in. We are extending the deadline to complete the survey to September 16^th, 2011 to allow everyone to provide input. Your feedback helps us on the broad SQL Connectivity components that address major development platforms, including ODBC, ADO.NET, JDBC and PHP.

We view your organization as a key stakeholder in the process that we have to identify areas for future investments. The feedback you provide is valuable and each response will be read and will be treated with utmost confidence. The survey can be found in the link below and will be available until 16^th September, 2011 5:00 PM PST.

http://www.zoomerang.com/Survey/WEB22CS45XT9FE/

Thanks

SQL Team

Annual SQL Connectivity Customer Survey Deadline Extended

dpblogs — Thu, 08 Sep 2011 01:17:56 GMT

http://www.zoomerang.com/Survey/WEB22CS45XT9FE/

Thanks

SQL Team

Checking Your SQL Azure Server Connection

dpblogs — Mon, 29 Aug 2011 23:41:47 GMT

This entry has been cross-posted from the Windows Azure Team Blog.

As the SQL Azure July 2011 Service Release is being rolled out, we want to advise you of an important consideration for your application logic. Some customers may be programmatically checking to determine if their application is connected to SQL Azure or another edition of SQL Server. Please be advised, you should not base your application logic on the server version number, since it changes across upgrades and service releases. It is okay, however, to use the version number for logging purposes.

If you want to check to see if you’re connected to SQL Azure, use the following SQL statement:

SELECT SERVERPROPERTY('EngineEdition') == 5.

See the SQL Server Books Online for a full description of the SERVERPROPERTY function.

The current SQL Azure service release will upgrade the underlying SQL Azure database engine version from 10 to version 11 as it is rolled out across data centers.

You will see this server version number change show up in server-side APIs such as:

• SERVERPROPERTY('ProductVersion')

• @@VERSION

and also client-side APIs such as:

• ODBC: SQLGetInfo (SQL_DBMS_VER)

• SqlClient: SqlConnection.ServerVersion

There will be a period of time during the service upgrade, measured in days, during which some user sessions will connect to version 10.25.bbbb.bb SQL servers and other user sessions will connect to version 11.0.bbbb.bb SQL servers (bbbb.bb is the build #). One given user connection to one database may see different server version numbers reported at different times. At the end of the upgrade all sessions will be connecting to version 11.0.bbbb.bb SQL Servers.

User queries and applications should continue to function normally and should not be adversely affected by the upgrade.

The July 2011 Service Release is foundational, with significant upgrades to the underlying engine that are designed to increase overall performance and scalability. This upgrade also represents a big first step towards providing a common base and feature set between the cloud SQL Azure service and our upcoming release of SQL Server Code Name “Denali”. Please read the blog post, “Announcing: SQL Azure July 2011 Service Release” for more information.

Annual SQL Connectivity Customer Survey

dpblogs — Mon, 15 Aug 2011 21:23:00 GMT

Greetings to the Developer community:

Microsoft SQL Server team has been interacting on a regular basis with the developers and users in the form of surveys. During the last 2 years, we completed surveys that focused on the broad SQL Connectivity components that address major development platforms, including ODBC, ADO.NET, JDBC and PHP. These surveys provide us with an ability to validate some of the requests we have got from developers, users and partners such as you as well as ideas that we have gathered internally as a part of our development process. You have seen our roadmap for SQL Server evolve based on the feedback that we have received.

http://www.zoomerang.com/Survey/WEB22CS45XT9FE/

Thank you,

Raghu Ram

Principal Group Program Manager

SQL Connectivity

SQL Server RDBMS Group

Microsoft Corporation

Microsoft JDBC Driver 4.0 for SQL Server CTP2 is Released!!!

dpblogs — Tue, 12 Jul 2011 21:45:00 GMT

Dear SQL Server developers and users:

Thank you for providing great feedback on our first Community Technology Preview (CTP) of Microsoft JDBC Driver 4.0 for SQL Server. I am very pleased to announce the availability of our second CTP. This CTP includes bug fixes based on your feedback and additional features in “Denali”.

This release includes:

- Type-4 Kerberos Integrated Security

Support for authentication via TGT in cache
Login configuration file support
Single sign-on through mid-tier

- Client side support for SQL Server AlwaysOn Feature for Denali

Support for multi-subnet failover for AlwaysOn
Support for connecting to read-only replicas for AlwaysOn

- Support for SQL Azure

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.

Thank you,

Amina Saify, Program Manager – SQL Server/JDBC

SQL Connectivity UserVoice Site is Live!

dpblogs — Tue, 24 May 2011 21:36:27 GMT

Greetings to the SQL Server community:

Back around October 2009, we introduced the process of interacting on a regular basis with the developers and users in the form of surveys. Today, we are happy to introduce the ability for you to suggest and vote on feature scenarios through UserVoice. Our UserVoice site http://mssqlconn.uservoice.com enables you to vote for the feature most important to you and if you do not see the feature you need most, you can enter your own feature idea. This provide us with the ability to validate some of the requests we have got from developers, users and partners such as you as well as ideas that we have gathered internally as a part of our development process.

Regards,

Microsoft SQL Server

Thank you for your feedback!!!

dpblogs — Fri, 04 Mar 2011 01:54:08 GMT

Dear SQL Server developers and users:

Thank you for taking the time to evaluate our Microsoft JDBC Driver 4.0 for SQL Server Community Technical Preview (CTP). We have received some great feedback and we will be making appropriate changes based on it. The Microsoft JDBC team truly appreciates all the effort and enthusiasm by the community. We are in the execution phase of our development and we will stop taking bug fixes on this CTP by March 30th, 2011. Bugs reported after that date will be considered in future milestones. So if you have not tried our driver, this is your chance!

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.

Thank you,

Amina Saify, Program Manager – SQL Server/JDBC

Microsoft SQL Server JDBC 3.0 and SQL Azure

dpblogs — Tue, 22 Feb 2011 02:21:00 GMT

Dear SQL Server and SQL Azure developers and users:

We are very pleased to announce the availability of an updated version of Microsoft SQL Server JDBC Driver 3.0 supporting Microsoft SQL Azure database:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ae924066-2946-40a7-93c6-c7e83f54072f&displaylang=en

This updated version supersedes the release version of SQL Server JDBC Driver 3.0 and also addresses an issue with JDBC API getSchemas. For further information on getSchema issue, please refer to http://support.microsoft.com/kb/2504052 and the corresponding release notes.

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.

The previous release version of Microsoft SQL Server JDBC Driver 3.0 is available here for reference:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a737000d-68d0-4531-b65d-da0f2a735707&displaylang=en

If you do not plan to connect to SQL Azure or are not impacted by getSChema issue, you can continue to use the previous release of Microsoft SQL Server JDBC Driver 3.0

Thank you

Amina Saify [SQL Server]

Microsoft JDBC 4.0 Driver for SQL Server CTP is Released!!!!

dpblogs — Sat, 22 Jan 2011 01:19:00 GMT

Dear SQL Server developers and users:

As a follow up to my last post regarding the next release of our JDBC driver called the Microsoft JDBC Driver 4.0 for SQL Server, I am very pleased to announce the availability of our first community technology preview (CTP).

http://www.microsoft.com/downloads/details.aspx?FamilyID=49c554ca-41a0-472c-b728-75df5789369c

This release includes:

- Type-4 Kerberos Integrated Security

o Support for authentication via TGT in cache

o Login configuration file support

- Client side support for SQL Server AlwaysOn Feature for Denali

o Support for multi-subnet failover for AlwaysOn

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.

Thank you,

Amina Saify, Program Manager – SQL Server/JDBC

Next release of Microsoft JDBC Driver...

dpblogs — Wed, 19 Jan 2011 04:13:00 GMT

Dear SQL Server developers and users:

Happy new year to all the SQL Server® developers and users! In my last post I mentioned that the Microsoft® JDBC team is working very hard on the next release of our JDBC driver for SQL Server. We will be coming out with the community technology preview (CTP) of the next version of the JDBC driver called “Microsoft JDBC Driver 4.0 for SQL Server” in the next few days.

Based on your input in our JDBC survey in April 2010, one of the main features which we are introducing in Microsoft JDBC Driver 4.0 for SQL Server is support for type-4 Kerberos integrated security. Type-4 Kerberos integrated security came out to be the number one feature ask from the SQL Server developer community. In this release we will be adding support for authentication via TGT in cache and login configuration file support.

This version of the JDBC driver will also provide support for features in Microsoft SQL Server code-named 'Denali' such as AlwaysOn. SQL Server AlwaysOn is the new comprehensive high availability and disaster recovery solution. Using AlwaysOn, you can increase application availability and get a better return on your hardware investments through a simplified high availability (HA) deployment and management experience. In this CTP, we have added support for multi-subnet failover for AlwaysOn, which allows a JDBC client to connect to a SQL Server that has failed over on a secondary node in a different subnet.

Stay tuned to our blog for the CTP release announcement!

Thank you,

Amina Saify, Program Manager – SQL Server/JDBC

Happy Holidays from Microsoft JDBC Team

dpblogs — Wed, 22 Dec 2010 18:32:00 GMT

Dear SQL Server developers and users, Based on your input via a survey back in April 2010, various customer engagements, forums, SQL PASS conference, JDBC team has been working very hard on the next release of Microsoft JDBC driver for SQL Server. We are getting ready to bring our first community technology preview (CTP) to SQL Server and Java users early next year. Stay tuned to our blog for the official CTP announcement next year. We would love to hear your feedback!

Wishing you happy holidays from SQL Server and JDBC team at Microsoft.

SQL Server Customer Survey (Fall 2010)

dpblogs — Tue, 19 Oct 2010 00:38:45 GMT

Greetings to the SQL Server community:

Last year in October 2009, we introduced the process of interacting on a regular basis with the developers and users in the form of surveys. During the last 12 months, we completed surveys that focused on the broad SQL Connectivity components, including ODBC, ADO.NET, JDBC and PHP. These surveys provide us with an ability to validate some of the requests we have got from developers, users and partners such as you as well as ideas that we have gathered internally as a part of our development process. You have seen our roadmap for SQL Server evolve based on the feedback that we have received.

The survey can be found in the link below and will be available until 25th October, 2010 5:00 PM PST.

http://www.zoomerang.com/Survey/WEB22BAW29Z8P2

Thank you,

Raghu Ram

Principal Group Program Manager

SQL Connectivity

SQL Server RDBMS Group

Microsoft Corporation

Support Matrix for Microsoft SQL Server JDBC Driver

dpblogs — Fri, 02 Jul 2010 22:44:00 GMT

Dear SQL Server developers and users:

In the last few weeks, I have received a number of queries on which driver version is supported with which SQL server version. I have created a support matrix describing the supported configuration. Matrix also lists the dates when we plan to end support for each driver.

Driver Name	Supported SQL Server Version	JRE	End of Support
Microsoft SQL Server 2000 JDBC	SQL Server 2000	1.4 or later	July 9^th 2010
Microsoft SQL Server 2005 JDBC Driver 1.0	SQL Server 2000, SQL Server 2005	1.4 or later	June 25^th 2011
Microsoft SQL Server 2005 JDBC Driver 1.1	SQL Server 2000, SQL Server 2005	1.4 or later	June 25^th 2011
Microsoft SQL Server 2005 JDBC Driver 1.2	SQL Server 2000, SQL Server 2005	1.4 or later	June 25^th 2011
Microsoft SQL Server JDBC Driver 2.0	SQL Server 2000, SQL Server 2005, and SQL Server 2008	1.5 or later	December 31^st 2012
Microsoft SQL Server JDBC Driver 3.0	SQL Server 2000, SQL Server 2005, SQL Server 2008 and SQL Server 2008R2	1.5 or later	April 23^rd 2015

Hopefully this matrix will help you in determining the supported configuration for your solution. Thank you for choosing Microsoft SQL Server JDBC Driver!

Thank you,

Amina Saify [SQL Server]

Announcing End of Support for SQL Server JDBC Driver 1.0, 1.1 and 1.2

dpblogs — Fri, 25 Jun 2010 22:53:00 GMT

Dear SQL Server developers and users:

On June 25th 2011, Microsoft will end support for SQL Server JDBC Driver 1.0, 1.1 and 1.2. Microsoft will retire public and technical support, including security updates, on this date.

We will discontinue the download for these three versions on December 1^st, 2010 even though we continue to support these versions through June 25^th 2011.

Thank you,

Amina Saify [SQL Server]