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: Enterprise
Expertise: Advanced
Mar 21, 2000



Application Security Testing: An Integral Part of DevOps

Take Advantage of ADO Optimizations

A common user scenario in a development environment is where the code typically opens a connection, executes a row or non-row returning command, processes results, and closes the connection. For such scenarios, it is better to use Connection::Execute than Recordset::Open or Command::Execute.

ADO 2.0 utilizes some optimizations for one-time command executions when done through Connection::Execute. Actually, when Connection::Execute is used, ADO doesn't preserve any command state information and therefore leads to an improved performance.

Jai Bardhan
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