Page History
...
- Heavy Statement
- Heavy Collapsed Statement
- Major Statement in Batch
- Heavy Operators
- Missing Indexes
- Missing Statistics
- Table Schema Change May Increase Its Accessing Time
- Statement Is Not Scalable
- Table Growth May Increase Its Accessing Time
- Increase in Resource Consumption
- Statement or Batch Was Locked
- Statement Activity Consistently High
...
Table 13-7 Table Schema Change May Increase Its Accessing Time findings
| Column |
|---|
...
| Description |
|---|
| What to do |
...
| next | In the SQL tab, examine the information displayed in the History tab to identify object changes and correlate these changes to performance degradation. |
Column Description
...
| Advice | Several changes may effect In MS-SQL time and may effect other statements In MS-SQL as well. Changes such as index creation/drop can cause access plan changes that can effect statement performance. Do the following: |
...
|
...
|
| Anchor | ||
|---|---|---|
|
...
|
Statement resource consumption was increased by n% as a result of an increase in its executions.
Table 13-8 Statement 8 Statement Is Not Scalable findings
| Column |
|---|
...
| Description |
|---|
| What to do |
...
| next | Perform one of the following options: |
...
|
...
|
...
|
| Advice |
...
Perform the following options: |
...
|
...
|
...
|
...
|
...
Table Growth May Increase Its Accessing Time
...