What, if any, effect does creating multiple recordsets have on ASP page load
time?
By new recordsets, I'm referring to:

server.createobject("adodb.recordset")

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.377 / Virus Database: 211 - Release Date: 7/15/2002
 

You are instantiating an object instance. Doing this always incurs overhead.

The real killer though is:
a) what you put into it (a recordset that needs to hold 1,000,000 records is
obviously going to be much more heavier than one that holds 10 records. Also
a recordset that has 50 large fields in much heavier than a recordset that
has 2 fields)

b) what type of cursor you use: adOpenStatic/adOpenKeySet cursors are much
more expensive than adOpenForwardOnly/adLockReadOnly

c) how long you keep the connection open. If you use .GetRows to pump the
data into a VBScript array you can dispose of the Recordset object (and the
underlying connection) straight away, giving you greate scalability (ie the
ability to support more simultaneous users, even if the speed of each page
isn't much faster)

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "Young, Ashley" <Ashley.Young@c...>
Subject: [access_asp] What effect does multiple recordsets have on load
time?


: What, if any, effect does creating multiple recordsets have on ASP page
load
: time?
: By new recordsets, I'm referring to:
:
: server.createobject("adodb.recordset")

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~