#Microsoft sql native client download driver
Instead, use the new Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) which will be updated with the most recent server features. 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. The OLE DB provider is expected to be registered with the specified PROGID in the registry. Using SQLNCLI will redirect SQL Server to the latest version of SQL Server Native Client OLE DB Provider.
provider_name is nvarchar(128), with a default of NULL however, if provider_name is omitted, SQLNCLI is used. SQLOLEDB has been deprecated for some time but is provided for backwards compatibility in modern Windows operating systems as part of Windows Data Access Components. provider_name must be unique for the specified OLE DB provider installed on the current computer. Both the SQL Server Native Client 10.0 OLE DB provider (SQLNCLI10) and SQL Server OLE DB driver (SQLOLEDB) are OLE DB providers shipped by Microsoft. Is the unique programmatic identifier (PROGID) of the OLE DB provider that corresponds to this data source.
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įrom their documentation on sp_addlinkedserver (the default client is SQLNCLI )
0 kommentar(er)
