Microsoft SQL Server 2005 JDBC Driver — RTW [Shelby Goerlitz]

After two betas and 6 months of customer feedback the SQL Server 2005 JDBC Driver is generally available for download here –


Our core goal with this new driver is to demonstrate our long-term commitment to providing enterprise-class SQL Server data access support for the Java development community – to include JDBC in the family of data access technologies that Microsoft ships for SQL Server:  ADO.Net, MDAC, and SQL Native Client.


To ship this version of the driver we worked closely with most of the major technology vendors in J2EE and we look forward to extending those relationships to make SQL Server an even better fit for Java developers.


A big thanks to all the customers who left feedback and comments for our betas – we did our best to get back to everyone and we look forward to hearing from you in the future.


-Shelby Goerlitz

Microsoft SQL Server Data Programmability

Comments (2)

  1. Richard Yeo says:

    We are in the process of migrating the application that runs our business

    from Sybase ASE 12.5.3 to MS SQL Server 2005 SP x64

    Our application is a large java application which runs on Redhat Enterprise

    Linux 4, Tomcat, etc.

    We have written a standalone java console application to test the

    performance of the Microsoft JDBC driver (released version not beta version) that uses our existing applications

    database abstraction layer to call a stored procedure that inserts a record

    into a database table.

    Sybase ASE with Sybase JDBC driver = 780 calls per second

    SQL Server with MS JDBC driver = 463 calls per second

    the difference in performance would appear to be purely down to the JDBC

    driver as we know SQL server is capable of over 1,100 calls per second using

    MS ADO let alone ADO.Net 2.0 (which uses Sql server 2005’s new native client


    All testing was done on the same hardware spec servers.

    Does anybody within Microsoft have any ideas why the performance is so bad?

  2. MSDN Archive says:


    Your best best is to ask here: