Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You decide how many top statements to display. The following types of findings on table shows the statement behavior are displayed:

...

displayed on findings.

Table 12-6 Statement behavior displayed on findings

StatementDescription

...

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.

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.

Heavy Operators

The statement or batch has an operator that accesses the object and shows a high cost percentage.

Missing Indexes

During SQL Server optimization, missing indexes were identified for one or more statements or batch. This means there can be one or more indexes, but they are not used because of a mismatch of column types. The SQL Server optimizer recommended creating indexes to improve the performance of the statement or batch. Detailed information regarding the index recommendation for this statement or batch can be found in the Recommend tab of the SQL tab.

Missing Statistics

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 objects accessed by a specific statement or batch. Detailed information on missing statistics for this statement or batch can be found in the Recommend tab in the SQL tab.

Table Schema Change May Increase Its Accessing Time

The average In MS-SQL time increased after an object change. Check the changes and how they affected the statement or batch execution time.

Statement Is Not Scalable

Statement resource consumption was increased by n% as a result of an increase in its executions.

Table Growth May Increase Its Accessing Time

The average In MS-SQL time of the statement increased following a major change in table size.

Increase

...

In Resource Consumption

The SQL Server resources consumed by the statement increased by

...

n%.

Statement Was Locked

Much of the statement or batch time was spent waiting for a lock. Regular locks can be categorized as follows:

  • During the blocker session, a locked statement or batch ran for a short period of time. Afterwards the session was idle or continued running other statements or batches. In this case, it is possible to identify the blocker session, but not necessarily the blocker statement or batch.
  • During the blocker session, a locked statement or batch ran for a long period of time. Identifying the blocker statement or batch is easier in this case.
Statement Activity Consistently High

Total In MS-SQL time of the statement was consistently high and reached the thresholds of the top statements.

About Collapsed Statement

...

Findings

A collapsed statement includes several statements that use the same text, but not the same constants.

Heavy Collapsed Statement

A set of collapsed statements constitute a major consumer of MS-SQL resources.

Statement Is Not Scalable

Statement resource consumption was increased by n% as a result of an increase in its executions.

About Object findings

Object findings are checked for top objects.

...

  • 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

Heavily Accessed Object

Object is a major consumer of MS-SQL resources. By tuning the object, you can free resources needed by other statements and processes.

Heavy Operators

One or more statements access this object using heavy operators. Statement has major access plan operators for this object that scan a great deal of data and show a high cost percentage.

...