PearlJammer1 (5/14/2013)
Grant,The query with the largest numbers against it is the second one in the list:
INSERT INTO @MemStat
EXEC ('DBCC memorystatus() WITH tableresults');
From query plan: 0x06000100e090292b40e18282000000000000000000000000
*****************************************************************
Thje metrics are:
execution count = 4, duration(ms) = 401, cpu time(ms) = 399, physical reads = 0, logical reads = 1858, logical writes = 0
These are the metrics next to the tsql text - do i need to look at anything else ?
Accumulated execution time then is 400ms or less than 1/2 of 1 second. I suspect pretty strongly that this can't be the problem. You probably need to explore forward or backward in time to see what else is going on. I'd be seriously shocked if a query taking 100ms is hurting your server.
"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