Don’t Create a Recordset Unless It’s Required

Don’t Create a Recordset Unless It’s Required

When running action queries make sure you add the adExecuteNoRecords option, so that a recordset is not created. You can also use this technique in lookup situations when returning just a single row with one or two fields (ID values for example). In this case a stored procedure and outparameter will be faster. Here is an example:

 Set cmdUpdate=Server.Createobject(ADODB.Command")strsql = "UPDATE Titles SET Price = Price*1.0" & "WHERE Type _= 'Business'"cmdUpdate.ActiveConnection = cmdUpdate.CommandText = cmdUpdate.CommandType = adcmdstoredprocedurecmdUpdate.Execute , , adExecuteNoRecords

This runs the Update command and ensures that no recordset is created.

Share the Post:
data observability

Data Observability Explained

June 8, 2023

Data is the lifeblood of any successful business, as it is the driving force behind critical decision-making, insight generation, and strategic development. However, due to its intricate nature, ensuring the

Heading photo, Metadata.

What is Metadata?

June 1, 2023

What is metadata? Well, It’s an odd concept to wrap your head around. Metadata is essentially the secondary layer of data that tracks details about the “regular” data. The regular

Show More