You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/connect/oledb/oledb-driver-for-sql-server.md
+4-9Lines changed: 4 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,25 +23,20 @@ ms.workload: "Active"
23
23
24
24
MSOLEDBSQL, or OLE DB Driver for SQL Server, is a term that has been used interchangeably to refer to OLE DB Driver for SQL Server.
25
25
26
-
## Different Incarnations of OLE DB Drivers
27
-
28
-
There are three distinct incarnations of Microsoft OLE DB providers for SQL Server.
26
+
## Different generations of OLE DB Drivers
29
27
28
+
There are three distinct generations of Microsoft OLE DB providers for SQL Server.
30
29
31
30
### 1. Microsoft OLE DB Provider for SQL Server (SQLOLEDB)
32
-
33
31
The [Microsoft OLE DB Provider for SQL Server](../../ado/guide/appendixes/microsoft-ole-db-provider-for-sql-server.md) (SQLOLEDB) still ships as part of [Windows Data Access Components](https://msdn.microsoft.com/en-us/library/ms692897.aspx). It is not recommended to use this driver for new development.
34
32
35
33
36
34
### 2. SQL Server Native Client (SNAC)
37
-
38
35
Starting in SQL Server 2005, the [SQL Server Native Client (SNAC)](../../relational-databases/native-client/sql-server-native-client.md) includes an OLE DB provider interface (SQLNCLI) and is the OLE DB provider that shipped with SQL Server 2005 through SQL Server 2017.
39
36
40
37
It was [announced as deprecated in 2011](https://blogs.msdn.microsoft.com/sqlnativeclient/2011/08/29/microsoft-is-aligning-with-odbc-for-native-relational-data-access/) and it is not recommended to use this driver for new development.
41
38
42
-
43
39
### 3. Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)
44
-
45
40
OLE DB was [announced as undeprecated in 2017](https://blogs.msdn.microsoft.com/sqlnativeclient/2017/10/06/announcing-the-new-release-of-ole-db-driver-for-sql-server/). A new planned release was announced for 2018.
46
41
47
42
The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The new provider will be updated with the most recent server features going forward.
@@ -59,5 +54,5 @@ Information on the OLE DB Driver for SQL Server features:
59
54
-[Accessing Diagnostic Information in the Extended Events Log](../oledb/features/accessing-diagnostic-information-in-the-extended-events-log.md)
60
55
61
56
## See also
62
-
[Install OLE DB Driver for SQL Server](../oledb/applications/installing-oledb-driver-for-sql-server.md)
63
-
[OLE DB Driver for SQL Server Features](../oledb/features/oledb-driver-for-sql-server-features.md)
57
+
[Install OLE DB Driver for SQL Server](../oledb/applications/installing-oledb-driver-for-sql-server.md)
58
+
[OLE DB Driver for SQL Server Features](../oledb/features/oledb-driver-for-sql-server-features.md)
@@ -22,7 +22,6 @@ This article provides download links to connection modules or *drivers* that you
22
22
- MacOS
23
23
- Windows
24
24
25
-
26
25
#### OOP-to-relational mismatch
27
26
28
27
*Relational*: Client programs that are written in an object-oriented programming (OOP) language often use SQL drivers which return queried data in a format that is more relational than object oriented. C# using ADO.NET is one example. The OOP-relational format mismatch sometimes makes the OOP code harder to write and understand.
@@ -31,7 +30,6 @@ This article provides download links to connection modules or *drivers* that you
31
30
32
31
The present article devotes separate sections to these two kinds of connection drivers.
33
32
34
-
35
33
<aname="anchor-20-drivers-relational-access" />
36
34
37
35
## Drivers for relational access
@@ -48,19 +46,17 @@ PHP driver in Github.com also uses this FWLink: http://go.microsoft.com/fwlink/
48
46
although the FWLink is less precise than is http://github.com/Microsoft/msphpsql/tree/dev#install-unix .
49
47
-->
50
48
51
-
52
49
| Language | Download the SQL driver |
53
50
| :------- | :---------------------- |
54
-
| C# |[ADO.NET](http://www.microsoft.com/net/download/)<br /><br />[.NET Core, for Linux-Ubuntu](https://www.microsoft.com/net/core#Ubuntu)<br />[.NET Core, for MacOS](https://www.microsoft.com/net/core#macos)<br />[.NET Core, for Windows](https://www.microsoft.com/net/core)|
55
-
| C++ |[ODBC](http://docs.microsoft.com/sql/connect/odbc/download-odbc-driver-for-sql-server)|
[http://aka.ms/sqldev](http://aka.ms/sqldev) takes you to a set of *Build-an-app* webpages. The webpages provide information about numerous combinations of programming language, operating system, and SQL connection driver. Among the information provided by the Build-an-app webpages are the following items:
89
82
90
83
- Details about how to get started from the very beginning, for each combination of language + operating system + driver.
@@ -94,25 +87,17 @@ The following table lists examples of Object Relational Mapping (ORM) frameworks
94
87
- ORM code examples.
95
88
- Columnstore index demonstrations for much faster performance.
96
89
97
-
98
90
#### First page, of Build-an-app webpages
99
-
100
91
![Build-an-app webpages, first page screenshot][image-ref-163-buildanapp-webpages-first-page]
101
92
102
-
103
93
#### Menu for Java - Ubuntu, of Build-an-app webpages
104
-
105
94
![Build-an-app webpages, menu Java Ubuntu][image-ref-167-buildanapp-webpages-menu-java-ubuntu]
106
95
107
-
108
96
109
97
110
-
111
98
## Related links
112
-
113
99
-[Code examples for connecting to Azure SQL Database in the cloud, with Java and other languages](http://docs.microsoft.com/azure/sql-database/sql-database-connect-query-java).
[!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] supports two availability modes—asynchronous-commit mode and synchronous-commit mode, as follows:
51
+
[!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] supports three availability modes—asynchronous-commit mode, synchronous-commit mode, and configuration only mode as follows:
52
52
53
53
-*Asynchronous-commit mode* is a disaster-recovery solution that works well when the availability replicas are distributed over considerable distances. If every secondary replica is running under asynchronous-commit mode, the primary replica does not wait for any of the secondary replicas to harden the log. Rather, immediately after writing the log record to the local log file, the primary replica sends the transaction confirmation to the client. The primary replica runs with minimum transaction latency in relation to a secondary replica that is configured for asynchronous-commit mode. If the current primary is configured for asynchronous commit availability mode, it will commit transactions asynchronously for all secondary replicas regardless of their individual availability mode settings.
0 commit comments