Page History
This section includes the following topics:
...
...
...
...
...
...
...
...
...
| Anchor |
|---|
...
|
...
|
The Findings view displays recommendations that can be used to create a better execution plan and improve the performance of a statement. The Findings vary according to the type of operation in a statement, the Precise product and the technology.
| Anchor | ||
|---|---|---|
|
...
|
...
The Highlights area displays a brief description of the findings for the selected type of operation.
| Anchor | ||
|---|---|---|
|
...
|
...
The What to do next area displays one or more recommended steps to identify the cause of the problem. Carefully review all data for the finding before continuing.
| Anchor | ||
|---|---|---|
|
...
|
The Advice area displays one or more recommended options to resolve or reduce the problem for the selected finding. Carefully review all data for the finding and then perform the advice that best suits your needs.
| Anchor | ||
|---|---|---|
|
...
|
...
When you start investigating the findings, it is good practice to start with the finding that has the highest severity ranking in the Findings table.
To investigate a finding
...
- Identify the finding with the highest severity ranking in the Findings table.
...
- Select the finding type to view additional information on the selected type of operation.
...
- Read the Highlights and What to do next areas for the finding.
...
- After you have studied all of the information provided, read the Advice area and perform the recommendation that best suits your needs.
...
- Follow up on performance to verify that the problem was resolved.
...
| Anchor | ||
|---|---|---|
|
...
|
The following statement findings can help you tune your system:
...
- 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
...
Heavy Statement
The statement is a major consumer of MS-SQL resources. By tuning the statement, you can free resources needed by other statements and processes.
Table 13-1 Heavy 1 Heavy Statement findings
| Column |
|---|
...
| Description |
|---|
| What to do |
...
| next | Try to determine what is causing the statement’s high resource consumption. In the SQL tab, examine the text of the relevant statement, and its findings, execution plan, change data and statistics. |
| Advice |
...
The following scenarios indicate what factors can lead to heavy resource consumption and what steps you can take: |
...
|
...
|
...
|
...
|
Heavy Collapsed Statement
A collapsed statement includes several statements that use the same text, but not the same constants.
A set of collapsed statements constitute a major consumer of MS-SQL resources. By tuning the set of statements, you can free resources needed by other statements and processes.
Table 13-2 Heavy 2 Heavy collapsed statement findings
| Column |
|---|
...
| Description |
|---|
| What to do |
...
| next | In the SmarTune tab, examine the text of the relevant statements. Check their scalability and associated list of statements. Select the statement you want to analyze, and launch to the SQL tab with the statement in context. Examine its execution plan, change data and statistics to determine what is causing its high resource consumption. |
...
| Advice | The following scenarios indicate what factors can lead to heavy resource consumption and what steps you can take: |
...
|
...
|
...
|
...
|
...
|
...
|
...
Major Statement in Batch
The statement consumed more than 50% of MS-SQL batch resources. By tuning the statement, you can free resources needed by other statements and processes.
...
For example: Consider scheduling different activities that uses the same resource at different times, thereby freeing the resources for the statement.
| Anchor |
|---|
...
|
...
The following object findings can help you tune your system:
...
What to do next ■ Examine the difference between the number of rows and allocated pages and consider rearranging the table by creating a cluster index and then dropping it.
| Anchor | ||||
|---|---|---|---|---|
|
The following instance findings can help you tune your system:
...
■ Examine the overall CPU usage (using Insight OS) to find out if other processes occupy the CPUs.
| Anchor | ||||
|---|---|---|---|---|
|
The following Storage findings can help you tune your system:
...