SQL statements are classified as Problematic SQL if they meet any one of the following requirements:
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.
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.
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.
Specify that SQL statements involving the number of worktables greater than or equal to the defined number are classified as Problematic SQL statements.
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center