Printable View
When programming ASP in a Windows server environment...
Im curious how many recordsets are too many?
Anyone have an idea? I understand the speed of the server and the current server load play a huge role in deciding how many recordsets a single page can have... but i dont have any idea how to balance the two.
Anyone have any thoughts?
It just really depends on how long it takes to get the data in those recordsets - how complex are the queries, etc.? Then it depends on what your ASP is doing with the recordset before sending the page to the browser. And then of course the amount of time all of that takes depends on the web server load and the database server load. Add all of that time up and if it's too long for most users, then it's too much.
You can increase performance dramatically by using stored procedures in the database and by using GetRows in your ASP. And static, frequently-accessed data should go into Application variables.
But there's no rule of thumb that I know of that says "this many recordsets is too many".