![]() Support lifecycle exception for SQL engine feature i.e.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. You can read the following articles to learn more about it:ĭifferent generations of Microsoft OLE DB provider for SQL Serverĭeprecation of Microsoft SQL Server OLE DB provider (SNAC) in 2011 Microsoft OLE DB provider for SQL Server has a long history. Programmatic identifiers of the corresponding providers will not be listed in the Object Explorer tree of SSMS under Server Objects -> Linked Servers -> Providers anymore:Ĭhange any existing transact-SQL (T-SQL) scripts for creation of linked server objects in Azure SQL Managed Instance to provide MSOLEDBSQL as parameter, instead of SQLNCLI. Several providers will be removed from the Provider dropdown list in SQL Server Management Studio (SSMS) wizard for creating linked server on Azure SQL Managed Instance since they are deactivated, to avoid any confusion: To create new linked server using SQL Server Management Studio (SSMS) wizard, choose Microsoft OLE DB Driver for SQL Server from the Provider dropdown list: Important: If you prefer using SQL Server Management Studio (SSMS) wizard for creation of linked servers, make sure to download and install the latest version of SSMS. Pass MSOLEDBSQL as the parameter value of sp_addlinkedserver stored procedure:ĮXEC = stored procedure will return error message when ‘SQLNCLI’ is passed as a parameter value. Use MSOLEDBSQL when creating new linked serversĪfter deactivation of SQLNLCI you should create any new linked servers with MSOLEDBSQL provider specified.Ĭreating linked server using stored procedure That’s because the underlying metadata remains unchanged and MSOLEDBSQL provider will be used thanks to dynamic rerouting implemented. Please note that sys.servers system view will keep reporting SQLNCLI as provider for existing linked servers. ![]() ![]() No actions needed for existing linked serversĪll existing linked servers with SQLNCLI provider specified will be automatically rerouted to use MSOLEDBSQL provider - you do not have to take any manual actions. Service update retiring SQLNCLI will be rolled out in all Azure regions during late May and June this year. In November 2022 we sent email notifications to all Azure SQL Managed Instance customers using linked server feature announcing that SQLNCLI is also going to be deactivated and retired in Azure SQL Managed Instance. SQLNCLI was finally removed from SQL Server Database engine with SQL Server 2022 release. MSOLEDBSQL is still current and recommended Microsoft OLE DB provider for SQL Server. In 2018 a next generation of OLE DB provider for SQL Server known by programmatic identifier MSOLEDBSQL was released keeping backwards compatibility with SQLNCLI and adding support for features introduced in newer versions of SQL Server. ![]() Based on the Support Lifecycle exception SQLNCLI continued to be shipped as a component of SQL Server Database engine up until SQL Server 2019 release, for exclusive use by database engine features like linked servers. The SQL Server Native Client (often abbreviated SNAC) OLE DB provider with programmatic identifier SQLNCLI is a legacy Microsoft OLE DB provider for SQL Server that was shipped with SQL Server 2005 (9.x) through SQL Server 2012 (11.x) and then deprecated for use by database application connections. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |