Page History

...

Column	Description
	Click to launch the SQL tab with the selected entity, to continue your analysis of the selected statement or batch.
Entity Name (such as Statement)	Displays the name of the entity.
CPU Time	Cumulative CPU time for the entity during the selected time period.
Physical I/O Operations	Total number of physical I/O requests performed by the selected entity during the selected time period.
Parallel Sessions (Min)	Minimum number of threads used to execute the statement or batch in parallel. This counter is calculated from the ecid column in sysprocesses. This enables you to verify that SQL Server is using the best execution plan for the current statement.
Parallel Sessions (Max)	Maximum number of threads used to execute the statement or batch in parallel. This counter is calculated from the <command>ecid</command> ecid column in sysprocesses. This enables you to verify that SQL Server is using the best execution plan for the current statement.

...

...

About the lock tree structure

...

1. In the Instance list, choose the item you want to analyze.
2. In the Time Frame list, choose the period of time you want to analyze.
3. On the View controls in the Main area, click Overview. Examine the entire instance and determine which are the dominant resources that are consumed by your system.
4. On the Association controls in the Association area, click Databases.
5. On the Performance tab, place the cursor in the In MS-SQL column of the top database and view the information displayed on its resource consumption.

...

Anchor
Identifyingheavyresourceconsumers Identifyingheavyresourceconsumers

Identifying heavy resource consumers

...

1. In the Instance list, choose the item you want to analyze.
2. In the Time Frame list, choose the period of time you want to analyze.

3. On the View controls in the Main area, click In MS-SQL to view a breakdown of the In MS-SQL time.

   Note:

   Info

   One of the components of In MS-SQL time that you can observe in the In MS-SQL graph is Internal Wait. You can view additional information on that particular component, over the selected time frame, by clicking Internal Waits on the View controls in the Main area. This view lets you analyze a breakdown of the Internal Wait parameter and determine which internal wait parameter is consuming the most time and resources.

4. On the Association controls in the Association area, click Programs.
5. On the Performance tab, place the cursor in the In MS-SQL column of the top program entity and view the information displayed regarding its resource consumption.
6. Drill down on the entity to focus on additional components.
7. Go back to the overview of the instance you originally selected.
8. In the Association area, use the Association controls to select different entities associated with the instance, and analyze the average duration of each entity.

...

1. In the Instance list, choose the item you want to analyze.
2. In the Time Frame list, choose the period of time you want to analyze.
3. On the View controls in the Main area, click In MS-SQL.
4. Move the cursor over the bars in the graph to view the instance's resource consumption over time.

...

1. In the Instance list, choose the item you want to analyze.
2. In the Time Frame list, choose the period of time you want to analyze.
3. On the View controls in the Main area, click In MS-SQL.
4. On the Association controls in the Association area, click Storage Devices.
5. Observe the I/O waits for each storage device unit.
6. If you locate storage devices suffering from I/O waits, you can check which logical files reside on the storage device and move a few to a different storage device. Drill down from the storage device and analyze the Logical Files entities. Once you have identified which logical file(s) should be moved to a different storage device, check the I/O pattern on that storage device, to ensure that the move will not cause the I/O pattern on the new storage device to deteriorate.

...

1. In the Instance list, choose the item you want to analyze.
2. In the Time Frame list, choose the period of time you want to analyze.
3. On the View controls in the Main area, click Scalability.
4. In the Session Duration (Avg) vs. Sessions graph, observe the number of sessions and the impact of the average session duration, over the selected time period. For example, if you observe that average session duration increases when the number of sessions decrease, this may indicate that the application has a scalability problem.
5. On the View controls in the Main area, click System  System Scalability.
6. Analyze the In MS-SQL vs. SQL Server CPU usage graph to determine if SQL Server CPU consumption growth affects the server CPU consumption and I/O wait times. Check the Physical I/O Operations vs. Queue Length graph to determine if a growth in I/O requests increases the time I/Os have to wait in the queue to be served.

...