Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL Server
Expertise: Beginner
Dec 20, 1999



Application Security Testing: An Integral Part of DevOps


Which implementation works faster, ADO or ODBC? Is there any relevant information (or benchmarks) comparing the difference between linking directly to the ODBC or accessing databases through the ADO components?

I haven't timed them so I can't say. There's also another variable that could weigh in your choice.

My understanding is that ADO is built on OLE DB and so has the capacity to manipulate nontabular data, in contrast to ODBC, which is only for database tables.

I wouldn't approach the choice from the dimension of speed. It has more to do with flexibility in handling nondatabase data (like project files or documents), not to mention that ADO's object model gives you much more control over the object and easier trappable error information about your process.

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date