然而，就您的情况而言，如果您有一个使用 MS JDBC 驱动程序构建和测试的系统，那么您确实应该坚持这样做。
同时，进行一些测试，看看您是否可以收集确实的数据，表明 JTDS 在您的用例中优于 MS JDBC。 如果数据支持这些断言，那么就制定一个计划，在您的开发和测试周期中开始使用 JTDS，最后将其推广到您的生产版本。
I've used the JTDS driver in production for around a year without any problems.
However, in your case, if you've got a system that been built and tested with the MS JDBC driver, then you really ought to stick to that.
In the meantime, conduct some tests and see if you can collect hard figures that show JTDS outperforming MS JDBC for your use cases. If the data back up these assertions, then come up with a plan to start using JTDS in your development and test cycles, finally rolling it out to your production release.
由于 MS SQL Server 协议有许多专有部分，因此当您在服务器上应用维护更新时，MS 可能会执行破坏 jTDS 的更改。
不像 MS 驱动程序那么最新。 当MS推出新的SQL Server版本时，JDBC驱动程序通常会一起发布。 jTDS 必须努力迎头赶上，这可能需要几个月的时间。
We are using jTDS drivers for about an year. As of today, I can tell the following:
Pros:
Smaller JAR.
ResultSets are faster. Fetching is configurable.
Caches huge results on disk (MS driver requires you to use slow bidirectional cursors or caches results on memory, yielding occasional OutOfMemoyErrors).
Documentation is small but enough (MS driver documentation is spread in hundreds of MSDN pages).
Better error reporting (always a nice SQLException, while MS driver sometimes gives ClassCastException or other RuntimeException).
Open source.
Cons:
Bad support, due to:
Relatively small user base, giving bad community support.
Not backed by a big company, so if you need some solution fast, you must hope the developers are available and willing to help (and remember they are not paid for answering forums messages).
Because MS SQL Server protocol has many proprietary parts, MS can perform changes that break jTDS when you apply maintenance updates on the server.
Not as up-to-date as the MS driver. When MS launches a new SQL Server version, the JDBC drivers are usually released together. jTDS must work to catch up and that may take months.
发布评论
评论（3）
我已经在生产中使用 JTDS 驱动程序大约一年了，没有出现任何问题。
然而，就您的情况而言，如果您有一个使用 MS JDBC 驱动程序构建和测试的系统，那么您确实应该坚持这样做。
同时，进行一些测试，看看您是否可以收集确实的数据，表明 JTDS 在您的用例中优于 MS JDBC。 如果数据支持这些断言，那么就制定一个计划，在您的开发和测试周期中开始使用 JTDS，最后将其推广到您的生产版本。
I've used the JTDS driver in production for around a year without any problems.
However, in your case, if you've got a system that been built and tested with the MS JDBC driver, then you really ought to stick to that.
In the meantime, conduct some tests and see if you can collect hard figures that show JTDS outperforming MS JDBC for your use cases. If the data back up these assertions, then come up with a plan to start using JTDS in your development and test cycles, finally rolling it out to your production release.
我们使用 jTDS 驱动程序大约一年了。 截至今天，我可以告诉您以下内容：
优点：
缺点：
We are using jTDS drivers for about an year. As of today, I can tell the following:
Pros:
Cons:
即将发布，没有。
稍后再做，是的。
JTDS 比 MS 具有优势，例如您可以使用域服务帐户进行 SQL 连接并支持加密 SSL。
Close to release, no.
Do it later, yes.
JTDS has benefits over the MS one such as you can use a domain service account for your SQL connection and supports encrpyted SSL.