Re: MS SQL Server 2005 JDBC Driver Performance Issue

Richard,
If you have source code that shows the performance problem I would recommend
that you file a bug directly on the JDBC driver at:
http://msdn.microsoft.com/data/ref/jdbc/ just click on the "Submit Feedback
on the JDBC Driver" link.

We are very interested in performance this milestone and we are making a
heavy investment on improving performance in the request scenario (retrieve
data from the database). It is possible that we could do something about
insert scenarios for v1.1 if we were to get a specific repro early enough.

Thank you,
--
Angel Saenz-Badillos [MS] Data Programmability
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging: http://blogs.msdn.com/angelsb/




"Richard Yeo" <RichardYeo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FAB8DC00-388E-4D25-9BD6-F46DFE41E3B2@xxxxxxxxxxxxxxxx
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.

Richard

"Peter T" wrote:

You could very well end up being correct but regardless of underlying
code
testing against two different DBs is not a good comparison test nor is
testing SQL server raw throughput with ADO. Though indexing/procs/etc...
may
be the same it does not mean they behave the same way across DB
platforms.
Doing a like hardware test where only the driver switches is a valid
comparison (at least in my way of thinking).


.

Loading