![]() Microsoft/Windows Data Access Components (MDAC/WDAC) are shipped with and supported by Windows for application backwards compatibility and aren't part of the current SQL Server technology stack. Microsoft or Windows Data Access Components For more information, see Node.js Driver for SQL Server. Microsoft currently contributes to and supports the open-source tedious module in Node.js for connectivity to SQL Server using JavaScript. It isn't recommended to create new applications using the Microsoft Driver for Node.js for SQL Server.įor more information about the Microsoft Driver for Node.js for SQL Server, see WindowsAzure / node-sqlserver. Development efforts are no longer being focused on this driver. The Microsoft Driver for Node.js for SQL Server allows Node.js applications on Microsoft Windows and Microsoft Azure to access Microsoft SQL Server and Microsoft Azure SQL Database. Node.js Microsoft Driver for Node.js for SQL Server For the latest information, including how to download the PHP driver, see Microsoft Drivers for PHP for SQL Server. Introduced in 2009 as an open-source project, the Microsoft Drivers for PHP for SQL Server continue to be improved and maintained. PHP Microsoft Drivers for PHP for SQL Server For the latest information, including how to download the driver, see Overview of the JDBC Driver. Introduced in 2000, the Microsoft JDBC Driver for SQL Server continues to be improved and maintained. JDBC Microsoft JDBC Driver for SQL Server For more information about the namespace, see Microsoft ADO.NET for SQL Server. Introduced in 2019, the Microsoft SqlClient Data Provider for SQL Server is an ADO.NET data provider supporting applications that target. is still supported but isn't receiving feature updates and isn't recommended for new development. NET in general, development of SqlClient needed to shift to a package outside of. Up until 2019, it was receiving regular feature updates. The SqlClient library is an ADO.NET data provider that provides connectivity to SQL Server and Azure SQL data sources. NET Framework and continues to be improved and maintained in. ADO.NET was introduced with the Microsoft. ADO.NETĪDO.NET is a set of classes that defines an interface for accessing any kind of data source, both relational and non-relational. The new OLE DB provider is called the "Microsoft OLE DB Driver for SQL Server" (MSOLEDBSQL) and is currently maintained and supported. In 2017, OLE DB data access technology was later undeprecated and a new planned release was announced for 2018. It was announced as deprecated in 2011 and it isn't recommended to use this driver for new development. Starting in SQL Server 2005, the SQL Server Native Client includes an OLE DB provider interface (SQLNCLI) and is the OLE DB provider that shipped with SQL Server 2005 through SQL Server 2017. This provider won't be updated with new features and it isn't recommended to use this driver for new development. The first "Microsoft OLE DB Provider for SQL Server" (SQLOLEDB) still ships as part of Windows Data Access Components. There are three distinct generations of Microsoft OLE DB providers for SQL Server. For more information, see the Microsoft ODBC Driver for SQL Server documentation. Microsoft ODBC Driver for SQL ServerĪfter SQL Server 2012, the primary ODBC driver for SQL Server has been developed and released as the Microsoft ODBC Driver for SQL Server. Switch to the Microsoft ODBC Driver for SQL Server or the Microsoft OLE DB Driver for SQL Server if you want to take advantage of new SQL Server features going forward.įor complete documentation of the SQL Server Native Client, see the SQL Server Native Client documentation. (Microsoft/Windows Data Access Components aren't updated for these new features in SQL Server.) For new features beyond SQL Server 2012, SQL Server Native Client won't be updated. SQL Server Native Client can be used for applications that need to take advantage of new features introduced in SQL Server 2005 through SQL Server 2012. SQL Server Native Client (often abbreviated SNAC) was included in SQL Server 2005 through 2012. SQL Server Native Client is a stand-alone library that is used for both OLE DB and ODBC. After SQL Server 2012, the Microsoft ODBC Driver for SQL Server is the driver that is updated with the most recent server features going forward. This driver also isn't recommended for new development. Starting in SQL Server 2005, the SQL Server Native Client includes an ODBC interface and is the ODBC driver that shipped with SQL Server 2005 through SQL Server 2012. This driver isn't recommended for new development. The first "SQL Server" ODBC driver still ships as part of Windows Data Access Components. There are three distinct generations of Microsoft ODBC drivers for SQL Server. This page describes Microsoft's historical data connection technologies for connecting to SQL Server. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |