bbkevin
asked on
Asynchronous
Hi Experts,
I have very long stored procedure that require to running for few hours. The current situation is allow the user to start the stored procedure and check the status in the ASP.NET web application.
Current Items
- Web Page contains single START button only
- Stored Procedure named SP_Retrieve_Internet_Recor
- Table named tblStatus contains one varchar column named Status.
Some suggestion on the web say calling Web Services Asynchronously,
and other say using delegate.
If you can give some examples it will be greatly appreciated.
I have very long stored procedure that require to running for few hours. The current situation is allow the user to start the stored procedure and check the status in the ASP.NET web application.
Current Items
- Web Page contains single START button only
- Stored Procedure named SP_Retrieve_Internet_Recor
- Table named tblStatus contains one varchar column named Status.
Some suggestion on the web say calling Web Services Asynchronously,
and other say using delegate.
If you can give some examples it will be greatly appreciated.
ASKER
The user may not start the process because of bad weather such as earthquake, hurricane, tsunami, typhoon, cyclone...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Do you think attached code is common practice?
Default.aspx
Default.aspx.cs
SP-Process.sql
SP-Status.sql
tblStatus.sql
ThreadUtil.cs
WebService.cs
Default.aspx
Default.aspx.cs
SP-Process.sql
SP-Status.sql
tblStatus.sql
ThreadUtil.cs
WebService.cs
is there some reason that this process needs to be started by the user? if, for example, it runs every day, you could create a scheduled task to run the stored procedure, and then generate a report, email, etc. that would notify the user when it is complete.