Re: application slow
- From: "kumar" <srimkumarp@xxxxxxxxx>
- Date: Thu, 30 Apr 2009 12:45:34 +0530
Hi,
Today we had restarted the both application server and sql server, but
problem still continuing...please suggest where i need to check..
"kumar" <srimkumarp@xxxxxxxxx> wrote in message
news:OCU1jqKyJHA.2656@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
i've downloaded clear trace and checked. it shows the output.please do the
needfull....
ITEM # cpu reads writes duration
.Net SqlClient Data Provider 249 3,250 244,220 27 4,004,889
Internet Information Services 364 1,534 109,515 51 1,836,676
Microsoft SQL Server Management Studio - Query 4 47 214 0 43,537
Microsoft SQL Server Management Studio 26 31 670 0 117,627
SQLAgent - Alert Engine 2 0 2 0 1,008
in my application server the performance counter is not working.instead of
showing couter name it is showing as numbers.
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uFfYfmGyJHA.3872@xxxxxxxxxxxxxxxxxxxxxxx
I find it odd that no queries are running over a second yet user
experience unusual slowness, including timeouts. Does performance monitor
indicate any spike in activity (CPU, disk I/O) during the problem period?
Could the cause be external to SQL Server?
You might try the same trace without a filter during the problem period
to see if you can spot unusual activity. The ClearTrace John mentioned
ought to help categorize frequently run queries below the duration
threshold of the filtered trace. The fact that the problem occurs
predictably seems to indicate a scheduled process, though.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"kumar" <srimkumarp@xxxxxxxxx> wrote in message
news:%234X0ytAyJHA.1712@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I've ran the SQL Trace for long running queries-1000 milli seconds.
No queries are taking this much time...
thanks, kumar...
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23gDgrk$xJHA.5156@xxxxxxxxxxxxxxxxxxxxxxx
I suggest you run a SQL Trace of batch and rpc completed events and
include a duration filter to include only long-running queries(e.g.
1000000 microseconds). Perhaps this will provide a clue as to the
activity that is the root cause of the slowness.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"kumar" <srimkumarp@xxxxxxxxx> wrote in message
news:OTywNJ8xJHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
We are facing application slowness daily morning 11 am.Even saturday
and sunday also.
for backend we are using sql server 2005 running on win 2003.
i have traced from all sides like i've run the profilers and every
month i've updated the stats and index rebuild,reindexes also doing.
Still problem continuous can any one please let me know where i have
to check.
thanks, kumar
.
- Prev by Date: Re: Mmanaging a transaction table with 50,000+ records / hr
- Next by Date: RE: Alias best way in SQL Server
- Previous by thread: SAN
- Next by thread: Re: application slow
- Index(es):
Relevant Pages
|