January 23, 2013 at 3:57 pm
Hi
We have simple Adhoc queries running from an application.
The query runs for hours and gets timed out.
At the same time I could see from Activity Monitor that it uses multiple threads.
I even changed the Arithmetic Abort Enabled to True for the database but still its running for hours.
The same query when run in SSMS finishes within 5-10 mintues and also uses only one thread.
I am pretty confused on fixing this behaviour.
Any insight would be helpful.
Thanks.
January 23, 2013 at 5:21 pm
Abdul Rahman (1/23/2013)
HiWe have simple Adhoc queries running from an application.
The query runs for hours and gets timed out.
At the same time I could see from Activity Monitor that it uses multiple threads.
That by itself isn't necessarily an issue. What wait types did you have besides CXPacket?
I even changed the Arithmetic Abort Enabled to True for the database but still its running for hours.
What did you hope to accomplish with that choice? Not being rude, we just don't know what you're seeing that you thought it would affect it.
The same query when run in SSMS finishes within 5-10 mintues and also uses only one thread.
This is telling. First, I'd check on all the settings that the connection is using vs. the ones you default to for SSMS. Connections also default setings, like SET ANSI_NULL on, things like that. This may help you locate part of your issue.
Secondly, I'd confirm that it's the EXACT same query by using profiler and trapping the query on its way in from the application. Very minor differences can make a huge difference. It's also an easy way to tell the set statements the connection will force during a connection.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
January 23, 2013 at 5:49 pm
The wait types are CXPacket only.
I found online that having Arithabort ON could resolve this issue and tried that.
I did ran Profiler and yes it is the same query, which we had to kill as it was running forever.
It's also an easy way to tell the set statements the connection will force during a connection.
I am not sure on where to check this on the connection ?
The query is being generated by the Application and we cannot add any SET commands to it.
January 23, 2013 at 10:18 pm
I also sense the difference in settings between SSMS and the Application Server.
I will have to check it on the Application Server.
But I am not able to understand why the same query is using so many threads when executed using the application and only a single thread when executed through SSMS ?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply