![odbc driver for sql server 2008 download odbc driver for sql server 2008 download](https://www.sqlrelease.com/wp-content/uploads/2017/11/Connecting-Python-3-to-SQL-Server-2017-using-pyodbc-Delete-query-output.jpg)
#Odbc driver for sql server 2008 download code
Of course, if you have or are planning on moving to a managed code base for data access, then the ADO.NET data access classes of the. Your existing OLE DB and ODBC code will work just fine. If you don’t need any of the new features of SQL Server 2019, then you don’t need to use SQL Native Client.
![odbc driver for sql server 2008 download odbc driver for sql server 2008 download](http://lh4.ggpht.com/-ntDvqwBHLUQ/UKd6NAfIt8I/AAAAAAAALBI/tv6w-HzWICM/image_thumb1.png)
When would you actually want to use SQL Native Client as opposed to MDAC, or even ADO.NET? The answer is – only if you are upgrading existing or developing new COM-based (or native) applications that will target the new features of SQL Server 2019. SQL Native Client was introduced in Microsoft SQL Server 2005 to provide new functionality above and beyond that supplied by the Microsoft Data Access Components (MDAC). Microsoft SQL Server Native Client (SQL Native Client) contains the SQL ODBC driver and SQL OLE DB provider in one native dynamic link library (DLL) supporting applications using native-code APIs (ODBC, OLE DB, and ADO) to Microsoft SQL Server. SQL Native Client can be used rather than Microsoft Data Access Components (MDAC) to create new applications or enhance existing applications that need to take advantage of new SQL Server 2019 features, such as Multiple Active Result Sets (MARS), Query Notifications, User-Defined Types (UDT), and XML data type support.