Is it worth switching from SQLOLEDB to Native Client?

Is it worth switching from SQLOLEDB to Native Client?

am 15.11.2007 15:17:19 von David Morgan

Hello

We have recently upgraded to SQL Server 2005 but our connection string still
references SQLOLEDB.1. (No I did not expect the SQL upgrade to upgrade our
connection strings!)

Having read this article,
(http://msdn2.microsoft.com/en-us/library/ms810810.aspx), it would seem that
there is no performance benefit to be gained by updating our connection
string to use the new Native Client.

Would anyone disagree with what Microsoft are saying here?

SQL Server Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access application
programming interface (API) that is used for both OLE DB and ODBC. It
combines the SQL OLE DB Provider and the SQL ODBC Driver into one native
dynamic-link library (DLL), while providing also new functionality that is
separate and distinct from the Microsoft Data Access Components (MDAC). SQL
Server Native Client can be used to create new applications or enhance
existing applications that must take advantage of new SQL Server 2005
features such as Multiple Active Result Sets (MARS), User-Defined Types
(UDT), and XML data-type support.

Thanks

David

Re: Is it worth switching from SQLOLEDB to Native Client?

am 15.11.2007 15:38:25 von reb01501

David Morgan wrote:
> Hello
>
> We have recently upgraded to SQL Server 2005 but our connection
> string still references SQLOLEDB.1. (No I did not expect the SQL
> upgrade to upgrade our connection strings!)
>
> Having read this article,
> (http://msdn2.microsoft.com/en-us/library/ms810810.aspx), it would
> seem that there is no performance benefit to be gained by updating
> our connection string to use the new Native Client.

AFAICS, the only reason to switch is if you need the new functionality
provided by the Native Client (MARS, etc.)
I haven't seen any performance benefit (except for the benefits achieved
through the use of the new features, that is): I don't believe the
provider itself would be the bottleneck for performance issues: network
bandwidth, server resources, etc would be more likely culprits in my
view.

Don't forget, you still may have clients that do not have the native
client installed for one reason or another.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.