1

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?

Paul White ♦
95.4k30 gold badges440 silver badges689 bronze badges
asked Dec 13, 2012 at 13:27
1
  • Thx SQL Kiwi Commented Dec 14, 2012 at 19:57

1 Answer 1

2

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.

Glorfindel
2,2095 gold badges19 silver badges26 bronze badges
answered Dec 13, 2012 at 13:55
1
  • 1
    Thx Mike Walsh Commented Dec 14, 2012 at 20:00

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.