JDBC 2005 v1.1 is now available.


The v1.1 2005 JDBC driver is now available for download here:


http://msdn.microsoft.com/data/ref/jdbc/


 


This is a release I am personally really proud of, and we could not have done it without you!


 


Maybe it’s the fact that not that many people in the company are doing java development, that we are using eclipse as our main IDE, junit for our testing, using JBOSS and other application servers, the Solaris machine and multiple unix flavors we play with…  Maybe it’s the short fast and furious product cycles with betas thrown in for good measure, we have shipped two products and three betas in little over a year.   


 


I like to think that one of the most important things we have going for us here is the feedback we are getting from the java community. I am not going to go and claim that we have been embraced , but there have been a set of people that just _get_ what we are trying to do here and are willing to work with us in this space. To those of you, thank you and looking forward to more of your feedback and support.


 


New features for v1.1


Integrated security:


Only supported on Windows OS, this feature allows your JDBC driver to connect to Sql Server using your Windows credentials.


 


Client Failover, Database Mirroring support:


The JDBC v1.1 driver will work with the Sql Server 2005 Database Mirroring feature: http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx


 


When connecting to a Sql Server 2005 Database that has a failover partner the JDBC v1.1 driver will cache failover information and retry to the failover partner on primary failure. Additionally you can use the new “failoverPartner” connection string keyword to handle initial connection failure scenarios.


 


packetSize


[512..32767] Default  4096. The network packet size used to communicate with SQL Server, specified in bytes. This feature allows you to customize the network packet size to handle larger than 256MB data and to optimize performance in some scenarios.


 


 


Here are some of the important issues that got resolved this release.


For the complete list take a look at the release.txt file that ships with the v1.1 package.


NOTE: the numbers are just IDs to be used to identify specific issues, they do not have any real meaning.


 


426389 Calling Statement.execute no longer causes an SQLException with the


       message “sp_cursoropen/sp_cursorprepare: The statement parameter can


       only be a single select or a single stored procedure” for UPDATE


       WHERE queries when the selectMethod=cursor connection property is set.


 


436718 Calling PreparedStatement.execute no longer causes an SQLException


       with the message “sp_cursoropen/sp_cursorprepare: The statement


       parameter can only be a batch or a stored procedure with a single


       select, without FOR BROWSE, COMPUTE BY, or variable assignments” for


       INSERT INTO queries when the selectMethod=cursor connection property is set.


 


450639 The driver no longer throws an SQLException with the message “Server


       failed to resume the transaction, desc:  4600000001.” when configuring


       SQL Server 2005 as the JBoss JMS message store.


 


435796 Executing SQL WRITETEXT statements no longer throws an SQLException


       with the message “No TDS_RET_STATUS was found for the stored procedure


       output parameters.”


 


424295 DatabaseMetaData.getMaxConnections no longer throws an SQLException with


       the message “The configuration option ‘user connections’ does not exist,


       or it may be an advanced option” for SQL Server 2005 servers.


 


433394 Calling Statement.executeBatch after setting a BLOB value no longer throws


       an SQLException with the message “The conversion from BLOB to BINARY is unsupported.”


 


435448 The driver no longer throws an SQLException with the message


       “com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ‘-‘”


       when sending a BigDecimal prepared statement parameter value to the server


       with the 5.0 JRE.