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
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
Bug Details: JDBC 2005 GA Driver error when running a callablestatement on SQLServer 2000
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
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**
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.”