October 13, 2015 at 10:06 am
Hi All.
I am facing a database slowness/hangs in my production environment.Last 10 days I got 3 calls from users complaining about performance(application running very slow or hanging). Once user logs in and app fires up first select statement(very simple statements) it hangs.Not always.As i said we had 3 occurrences in 10 days.Could not find anything in SQl Server Error log or Windows Event Log.App runs on different box.So i searched for solution and decided to run profiler to capture the cause. Once I run a trace in our DEV box and got calls from developers about system performance.So i turned if off.Events that selected are:
RCP:Completed
SP:StmtCompleted
SQL:BatchCompleted
SQL:StmtCompleted
and i selected 'Save to table' option.
We have SQl server 2008 R2 STD edition,32GB ram
Now i have 2 question.
1.Why is app hanging and how to solve this problem
2.Why is Profiler drags performance down.
Thank you
October 13, 2015 at 10:14 am
For one thing, "save to table" is a lot of overhead. Save it to file(s) instead, then load the file(s) into tables later to analyze.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
October 13, 2015 at 10:30 am
use a server side trace and save to file.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply