Page History
...
- Heavily Accessed Object
- Heavy Operators
- Missing Indexes
- Missing Statistics
- Table Schema Change May Increase Its Accessing Time
- Object Is Not Scalable
- Table Growth May Increase Its Accessing Time
- Increase in Resource Consumption
- Locked Object
- Index Overhead
- High Amount of Index Scans
- High Amount of Table Lookups
- High Amount of Unused Heap Pages
| Anchor | ||||
|---|---|---|---|---|
|
...
■ Use the What if feature in the Recommend tab to evaluate which statements were affected, based on a large set of statements that were active during the selected time frame. This feature lets you check whether it is possible to improve performance by creating one or several indexes.
| Anchor | ||||
|---|---|---|---|---|
|
The Missing Statistics warning was issued by the SQL Server optimizer when the access plan was created. This means that the SQL Server optimizer recommends creating and updating the statistics on the object. Detailed information on missing statistics for this object can be found in the Recommend tab in the Object tab.
...
Once statistics are collected, remember that statistics should be periodically maintained.
| Anchor | ||||
|---|---|---|---|---|
|
The total In MS-SQL time of the object increased after changes were made to the schema.
...
■ Examine the change, when it was made, the performance changes related to the change, and identify any other changes in the object that may result from the change.
| Anchor | ||||
|---|---|---|---|---|
|
The total In MS-SQL contribution of the object increased when the number of statements executions changed.
...
■ Identify major users by associating to users or machines in the Association. Determine if this is acceptable for your system based on your knowledge of your system.
| Anchor | ||||
|---|---|---|---|---|
|
The total In MS-SQL time of the object increased following a major change in the table size.
...
Try to identify the heaviest statements and tune them.
| Anchor | ||||
|---|---|---|---|---|
|
The total In MS-SQL time of the object has increased.
...
Advice The average In MS-SQL time of the object has increased but not as a result of major table growth, scalability change or schema changes. A major change can result from a change in execution plan. Examine the table details and the statement accessing it and try to identify what caused the change. Compare explain plans using the Compare tab.
| Anchor | ||||
|---|---|---|---|---|
|
Much of the In MS-SQL time was spent waiting for a lock on the table.
...
Advice Identify the blocker session in the Activity tab and examine the application and application timing. Examine the lock chain to identify the statement holding the lock.
| Anchor | ||||
|---|---|---|---|---|
|
Most of the activity on the index is due to the fetching of index pages from the disk, reflecting changes made by
...
■ If the index is not used in execution plans consider dropping the index or unused columns from the index, to reduce index overhead. If the index is used in execution plans, launch to the What-If tab to see which statements may be effected by this change.
| Anchor | ||
|---|---|---|
|
...
|
The index is mainly used for scans and not for seeks which is the recommended method.
...
■ Use the What If feature in the Recommend tab to evaluate which statements or batches were affected, based on a large set of statements or batches that were active during the selected time frame. This feature lets you check whether it is possible to improve performance by creating one or several indexes.
| Anchor | ||||
|---|---|---|---|---|
|
The table has a high amount of lookups which can cause excessive I/O wait.
...
■ Use the What If feature in the Recommend tab to evaluate which statements or batches were affected, based on a large set of statements or batches that were active during the selected time frame. This feature lets you check whether it is possible to improve performance by creating one or several indexes.
| Anchor | ||||
|---|---|---|---|---|
|
SQL Server reads a high amount of unused Heap Pages, which can lead to unnecessary I/O Wait.
...