Hi all.
I just run the get_waitstats_2005 SP against my database.
Here are the top rows from the output.
Could you please help me interpreting this output ?
thank you,
mario
wait_type
waiting_tasks_count Resource wt (T1-T0) res_wt_%
Signal wt (T2-T1) sig_wt_% Total wt
(T2-T0) wt_%
------------------------------------------------------------
-------------------- --------------------
--------------------------------------- --------------------
--------------------------------------- --------------------
---------------------------------------
***total*** 0
22205791 100.0 690309
100.0 22896100 100.0
LCK_M_U 25982
11947062 53.8 7531
1.1 11954593 52.2
LATCH_EX 1405393
7705063 34.7 525921
76.2 8230984 35.9
CXPACKET 89442
2269953 10.2 36828
5.3 2306781 10.1
1) Get this word document from microsoft.com: SQL Server 2005 Waits and
Queues
2) There are quite a few signal waits, indicating CPU overload.
3) lck_m_u indicates update lock blocking. Likely due to missing indexes
and locks being taken on a table instead of an index seek.
4) latch_ex can be from a variety of causes. Best would be to get an expert
in to review the system.
5) cxpacket is waits due to parallelism. Again a variety of causes.
Missing indexes could be at play here, as could poor statistics or simply a
lot of data.

Signature
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
> Hi all.
> I just run the get_waitstats_2005 SP against my database.
[quoted text clipped - 25 lines]
> 2269953 10.2 36828
> 5.3 2306781 10.1