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 |
|
healthhavencom
Starting Member
1 Post |
 Posted - 2008-04-01 : 14:26:20
|
| of query timeouts in SQL Server Management Studio?I have increased the timeout setting in many places and still receive a timeout message within 40 seconds for certain update queries that involve large tables and many records. The only workaround is to break up the job into smaller queries but this makes management, unmanageable.Is there a solid alternative to SQL Server Management Studio? |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-04-01 : 14:41:13
|
| Make your query timeout infinite by 0 |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-01 : 15:07:17
|
quote:
Originally posted by sodeep
Make your query timeout infinite by 0
That is terrible advice.healthhavencom, post the queries that are timing out plus the CREATE TABLE statements and indexes for those tables.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2008-04-01 : 15:52:07
|
| IMO - I only think that is terrible advice in certain contexts.If you expect to have long running processes running based on rollups, maintanence, and other non user application based calls then I think an unlimited timeout for "server execution timeout" is fine.healthhavencom, when you say, "I have increased the timeout setting in many places" what places specifically? Are these queries launched from a query window or from an application?Be One with the OptimizerTG |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-01 : 16:29:24
|
| Timeout values should not be changed until all other avenues have been exhausted, otherwise you are only masking the problem.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2008-04-01 : 16:59:44
|
| I totally agree about the importance of optimization and how problems can be masked. I'm curious though, Tara, do you have "execution timeout" set to > 0 on any of your db servers? We maintain timeout durations at the application/webservice level via connection and command timeouts.I assumed the OP was timing out in a query window in Management Studio.Be One with the OptimizerTG |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-01 : 17:09:04
|
| We do not have any timeouts set to 0 in production. In fact we have alerts that fire from MOM to notify us if any queries go over a certain threshold so that we can be proactive with performance issues.If SSMS is left at the default, then it wouldn't be timing out, so that's why I thought the issue was elsewhere.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
|
|
Timeouts: What are all of the possible causes