- #Sql server native client 10 and sql server 2012 driver
- #Sql server native client 10 and sql server 2012 windows
NET Framework Data Provider for SQL Server, which is part of the. When deciding whether to use SQL Server Native Client as the data access technology of your application, you should consider several factors.įor new applications, if you're using a managed programming language such as Microsoft Visual C# or Visual Basic, and you need to access the new features in SQL Server, you should use the. For a discussion of the different data-access technologies, see Data Access Technologies Road Map SQL Server Native Client is one technology that you can use to access data in a SQL Server database. However, no features added after SQL Server 2005 (9.x) will be available in this case.Applies to: SQL Server (all supported versions) Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW) OLE DB applications that use OLE DB Service Components can only use SQL Server Native client if they specify DataTypeCompatibility=80 in their connection strings.
OLE DB applications that have not been certified for use with SQL Server Native Client can use SQL Server Native client if they specify DataTypeCompatibility=80 in their connection strings.
You can use the SQL Server Native Client OLE DB provider if the application is certified for use with a specific version of SQL Server Native Client.
#Sql server native client 10 and sql server 2012 windows
OLE DB Support PoliciesĪpplications should use the SQL Server OLE DB provider included with the Windows operating system.
#Sql server native client 10 and sql server 2012 driver
You can use the SQL Server Native Client ODBC driver if the application is certified it for use with a specific version of SQL Server Native Client. ODBC Support PoliciesĪpplications should use the SQL Server ODBC driver included with the Windows operating system. BCP Support Policiesīeginning in SQL Server 2008, bcp.exe supports data files that are no more than three SQL Server versions older than the version of SQL Server in which bcp.exe shipped. Only features from SQL Server 2005 (9.x) are available when DataTypeCompatibility=80 is present in the connection strings. ADO applications can also use SQL Server Native Client 11.0 (included in SQL Server 2014 (12.x)), but if they do so they must specify DataTypeCompatibility=80 in the connection strings. SQL Server Native Client 11.0 (SQL Server 2012 (11.x) and SQL Server 2014 (12.x))ĪDO applications can use the SQLOLEDB OLE DB provider that is included with Windows if they do not require any of the features of SQL Server 2005 (9.x) or later.ĪDO applications can use the version of SQL Server Native Client included in SQL Server 2005 (9.x). Microsoft Windows XP Service Pack 2 or later SQL Server Native Client 10.5 (SQL Server 2008 R2) Microsoft Windows XP Service Pack 2, or later Microsoft Windows Server 2003 Service Pack 2, or later SQL Server Native Client 10.0 (SQL Server 2008) Microsoft Windows Server 2008 R2 (requires SQL Server Service Pack 2, or later) Microsoft Windows Vista (requires SQL Server Service Pack 2, or later) Microsoft Windows XP Service Pack 1 or later Microsoft Windows 2000 Service Pack 4 or later SQL Server Native Client (SQL Server 2005) The following table lists which operating systems support SQL Server Native Client. SQL Server Native Client 11.0 supports connections to, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 (11.x), SQL Server 2014 (12.x), and Azure SQL Database. This topic discusses how various data-access components can be used with SQL Server Native Client.
Applies to: SQL Server (all supported versions) Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW)
0 kommentar(er)
