The article is very dense in relevant information. However, a discussion of the choice of cursor location on performance would be helpful. It is clear from the basic documentation that you should use readonly, forward only cursors and in what order the cursors will take more time/resources, but there is little discussion about cursor location and its effect on performance. Background on the way that records are transfered from server to client would be helpful. Also, a discussion on how things work on the server, the use of the TempDB, the visibility of added/deleted records etc when in a transaction would be helpful - and does the cursor location effect this?

WILLIAM1/3/2007 12:18:32 PM

Good article..

Denis6/14/2004 6:32:06 AM

Finally, an article that really goes into detail about "how to" use ADO more effectively.

Martin Barron 5/9/2003 10:27:17 AM

This article is excellent. I've been working with SQL for about a year now, and 2-3 of the ideas discussed are new to me. I think the proper coding of SQL and actually learning the many different ways to do one thing is what sets experienced SQL developers apart from the pack...

Keith8/21/2001 10:24:15 PM

This article is really great. I have a few of Bill's books for my own collection and reference. I think this article explains the practicality of applying Microsoft data-access technology the way it should be used for real-world apps.

Asri Ismail 7/29/2001 10:23:42 PM

This is in reference to the article "ADO Best Performance Practises" (i.e InstantDoc 16272). It says
With the procedures as Connection methods, you can pass the stored procedure's input arguments as method arguments, and if a Recordset is returned, you can reference the Recordset as the last argument in the method call. For example, the following ADO statement executes a stored procedure called "Fred" that has two input parameters and a returned Recordset:

MyConnection.Fred "InputArg1", 2, myRecordset

"


Microsoft JET Database Engine error '80040e10'

Too few parameters. Expected 1.

kamran7/13/2001 1:03:33 PM

This is the type of a article that all developers should see. Thanks for sharing this knownledge with us.

Filipe Santos 7/11/2001 3:44:08 PM

I bought Bill Vaughn's book for reference. As a DBA, I refer to it quite often to troubleshoot issues that developers bring up. The book gives us an idea of what to look for, both in SQL and in ASP/ADO app code.

Mike Beadles 6/20/2001 2:43:14 PM

Good stuff! I'm struggling now to improve my application's performance. This article gave me good advice with deep explanations.
Thank you.

Victor Kuzmich 6/18/2001 7:50:24 PM

Why not using the GetRows method? Isn't it even faster and more practical than the prebinding?

Richard Nolasque 5/4/2001 2:54:57 PM