Opening Mulitple Recordsets

I have a single .asp page that opens a connection and then sequentially
opens and closes 14 recordsets from stored procedures to obtain various
product information before closing the connection.

Is it common practice to do something like this? Or is opening 14
recordsets going to become a real problem when the page goes live and starts
getting high web traffic?

Thank you in advance for any information you might provide.

DaveHi

There is not really enough detail to know if you will have problems with
this although 14 seems quite a few it may not necessarily cause any problems
if the number of records being retrieved is not excessive. You should
simulate different levels of usage on your system before it goes live to get
some idea of the response.

If you are making muliple calls to different stored procedures, you may wish
to use a controlling procedure that returns multiple result sets see:
http://www.aspfaq.com/show.asp?id=2319

John

"Toonman" <toonman@.NOSPAMtoonman.com> wrote in message
news:4fZLb.10540$uF6.3301521@.news1.news.adelphia.n et...
> I have a single .asp page that opens a connection and then sequentially
> opens and closes 14 recordsets from stored procedures to obtain various
> product information before closing the connection.
> Is it common practice to do something like this? Or is opening 14
> recordsets going to become a real problem when the page goes live and
starts
> getting high web traffic?
> Thank you in advance for any information you might provide.
> Dave|||John,

Your information was extremely helpful... thank you again.

Dave

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:btpp2d$8ja$1@.sparta.btinternet.com...
> Hi
> There is not really enough detail to know if you will have problems with
> this although 14 seems quite a few it may not necessarily cause any
problems
> if the number of records being retrieved is not excessive. You should
> simulate different levels of usage on your system before it goes live to
get
> some idea of the response.
> If you are making muliple calls to different stored procedures, you may
wish
> to use a controlling procedure that returns multiple result sets see:
> http://www.aspfaq.com/show.asp?id=2319
> John
> "Toonman" <toonman@.NOSPAMtoonman.com> wrote in message
> news:4fZLb.10540$uF6.3301521@.news1.news.adelphia.n et...
> > I have a single .asp page that opens a connection and then sequentially
> > opens and closes 14 recordsets from stored procedures to obtain various
> > product information before closing the connection.
> > Is it common practice to do something like this? Or is opening 14
> > recordsets going to become a real problem when the page goes live and
> starts
> > getting high web traffic?
> > Thank you in advance for any information you might provide.
> > Dave