This topic is locked

will ASPRunner support 1 million + rows of data ?

3/14/2008 9:09:40 PM
ASPRunnerPro General questions
E
euterpe author

Hello, I have generated a front end to 2 simple tables to display data. These tables will hold a million plus rows and counting when commissioned in use. My question is, will ASPRunner's code be able to handle this? Right now, when I am testing it, it just has a 100 rows so its fine. But what happens when there are a million rows to display?
Will ASPRunner run the SQL query in step 3 of the process and try to hold all that data somewhere when the 'Show All" option is displayed? I need to make sure that ASPRunner generated code works for large number of rows. Typically, I am guessing, that it should query and display botton N number of rows and display.
But how does ASP Runner work? If you choose 20 rows per page and chen click on 'Show All", will it query the top N or botton 20 rows for display?..and then so on...OR will it - based on the straight query in step 3or 4 try to query all available rows against the database? In that case I am guessing, even the cache will not hold so much data and ASPRunner generated pages will errror out.
Please advice or comment. Anyone from ASPRunner Development team can make a comment on this?
Thanks,

Euterpe.

U
Ugain 3/18/2008

Hello, I have generated a front end to 2 simple tables to display data. These tables will hold a million plus rows and counting when commissioned in use. My question is, will ASPRunner's code be able to handle this? Right now, when I am testing it, it just has a 100 rows so its fine. But what happens when there are a million rows to display?

Will ASPRunner run the SQL query in step 3 of the process and try to hold all that data somewhere when the 'Show All" option is displayed? I need to make sure that ASPRunner generated code works for large number of rows. Typically, I am guessing, that it should query and display botton N number of rows and display.
But how does ASP Runner work? If you choose 20 rows per page and chen click on 'Show All", will it query the top N or botton 20 rows for display?..and then so on...OR will it - based on the straight query in step 3or 4 try to query all available rows against the database? In that case I am guessing, even the cache will not hold so much data and ASPRunner generated pages will errror out.
Please advice or comment. Anyone from ASPRunner Development team can make a comment on this?
Thanks,

Euterpe.


The technnology, ASP/php/cgi/.NET, that you will use does not really matter. It's the database that will impose limits on your data. If you are planning to use MS Access then you may as well forget it. You will have to use MSSQL or mySQL to handle the large number of records.
Who in their right mind would want to see million records on their screen at one time as in "Show All"? If I see more than 20 items per page with 10 or more pages to go thru then I would want a way to filter this data (search ?).

Sergey Kornilov admin 3/18/2008

Ugain,
thank you for thoughtful comment.
I cannot agree more, giving visitor a million records to loop through is a bad idea. With this amount of data you should use No records on first page option to allow users search for something first. Dropping Show all button is also a good idea.
ASPRunnerPro handles your data the same way no matter how many records you have. If you to view first 20 records ASPRunnerPro automatically adds TOP 20 clause to SQL query to select as many data records as required. It really depends on database and server performance. SQL Server and MySQL should be able to handle this amount of data just fine.