Best MS jdbc driver for jdbc 1.0 centric features
bogachkov_at_hotmail.com
Date: 01/21/05
- Previous message: Mark Matthews: "Re: EOFException"
- Next in thread: Joe Weinstein: "Re: Best MS jdbc driver for jdbc 1.0 centric features"
- Reply: Joe Weinstein: "Re: Best MS jdbc driver for jdbc 1.0 centric features"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 20 Jan 2005 17:31:03 -0800
Hello
My situation:
Recently, by company's web-app has been getting worse and worse
performance from our jdbc driver (we use the free MS jdbc driver) -
things like strange transaction resource handling, chopy overall
performance, etc.. I have spent significant time tweaking it (following
various advice on newgroups...). As the project's architect, I need to
do something about this problem - but various high-level tunnings that
I have done to the way we use connections with this driver haven't
significantly improved perfomance under normal everyday load. (Our
queries often span tables with millions of records, and are relatively
dynamic. We use a seperate pool of autocommit-off connections for
writes, and autocommit-on connecions for reads)
So, then, my question - based on day-to-day production experience
(versus benchmarks) - what is the BEST driver from SQL Server 2000
given the following needs:
Things I need it to have are solid jdbc 1.0, solid transaction
handling, decent concurrent load handling, stable implementation of
resource handling (i.e. auto closing result sets when parent statements
close, closing of result sets & statements when connections close) and
support for multiple open statements/result sets per connection.
Things I do not have a direct need for:
Connection Pooling (I keep my own pool of open connections), DataSource
support, distributed transactions or 2-phase commit support, RowSet
variants, jdbc 3.0 autokey generation, J2EE compliance. We do make use
of updatable result sets - but I don't care if it isn't supported since
I can still use MS driver for those, as they are mainly done it batch
jobs).
Things that are nice:
It would also be good to have a driver that can handle prep statement
caching on a driver level (vs connection level) although this isn't a
necessity, and if it is available - it would need to have a
configurable caching strategy (or have a way to be turned off :)
I very much appreciate your help in advance
Thanks
Gary Bogachkov
System Architect
Stericycle Direct Return
- Previous message: Mark Matthews: "Re: EOFException"
- Next in thread: Joe Weinstein: "Re: Best MS jdbc driver for jdbc 1.0 centric features"
- Reply: Joe Weinstein: "Re: Best MS jdbc driver for jdbc 1.0 centric features"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|