为SQL Server选择正确的ODBC驱动程序 [英] Choosing the correct ODBC driver for SQL Server

问题描述

我正在写一些文档，说明如何通过ODBC将Access连接到SQL.老实说，我总是选择"11.0"作为驱动程序.但是我想知道是什么决定了我应该"使用的驱动程序?

SQL Server的版本确定吗?而且我假设用户的"计算机没有我在这里看到的所有驱动程序，因此有人可以澄清选择正确驱动程序的规则吗?

解决方案

根据位于

因此，由于Windows附带了古老的"SQL Server"(MDAC)ODBC驱动程序，并且该驱动程序可在任何计算机上使用，因此这将是最简单的解决方案.我怀疑使用一种较新的本机客户端"驱动程序会伤害，但是我也怀疑在这种情况下，它是否会帮助很多(如果有的话). >

I'm writing some documentation on how to connect Access to SQL via ODBC. I honestly always just choose "11.0" when it comes to drivers, just because. But I'm wondering what determines the driver I "should" be using?

Does the version of SQL Server determine this? And I'm assuming the "User's" computer won't have all the driver's I'm seeing here so can someone just clarify the rules to choosing the correct driver?

解决方案

According to a blog post located here,

SQL Native Client was introduced in Microsoft SQL Server 2005 to provide new functionality above and beyond that supplied by the Microsoft Data Access Components (MDAC).

It goes on to list some of the new features:

SQL Native Client can be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2005 features such as Multiple Active Result Sets (MARS), user-defined data types (UDT), query notifications, snapshot isolation, and XML data type support.

I think it unlikely that a SQL Server linked table in Access would leverage any of those newer SQL Server features for two reasons:

1. ODBC links to SQL Server from Access are probably kept fairly generic to support links to older versions of SQL Server, and

2. As I understand it, all operations on an Access linked table are handled first by the ACE/Jet database engine, which in turn sends requests to the ODBC driver. I suspect that if a query involved any "fancy stuff" then ACE/Jet would take care of it and send relatively routine requests to the SQL Server via ODBC.

Therefore, since the venerable "SQL Server" (MDAC) ODBC driver is shipped with Windows and will be available on any machine then that would be the most straightforward solution. I doubt that using one of the newer "Native Client" drivers would hurt, but I also doubt that it would help much (if at all) in this case.

这篇关于为SQL Server选择正确的ODBC驱动程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！