SQL Server Native Client 11.0 support for SQL Server 2019

Ashwin kumar 6 Reputation points
2020-05-20T15:48:22.993+00:00

From the below document it looks like SQL Native Client 11.0 does not support connection to SQL Server 2016 and above.

https://learn.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client?view=sql-server-ver15

“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 Databases";

Connection to SQL Server 2019 using Native Client 11.0 works in some environments and fails in another.
Could you please clarify whether Native Client 11.0 supports connection to SQL Server 2019.

8531-sqlncli11.jpg

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
37,078 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Leon Laude 85,701 Reputation points
    2020-05-20T15:58:38.837+00:00

    Hi,

    As the Microsoft documentation states, the SQL Server Native Client version 11.0 only supports up to SQL Server 2014, which means it does not support SQL Server 2019.

    The SQL Server Native Client (SQLNCLI) remains deprecated and it is not recommended to use it for new development work.
    Instead, use the new Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) which will be updated with the most recent server features.

    You'll also find more SQL experts in the dedicated forum over here:
    https://social.technet.microsoft.com/Forums/en-US/home?category=sqlserver

    Best regards,
    Leon

    2 people found this answer helpful.

  2. Daniel Carollo 11 Reputation points
    2021-09-10T22:07:04.117+00:00

    The irony here is that Microsoft has been trying to deprecate SQLNCLI11 for years -- and yet even as late as SQL 2019, Replication setup still creates linked servers using SQLCNLI11 under the hood! Not only that, since the driver doesn't support multi-subnet aware, our AlwaysOn automatic publisher redirect fails whenever we failover our Publisher to a replica in a different subnet than our distribution server! Go figure

    From their documentation on sp_addlinkedserver (the default client is SQLNCLI )

    https://learn.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-addlinkedserver-transact-sql?view=sql-server-ver15

    [ @provider = ] 'provider_name'
    Is the unique programmatic identifier (PROGID) of the OLE DB provider that corresponds to this data source. provider_name must be unique for the specified OLE DB provider installed on the current computer. provider_name is nvarchar(128), with a default of NULL; however, if provider_name is omitted, SQLNCLI is used.

    Note

    Using SQLNCLI will redirect SQL Server to the latest version of SQL Server Native Client OLE DB Provider. The OLE DB provider is expected to be registered with the specified PROGID in the registry.

    Important

    The previous Microsoft OLE DB Provider for SQL Server (SQLOLEDB) and SQL Server Native Client OLE DB provider (SQLNCLI) remain deprecated and it is not recommended to use either for new development work. Instead, use the new Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) which will be updated with the most recent server features.

    2 people found this answer helpful.
    0 comments No comments