This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
whats the difference between the following ? which is performs better ?
what's the difference between the provider , in the oledbconnection string ??
Provider=Microsoft.Jet.OLEDB.4.0 and
Provider=MSOLEDBSQL
?which one is better in performance ?
In the C#
Using System.Data.OleDb, < which the connection will be using ADO.NET through oledb .
Is it possible to use native oledb driver inside a C# program ?
You can see the answers posted in this thread : What is the difference between System.Data.SqlClient, System.Data.OledbClient and System.Data.OdbcClient for accessing sql data
I think it's right which back to year of 2010 ???
See recent documentation, like .NET Framework Data Providers
with :
"
The .NET Framework Data Provider for SQL Server (SqlClient) uses its own protocol to communicate with SQL Server. It is lightweight and performs well because it is optimized to access a SQL Server directly without adding an OLE DB or Open Database Connectivity (ODBC) layer.
"
A data provider like SqlClient is optimized for performance to SQL-Server along with offering access to features specific to SQL-Server. In short, SqlClient is the choice to use for SQL-Server.
what about the following comment ?
In regards to the data drivers, let's say you are coding with .NET Framework 4.8 or below, there is no reason not to use these. If using .NET Core Framework then use Microsoft.Data.SqlClient rather than System.Data.SqlClient installed via NuGet.
From Microsoft
The Microsoft.Data.SqlClient package will be the flagship data access driver for SQL Server going forward.
Did you find comments for SqlClient too?