I have a stored proc that runs and calls others and sometimes the
process runs for 3 to 5 minutes depending on traffic. ASP.NET -
ADO.NET - Sql 2000
Code -
dim cmdV as sqlcommand = new
sqlcommand("ValidateUpdatePrograms",cnOAP)
cnoAP.Open()
cmdV.ExecuteNonQuery()
cmdV = nothing
cnoap.Close()
Does the CommandTimeout property refer to the time to wait until a
command starts processing or does it refer to how long a command can
process before it is considered overdue? If it is the second case
will sql actually stop in the middle of processing?
Currently I am getting Application Unavailable in the browser after
the Machine.config setting responseDeadlockInterval has been exceeded.
I will set this higher. But I am wondering if sql is still processing
and the web server times out, will sql continue processing until it is
done? I have tested and it seems like it does. It seems like it will
also stick with the command until it is done no mater how long it
takes. I have not set the CommandTimeout. I am trying to figure out
how to make sure sql doesn't stop.
Thanks!