SQL TIME
Hello
I need help on the below mentioned issue .
" Executed SQL statement: INSERT INTO fact_RADCOM_Report([Key_Measuring Probe], Key_service, [SRC Alias], [DST Alias], concatenate, [probe/service], Seconds, [PESQ Score - In MOS], [PESQ - LQ - In MOS], [Round Trip Delay mSec ], [Signal Level - In dBov], [Background Noise...
Error Source: .Net SqlClient Data Provider
Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. "
Regards
Puneet- Moved byBob BeaucheminMVP, AnswererTuesday, November 03, 2009 9:25 PMMoved to a more appropriate group (From:.NET Framework inside SQL Server)
Answers
- This is a command timeout issue, basically SQL Server took too long to execute the requested SQL. This is one of the more "mystical" parts of client/server programming. You can update the timeout to be longer (or infinite) which means that it takes longer for the client to realize that the server is unavailable -- or you can look into improving performance on the server. It depends on the task and importance of the operation. Many times, people add in retry logic in case this happens to account for possible server failures.
SqlCommand.CommandTimeout property is what you are looking for.
http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.commandtimeout(VS.80).aspx
Hope that helps,
John
This post is provided 'as is' and confers no express or implied warranties or rights.- Marked As Answer byJohn C GordonMSFT, ModeratorTuesday, November 03, 2009 9:39 PM
All Replies
- This is a command timeout issue, basically SQL Server took too long to execute the requested SQL. This is one of the more "mystical" parts of client/server programming. You can update the timeout to be longer (or infinite) which means that it takes longer for the client to realize that the server is unavailable -- or you can look into improving performance on the server. It depends on the task and importance of the operation. Many times, people add in retry logic in case this happens to account for possible server failures.
SqlCommand.CommandTimeout property is what you are looking for.
http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlcommand.commandtimeout(VS.80).aspx
Hope that helps,
John
This post is provided 'as is' and confers no express or implied warranties or rights.- Marked As Answer byJohn C GordonMSFT, ModeratorTuesday, November 03, 2009 9:39 PM
