Rappel : qui dit driver de type 4, dit pas d'installation sur les postes clients ni serveurs utilisant cette technologie (cad, Pure Java JDBC Driver)

Bonus : le portail dédié au driver JDBC pour SQL Server

Changes


The following is a list of changes that have been made in the Microsoft SQL Server 2005 JDBC Driver since the version 1.1 release in September 2006.

35034 The getDate method now works on the IBM WebSphere Application Server versions 5.1 and 6.0.

36085 The driver now correctly uses the GENERATED_KEYS for the column name in the ResultSet returned by the SQLServerStatement.getGeneratedKey method.

37030 Setting the connection string property sendStringParametersAsUnicode=false no longer results in the Error 17805 (invalid buffer received from client) from SQL Server for some database collations.

37556 The driver now correctly handles setting character streams containing Unicode data to non-Unicode database columns.

39311 The driver now provides a better performance on the SQLServerResultSet for the queries that return char, varchar or text column data types with collations.

39941 The driver no longer closes the connection when the application inserts or updates the java.io.Reader or java.io.InputStream objects with incorrectly specified lengths.

43090 SQLServerStatement.getUpdateCount method now returns the correct update count when the SQLServerStatement.setMaxRows is set.

45827 The SQLServerStatement.executeQuery method now throws an SQLException if the specified argument, an SQL statement, returns a result other than a single ResultSet.

46707 The driver now correctly supports calling the stored procedures by using the named parameters.

49243 The driver now supports the default packetSize value for the IBM WebSphere Application Server version 6.1.

50554 The driver no longer truncates an output string parameter from a stored procedure to 4000 characters when the actual string length is larger than 4000.

55059 The driver now supports all Hindi, Divehi, Indic, Syriac, and AltDiction2 (alternate dictionary order) collations.

57032 The driver no longer logs exceptions due to the closing of an internal prepared statement with a handle -1.

57853 The SQLServerConnection.setTypeMap method no longer causes an SQLException when connecting by using XA data source through the IBM WebSphere Application Server version 5.1.

60179 The client machine without a hostname no longer fails while connecting to a SQL Server.

61202 The driver now correctly clears the SQLWarning message chain after a statement execution.

92866 Calling the SQLServerStatement.setMaxRows method on a statement no longer results in wrong row counts in the successive statements on the same connection.


KNOWN ISSUES


The following are known issues with the Microsoft SQL Server 2005 JDBC Driver:

1) DRIVER LOAD CONFLICT WITH THE SQL SERVER 2000 JDBC DRIVER
2) LIMITATIONS GETTING PARAMETER METADATA FOR PREPARED STATEMENTS
3) SQL SERVER 2000 DATA CONVERSION LIMITATIONS
4) LIMITATIONS WITH NAMED PARAMETERS
5) XA TRANSACTION FAILURE ON WINDOWS XP
6) SUN SOLARIS NEEDS GZIP TO INSTALL THE JDBC DRIVER
7) CONNECTION TIMEOUTS USING DATABASE MIRRORING
8) CONVERSION OF BIGDECIMAL VALUES
9) JDBC IPV6 CONNECTION BEHAVES INCONSISTENTLY WHEN USING INTEGRATED SECURITY
10) LARGE LIMIT VALUE FOR Reader.mark(readAheadLimit) IN ADAPTIVE MODE
11) DATA TYPE CONVERSION FAILURE IN ADAPTIVE MODE
12) AVOID CREATING TEMPORARY TABLES via PreparedStatement or CallableStatement CLASSES