Angel Saenz-Badillos : JDBC General

JDBC 2005 v1.1 is now available.

angelsb — Wed, 23 Aug 2006 00:51:00 GMT

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...(read more)

JDBC June 2006 Community Tech Preview available.

angelsb — Mon, 26 Jun 2006 19:03:00 GMT

Announcing the June 2006 Community Tech Preview of the JDBC 2005 driver: http://www.microsoft.com/downloads/details.aspx?familyid=f914793a-6fb4-475f-9537-b8fcb776befd&displaylang=en This preview contains all the changes of CTP 1 including Integrated...(read more)

JDBC v1.1 CTP and the Product Feedback Center

angelsb — Thu, 20 Apr 2006 23:35:00 GMT

When you get down to it Customer feedback is what makes a project like this interesting and worthwhile. This is the first project I have worked in where the Product Feedback Center has made such an important difference and a BIG thank you to those of you that have taken the time to file bugs directly on the JDBC provider: http://lab.msdn.microsoft.com/productfeedback/default.aspx

I want to make sure that you understand that we take these bugs very seriously. We triage them daily and treat them as the highest priority bugs come release time. Here is a list of customer bugs that we have received since we shipped RTM.

All of these bugs have been fixed in our latest JDBC V1.1 CTP. you can download this CTP by contacting the JDBC project manager directly at shelbyg<at>Microsoft<dot>com.

Bug Details: Statement.execute() returns incorrect results for stored procedures

http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=dc43eb80-69b5-4137-8671-9f4e813ce259

Bug Details: JDBC 2005 GA Driver error when running a callablestatement on SQLServer 2000

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=3fcf439d-79ed-44d9-bbbf-320e4ee25d89

Exception Message: “SQL Error: A server cursor is not allowed on a remote stored procedure or stored procedure with more than one SELECT statement. Use a default result set or client cursor”

Bug Details: JDBC Driver executeBatch does not work with INSERT statement

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=e13a8009-7466-4803-ba19-6bfd4b5f8966

Exception Message: “java.sql.BatchUpdateException: com.microsoft.sqlserver.jdbc.SQLServerException: sp_cursoropen/sp_cursorprepare: The statement parameter can only be a single select or a single stored procedure.“

Bug Details: SQL2005 JDBC Driver bug with time zone handling **Available as a QFE**

http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=e73c8b79-53a6-4779-98f1-71c0043179eb

Additional customer issues addressed that have no associated external bugs:

Bug Detail: Using sendStringParametersAsUnicode does not work with XA transactions.

Exception Message: “java.sql.SQLException: Failed to create the XA control connection.”

JDBC V1.1 CTP Available

angelsb — Fri, 14 Apr 2006 23:00:00 GMT

I am proud to say that the first community preview release of the SQL Server 2005 JDBC v1.1 driver is now available.

This build includes Type-2 integrated authentication for Windows XP and Windows 2003 clients (windows 2000 client support to come in the next CTP). It also incorporates bug fixes from customer feedback of the v1.0 driver and a fair ammount of plumbing under the covers. We really want to get as much feedback on this as possible.

To get the v1.1 CTP1 please email the JDBC Project Manager directly at
shelbyg<at>microsoft<dot>com.

I have a bet going with him on the number of requests he will receive so don't let me down!

JDBC Beta 2 connection string properties

angelsb — Sat, 01 Oct 2005 00:11:00 GMT

As you have probably seen by now we have shipped beta 2 of the Sql Server 2005 JDBC driver.

http://www.microsoft.com/sql/downloads/2005/jdbc.mspx

We have put a lot of work into this beta and it is with some trepidation that I see it go out the door. We have made a lot of hard decisions, our design philosophy has been to "do it right". This means that there are a lot of changes, some that may break some scenario that worked before (those are the ones I am most interested in hearing about). I can assure you that for every single change we have spent hours pouring over the "Maydene Fisher/Jon Ellis/Jonathan Burce, JDBC API Tutorial and Reference, third edtion" trying to do the right thing and I want to write a few blogs about some of these changes.

I will start with the easy one, we have cleaned up the connection string properties. We no longer allow duplicate connection string values, we now allow escaping values (using the '{' and '}' brackets) we will now throw an exception whenever you enter a name value pair that we don't understand etc. Besides all of that house keeping we have made some hard decisions, feel free to leave feedback on any of the following:

codepage has been removed, we now keep track of the codepage that you are using. There are some problems with this approach, we are currently supporting the 850+ codepages that the JVM supports. The problem is that there are a number of Codepages that are not supported by the VM that will now fail! In beta 2. We feel that explicitly failing is better than the possible data corruption that we were exposing before. Important: If you depend on a specific codepage that is _not_ supported by the JVM please contact us directly.

selectMethod has become forwardReadOnlyMethod. We wanted to make it very explicit that this method only affects the statements opened with Forward Only Read Only cursors (the default)

workstationID has been added, use this to identify the specific workstation in various SQL Server profiling and logging tools

trustedAuthentication has become integratedSecurity and ntlmAuthentication + domain have been removed. We are working on this feature but quite frankly we are seriously looking at this feature.

sqlVersion has been removed, we only support Sql Server 2000 and Sql Server 2005.

enableFailover has been removed, the implementation had some security issues so we are removing it until we can do it correctly.

logfile has been removed we have moved diagnostics to java.util.logging.Logger

asciiStringParameters becomes logically inverse sendStringParametersAsUnicode. We don’t always send the string parameters as ascii when not sending them as Unicode, renaming this property makes this clearer.

booleanLiterals has been removed, we were parsing SQL statements and translating Oracle boolean literas to Sql Server numeric values. This is a very incomplete feature so we have decided to postpone Oracle migration features to a later release.