Udostępnij za pośrednictwem

Microsoft SQL Server 2005 JDBC Driver v1.2 official release

  • Artykuł

The Microsoft SQL Server JDBC team is proud to announce the general availability of the v1.2 RTW release.  The driver can be found at https://msdn.microsoft.com/data/jdbc.  In this release we significantly reduced the driver's memory footprint usage especially when handling large clobs and blobs on multiple active connections.  This resulted in performance and scalability improvements, through the use of "responseBuffering=adaptive" connection property.  We also introduced SQL Server SSL encryption support.

Jimmy Wu
Microsoft SQL Server

Comments

  • Anonymous
    October 12, 2007
    PingBack from http://www.artofbam.com/wordpress/?p=8019

  • Anonymous
    October 17, 2007
    Can I found release notes somewhere? thanks.

  • Anonymous
    October 18, 2007
    Yes - where can I get the release notes? Also is there some performance benchmarking for SSL enabled connections. Thanks!!

  • Anonymous
    October 19, 2007
    The comment has been removed

  • Anonymous
    October 23, 2007
    JDBC driver behaves differently for the next query: IF (db_id('x') IS NULL) BEGIN  CREATE DATABASE "x";  SELECT db_id('x') AS id; END ELSE SELECT NULL AS id; Ver 1.1 returns a ResultSet or NULL. Ver 1.2 throws an exception if database was created (obviously according to No. 45827 from release notes: The SQLServerStatement.executeQuery method now throws an SQLException if the specified argument, an SQL statement, returns a result other than a single ResultSet). It looks like general approach to executing a number of statements in one query changed: result of the first or last  statement is returned. Which approach is here to stay - 1.1 or 1.2? Thanks, Michael

  • Anonymous
    October 24, 2007
    Looks like you introduced a severe bug in version 1.2: subclasses of Throwable (like SQLServerException) must implement Serializable. However, this is no longer the case for SQLServerException, as it has a StreamError field, which isn't Serializable anymore in 1.2 (it was in 1.1). Is this a known bug?

  • Anonymous
    October 24, 2007
    Looks like you introduced a severe bug in version 1.2: subclasses of Throwable (like SQLServerException) must implement Serializable. However, this is no longer the case for SQLServerException, as it has a StreamError field, which isn't Serializable anymore in 1.2 (it was in 1.1). Is this a known bug?

  • Anonymous
    October 26, 2007
    Hi,  We are evaluating JDBC v1.2 and found out there is different result with getBytes Method (SQLServerResultSet) call. this is output when I tried two drivers: using JDBC v1.1 Timestamp from DB is: 2007-10-26 12:45:45.9 byte array is: 0 is -45 1 is -103 2 is 0 3 is 0 4 is -38 5 is 82 6 is -46 7 is 0 using JDBC v1.2 Timestamp from DB is: 2007-10-26 12:44:42.04 0 is 0 1 is 0 2 is -103 3 is -45 4 is 0 5 is -46 6 is 8 7 is 4 you can see first 4 elements values have been changed (with different order).  can someone provide more information about this? Thanks. --Tony

  • Anonymous
    October 29, 2007
    The comment has been removed

  • Anonymous
    October 29, 2007
    The comment has been removed

  • Anonymous
    November 01, 2007
    The comment has been removed

  • Anonymous
    November 02, 2007
    we use SQL statement select getdate() from DB server to get DB server timestamps, then use getBytes() method for our persistence lay to do real work. I have a sample java program just to get a timestamp from a table   and use getBytes() on SQLServerResultSet, you can see the result different: v1.2 result: 2007-10-22 10:04:32.623 0 is 0 1 is 0 2 is -103 3 is -49 4 is 0 5 is -90 6 is 10 7 is -5 v1.1 2007-10-22 10:04:32.623 0 is -49 1 is -103 2 is 0 3 is 0 4 is -5 5 is 10 6 is -90 7 is 0 first 4 elements order reverse which represents   day and last 4 elements also reverse order which represents time.

  • Anonymous
    November 13, 2007
    Hi Tony, Thank you for your patience. We have investigated the problem you reported and confirmed that it is a not a regression but rather the intended consequence of fixing a defect in v1.1. Basically, the byte order you observe in v1.1 disallows round tripping binary datetime values with the server. You should now be able to do this in v1.2. Hope this helps and thank you for your feedback, Yesim [MSFT]

  • Anonymous
    April 25, 2008
    I see that in the 1.2 driver uniqueness constraint violations no longer cause an exception when the insert happens within a stored procedure.  The violation is silently ignored, the insert is not done. Has anyone else seen this? -- Georg.

  • Anonymous
    June 12, 2008
    Hi, I've found a strange performace with numeric(18,0) column (idPersona) in SQL Server 2000 when do a simple querie: select * from Persona where idPersona=?). IdPersona has a clustered index. The query ellapsed this time is it's used the next java type in preparedstatement (I use setObjet method):

  • java.math.BigDecimal 148 ms
  • java.util.Long 243
  • java.util.Integer 4 ms. ¿Why is very faster use Integer Java Object instead BigDecimal, if JDBC SQL mapping is BigDecimal -> NUMERIC -> numeric?

  • Anonymous
    June 18, 2008
    The comment has been removed

  • Anonymous
    July 12, 2008
    Whenever there is a upgrade or a new release or new version of any software it should have the backward compatibility. Here I am trying to connect MSSQL Server 2000 using MSSQL Server 2005 JDBC driver. Most of the functionalities are working (Hope so). But still there are some issues while trying access a stored procedure which intern talks to Oracle RDBMS thru Microsoft data transformation services, It throws some SQL exception say “This statement did not return any result sets. But the same code is working fine with MSSQL Server 2000 JDBC driver. This supposed to be fixed. -Vinay

  • Anonymous
    October 12, 2008
    I have an application run with SQL2000 originally, last month the database has been migrated to SQL2005, I've updated the jdbc driver to version 1.2 accordingly, but found the performance of the application is greatly downgrade, it take around 4 times as long as before for the same task. Anyone can guide me to fix such problem? Thanks in advance Greale

  • Anonymous
    October 14, 2008
    The comment has been removed

  • Anonymous
    October 14, 2008
    The comment has been removed

  • Anonymous
    October 07, 2009
    Hi we are using the Microsoft SQL Server 2005 JDBC in sap Application , and the legacy system has MS SQL 2000 JDBC driver Will these be compatible if we have diffeent versions of the Servers in the both ends. Please let me know if any one has solution for these. Thansk Praveen Will the Ms SQL 2005 is installed

  • Anonymous
    November 20, 2009
    The getBytes() method is buggy. It throws an exception "com.microsoft.sqlserver.jdbc.SQLServerException: The conversion from int to BINARY is unsupported." when I am trying to get a short variable and the getColumnTypeName() says its a "smallint" !! Please advise

  • Anonymous
    April 29, 2014
    I cannot find "Microsoft SQL Server 2005 JDBC Driver v1.2" in this link.