Re: MS SQL Server 2005 JDBC Driver Performance Issue

Starting with the disclaimer that I'm a DBA looking for answers and not a
coder with a solution, I'll mention what sent me here and see if it meshes
with this issue...

We are also running the SQL 2005 driver against SQL 2000 (build 2187) and we
have found that no matter WHAT you do (based on available info), straight
stored procedure calls are still packaged and delivered as prepared
statements so we 'lose' all of the benefits of RPC. I suspect we are losing
15-30% in dearly needed throughput because of this.

Is this an oversight, a limitation, or a case where the development team
can't find the needle in the haystack?

Since this is a first visit, I can be found on yahoo mail by the given
screen name with ideas or solutions.

Bill Clark


"Richard Yeo" wrote:

With the jTDS driver, SQL Server 2005 managed inserts at the rate of: 966.88
records/sec. This is effectively twice that of the Microsoft driver

And in Sybase, the records are inserted at the rate of: 829.18 records/sec.

Shame on Microsoft and Sybase for writing such badly performing JDBC
drivers!!!

We are now going to start end to end testing with the jTDS driver. Peter T
thanks for recommending this driver.

Only once it has completed end to end testing will i be happy.

"Robert Klemme" wrote:

Richard Yeo wrote:
Peter

If you are porting an application particularly one as hard on performance
(calls many stored procs per page using JDBC) as ours the performance the
application receives from the JDBC Driver and RDBMS combination is very
important!

Our test is very valid given the ported DB needs to perform at similar
levels. We are testing all areas of performance not just the driver. You
can't just test one area. You have to test each link and identify the weak
link in the chain which is clearly the JDBC driver.

Just to throw in another opinion: since you're running against different
databases not only the driver *implementation* may be the issue but
network protocols may differ! Also, did you try out different
connection settings? There are actually settings of the JDBC driver (I
know for jTDS but I believe this is true for MS as well) that affect
performance.

Did you do the comparison test with jTDS yet?

Kind regards

robert

.

Relevant Pages

  • Re: fetching stacked record sets in stored procedure
    ... >> Alin. ... Obviously the driver couldn't make any difference, ... > We never even wanted to be in the JDBC driver business. ... Actually I haven't made a dollar out of jTDS. ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: JDBC and ResultSet problem
    ... Several MSSQL JDBC drivers employ the same scheme, they create multiple ... connections transparantly and use those for the multiple rowsets. ... extremely bitten by this behaviour once using the JTDS driver. ... I implemented the JDBC driver to ...
    (comp.lang.java.databases)
  • Re: Is perl better? :(((
    ... > Apparently you haven't been reading the thread. ... Oracle's JDBC driver ... such as executeQuery() *were* closed properly when the statement ... > If it is confirmed that this is a problem with Oracle's JDBC driver, ...
    (comp.lang.java.programmer)
  • Re: MS SQL Server 2005 JDBC Driver Performance Issue
    ... the trace data records that approximately 50% of our CPU ... trace is recording CPU cycles 'twice' (once against the RPC and again against ... On to the v1.1 driver! ... link in the chain which is clearly the JDBC driver. ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: Is perl better? :(((
    ... > Apparently you haven't been reading the thread. ... Oracle's JDBC driver ... such as executeQuery() *were* closed properly when the statement ... > If it is confirmed that this is a problem with Oracle's JDBC driver, ...
    (comp.lang.java.databases)
Loading