Hi,

I think you have a trade-off here though, so there's only one way to find
out and that is testing your specific situation. There are a lot of things
involved in increasing performance. One of them is the use of well defined
indexes on the specific tables. The number of recordsets and the number of
joins should be "in balance", to get the best performance... It's a
theoretical approach, but it's a start...

What I would do is to test the extremes, ie.
- Test how long it takes to build a lot of recordsets and
- Test how long it takes to build one ( or two ) recordsets by joining the
tables.

Hope this helps,

Serge

----- Original Message -----
From: "Håkan Frennesson" <hakan@c...>
To: "ASP Databases" <asp_databases@p...>
Sent: Thursday, June 06, 2002 9:58 AM
Subject: [asp_databases] Performance issues


> Hi!
>
> I would like some advice from you all regarding performance issues and
what road to take.
>
> When showing records from many tables on one page, what is preferable:
> A) Several recordsets OR
> B) A few recordsets with many joins OR
> C) Several INCLUDE pages defining one recordset in each OR
> D) Should I look for other alternatives.
>
> The database in question is in SQL Server 2000 and does not not hold a lot
of records, just many tables.
>
> All advices, hints or links are greatly appreciated.
>
> Regards,
>
> Håkan
>
>

Here are some of the guidelines,
Don't use too much of include pages, instead u can use server.execute method
to achieve the same.
Don't keep the recordsets open for longer time, use it and immediately
close. Keeping the recordset in memory for longer time is costly.
Better the nested queries, if u feel it is slow go for the stored
procedures.

-Naveen


----- Original Message -----
From: Håkan Frennesson <hakan@c...>
To: ASP Databases <asp_databases@p...>
Sent: Thursday, June 06, 2002 1:28 PM
Subject: [asp_databases] Performance issues


Hi!

I would like some advice from you all regarding performance issues and what
road to take.

When showing records from many tables on one page, what is preferable:
A) Several recordsets OR
B) A few recordsets with many joins OR
C) Several INCLUDE pages defining one recordset in each OR
D) Should I look for other alternatives.

The database in question is in SQL Server 2000 and does not not hold a lot
of records, just many tables.

All advices, hints or links are greatly appreciated.

Regards,

Håkan

Hi!

I would like some advice from you all regarding performance issues and 
what road to take.

When showing records from many tables on one page, what is preferable:
A) Several recordsets OR
B) A few recordsets with many joins OR
C) Several INCLUDE pages defining one recordset in each OR
D) Should I look for other alternatives.

The database in question is in SQL Server 2000 and does not not hold a 
lot of records, just many tables.

All advices, hints or links are greatly appreciated.

Regards,

H=E5kan