March 7, 2010 at 8:13 pm
Hi,
We've got a Control-M job which runs an IS package, which times out if one of the queries takes longer then 30 seconds. It does not look like SQL Server timeout.
Any ideas where this timeout setting comes from?
Thanks.
March 8, 2010 at 7:32 pm
Have you tried running the package interactively in BIDs?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
March 9, 2010 at 6:15 am
Isn't 30 seconds the default time out interval for a Command object execution in .NET languages?
Just a thought.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
March 9, 2010 at 6:53 am
Yes Paul you are correct. Thank you for correcting me.
The default is 30 seconds.
If you set the default value to 0 it will run indefinitely.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply