Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
smartlizard
Starting Member
24 Posts |
 Posted - 2001-11-30 : 00:56:13
|
| I need to run a report from an ASP page. It must look through several million records and multiple Stored Procedures.The user could get quite bored by looking at a blank white screen and a rotating IE logo for a few minutes. (or could click refresh multiple times!)Is there some way to have a progress bar or something?Or a way to pass this off to some sort of Que so that the user can go off and surf somewhere else and return in 5 mintutes, to see if his report is ready?Whew! Thanks for the help.Ron Sellhttp://smartLIZARD.comEdited by - smartlizard on 11/30/2001 00:58:18 |
|
|
sica
Posting Yak Master
143 Posts |
Posted - 2001-11-30 : 03:21:07
|
| Hi,Why don't you schedule the report and have different status to describe the job like run,waiting,ready.Give the report a name and id and create a table to save it.Sica |
 |
|
|
smartlizard
Starting Member
24 Posts |
Posted - 2001-11-30 : 08:54:03
|
| Sounds Great!How do you do this?Remember, The report will be initiated from an ASP web page.They click, "Crete Report", then they are transported to a page that tells them to come back in 5 minutes, while they continue to surf to other pages (possibly even getting another report), the report is being compiled on the server. Later, they log back in to see if the report is finished yet, if it is, they click on the link and whamo! there is the report. :)Thanks for the help!Ron Sellhttp://smartLIZARD.com |
|
|
|
sica
Posting Yak Master
143 Posts |
Posted - 2001-11-30 : 09:17:31
|
| Create a table w/ all information you need that is being parse every minute by a job.The job can contain a sp that that starts other sp that create the report,updates status of the report,time etc.It's up to you.Every time the job start it takes all the posts that are not have been treated.Every report can have a unique identity in order to create the table that show information to the user.It's just an idea ...You can schedule reports as well to run under night if you add a date that user can fill.Sica |
|
|
|
GreatInca
Posting Yak Master
102 Posts |
Posted - 2001-11-30 : 12:25:55
|
| You can also make a makeshift pre-grouped DB Warehouse fact table that gets every night or every 6 or 12 hours or something and have the ASP page query the fact table. The efficient non nuke & create Updating fact tables is easiest if a time block (day, hour, month, etc.. expressed as the starting date of the range) is involved in the group-by.You'll need separate fact / pre-aggrate tables for each would-be group by (even if its different units of time or different detail granularities, but these things boost performance tremendously and retain parameter flexibility.The 'Dimension tables' would be the the your regular OLTP tables so its not a proper data warehouse unless the OLTP tables being used have no underling tables (parent tables ok - just the star turns into snowflake) and the tables are 'read-only' except in batch updates (2nd is less important than first).Edited by - GreatInca on 11/30/2001 12:27:38 |
|
|
|
|
|
|
|
|
Looooong Running Queries