If I narrow down "Workload" to just CPU or memory under History, only one TSQL Batch is listed.
Having disk subsystem (SAN) upgrade issues that drove IO wait to intolerable levels
When the TSQL Batches dimension is selected and the Resource is set to Workload, the Resource Breakdown shows mainly I/O wait and Log wait with some Latch wait. The main resource wait associated with TSQL Batches during the selected time inverval is I/O wait (not CPU) which is why only one TSQL Batch is listed (screenshot attached)
When the Resource is change from Workload to just CPU, only one TSQL Batch is listed because CPU usage is negligible during the selected time range.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center