Price: Free for a single user with only 1 database connection. Pros: Much faster than the official Microsoft JDBC driver. JDBC compliance: Claims to be be JDBC 3.0/4.0 compliant Has a way to disable prepared statements. isClosed() aren't supported because these are JDBC 4.0 methods. This is a deal breaker for me because important methods like. JDBC compliance: JDBC 3.0 compliant only. Has a way of disabling prepared statements. JDBC compliance: Claims to be be JDBC 4.0 compliant Pros: Claims to be top class, used by numerous applications like Informatica, etc and the company is been around for ages! Have quick support - I have dealt with them briefly. JDBC compliance: Claims to be be JDBC 4.0 compliant although many methods throw UnimplementedException!!!! Doesn't have a way of disabling statement preparation/pooling which is something I am looking for. I was told this by JNetDirect JSQLConnect's support.Ĭons: Seems to have a lot of connectivity/stability issues, don't believe me, just Google about it :). Pros: Official Microsoft JDBC driver for SQL Server 2008! Based on the JNetDirect JSQLConnect driver v3 as it was purchased by Microsoft a few years ago and they have been building on top of it since. My question is, are there any other JDBC drivers that are compatible with SQL Server 2008 that I should also look into reviewing? I gathered a list of ones that I found and have listed them below. I am in the process of evaluating a whole whack of JDBC drivers, specifically to use with SQL Server 2008 with Windows authentication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |