Re: MS SQL Server 2005 JDBC Driver Performance Issue
- From: "David Browne" <davidbaxterbrowne no potted meat@xxxxxxxxxxx>
- Date: Thu, 13 Jul 2006 16:12:14 -0500
"Richard Yeo" <RichardYeo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C7EFE49-7DAF-4C21-AE42-1F81DAD0AA30@xxxxxxxxxxxxxxxx
We are in the process of migrating the application that runs our business
from Sybase ASE 12.5.3 to MS SQL Server 2005 SP x64
Our application is a large java application which runs on Redhat
Enterprise
Linux 4, Tomcat, etc.
We have written a standalone java console application to test the
performance of the Microsoft JDBC driver that uses our existing
applications
database abstraction layer to call a stored procedure that inserts a
record
into a database table.
Sybase ASE with Sybase JDBC driver = 780 calls per second
SQL Server with MS JDBC driver = 463 calls per second
the difference in performance would appear to be purely down to the JDBC
driver as we know SQL server is capable of over 1,100 calls per second
using
MS ADO let alone ADO.Net 2.0 (which uses Sql server 2005's new native
client
library).
You haven't gotten there yet. Are the procedure calls wrapped in a
transaction? If not then you may just be testing how many physical IO's per
second the database server can generate against its log file.
You might use a stored procedure that does no real work to better isolate
the driver and network overhead.
(BTW the new native client SQL Native Client is an unmanged ODBC and OleDB
driver, and can be used from ADO. ADO.NET 2.0 uses a different and also new
client library).
David
.
- Prev by Date: Re: JDBC and Virtual Machines
- Next by Date: Re: JDBC and Virtual Machines
- Previous by thread: Re: MS SQL Server 2005 JDBC Driver Performance Issue
- Next by thread: Sql Server 2005 JDBC driver requires Java 1.4
- Index(es):
Relevant Pages
|
