J
jfer
Hi everyone, I'm creating a ASP.NET 2.0 web application utilizing sql
server 2000 as a database. My problem revolves around multiuser acces
with long running processes.
Some of the pages in the application have
long running processes against large tables in the database, lets say
that take 5minutes to complete. My problem is how do I utilize ado.net
properly in the rest of my application to display a message to users
who may try to access data associated with a table while in the midst
of one of its long running processes? For instance I would like to
notify the user that "Table X is currently locked, please try again in
a few minutes".
Do I catch sqlException and examine the .Number property? Any insight
is appreciated.
Thanks.
server 2000 as a database. My problem revolves around multiuser acces
with long running processes.
Some of the pages in the application have
long running processes against large tables in the database, lets say
that take 5minutes to complete. My problem is how do I utilize ado.net
properly in the rest of my application to display a message to users
who may try to access data associated with a table while in the midst
of one of its long running processes? For instance I would like to
notify the user that "Table X is currently locked, please try again in
a few minutes".
Do I catch sqlException and examine the .Number property? Any insight
is appreciated.
Thanks.