Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I've been running through some Classic ASP code recently and was wondering if there was a performance difference between connecting using:

Provider=SQLOLEDB;server=NTSERVERNAME\SQLEXPRESS;database=DBNAME;uid=USER;pwd=PASSWORD;

Or

Provider=SQLNCLI;server=NTSERVERNAME\SQLEXPRESS;database=DBNAME;uid=USER;pwd=PASSWORD;

I seem to recall that there is a performance impact with some provider options (mostly from the days of SQL Server 2000 and earlier), but I've not been able to find if that is the case with these two providers.

The only thing I've been able to find are articles explaining that the latter will let me use some of the new features in SQL Server 2005 (XML data type, etc.) and some other feature support issues - but nothing about performance.

share|improve this question

1 Answer 1

up vote 4 down vote accepted

I talked to Erland Sommarskog about this and here is his response.

I attended a presentation as PASS 2005 about SQL Native Client. The then-PM for SQL Server Client said that for ODBC they had achieved a 20% perf improvement, but for OLE DB, it was about even.

But since SQLNCLI provides more features, that is probably the provider to use. Then again, with old ADO a lot of the features are unavailable anyway.

HTH

share|improve this answer
    
That helps. I'll probably go ahead and start using the SQLNCLI. –  AnonJr May 25 '11 at 14:06

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.