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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2001-06-18 : 13:07:21
|
Pat writes "In my application we have stored procedures that are "long running;" for example, 5 minutes in duration, due to large hierarchical datasets that must be traversed recursively. During execution of these stored procedures, our users sit befuddled, kind of wondering if anything is really happenning. Putting up a "please wait" or an enlessly turning hourglass indicates that tis working, but what we'd really like to do is convey some sort of progress to the user. Because the operation is largely recursive, it is not particualrly feasible to unroll one or more layers of loops into the application (i.e. out of the stored procedure) nor does that seem like a particularly good way of doing things in general. Progress would be relatively easy to report from within the stored procedure using PRINT statements or the like, but it would seem that there is no way to get at that text stream from ADO (we are using Access and ASP) and even if we could get at it, who knows if its buffered or what. So, the question is: How do you convey progress to a user when a Stored Procedure is executed via ADO?
Thanks Pat" |
|
|
|
|
|