L
Lyle Bruney
I have a asp page that launches a specified stored procedure using the
sqlCommand object. The stored procedure will take several hours to complete
so I don't want the user to wait around for the response.
Is there a solid method/solution for ensuring that the stored procedure is
fired off and then the web page can be closed without repercussions to the
requested stored procedure execution?
I have tried using the sqlCommand object's (BeginExecuteNonQuery()) method
but it requires the ENdExecuteNonQuery() method before it completes and
allows the code to continue forward.
What alternative solutions and/or answers to this question can be utilized?
Thanks in advance!
sqlCommand object. The stored procedure will take several hours to complete
so I don't want the user to wait around for the response.
Is there a solid method/solution for ensuring that the stored procedure is
fired off and then the web page can be closed without repercussions to the
requested stored procedure execution?
I have tried using the sqlCommand object's (BeginExecuteNonQuery()) method
but it requires the ENdExecuteNonQuery() method before it completes and
allows the code to continue forward.
What alternative solutions and/or answers to this question can be utilized?
Thanks in advance!