December 18, 2008 at 5:31 pm
Hi Folks,
what are the ramifications of changing the remote query timeout server option? I have got a timeout error in sql server for a large report and I believe there are no locks that are causing this.
December 18, 2008 at 6:51 pm
The standard answer is "That depends". I believe the default value for a remote query timeout is 600 seconds.. heck that is enough time to take a coffee break and then some.
Might I suggest you post the T-SQL code here and maybe recieve some help in optimizing the code so it runs quicker.
December 19, 2008 at 6:10 am
Or at least post the execution plan.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 21, 2008 at 8:39 pm
High Folks,
My timeout was not a sql timeout apparently. It was an application timeout. The default ADO execution timeout is 30 seconds which was why I was getting errors.
thanks
December 22, 2008 at 12:29 am
30 sec is still a long time for a query to run, unless it's some massive report. I don't know many users who will be happy waiting 30 sec or so to get their data back.
We can probably help you optimise it, if you want.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 23, 2008 at 5:28 pm
the execution plan is massive.. how can I send it on the list?
December 23, 2008 at 11:43 pm
Save as a .sqlplan file, zip and attach to the post.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply