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 |
|
jag_chat
Starting Member
3 Posts |
 Posted - 2004-01-28 : 21:36:29
|
| I wrote a stored procedure...and executed in Query Analyser.It took 40min to execute....ofcourse...it is something like archieving database of millions of rows along with distributed queries....I am quite ok with the stored procedure.....(even time taking)...But, then I executed the same stored procedure in my program using the command object which within less than a min...I am returned with the following error:TIMEOUT EXPIRED. THE TIMEOUT PERIOD ELAPSED PRIOR TO COMPLETION OF THE OPERATION OR THE SERVER IS NOT RESPONDING.I think the connection could not sustain till the completion of store procedure.Can any one help me how to execute through UI. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-01-28 : 23:45:35
|
| The reason is because the ADO objects default to a 30 second command timeout, any command that takes longer will terminate the connection and the command.You are far better off NOT running this procedure through an ADO Command object. Instead, you should create a job that runs this procedure and use the Command object to call sp_start_job to run the job. Anything that takes that long should not be dependent on interaction from another tier. |
 |
|
|
|
|
|
Timeout expired