Problematic SQL
View SQL Classification-Problematic page
SQL statements are classified as Problematic SQL if they meet any one of the following requirements:
Number of table operations greater than (Default = 3)
Read-only field indicating the number of table operations references in the query plan. If the total number of table operation is greater than this value, then this SQL statement is classified as Problematic. This value is the same as the upper limit of the Complex table operations range.
With full table scan
Specify that SQL statements with full table scan are classified as Problematic SQL statements. This classification depends upon the size of the table or the number of row.
Table size (KBytes): (Default = 16, Range= 8 to 9,999,996)
Number of rows: (Default = 1000)
In the case of a temporary table where the size is unknown when the query plan is retrieved, any full table scan will be classified as problematic.
Note: Table size is calculated using sp_spaceused.
You can specify to include or exclude inserted or deleted simulation temp table created in the SQL Scanner Trigger Conversion by using the Including inserted simulation temp table and Including deleted simulation temp table checkboxes.
With full table scan iterated by nested loop
Specify whether SQL statements with a full table scan inside a nested loop are classified as Problematic SQL statements. This classification depends upon the size of the table or the number of row.
Table size (KBytes): (Default = 16, Range= 8 to 9,999,996)
Number of rows: (Default = 1000)
You can specify to include or exclude inserted or deleted simulation temp table created in the SQL Scanner Trigger Conversion by using the Including inserted simulation temp table and Including deleted simulation temp table checkboxes.
With number of worktables greater than or equal to (Default = 1, Range = 1 to 99)
Specify that SQL statements involving the number of worktables greater than or equal to the defined number are classified as Problematic SQL statements.
With number of Reformattings greater than or equal to (Default = 1, Range = 1 to 99)
Specify that SQL statements whose query plan uses reformatting are classified as Problematic SQL. Reformatting is the process of generating a worktable with a clustered index and performing a nested-loop join. The Adaptive Server optimizer may choose this strategy when the table is large and does not have any useful index for a join.
Complex SQL
SQL statements are classified as Complex SQL if they meet any one of the following requirements and do not meet any requirement for being a Problematic SQL statement:
Number of table operations (Default = 2 /3, Range 2 to 99)
Specify the number of table references in the query plan for Complex SQL statements. Checkboxes are available to indicate whether you want the inserted and deleted simulated temp tables to be included in this table range.
You can specify to include or exclude inserted and deleted simulation temporary tables created in the SQL Scanner Trigger Conversion by using the Including inserted simulation temp table and Including deleted simulation temp table checkboxes.
With full index scan (Default = checked)
Specify whether SQL statements with full index scan are classified as Complex SQL statements.
Simple SQL
SQL statements are classified as Simple SQL if they meet the following requirement and do not meet any requirement for being a Problematic SQL statement or a Complex SQL statement:
Number of table operations less than (Default = 2)
Read-only field indicating the number of table operations references in the query plan. If the total number of table operation is less than this value, then this SQL statement is classified as Simple. This value is the same as the lower limit of the Complex table operations range.
Invalid SQL
In some cases the scanned SQL statements are classified as invalid. They may fall into one of the following:
No privilege to tables or views
The logon user does not have privilege to the tables or views referenced even though the syntax of the SQL statement is correct.
Using the wrong database or user
You can declare the database and user used to scan for SQL statements. If these do not match with the SQL statement, it may be classified as invalid.
Dynamic SQL statements
The SQL Scanner is unable to identify SQL statements that are dynamically created if the text of the SQL statement is not all on one command line.