Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers

Webmaster Forum / ASP / Database Access / November 2007



Tip: Looking for answers? Try searching our database.

Is it worth switching from SQLOLEDB to Native Client?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David Morgan - 15 Nov 2007 14:17 GMT
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
Bob Barrows [MVP] - 15 Nov 2007 14:38 GMT
> Hello
>
[quoted text clipped - 6 lines]
> 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.

Signature

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.

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.