SQL Server 2008 R2 Express v SQL Server 2012 Express

What is the difference between this connection string:
conn.Open "Provider=SQLNCLI10;Server=localhost\SQLExpress;Database=xxx;Uid=xxx;Pwd=xxx;"

And this one:
conn.Open "Provider=SQLNCLI11;Server=localhost\SQLExpress;Database=xxx;Uid=xxx;Pwd=xxx;"

The first one I used when I used SQL Server 2008 and it also works with 2012 on my web pages but on my windows apps I had to change to the second one in order to get them to run once I upgraded to 2012.

Just wondering about the apparent inconsistencies.

THanks!
Bob SchneiderCo-OwnerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ste5anSenior DeveloperCommented:
Obviously the provider... and a provider is nothing else then - may be you may guess?? - a driver. The correct driver must be installed, otherwise it won't work. btw, SQLNCLI is short for SQL Server Native Client.
0
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
I don't believe sqlncli10 is a valid provider for sql server 2012. looking for some documentation to back that up right now.....
0
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
according to here, it isn't compatible with sql server 2012:

https://www.connectionstrings.com/sql-server-native-client-10-0-oledb-provider/

i'm not sure how you're getting it work with your web apps. I recommend using the correct provider for sql server 2012, which is version 11
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Bob SchneiderCo-OwnerAuthor Commented:
Thanks.  I will switch it all over to the preferred provider.
0
ste5anSenior DeveloperCommented:
Both native clients work with both server versions. The problem is that the provider string is used to look up only this driver, not a compatible one. So, in one of the scenarios the provider pointed to an uninstalled version.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.