JDBC drivers for MS SQL 2000

any one tried any drivers for ms sql 2k ?
currently i am using one by microsoft
it is not too slow but has some problems
e.g. from a same connection object if i try to create multiple statements, and use transactions I get an error while connection.setAutocommit(false)
I also want to see whether other drivers are fast/better
the sun jdbc site has listed 40 drivers for ms sql
some of them are j2ee 1.2/1/3 certified
I want to know if someone has had any experience about any particular of them
Kalps

You probably get that error because that feature is not allowed in MS's version of the Driver.

Originally posted by Kalpesh Soni:
the sun jdbc site has listed 40 drivers for ms sql
some of them are j2ee 1.2/1/3 certified
Kalps

Where did you find that list? Can you give me a link.

I too got the same error
precisely:
[java] java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Can't start a cloned connection while in manual transaction mode.
Had anyone able to solve this problem ??

I just solved the problem by adding selectmethod as suffix, please see here for more info http://www.websina.com/bugzero/faq/exception-sql2000.html
Now i can make connection pooling with sqlserver 2000 with Microsoft jdbc driver.

Originally posted by Kalpesh Soni:
any one tried any drivers for ms sql 2k ?
currently i am using one by microsoft
it is not too slow but has some problems
e.g. from a same connection object if i try to create multiple statements, and use transactions I get an error while connection.setAutocommit(false)
I also want to see whether other drivers are fast/better
the sun jdbc site has listed 40 drivers for ms sql
some of them are j2ee 1.2/1/3 certified
I want to know if someone has had any experience about any particular of them
Kalps

I just solved the problem by adding selectmethod as suffix, please see here for more info http://www.websina.com/bugzero/faq/exception-sql2000.html
Now i can make connection pooling with sqlserver 2000 with Microsoft jdbc driver.

SelectMethod=cursor is very expensive
what it does is, it dumps all inserts/updates within a transaction in tempdb and then updates your db when transaction is committed at one go
our application is big and our tempdb grows to 1-2 GB!
so in short , do not use it !
work around ?! use different connections

Gregg the link is
http://industry.java.sun.com/products/jdbc/drivers
using it u can search for drivers
No one answered my first question though

Thanks for the link. That is a good resource.