com.microsoft.jdbc.sqlserver.SQLServerDrive seems to suffer from memory leaks, I would not use it for a production system. Sun recommend you use a pure Java driver rather than a bridge - there's a chance the VM will be messed up by the native code brought in by the driver. Again, because of this I would not use it in a production system. You might want try jTDS (seach sourceforge), which is free and despite only being at version 0.7.1 is much better than the MS driver. If you need a proper production ready driver for MSSQL Server though, I'm afraid you'll probably have to buy something.
Hi Nan, Stands to reason the specialized SQL Server driver will be faster. After all there is only one translation step: JDBC <--> TDS protocol, whereas the JDBC-ODBC bridge entail two steps: JDBC <--> ODBC <--> TDS. I never tried though. I agree with Aemmon for the rest: better not use either driver for serious work. I personally have good experiences with Inet software's Opta2000 driver for SQL Server. Good riding, Rudy.