Re: Microsoft SQL Server JDBC performance issue

Are you sure you are executing the sp as a RPC and not a batch?

--
Andrew J. Kelly SQL MVP

"Richard Yeo" <RichardYeo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:89A75E0A-20ED-4A0B-8111-FA1EFB31F7D4@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).

All testing was done on the same hardware spec servers with the same
T-SQL.

Does anybody within Microsoft have any ideas why the performance is so
bad?



.

Relevant Pages

  • Re: MS SQL Server 2005 JDBC Driver Performance Issue
    ... performance of the Microsoft JDBC driver that uses our existing ... Sybase ASE with Sybase JDBC driver = 780 calls per second ... SQL Server with MS JDBC driver = 463 calls per second ... (BTW the new native client SQL Native Client is an unmanged ODBC and OleDB ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: Method cleanup failed while trying to execute method cleanup on ManagedConnection
    ... JDBC driver name: Microsoft SQL Server 2005 JDBC Driver ... Our application seems to be working fine but every time a connection is closed we get a stack trace in the log indicating that destroy failed and that a method is not supportd with "Caused by: java.sql.SQLException: This operation is not supported.DSRA0010E: SQL State ... We have used the same set up but using the SQL Server 2000 JDBC driver talking to a SQL Server 2000 database without a problem, the only difference is we switched it to use SQL Server 2005. ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Tricky: java.lang.StackOverflowError due to recursive call in warning messages construction
    ... I got this problem with both SP2 and SP3 of the JDBC driver for SQL Server ... As PRINT statements are returned as warning messages, ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Method cleanup failed while trying to execute method cleanup on ManagedConnection
    ... JDBC driver name: Microsoft SQL Server 2005 JDBC Driver ... SQL State = null, Error Code = 0 ...
    (microsoft.public.sqlserver.jdbcdriver)
  • RE: Cannot connect to my SQL 2005 server using JDBC - can any dia
    ... associated with the named instance, instead of the name of the ... This seems to suggest that whatever version of the JDBC driver the article ... Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is? ... Running SQL Server 2005 SP2 and using named instances. ...
    (microsoft.public.sqlserver.jdbcdriver)
Loading