Versions Compared

Key

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

...

Holds statements collected by the Precise for SQL Server collector and statements inserted through the statement workshop (SQL workspace). The table holds one row per statement and connects it to the first batch in which the statement was sampled. You can join the statement with other batches run, but only for statistics tables. (PW_SQST_STATEMENTS_STATS or PW_STSE_SESS_STATEMENTS_STATS).

Column NameColumn Description
SQSM_PWII_INSTANCE_IDID of the SQL Server instance.
SQSM_STATEMENT_HVUnique identifier (number) assigned to the statement.
SQSM_STATEMENT_IDUnique identifier (string) assigned to the statement.
SQSM_COLLAPSED_STATEMENT_HVUnique identifier (number) assigned to the statement in its collapsed form.
SQSM_COLLAPSED_STATEMENT_IDUnique identifier (string) assigned to the statement in its collapsed form.
SQSM_INSERT_TIMEDate and time the statement was saved in the database.
SQSM_PARSING_USEROne of the SQL Server users who executed this statement. If this statement is not part of a stored procedure, this is the user used as the parsing user when explaining this batch.
SQSM_PARSING_USER_IDOne of the SQL Server users who executed this statement. If this statement is not part of a stored procedure, this is the user used as the parsing user when explaining this batch, normalized in table PW_SQUN_USE_NAMES_N.
SQSM_WORKSHOP_HVUnique identifier (Number) assigned to statements inserted in the SQL workspace.
SQSM_SOURCE

Indicates how the statement was loaded. Possible values:

  • PMDB. Sampled and loaded by the Collector.
  • Manually. Entered through the statement workshop (SQL workspace).
  • Saved automatically. Explained from the Current workspace or Activity workspace.
SQSM_LAST_EXPLAINEDLast time the statement was explained.
SQSM_TOTAL_MSSQL_TIMENot in use.
SQSM_DO_NOT_EXPLAIN

Indicates an error during the explain of the statement. If Y, do not try to re-explain.

SQSM_EXPLAIN_ERROR_MSGError that occurred during the last explain process.
SQSM_LAST_ACC_PATH_CHANGEDLast time the access plan of the statement changed.
SQSM_ACCESS_PATH_HVUnique identifier (number) assigned to the access plan of the statement.
SQSM_TOTAL_ESTIMATED_COSTEstimated cost of the statement’s execution. A high cost value may indicate a problem in the current implementation of the statement. To determine which operation may have caused the problem, you can use the Estimated Cost Breakdown graph to drill down easily and see the most resource consuming operation. To determine whether the operation is an I/O consuming operation or a CPU consuming operation (or both), check the Estimated I/O cost and Estimated CPU cost values.
SQSM_DATABASE_NAMEName of the database to which the statement belongs.
SQSM_DATABASE_IDID of the database, in which the statement belongs, normalized in table PW_SQDN_DATABASE_NAMES_N.
SQSM_BATCH_HVUnique identifier (number) assigned to the batch. Only the first batch appears.
SQSM_COLLAPSED_BATCH_HVUnique identifier (number) assigned to the batch. Only the first batch appears.
SQSM_STATEMENT_OFFSETThe offset of the statement in the first batch sampled, running the statement by the Collector agent.
SQSM_STATEMENT_LENGTHLength of the statement in the first batch sampled running the statement.
SQSM_STATEMENT_ID_IN_BATCHStatement number in the first batch sampled running the statement.
SQSM_START_EXEC_ORDER_IN_BATCHExecution order the statement started with in the access plan of the batch.
SQSM_START_TREE_LEVELStart level of the statement in the access plan of the batch.
SQSM_EXPLAIN_USAGE_MAPInternal bit representative of the types of the operators in the execution plan.
SQSM_ACTUAL_PLAN_INDMS-SQL 2005 only. Indication if the last execution plan of the statement is Actual or estimate.
SQSM_MISS_INDEXES_IMPACTMS-SQL 2005 only. Indication if the last execution plan of the statement has missing indexes indication.
SQSM_STATEMENT_TYPERepresenting the type of the statement. Such as INSERT and SELECT.

PW_SQBA_BATCHES

Holds information on batches.

Column NameColumn Description
SQBA_PWII_INSTANCE_IDID of the SQL Server instance.
SQBA_BATCH_HVUnique identifier (number) assigned to the batch.
SQBA_COLLAPSED_BATCH_HVUnique identifier (number) assigned to the batch in its collapsed form.
SQBA_PARSING_USEROne of the SQL Server users who executed this batch. If this batch is a stored procedure, this is the user used as the parsing user when explaining this batch.
SQBA_PARSING_USER_IDOne of the SQL Server users who executed this batch. If this batch is a stored procedure, this is the user used as the parsing user when explaining this batch, normalized in table PW_SQUN_USER_NAMES_N.
SQBA_DATABASE_NAMEName of the database to which the batch belongs.
SQBA_DATABASE_IDThe ID of the database, to which the batch belongs, normalized in table PW_SQDN_DATABASE_NAMES_N.
SQBA_BATCH_IDUnique identifier (string) assigned to the batch.
SQBA_COLLAPSED_BATCH_IDUnique identifier (string) assigned to the batch in its collapsed form.
SQBA_LAST_EXPLAINEDLast time the statement was explained.
SQBA_DO_NOT_EXPLAINIndicates an error during the explain of the statement. If Y, do not try to re-explain.
SQBA_EXPLAIN_ERROR_MSGError that occurred during the last explain process.
SQBA_LAST_ACC_PATH_CHANGEDLast time the access plan of the batch changed.
SQBA_ACCESS_PATH_HVUnique identifier (number) assigned to the access plan.
SQBA_TOTAL_ESTIMATED_COSTEstimated cost of the statement’s execution. A high cost value may indicate a problem in the current implementation of the statement. To determine which operation may have caused the problem, you can use the Estimated Cost Breakdown graph to drill down easily and see the most resource consuming operation. To determine whether the operation is an I/O consuming operation or a CPU consuming operation (or both), check the Estimated I/O cost and Estimated CPU cost values.
SQBA_PROC_DB_IDID of the database that holds the stored procedure.
SQBA_PROC_OBJECT_IDID of the stored procedure.
SQBA_EXPLAIN_USAGE_MAPInternal bit representative of the types of the operators in the execution plan.
SQBA_ACTUAL_PLAN_INDMS-SQL 2005 only. Indication if the last execution plan of the batch is Actual or estimate.
SQBA_MISS_INDEXES_IMPACTMS-SQL 2005 only. Indication if the last execution plan of the batch has missing indexes indication.
SQBA_DOTNET_HVUsed for correlation between Precise for Microsoft .NET and Precise for MS SQL Server.
SQBA_MIGRATEDData migration process only. Used to update several columns and distinguish between new batches and previous batches.
SQBA_CONSISTENT_HVUsed for correlation between all the other products and Precise for MS SQL Server.




Scroll Ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/precise/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 
|
 
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse