Broadly speaking, pure Java drivers are preferred for reasons of
portability.
To the best of my knowledge, there are no official benchmarks for JDBC
drivers.
Pure Java drivers for either Sybase or Microsoft SQL Server encapsulate the
TDS protocol. They do little in the way of preprocessing and therefore there
is little that can be wrong with them in terms of efficiency.
This is true of most pure Java JDBC drivers -- implementations seldom have
to do anything but map requests to a communications protocol, the exception
being when there is a basic service not implemented by a server. For
example, some SQL Servers do not implement cursors. There is no such problem
with the Microsoft and Sybase servers.
Avoid JDBC-ODBC bridge implementations like the plague. They are problematic
at best, for a variety of largely intractable reasons. One pragmatic
exception to this is the JDBC driver for Microsoft Jet. It is a JDBC-ODBC
bridge, but there is no other option, and Jet is very handy for prototyping.
----- Original Message -----
From: "Ma Cheng" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 07, 2001 3:55 AM
Subject: [jBoss-User] JDBC Driver
> Hi,
>
> We are currently evaluating JDBC Drivers for MS SQL SERVER 2000. It will
be
> great if you can share your information in following:
>
> 1. Is there any bench mark tests on different JDBC Drivers?
> 2. Is there a driver that you would like to recommand?
> 3. Is there a driver that we should avoid?
>
> Thank you in advance,
> Ma Cheng
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
