- #Microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit how to#
- #Microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit driver#
- #Microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit windows#
#Microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit driver#
Provides information about using the OLE DB Driver for SQL Server.įinding more OLE DB Driver for SQL Server information System requirements for OLE DB Driver for SQL Serverĭiscusses the system resources needed to use OLE DB Driver for SQL Server.
#Microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit how to#
This section also discusses OLE DB Driver for SQL Server installation and deployment, including how to redistribute the OLE DB Driver for SQL Server library.
#Microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit windows#
Provides an overview of OLE DB Driver for SQL Server development, including how it differs from Windows DAC, the components that it uses, and how ADO can be used with it. In this sectionĭiscusses how OLE DB Driver for SQL Server fits in with Microsoft data access technologies, how it compares to Windows DAC and ADO.NET, and provides pointers for deciding which data access technology to use.ĭescribes the features supported by OLE DB Driver for SQL Server.īuilding applications with OLE DB Driver for SQL Server To use the new Microsoft OLE DB Driver for SQL Server in existing applications, you should plan to convert your connection strings from SQLOLEDB or SQLNCLI, to MSOLEDBSQL. The new provider will be updated with the most recent server features going forward. The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). OLE DB was undeprecated and released in 2018. Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) For more information about the SNAC lifecycle and available downloads, refer to SNAC lifecycle explained. It was announced as deprecated in 2011 and it is not recommended to use this driver for new development. Starting in SQL Server 2005 (9.x), the SQL Server Native Client (SNAC) includes an OLE DB provider interface (SQLNCLI) and is the OLE DB provider that shipped with SQL Server 2005 (9.x) through SQL Server 2012 (11.x). It is not maintained anymore and it is not recommended to use this driver for new development. The Microsoft OLE DB Provider for SQL Server (SQLOLEDB) still ships as part of Windows Data Access Components. Microsoft OLE DB Provider for SQL Server (SQLOLEDB) There are three distinct generations of Microsoft OLE DB providers for SQL Server. You can use OLE DB Driver for SQL Server with the version of Windows DAC that is installed with any operating system supported by OLE DB Driver for SQL Server.
![microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit](https://i.stack.imgur.com/PgmcM.png)
While OLE DB Driver for SQL Server uses components in Windows DAC, it is not explicitly dependent on a particular version of Windows DAC.
![microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit](https://datasavvy.files.wordpress.com/2017/07/ace-engine-bittedness-error.png)
It provides a way to innovate and evolve new data access features without changing the current Windows DAC components, which are now part of the Microsoft Windows platform. OLE DB Driver for SQL Server was designed to provide a simplified method of gaining native data access to SQL Server using OLE DB. For more information about the use of these features with ADO, see Using ADO with OLE DB Driver for SQL Server. When using the OLE DB Driver for SQL Server, ADO applications may exploit those new features introduced in SQL Server 2005 (9.x) that are available via the OLE DB Driver for SQL Server via connection string keywords or OLE DB properties or Transact-SQL.
![microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit microsoft.jet.oledb.4.0 for sql server 2008 r2 64 bit](https://i0.wp.com/www.maxxxie.net/wp-content/uploads/2012/07/6_diskpartscripted.png)
The OLE DB Driver for SQL Server can be used in conjunction with OLE DB Core Services supplied with Windows DAC, but this is not a requirement the choice to use Core Services or not depends on the requirements of the individual application (for example, if connection pooling is required).ĪctiveX Data Object (ADO) applications may use the OLE DB Driver for SQL Server, but it is recommended to use ADO in conjunction with the DataTypeCompatibility connection string keyword (or its corresponding DataSource property). The previous Microsoft OLE DB Provider for SQL Server (SQLOLEDB) and SQL Server Native Client OLE DB provider (SQLNCLI) remains deprecated and it is not recommended to use either for new development work.