Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX


Microsoft's JDBC Driver for SQL Server Stacks Up Against Competition  : Page 2

At long last, a FREE Type 4 JDBC Driver for MS SQL Server 2000.




Application Security Testing: An Integral Part of DevOps

The Performance Evaluation
I downloaded several Type 4 drivers to compare with the new Microsoft SQL Server 2000 Driver for JDBC. The Microsoft driver is basically an old-ish version of the DataDirect Type 4 driver, so the performance results between the two are quite similar. I tested the drivers by writing some very basic insert and select query code. I purposely avoided "advanced" JDBC functions because when I tried them at least one of the drivers would fail each time. Table 1 shows the test results.

Editor's Note: This article was published in June of 2002. The data in this table reflects conditions as they were at that time.

Table 1: Performance Results for Driver Test
Driver Type Insert 1,000 Rows (Average Time in ms) Select 100,000 Rows (Average Time in ms) Total Time (ms) Factor Faster Than JDBC-ODBC
DataDirect Connect 4 6,623 3,167 9,790 3.6
Microsoft SQL Server 2000 Driver for JDBC 4 6,908 4,022 10,930 3.2
i-net SPRINTA 2000 4 6,595 2,636 9,231 3.8
Atinav AveConnect 4 6,962 7,607 14,569 2.4
JDBC-ODBC Bridge JDK 1.3.1 1 8,476 26,328 34,804 1
JDBC-ODBC Bridge JDK 1.4.0 1 8,664 24,317 32,981 1.06

The important column to look at is Factor Faster Than JDBC-ODBC, which shows how many times faster each driver is than the Type 1 JDBC-ODBC Bridge.

Listing 1 shows the code I used to test the drivers. You can use this test code to compare any other drivers as well. I cannot emphasize enough how important it is to run your own performance tests in a real-world test environment. Depending on what you are doing, the JDBC/ODBC bridge may actually be better than a Type 4 driver. For example, if you measure how fast a driver inserts large amounts of data into a database via the setBytes() method (e.g., 1MB blocks into an Image column), you'll discover that some of the Type 4 drivers are almost 10 times slower than the JDBC/ODBC bridge (see Table 2).

Table 2: Performance Results for Calling setBytes() on 1MB of Data
Driver Time (ms) Factor Slower Than JDBC-ODBC
DataDirect Connect 12,835 8.49
Microsoft SQL Server 2000 Driver for JDBC 12,515 8.28
i-net SPRINTA 2000 3,915 2.59
Atinav AveConnect 14,968 9.90
JDBC-ODBC Bridge JDK 1.3.1 1,512 1.00
JDBC-ODBC Bridge JDK 1.4.0 1,362 0.90

Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date