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. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a desktop application written in Visual Basic .NET. One our clients needs to use ODBC instead of OLEDB to connect to the SQL Server 2008 R2 Database. The company has several databases including Oracle, IBM DB2, and PostgreSQL.

We can migrate the connections, but we need to know what is the better: OLEDB or ODBC when connecting to SQL Server 2008 R2?

share|improve this question
Thx SQL Kiwi – RicardoBalda Dec 14 '12 at 19:57
up vote 2 down vote accepted

For most applications hitting SQL Server 2008 R2, you would be fine going either way, I think.

OLEDB support is being removed after SQL Server 2012 but until it is, you'd likely be fine either way based on your standards and your needs. That said, I'd look to future supportability and consider going ODBC with the Native Client.

I would say a more important decisions would be to consider using the Native Client for your .net apps if you aren't already.

share|improve this answer
Thx Mike Walsh – RicardoBalda Dec 14 '12 at 20:00

Your Answer


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.