|
IRISLIB database
|
|
|
IRISLIB database
|
|
<style type="text/css"> .section-head { color: darkblue; white-space: pre; font-family: 'Courier New'; } .info-head { white-space: pre; font-family: 'Courier New'; } DEP { color: red; font-weight: bold; } IMP { color: darkblue; background-color: #D3D3D3; border: 1px solid black; font-size: 1.05em; line-height: 100%; margin-left: 0px; margin-top: 0px; margin-bottom: 0px; padding-bottom: 15px; width: 80%; white-space: pre; display: block; } </style> More...
Static Public Member Functions | |
| _.Library.Status | aggregateSQLStats (ns, rtn, curs) |
| <style type="text/css"> .section-head { color: darkblue; white-space: pre; font-family: 'Courier New'; } .info-head { white-space: pre; font-family: 'Courier New'; } DEP { color: red; font-weight: bold; } IMP { color: darkblue; background-color: #D3D3D3; border: 1px solid black; font-size: 1.05em; line-height: 100%; margin-left: 0px; margin-top: 0px; margin-bottom: 0px; padding-bottom: 15px; width: 80%; white-space: pre; display: block; } </style> More... | |
| _.Library.Integer | clearError (_.Library.String errRowID) |
| Delete 'PTools/SQLStats' Application Error(s) More... | |
| _.Library.Status | clearGeneralStats (_.Library.String ns, _.Library.String rtn, _.Library.Integer ph3, _.Library.Integer clearErrs, _.Library.Integer returnType, _.Library.RawString ptInfo) |
| Delete all of the data stored in the 'SYS.PTools.Stats' class. More... | |
| _.Library.Status | clearSQLAnalysisDB (_.Library.String ns, _.Library.Integer clearErrs, _.Library.Integer returnType, _.Library.RawString ptInfo) |
| Delete all of the SQL Index Usage Analytical data stored in the 'SYS.PTools.UtilSQLAnalysisDB' class. More... | |
| _.Library.Status | clearSQLIndexStats (_.Library.String ns, _.Library.Integer clearErrs, _.Library.Integer silent, _.Library.Integer returnType, _.Library.RawString ptInfo) |
| Delete all of the data stored in the SQL Index/Analysis Stats classes. More... | |
| _.Library.Status | clearSQLStatements (_.Library.String ns, _.Library.Integer clearErrs, _.Library.Integer returnType, _.Library.RawString ptInfo) |
| Delete all of the SQL Statements data stored in the 'SYS.PTools.UtilSQLStatements' class. More... | |
| _.Library.Status | clearSQLStatsALL (_.Library.String ns, _.Library.String rtn, _.Library.Integer ph3, _.Library.Integer clearAll, _.Library.Integer clearSQLIndex, _.Library.Integer clearErrs, _.Library.Integer purgeCQ, _.Library.Integer silent, _.Library.Integer returnType, _.Library.RawString ptInfo) |
| Delete all of the data stored in the SQL Stats classes. More... | |
| _.Library.Status | exportGeneralStats (file, format, silent, statsType, rtnName, modName, _.Library.RawString conds, _.Library.RawString ptInfo) |
| Create a file containing the data from the 'SYS.PTools.Stats' class. More... | |
| _.Library.Status | exportIUAnalysis (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String p4, _.Library.String orderBy, _.Library.RawString conds, _.Library.RawString ptInfo) |
| Export all of the analysis data from the invocation of the 'indexUsage(...)' method. More... | |
| _.Library.Status | exportJIAnalysis (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String type, _.Library.String orderBy, _.Library.RawString conds, _.Library.Integer includeSQL, _.Library.Integer skipJIF4, _.Library.Integer indxFlgInfo, _.Library.RawString ptInfo) |
| Export all of the analysis data from the invocation of the 'joinIndices(...)' method. More... | |
| _.Library.Status | exportOIAnalysis (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String type, _.Library.String orderBy, _.Library.RawString conds, _.Library.Integer includeSQL, _.Library.Integer skipOIF4, _.Library.Integer indxFlgInfo, _.Library.RawString ptInfo) |
| Export all of the analysis data from the invocation of the 'outlierIndices(...)' method. More... | |
| _.Library.Status | exportSQLAnalysis (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String type, _.Library.String option, _.Library.RawString conds, _.Library.Integer includeSQL, _.Library.RawString ptInfo) |
| Export all of the data from joining both the SQL Statements & SQL Analysis tables. More... | |
| _.Library.Status | exportSQLAnalysisDB (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String option, _.Library.RawString conds, _.Library.RawString ptInfo) |
| Export all of the SQL Analysis data. More... | |
| _.Library.Status | exportSQLStatements (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String type, _.Library.RawString conds, _.Library.RawString ptInfo) |
| Export all of the SQL Statements data. More... | |
| _.Library.Status | exportSQLStats (file, format, silent, statsType, exportPlan, rtnName, modName, _.Library.RawString conds, _.Library.RawString ptInfo) |
| Export the data from the 'SYS.PTools.StatsSQL' class and return the output location. More... | |
| _.Library.Status | exportTIAnalysis (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String type, _.Library.String orderBy, _.Library.RawString conds, _.Library.Integer includeSQL, _.Library.RawString ptInfo) |
| Export all of the analysis data from the invocation of the 'tempIndices(...)' method. More... | |
| _.Library.Status | exportTSAnalysis (_.Library.String file, _.Library.String format, _.Library.Integer silent, _.Library.String type, _.Library.String orderBy, _.Library.RawString conds, _.Library.Integer includeSQL, _.Library.RawString ptInfo) |
| Export all of the analysis data from the invocation of the 'tableScans(...)' method. More... | |
| _.Library.Integer | getAllCachedQrySQLStmts (_.Library.Integer clearData, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all of the Cached Queries. More... | |
| _.Library.Integer | getAllClassMethSQLStmts (_.Library.Integer clearData, _.Library.Integer skipSysClass, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all of the Class Methods. More... | |
| _.Library.Integer | getAllClassQrySQLStmts (_.Library.Integer clearData, _.Library.Integer skipSysClass, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all of the Class Queries. More... | |
| _.Library.Integer | getAllIndices (_.Library.Integer clearData, _.Library.Integer skipSysClass, _.Library.Integer skipIDKeys, _.Library.Integer display) |
| Get SQL Indexes from all classes. More... | |
| _.Library.Integer | getAllRtnQrySQLStmts (_.Library.Integer clearData, _.Library.Integer skipSysRtn, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the Embedded SQL Statements from all of the MAC Routines. More... | |
| _.Library.Status | getAllSQLStmts (_.Library.Integer clearData, _.Library.Integer skipSysObj, _.Library.Integer skipInsStmts, _.Library.Integer display, _.Library.Integer returnType, _.Library.RawString ptInfo) |
| Get all of the SQL Statements from the IRIS database. More... | |
| _.Library.Integer | getCachedQrySQLStmtsByClass (_.Library.RawString items, _.Library.Integer clearData, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all Cached Queries provided in the 'items' array. More... | |
| _.Library.Integer | getCachedQrySQLStmtsByDays (_.Library.Integer days, _.Library.Integer clearData, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all of the Cached Queries that have had a Prepare in the last 'days' days. More... | |
| _.Library.Integer | getClassMethSQLStmtsByClass (_.Library.RawString items, _.Library.Integer clearData, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all Class Methods provided in the 'items' array. More... | |
| _.Library.Integer | getClassQrySQLStmtsByClass (_.Library.RawString items, _.Library.Integer clearData, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the SQL Statements from all Class Queries provided in the 'items' array. More... | |
| _.Library.Integer | getError (_.Library.String errRowID, _.Library.RawString PToolsErr) |
| Retrieve 'PTools/SQLStats' Application Error(s) More... | |
| _.Library.String | getImportSchema (_.Library.String ns, _.Library.String rtn, _.Library.String curs) |
| Retrieves the Import Schema. More... | |
| _.Library.String | getIndexFlagInfo (_.Library.Integer flagInt, _.Library.String indexMeth, _.Library.Integer returnInfo) |
| Get the specific information requested about an Index Analyzer Method. More... | |
| _.Library.String | getQueryText (_.Library.String ns, _.Library.String rtn, _.Library.String curs, _.Library.Boolean getInt) |
| Retrieves the SQL Query Text. More... | |
| _.Library.Integer | getRtnQrySQLStmtsByRtn (_.Library.RawString items, _.Library.Integer clearData, _.Library.Integer skipInsStmts, _.Library.Integer display) |
| Get the Embedded SQL Statements from all of the MAC Routines provided in the 'items' array. More... | |
| _.Library.String | getSQLStatsFlag (_.Library.Integer flagType, _.Library.RawString ptInfo) |
| Get the SQLStats-flag that controls whether or not we collect SQL Statistics for each SQL Query execution. More... | |
| _.Library.String | getSQLStatsFlagByPID (_.Library.String pid, _.Library.RawString ptInfo) |
| Get the SQLStats-flag that controls whether or not we collect SQL Statistics about each SQL Query execution for the given 'pid'. More... | |
| _.Library.Status | getSQLStmts (_.Library.Integer clearData, _.Library.Integer skipSysObj, _.Library.Integer skipInsStmts, _.Library.Integer getCachedQry, _.Library.Integer getClassMethQry, _.Library.Integer getClassQry, _.Library.Integer getRtnQry, _.Library.Integer display, _.Library.Integer returnType) |
| Get the SQL Statements from the IRIS database. More... | |
| _.Library.Status | indexUsage (_.Library.Integer clearData, _.Library.Integer getIndices, _.Library.Integer getSQLStmts, _.Library.Integer skipSysObj, _.Library.Integer skipIDKeys, _.Library.Integer skipInsStmts, _.Library.Integer display, _.Library.RawString ptInfo) |
| Generate a ShowPlan for each query and keep a count of how many times each index is used by each query. More... | |
| _.Library.Status | joinIndices (_.Library.Integer clearData, _.Library.Integer getSQLStmts, _.Library.Integer skipSysObj, _.Library.Integer skipInsStmts, _.Library.Integer display, _.Library.RawString ptInfo) |
| Identify all queries that perform a JOIN between tables, where their joined-fields use an index that supports the join. More... | |
| _.Library.Status | outlierIndices (_.Library.Integer clearData, _.Library.Integer getSQLStmts, _.Library.Integer skipSysObj, _.Library.Integer skipInsStmts, _.Library.Integer display, _.Library.RawString ptInfo) |
| Identify all queries that have outliers, and determines if there is an index defined to support the Outlier Condition. More... | |
| _.Library.String | setSQLStatsFlag (_.Library.Integer actionFlag, _.Library.String collectFlag, _.Library.String terminateCond, _.Library.RawString ptInfo) |
| Set the SQLStats-flag that controls whether or not the System collects SQL Statistics about each run of a query. More... | |
| _.Library.String | setSQLStatsFlagByNS (_.Library.String ns, _.Library.Integer actionFlag, _.Library.String collectFlag, _.Library.String terminateCond, _.Library.RawString ptInfo) |
| Set the flag that controls whether or not to collect SQL Statistics about each run of a query within the given 'ns' (namespace) More... | |
| _.Library.String | setSQLStatsFlagByPID (_.Library.String pid, _.Library.Integer actionFlag, _.Library.String collectFlag, _.Library.RawString ptInfo) |
| Set the SQLStats-flag that controls whether or not to collect SQL Statistics about each run of a query for the given 'pid'. More... | |
| _.Library.String | setSQLStatsFlagJob (_.Library.Integer actionFlag, _.Library.String collectFlag, _.Library.String p3, _.Library.RawString ptInfo) |
| Set the SQLStats-flag that controls whether or not this Process/Job collects SQL Statistics about each run of a query. More... | |
| startGeneralStats (_.Library.String ns, _.Library.String rtn, _.Library.String mod) | |
| This method is used to START the PTools statistics collection. More... | |
| stopGeneralStats (_.Library.String ns, _.Library.String rtn, _.Library.String mod) | |
| This method is used to STOP the PTools statistics collection. More... | |
| _.Library.Status | tableScans (_.Library.Integer clearData, _.Library.Integer getSQLStmts, _.Library.Integer skipSysObj, _.Library.Integer skipInsStmts, _.Library.Integer display, _.Library.RawString ptInfo) |
| Identify all queries that perform a table scan. More... | |
| _.Library.Status | tempIndices (_.Library.Integer clearData, _.Library.Integer getSQLStmts, _.Library.Integer skipSysObj, _.Library.Integer skipInsStmts, _.Library.Integer display, _.Library.RawString ptInfo) |
| Identify all queries that build a Temp Index/Table. More... | |
| _.Library.String | version () |
| Provide the current version for the SYS.PTools.Stats class/section of the Performance Tools (PTools) Application. | |
| _.Library.String | versionSQLAnalysis (fullVer) |
| _.Library.String | versionSQLStats () |
| Provide the current version for the SYS.PTools.StatsSQL class/section of the Performance Tools (PTools) Application. | |
 Static Public Member Functions inherited from Help | |
| _.Library.String | Help (_.Library.String method) |
| This is a helper class that is used by the various SYSTEM classes to provide a Help method. More... | |
<style type="text/css"> .section-head { color: darkblue; white-space: pre; font-family: 'Courier New'; } .info-head { white-space: pre; font-family: 'Courier New'; } DEP { color: red; font-weight: bold; } IMP { color: darkblue; background-color: #D3D3D3; border: 1px solid black; font-size: 1.05em; line-height: 100%; margin-left: 0px; margin-top: 0px; margin-bottom: 0px; padding-bottom: 15px; width: 80%; white-space: pre; display: block; } </style>
Class: SYSTEM.SQL.PTools Replaces: SYSTEM.SQL [PTools/SQLStats Methods] Purpose:
This class is designed to provides an interface for all of the PTools/SQLStats runtime methods. While most of these methods remain available from the classes in which they are defined, this interface is provided as a quick way to invoke these methods in one central location.
The special $SYSTEM variable, which is an alias for the SYSTEM package containing classes that provide methods for a wide variety of needs, can be used to invoke methods within this class:
<IMP> do $SYSTEM.SQL.PTools.method(...) </IMP>
Since this class extends the <class>SYSTEM.Help</class> class, the following method can be invoked to display all of the method Entry Points available to this class:
<IMP> do $SYSTEM.SQL.PTools.Help() </IMP>
The following example demonstrates how this class can be used to display the current SQLStats-flag setting:
<IMP> write $SYSTEM.SQL.PTools.getSQLStatsFlag() </IMP>
|
static |
<style type="text/css"> .section-head { color: darkblue; white-space: pre; font-family: 'Courier New'; } .info-head { white-space: pre; font-family: 'Courier New'; } DEP { color: red; font-weight: bold; } IMP { color: darkblue; background-color: #D3D3D3; border: 1px solid black; font-size: 1.05em; line-height: 100%; margin-left: 0px; margin-top: 0px; margin-bottom: 0px; padding-bottom: 15px; width: 80%; white-space: pre; display: block; } </style>
Class: SYSTEM.SQL.PTools Replaces: SYSTEM.SQL [PTools/SQLStats Methods] Purpose:
This class is designed to provides an interface for all of the PTools/SQLStats runtime methods. While most of these methods remain available from the classes in which they are defined, this interface is provided as a quick way to invoke these methods in one central location.
The special $SYSTEM variable, which is an alias for the SYSTEM package containing classes that provide methods for a wide variety of needs, can be used to invoke methods within this class:
<IMP> do $SYSTEM.SQL.PTools.method(...) </IMP>
Since this class extends the <class>SYSTEM.Help</class> class, the following method can be invoked to display all of the method Entry Points available to this class:
<IMP> do $SYSTEM.SQL.PTools.Help() </IMP>
The following example demonstrates how this class can be used to display the current SQLStats-flag setting:
<IMP> write $SYSTEM.SQL.PTools.getSQLStatsFlag() </IMP>
Aggregate all of the statistical properties for each SQL Query where data was collected
Method: aggregateSQLStats [SQL: PTools_aggregateSQLStats] Replaces: N/A Status: New Functionality Purpose: This function aggregates all of the statistical properties for each SQL Query where data was collected
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.aggregateSQLStats(...) SQL: CALL SYSTEM_SQL.PTools_aggregateSQLStats(...) SELECT SYSTEM_SQL.PTools_aggregateSQLStats(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Aggregate all of the statistical properties for the 'SAMPLES' namespace:
set status=$SYSTEM.SQL.PTools.aggregateSQLStats("SAMPLES")
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: ns - The namespace in which to aggregate SQL Statistics If none provided, spin through all namespaces where SQL Stats collected rtn - The routine in which to aggregate SQL Statistics If none provided, spin through all routines where SQL Stats collected curs - The cursor in which to aggregate SQL Statistics If none provided, spin through all cursor where SQL Stats collected
|
static |
Delete 'PTools/SQLStats' Application Error(s)
Method: clearError [SQL: PTools_clearError Replaces: N/A Status: New Functionality Purpose: This method deletes a specific 'PTools' Application Error for the given 'errRowID' or Deletes all errors if no 'errRowID' is provided.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.clearError(...) SQL: SELECT SYSTEM_SQL.PTools_clearError(...)
Data Storage: ^sqlcq($NAMESPACE,"PTools","Error",{errRowID})
Parameters: errRowID - The 'PTools' Error RowID to delete; If none specified, then delete all recorded PTools errors
RETURN Value: The 'PTools' Error RowID ({errRowID}) deleted, the empty string ("") if {errRowID} invalid, or the word 'all' indicating an array of all errors deleted.
|
static |
Delete all of the data stored in the 'SYS.PTools.Stats' class.
The following methods are used to remove all of the 'Stats' data:
The aforementioned methods remove data stored in the following classes:
Method: clearGeneralStats [SQL: PTools_clearGeneralStats] Replaces: N/A Status: New Functionality Purpose: This method deletes all of the data stored in the 'SYS.PTools.Stats' class, based on the specified 'ns' and 'rtn' parameters...
This method clears statistics which are gathered by the invocation of the following two methods: do $SYSTEM.SQL.PTools.startGeneralStats(namespace,routine,mod) // Start Stats Collection // Invoke the method in which statistics are to be collected do $SYSTEM.SQL.PTools.stopGeneralStats(namespace,routine,mod) // Stop Stats Collection
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.clearGeneralStats(...) SQL: CALL SYSTEM_SQL.PTools_clearGeneralStats(...) SELECT SYSTEM_SQL.PTools_clearGeneralStats(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: ns - The namespace in which to clear Statistics If none provided, use the current namespaces where Stats collected [DEFAULT: Current Namespace] rtn - The routine for which to clear Statistics If none provided, clear all routines in the given 'namespace' [OPTIONAL] ph3 - Placeholder Parameter for future extensibility clearErrs - 0 = Don't delete the 'PTools' Application Errors 1 = Delete all of the 'PTools' Application Errors [DEFAULT: 0] returnType - 0 = Return a Status code of either $$$OK or $$$ERROR() 1 = Return the number of Stats rows deleted from the following class: SYS.PTools.Stats [DEFAULT: 0] ptInfo - A Pass By Reference information array that returns detailed information to the user in the following format: ptInfo(category,variable)=value OR $LB(val1,...,valn) Where category = { "cnt" | "curr" | "term" | ... } variable = A var corresponding to the given 'category'
Example: ptInfo("cnt","clearStats")=The number of rows deleted via this method
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return a Status code of either $$$OK or $$$ERROR()
1: Return the number of Stats rows deleted from the following class; Otherwise, return an error message if an error occurred: SYS.PTools.Stats
|
static |
Delete all of the SQL Index Usage Analytical data stored in the 'SYS.PTools.UtilSQLAnalysisDB' class.
Method: clearSQLAnalysisDB [SQL: PTools_clearSQLAnalysisDB] Replaces: ClearResults SQL: ClearResults <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Delete all of the data stored in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class, based on the specified parameters...
This method clears SQL Index Usage Analytical statistics which are gathered when one of the following methods are invoked:
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.clearSQLAnalysisDB(...) SQL: CALL SYSTEM_SQL.PTools_clearSQLAnalysisDB(...) SELECT SYSTEM_SQL.PTools_clearSQLAnalysisDB(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Delete all of the data stored in the 'SYS.PTools.UtilSQLAnalysisDB' class in the current namespace:
set status=$SYSTEM.SQL.PTools.clearSQLAnalysisDB()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: ns - The namespace in which to clear SQL Index/Analysis Statstics [DEFAULT: Current Namespace] clearErrs - 0 = Don't delete the 'PTools' Application Errors 1 = Delete all of the 'PTools' Application Errors [DEFAULT: 0] returnType - 0 = Return a Status code of either $$$OK or $$$ERROR() 1 = Return the number of Stats rows deleted from the following class: SYS.PTools.UtilSQLAnalysisDB [DEFAULT: 0] ptInfo - A Pass By Reference information array that returns detailed information to the user in the following format: ptInfo(category,variable)=value OR $LB(val1,...,valn) Where category = { "cnt" | "curr" | "term" | ... } variable = A var corresponding to the given 'category'
Example: ptInfo("cnt","clearSQLAnalysisDB")=The number of rows deleted via this method
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return a Status code of either $$$OK or $$$ERROR()
1: Return the number of Stats rows deleted from the following class; Otherwise, return an error message if an error occurred: SYS.PTools.UtilSQLAnalysisDB
|
static |
Delete all of the data stored in the SQL Index/Analysis Stats classes.
The following methods are used to remove all of the 'SQL Index Stats' data:
The aforementioned methods remove data stored in the following classes:
NOTE: old = Backward-compatible data
Method: clearSQLIndexStats [SQL: PTools_clearSQLIndexStats] Replaces: N/A Status: New Functionality Purpose: This method deletes all of the data stored in the Optimal (new) PTools Utility SQL Index/Analysis Stats classes, based on the specified parameters...
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.clearSQLIndexStats(...) SQL: CALL SYSTEM_SQL.PTools_clearSQLIndexStats(...) SELECT SYSTEM_SQL.PTools_clearSQLIndexStats(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does. Since this method returns a $LIST() of Status codes, the output can be converted to a comma-delimited string by using the $LISTTOSTRING(...) function on the ObjectScript or SQL result.
Data Storage: ^sqlcq($NAMESPACE,"PTools",...)
Parameters: ns - The namespace in which to clear PTools Stats [DEFAULT: $NAMESPACE] clearErrs - 0 = Don't delete the 'PTools' Application Errors 1 = Delete all of the 'PTools' Application Errors [DEFAULT] silent - 0 = Display all messages during this method invocation [DEFAULT] 1 = Don't display any messages during this method invocation returnType - 0 = Return a Status code of either $$$OK or $$$ERROR() [DEFAULT] 1 = Return the total number of Stats rows deleted ptInfo - A Pass By Reference information array that returns detailed information to the user in the following format: ptInfo(category,variable)=value OR $LB(val1,...,valn) Where category = { "cnt" | "curr" | "term" | ... } variable = A var corresponding to the given 'category'
Example: ptInfo("cnt","clearStatsSQLIndexALL")=The number of rows deleted via this method
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return a Status code of either $$$OK or $$$ERROR()
1: Return the total number of Stats rows deleted; Otherwise, return an error message if an error occurred
|
static |
Delete all of the SQL Statements data stored in the 'SYS.PTools.UtilSQLStatements' class.
For each of the SQL Statements saved in the <class>SYS.PTools.UtilSQLStatements</class> class, and each of the SQL Statement Results in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class, use one of the following methods to delete all of the data stored in these classes:
Method: clearSQLStatements [SQL: PTools_clearSQLStatements] Replaces: ClearStatements SQL: ClearStatements <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Delete all of the data stored in the <class>SYS.PTools.UtilSQLStatements</class> class, based on the specified parameters...
This method clears SQL Index Usage Analytical statistics which are gathered when one of the following methods are invoked:
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.clearSQLStatements(...) SQL: CALL SYSTEM_SQL.PTools_clearSQLStatements(...) SELECT SYSTEM_SQL.PTools_clearSQLStatements(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Delete all of the data stored in the 'SYS.PTools.UtilSQLStatements' class in the current namespace:
set status=$SYSTEM.SQL.PTools.clearSQLStatements()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: ns - The namespace in which to clear SQL Index/Analysis Statstics [DEFAULT: Current Namespace] clearErrs - 0 = Don't delete the 'PTools' Application Errors 1 = Delete all of the 'PTools' Application Errors [DEFAULT: 0] returnType - 0 = Return a Status code of either $$$OK or $$$ERROR() 1 = Return the number of Stats rows deleted from the following class: SYS.PTools.UtilSQLStatements [DEFAULT: 0] ptInfo - A Pass By Reference information array that returns detailed information to the user in the following format: ptInfo(category,variable)=value OR $LB(val1,...,valn) Where category = { "cnt" | "curr" | "term" | ... } variable = A var corresponding to the given 'category'
Example: ptInfo("cnt","clearSQLStatements")=The number of rows deleted via this method
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return a Status code of either $$$OK or $$$ERROR()
1: Return the number of Stats rows deleted from the following class; Otherwise, return an error message if an error occurred: SYS.PTools.UtilSQLStatements
|
static |
Delete all of the data stored in the SQL Stats classes.
The following methods are used to remove all of the 'SQL Stats' data:
The aforementioned methods remove data stored in the following classes:
Optional:
NOTE: old = Backward-compatible data
Method: clearSQLStatsALL [SQL: PTools_clearSQLStatsALL] Replaces: N/A Status: New Functionality Purpose: This method deletes all of the data stored in the Optimal (new) PTools SQL Stats classes, based on the specified parameters...
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.clearSQLStatsALL(...) SQL: CALL SYSTEM_SQL.PTools_clearSQLStatsALL(...) SELECT SYSTEM_SQL.PTools_clearSQLStatsALL(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Data Storage: ^sqlcq($NAMESPACE,"PTools",...)
Parameters: ns - The namespace in which to clear PTools SQL Statistics [DEFAULT: $NAMESPACE] rtn - The routine in which to clear PTools SQL Statistics [DEFAULT: ""] If none provided, clear all routines in the given 'ns' ph3 - Placeholder Parameter for future extensibility clearAll - 0 = Delete all of the data, except the 'INFO' rows, stored in the StatsSQL class:
Example: ptInfo("cnt","clearSQLStatsALL")=The number of rows deleted via this method
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return a Status code of either $$$OK or $$$ERROR()
1: Return the total number of Stats rows deleted; Otherwise, return an error message if an error occurred
|
static |
Create a file containing the data from the 'SYS.PTools.Stats' class.
Method: exportGeneralStats [SQL: PTools_exportGeneralStats] Replaces: Report <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Create a Performance Tool file containing the data from the 'SYS.PTools.Stats' class and return the output location... By default, the file will be created in the current directory of the InterSystems IRIS instance.
NOTE: Current directory can be obtained in the following way, from a InterSystems IRIS Terminal: >write $ZU(12,"")
You can pass a different value for the 'file' parameters if you wish to override the default location and file name.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportGeneralStats(...) SQL: CALL SYSTEM_SQL.PTools_exportGeneralStats(...) SELECT SYSTEM_SQL.PTools_exportGeneralStats(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportGeneralStats($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportGeneralStats('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.Stats class: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_Stats_exportStats_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file bcFlag - This is a Backward-Compatibility flag used for [Internal Purposes ONLY]
RETURN Value: The status from the invocation of this method
|
static |
Export all of the analysis data from the invocation of the 'indexUsage(...)' method.
The following Exporting/Reporting methods allow for the exporting & reporting of SQL Statements and accompanying SQL Index Usage Analytical data generated from the invocation of one of the following SQL Index Analyzer methods:
SQL Index Analyzer Exporting/Reporting ================== ====================
NOTE: The data from the aforementioned methods are stored in the following classes/tables, and output the data from each method's corresponding Query with the same name:
Method: exportIUAnalysis [SQL: PTools_exportIUAnalysis] Replaces: N/A Status: New Functionality Purpose: Create a file containing all the data from joining both the <class>SYS.PTools.UtilSQLStatements</class> and <class>SYS.PTools.UtilSQLAnalysisDB</class> classes & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportIUAnalysis(...) SQL: CALL SYSTEM_SQL.PTools_exportIUAnalysis(...) SELECT SYSTEM_SQL.PTools_exportIUAnalysis(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportIUAnalysis($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportIUAnalysis('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
NOTE: To query this information via SQL, use the following View: SYS_PTools.UtilSQLAnalysis_indexUsage()
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements & SYS.PTools.UtilSQLAnalysisDB classes: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportIUAnalysis_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
EXAMPLE: 4d,1,2a => ORDER BY UsageCount DESC,SchemaName,TableName ASC
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the analysis data from the invocation of the 'joinIndices(...)' method.
Method: exportJIAnalysis [SQL: PTools_exportJIAnalysis] Replaces: N/A Status: New Functionality Purpose: Create a file containing all the data from joining both the <class>SYS.PTools.UtilSQLStatements</class> and <class>SYS.PTools.UtilSQLAnalysisDB</class> classes & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportJIAnalysis(...) SQL: CALL SYSTEM_SQL.PTools_exportJIAnalysis(...) SELECT SYSTEM_SQL.PTools_exportJIAnalysis(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportJIAnalysis($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportJIAnalysis('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
NOTE: To query this information via SQL, use the following View: SYS_PTools.UtilSQLAnalysis_joinIndices()
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements & SYS.PTools.UtilSQLAnalysisDB classes: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportJIAnalysis_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
EXAMPLE: 7d,1,2a => ORDER BY JoinIndexFlag DESC,SchemaName,TableName ASC
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] includeSQL - 0 = Don't include the SQL Text in the output as the last field 1 = Include the SQL Text in the output as the last field [DEFAULT] skipJIF4 - 0 - Export all rows regardless of the 'JoinIndexFlag' value 1 - Export all rows where the value of the 'JoinIndexFlag' is not 4 [DEFAULT] indxFlgInfo - The specific information that should be returned for the 'JoinIndexFlag' field: 0 = The Index-Flag Internal Value [DEFAULT] 1 = The Index-Flag Title 2 = The Index-Flag Definition 3 = The Index-Flag as 'Title: Definition' ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the analysis data from the invocation of the 'outlierIndices(...)' method.
Method: exportOIAnalysis [SQL: PTools_exportOIAnalysis] Replaces: N/A Status: New Functionality Purpose: Create a file containing all the data from joining both the <class>SYS.PTools.UtilSQLStatements</class> and <class>SYS.PTools.UtilSQLAnalysisDB</class> classes & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportOIAnalysis(...) SQL: CALL SYSTEM_SQL.PTools_exportOIAnalysis(...) SELECT SYSTEM_SQL.PTools_exportOIAnalysis(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportOIAnalysis($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportOIAnalysis('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
NOTE: To query this information via SQL, use the following View: SYS_PTools.UtilSQLAnalysis_outlierIndices()
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements & SYS.PTools.UtilSQLAnalysisDB classes: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportOIAnalysis_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
EXAMPLE: 8d,1,2a => ORDER BY OutlierIndexFlag DESC,SchemaName,TableName ASC
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] includeSQL - 0 = Don't include the SQL Text in the output as the last field 1 = Include the SQL Text in the output as the last field [DEFAULT] skipOIF4 - 0 - Export all rows regardless of the 'OutlierIndexFlag' value 1 - Export all rows where the value of the 'OutlierIndexFlag' is not 4 [DEFAULT] indxFlgInfo - The specific information that should be returned for the 'OutlierIndexFlag' field: 0 = The Index-Flag Internal Value [DEFAULT] 1 = The Index-Flag Title 2 = The Index-Flag Definition 3 = The Index-Flag as 'Title: Definition' ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the data from joining both the SQL Statements & SQL Analysis tables.
Method: exportSQLAnalysis [SQL: PTools_exportSQLAnalysis] Replaces: exportSQLUtilities SQL: PT_exportSQLUtilities <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Create a file containing all the data from joining both the <class>SYS.PTools.UtilSQLStatements</class> and <class>SYS.PTools.UtilSQLAnalysisDB</class> classes & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportSQLAnalysis(...) SQL: CALL SYS_PTools.PTools_exportSQLAnalysis(...) SELECT SYS_PTools.PTools_exportSQLAnalysis(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportSQLAnalysis($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYS_PTools.PTools_exportSQLAnalysis('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
NOTE: To query this information via SQL, use the following View: SYS_PTools.UtilSQLStmtsAndAnalysisDBView
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements & SYS.PTools.UtilSQLAnalysisDB classes: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportUtilSQLAnalysis_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] includeSQL - 0 = Don't include the SQL Text in the output as the last field 1 = Include the SQL Text in the output as the last field [DEFAULT] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the SQL Analysis data.
Method: exportSQLAnalysisDB [SQL: PTools_exportSQLAnalysisDB] Replaces: exportSQLUtilStmts SQL: PT_exportSQLUtilStmts <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Create a file containing all the data from the <class>SYS.PTools.UtilSQLAnalysisDB</class> class & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportSQLAnalysisDB(...) SQL: CALL SYS_PTools.PTools_exportSQLAnalysisDB(...) SELECT SYS_PTools.PTools_exportSQLAnalysisDB(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportSQLAnalysisDB($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYS_PTools.PTools_exportSQLAnalysisDB('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLAnalysisDB class: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportUtilSQLAnalysisDB_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the SQL Statements data.
The following methods allow for the exporting and reporting of SQL Statements and accompanying data that have been saved in one of the following two classes/tables:
Method: exportSQLStatements [SQL: PTools_exportSQLStatements] Replaces: exportSQLUtilStmts SQL: PT_exportSQLUtilStmts <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Create a file containing all the data from the <class>SYS.PTools.UtilSQLStatements</class> class & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportSQLStatements(...) SQL: CALL SYSTEM_SQL.PTools_exportSQLStatements(...) SELECT SYSTEM_SQL.PTools_exportSQLStatements(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportSQLStatements($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportSQLStatements('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements class: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportUtilSQLStatements_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export the data from the 'SYS.PTools.StatsSQL' class and return the output location.
Method: exportSQLStats [SQL: PTools_exportSQLStats] Replaces: Export & ExportAll (<class>SYS.PTools.SQLStats</class>) <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: Create a Performance Tool file containing the data from the 'SYS.PTools.StatsSQL' and return the output location... By default, the file will be created in the current directory of the InterSystems IRIS instance.
NOTE: Current directory can be obtained in the following way, from a InterSystems IRIS Terminal: >write $ZU(12,"")
You can pass a different value for the 'file' parameters if you wish to override the default location and file name.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportSQLStats(...) SQL: CALL SYSTEM_SQL.PTools_exportSQLStats(...) SELECT SYSTEM_SQL.PTools_exportSQLStats(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportSQLStats($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportSQLStats('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.StatsSQL class: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_StatsSQL_exportStatsSQL[_{Stmt|Plan}]_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the analysis data from the invocation of the 'tempIndices(...)' method.
Method: exportTIAnalysis [SQL: PTools_exportTIAnalysis] Replaces: N/A Status: New Functionality Purpose: Create a file containing all the data from joining both the <class>SYS.PTools.UtilSQLStatements</class> and <class>SYS.PTools.UtilSQLAnalysisDB</class> classes & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportTIAnalysis(...) SQL: CALL SYSTEM_SQL.PTools_exportTIAnalysis(...) SELECT SYSTEM_SQL.PTools_exportTIAnalysis(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportTIAnalysis($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYSTEM_SQL.PTools_exportTIAnalysis('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
NOTE: To query this information via SQL, use the following View: SYS_PTools.UtilSQLAnalysis_tempIndices()
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements & SYS.PTools.UtilSQLAnalysisDB classes: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportTIAnalysis_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
EXAMPLE: 9d,1,2a => ORDER BY BlockCount DESC,SchemaName,TableName ASC
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] includeSQL - 0 = Don't include the SQL Text in the output as the last field 1 = Include the SQL Text in the output as the last field [DEFAULT] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Export all of the analysis data from the invocation of the 'tableScans(...)' method.
Method: exportTSAnalysis [SQL: PTools_exportTSAnalysis] Replaces: N/A Status: New Functionality Purpose: Create a file containing all the data from joining both the <class>SYS.PTools.UtilSQLStatements</class> and <class>SYS.PTools.UtilSQLAnalysisDB</class> classes & return the output location... Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.exportTSAnalysis(...) SQL: CALL SYS_PTools.PTools_exportTSAnalysis(...) SELECT SYS_PTools.PTools_exportTSAnalysis(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples shows the use of this method:
#1 Display this export file to the screen via a InterSystems IRIS Terminal:
set tSC=$SYSTEM.SQL.PTools.exportTSAnalysis($IO)
#2 Display this export file via the SQL Query Page of the Management Portal:
CALL SYS_PTools.PTools_exportTSAnalysis('$IO','H')
Where: '$IO' = Output to the current device NOTE: '$IO' can be omitted, as it is the default 'file' when invoked via the CALL interface 'H' = Output the format in HTML format NOTE: 'H' can be omitted, as it is the default 'format' when invoked via the CALL interface
NOTE: To query this information via SQL, use the following View: SYS_PTools.UtilSQLAnalysis_tableScans()
Parameters: file - The path and file in which to create and store the data from the SYS.PTools.UtilSQLStatements & SYS.PTools.UtilSQLAnalysisDB classes: (e.g. C:\exportFile.txt) NOTE: $IO = Outputs the data to the screen '$IO' = Output the data to the current device when invoked from the CALL/SELECT-interface '$DEF' = Ouput the data to the DEFAULT file when invoked from the CALL/SELECT-interface [DEFAULT: {Current-Directory}\PT_exportTSAnalysis_YYYYMMDD_HHMMSS.{ext}] WHERE {Current-Directory} = The directory of the Namespace in which this method is invoked (e.g. $ZU(12,"")) NOTE 2: If Passed By Reference, then 'file' will be returned as the canonical name of the Export/Reporting file format - The output format of the Export/Reporting file This parameter has the following structure of constituent elements: format=<data-format>[:$LB(<delim>,<csv-header>,<csv-footer>)] Where the constituent elements have the following values: <data-format> - The format of the Export/Reporting file:
EXAMPLE: 8d,1,2a => ORDER BY BlockCount DESC,SchemaName,TableName ASC
conds - A string/array of possible conditions by which to restrict the output of the Export file, in the following format:
conds=<full condition> OR conds(0)=pos Count (WHERE pos = {1...n}) conds(pos)=$LIST() Pieces: 1) [<logical operator>] (Assumed Default: &&) 2) [{Heading}] (Omit for override cond) 3) <simple condition> | <complex condition>
WHERE: <full condition> := <full condition expression> <logical operator> := {&& | ||} (&& = AND | || = OR) <simple condition>@* := <oper>
<complex condition>@ := <complex condition expression>
@ = Contains no references to {Heading}
EXAMPLE: <full condition> conds="("",INFO,MAIN,""[("",""_{Module}_"",""))||({GlobalRefs}>20)" <simple condition> conds(0)=3 conds(1)=$LB(,"Module","=""INFO""") conds(2)=$LB("||","Module","=""MAIN""") conds(3)=$LB("||","GlobalRefs",">20") <complex condition> conds(0)=2 conds(1)=$LB(,"Module",""",INFO,MAIN,""[("",""_{*}_"","")") conds(2)=$LB("||","GlobalRefs","{*}>20") WHERE: {*} = value substitution for the 'Module' & 'GlobalRefs' fields NOTE: Conditions that don't contain any references to {Heading} fields, often called <override condition>s, can be included as <complex condition>s, as in the following example: conds(pos)=$LB(,,"$g(^zAction(""runIt""))=1")
NOTE: All conditions must be satisfied for the conds() to be considered true and for the row to be exported [PASS BY REFERENCE] includeSQL - 0 = Don't include the SQL Text in the output as the last field 1 = Include the SQL Text in the output as the last field [DEFAULT] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo(variable)=value ptInfo("outputFile")=The canonical name of the Export/Reporting file
RETURN Value: The status from the invocation of this method
|
static |
Get the SQL Statements from all of the Cached Queries.
Gather SQL Statements from all of the Cached Queries within InterSystems IRIS and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for Index Analysis and additional processing...
Method: getAllCachedQrySQLStmts [SQL: PTools_getAllCachedQrySQLStmts] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all of the Cached Queries created and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Cached Queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the SQL Statements from all of the Class Methods.
Gather SQL Statements from all of the Class Methods within InterSystems IRIS and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for Index Analysis and additional processing...
Method: getAllClassMethSQLStmts [SQL: PTools_getAllClassMethSQLStmts] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all of the Class Methods created and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipSysClass - 0 = Don't skip all System Classes 1 = Skip all System Classes that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Classes that are not defined in the namespace in which this method is invoked 3 = Skip all System Classes defined by InterSystems, even if the class is also defined in the namespace in which this method is invoked NOTE: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of cached queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the SQL Statements from all of the Class Queries.
Gather SQL Statements from all of the Class Queries within InterSystems IRIS and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for Index Analysis and additional processing...
Method: getAllClassQrySQLStmts [SQL: PTools_getAllClassQrySQLStmts] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all of the Class Queries created and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipSysClass - 0 = Don't skip all System Classes 1 = Skip all System Classes that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Classes that are not defined in the namespace in which this method is invoked 3 = Skip all System Classes defined by InterSystems, even if the class is also defined in the namespace in which this method is invoked NOTE: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Class Queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get SQL Indexes from all classes.
Gather SQL Indexes from all classes within InterSystems IRIS and add them to the <class>SYS.PTools.SQLUtilResult</class> class for Index Analysis and additional processing
Method: getAllIndices [SQL: PTools_getAllIndices] Replaces: N/A [AllIndices^SYS.PToolsDEP] Status: New Functionality Purpose: This method processes all of the classes/tables on the system and collects all of the defined Indexes and adds them to the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for future processing...
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.getAllIndices(...) SQL: CALL SYSTEM_SQL.PTools_getAllIndices(...) SELECT SYSTEM_SQL.PTools_getAllIndices(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show the data collected from the running of this method:
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_getAllIndices()
NOTE: These queries can either be invoked from a number of
tools, such as the SQL Query tool in the 'Management Portal'
or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as show
below:
>do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipSysClass - 0 = Don't skip all System Classes 1 = Skip all System Classes that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Classes that are not defined in the namespace in which this method is invoked 3 = Skip all System Classes defined by InterSystems, even if the class is also defined in the namespace in which this method is invoked NOTE: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) [DEFAULT: 1] skipIDKeys - 1 = Skip all the index that will be used to form the Object Identity value (IDKEY) for the given class [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Indexes added to the <class>SYS.PTools.UtilSQLAnalysisDB</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the Embedded SQL Statements from all of the MAC Routines.
Gather SQL Statements from all of the MAC Routines within InterSystems IRIS and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for Index Analysis and additional processing...
Method: getAllRtnQrySQLStmts [SQL: PTools_getAllRtnQrySQLStmts] Replaces: N/A Status: New Functionality Purpose: Get the Embedded SQL Statements from all of the MAC Routines and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipSysRtn - 0 = Don't skip all System Routines 1 = Skip all System Routines that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Routines that are not defined in the namespace in which this method is invoked 3 = Skip all System Routines defined by InterSystems, even if the routine is also defined in the namespace in which this method is invoked NOTE: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Embedded SQL Statements added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get all of the SQL Statements from the IRIS database.
Gather SQL Statements from all places within InterSystems IRIS and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for Index Analysis and additional processing...
Method: getAllSQLStmts [SQL: PTools_getAllSQLStmts] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all of the following locations and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing:
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.getAllSQLStmts(...) SQL: CALL SYSTEM_SQL.PTools_getAllSQLStmts(...) SELECT SYSTEM_SQL.PTools_getAllSQLStmts(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT Type, Name, MethodName, ImportPackage,
SQLTextExt AS "SQL Text"
FROM %SYS_PTools.UtilSQLStatements
ORDER BY Type, Name
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_getAllSQLStmts()
OR
SELECT Type, "Class/Routine Name", "Method Name", ImportPackage,
"SQL Text"
FROM %SYS_PTools.UtilSQLAnalysis_getAllSQLStmts()
NOTE: These queries can be invoked from a number of tools,
such as the SQL Query tool in the 'Management Portal'
or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as
shown below:
>do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipSysObj - 0 = Don't skip all System Objects (Classes & Routines) 1 = Skip all System Objects (Classes & Routines) that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Objects that are not defined in the namespace in which this method is invoked 3 = Skip all System Objects defined by InterSystems, even if the object is also defined in the namespace in which this method is invoked NOTE: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1] returnType - 0 = Return a Status code of either $$$OK or $$$ERROR() 1 = Return a $LIST of SQL Statements added to the <class>SYS.PTools.UtilSQLStatements</class> class [DEFAULT: 0] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo("insert-list")=The number of rows inserted in the 'SYS.PTools.UtilSQLStatements' class in the following $LIST format $LIST() pieces: 1) Grand Total of all SQL Query Statements added 2) Total of all Cached Query Statements added 3) Total of all Class Method Statements added 4) Total of all Class Query Statements added 5) Total of all Routine Statements added
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return a Status code of either $$$OK or $$$ERROR()
1: Return the number of SQL Statements added to the <class>SYS.PTools.UtilSQLStatements</class> class in the following $LIST format; Otherwise, return an error message if an error occurred.
$LIST() pieces: 1) Grand Total of all SQL Query Statements added 2) Total of all cached query Statements added 3) Total of all Class Method Statements added 4) Total of all Class Query Statements added 5) Total of all Routine Statements added
|
static |
Get the SQL Statements from all Cached Queries provided in the 'items' array.
Method: getCachedQrySQLStmtsByClass [SQL: PTools_getCachedQrySQLStmtsByClass Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all Cached Queries provided in the 'items' array and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: item - A comma delimited list or array of Cached Query class names NOTE: The class names must either all contain class extensions (e.g. myClass.CLS) or none at all (e.g. myClass) EXAMPLE: items="%sqlcq.SAMPLES.cls1,%sqlcq.SAMPLES.cls2" OR items("%sqlcq.SAMPLES.cls1")="" items("%sqlcq.SAMPLES.cls2")="" clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Cached Queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the SQL Statements from all of the Cached Queries that have had a Prepare in the last 'days' days.
Method: getCachedQrySQLStmtsByDays [SQL: PTools_getCachedQrySQLStmtsByDays] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all Cached Queries that have had a Prepare in the last 'days' days and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: days - The number of days since the last Cached Query was Prepared. If days=0, then get all Cached Queries. [DEFAULT: 0 (All)] clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Cached Queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the SQL Statements from all Class Methods provided in the 'items' array.
Method: getClassMethSQLStmtsByClass [SQL: PTools_getClassMethSQLStmtsByClass] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all Class Methods provided in the 'items' array and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: item - A comma delimited list or array of Class Methods class names NOTE: The class names must either all contain class extensions (e.g. myClass.CLS) or none at all (e.g. myClass) EXAMPLE: items="Cinema.Film,Sample.Person" OR items("Cinema.Film")="" items("Sample.Person")="" clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Class Methods added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the SQL Statements from all Class Queries provided in the 'items' array.
Method: getClassQrySQLStmtsByClass [SQL: PTools_getClassQrySQLStmtsByClass] Replaces: N/A Status: New Functionality Purpose: Get the SQL Statements from all Class Queries provided in the 'items' array and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: item - A comma delimited list or array of Class Query class names NOTE: The class names must either all contain class extensions (e.g. myClass.CLS) or none at all (e.g. myClass) EXAMPLE: items="Cinema.Film,Sample.Person" OR items("Cinema.Film")="" items("Sample.Person")="" clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Class Queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Retrieve 'PTools/SQLStats' Application Error(s)
The following methods are used to retrieve & remove all of the 'PToolsError' data:
The aforementioned methods remove data stored in the following global:
NOTE: old = Backward-compatible data
Method: getError [SQL: PTools_getError] Replaces: N/A Status: New Functionality Purpose: This method retrieve a specific 'PTools' Application Error for the given 'errRowID' or retrieve all errors if no 'errRowID' is provided.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.getError(...) SQL: SELECT SYSTEM_SQL.PTools_getError(...)
NOTE: 'PTools' Application Errors will be returned in the 'PToolsErr' array as follows: PToolsErr={errRowID} [Counter] PToolsErr({errRowID},0)=$LIST:
1) $HOROLOG [Timestamp Internal]
2) Timestamp External [Timestamp External: YYYY-MM-DD HH:MM:SS]
3) $NAMESPACE [Current Namespace]
4) $JOB [Current $JOB]
5) $ZN [Current Routine]
6) $zu(41) [Stack Level]
PToolsErr({errRowID},1)=$LIST:
1) {ns} [Error Namespace]
2) {job} [Error $JOB]
3) {rtn} [Error Routine]
4) {curs} [Error SQL Cursor]
5) {mod} [Error SQL Module]
6) {func} [Error Function/Method]
7) {ze} [Error $ZE]
8) {errMsg} [Error Message]
--- SQL Errors ---
9) {class} [Error Class]
10) {table} [Error Table]
11) {SQLCODE} [Error SQLCODE]
12) {%msg} [Error SQL Message]
PToolsErr({errRowID},2)=errLog(errLogID)=errLogMsg PToolsErr({errRowID},2,{errLogID})={errLogMsg}
Parameters: errRowID - The 'PTools' Error RowID to retrieve; If none specified, then retrieve all errors into the 'PToolsErr()' array PToolsErr - An array in which the 'PTools' Application Errors will be returned [PASS BY REFERENCE]
RETURN Value: The 'PTools' Error RowID ({errRowID}) retrieved, the empty string ("") if {errRowID} invalid, or the word 'all' indicating an array of all errors returned.
|
static |
Retrieves the Import Schema.
Method: getImportSchema [SQL: N/A] Replaces: ImportSchema (<class>SYS.PTools.SQLStats</class>) <DEP>[DEPRECATED]</DEP> Status: New Functionality Purpose: This method retrieves the Import Schema given the parameters: 'ns', 'rtn', & 'curs'
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.getImportSchema(...) SQL: N/A
Examples: The following examples shows the use of this method:
#1 Retrieve the SQL Text for any of the data rows retrieved from invoking the 'exportStatsSQL()' method:
CALL SYSTEM_SQL.PTools_exportSQLStats('$IO') set iSchema=$SYSTEM.SQL.PTools.getImportSchema($NAMESPACE,"%sqlcq.<namespace>.cls<#>.1","QRS0")
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: ns - The namespace from which to retrieve the SQL Query Text rtn - The routine from which to retrieve the SQL Query Text curs - The cursor from which to retrieve the SQL Query Text
Return: Return the Import Schema; Otherwise, return the Error Status if an error occurs.
|
static |
Get the specific information requested about an Index Analyzer Method.
Method: getIndexFlagInfo [SQL: PTools_getIndexFlagInfo] Replaces: N/A Status: New Functionality Purpose: Given an Index-Flag Internal Value 'flagInt', and the Index Analyzer Method 'indexMeth' for which this flag is associated, return the specific information requested by the 'returnInfo' parameter NOTE: This is a helper-method for the following Queries:
Parameters: flagInt - The Index-Flag Internal Value NOTE: The following example are the values specified for the 'joinIndices()' method: 4 = Exact Match: An index exists where its fields match all fields from the JOIN conditions 3 = Leading Match: An index exists where its leading fields match all fields from the JOIN conditions, but there are additional fields in the index 2 = Contains Match: An index exists where its fields contains all fields from the JOIN conditions, but not the leading fields 1 = Partial Match: An index exists where its fields contains some of the fields from the JOIN conditions, but not the leading field 0 = No Match: No index exists to support the fields from the JOIN conditions indexMeth - The Index Analyzer Method for which the 'flagInt' parameter is associated
RETURN Value: See the 'returnInfo' parameter for details ; Otherwise, return an error message if an error occurred
|
static |
Method: getQueryText [SQL: N/A] Replaces: QueryText (<class>SYS.PTools.SQLStats</class>) <DEP>[DEPRECATED]</DEP> Status: New Functionality Purpose: This method retrieves the SQL Query Text given the parameters: 'ns', 'rtn', 'curs', & 'getInt'
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.getQueryText(...) SQL: N/A
Examples: The following examples shows the use of this method:
#1 Retrieve the SQL Text for any of the data rows retrieved from invoking the 'exportStatsSQL()' method:
CALL SYSTEM_SQL.PTools_exportSQLStats('$IO') set sql=$SYSTEM.SQL.PTools.getQueryText($NAMESPACE,"%sqlcq.<namespace>.cls<#>.1","QRS0")
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: ns - The namespace from which to retrieve the SQL Query Text rtn - The routine from which to retrieve the SQL Query Text curs - The cursor from which to retrieve the SQL Query Text getInt - 0 = Return the External Query Text 1 = Return the Internal Query Text
Return: Return either the Internal or External SQL Query Text; Otherwise, return the Error Status if an error occurs.
|
static |
Get the Embedded SQL Statements from all of the MAC Routines provided in the 'items' array.
Method: getRtnQrySQLStmtsByRtn [SQL: PTools_getRtnQrySQLStmtsByRtn] Replaces: N/A Status: New Functionality Purpose: Get the Embedded SQL Statements from all of the MAC Routines provided in the 'items' array and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing...
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: item - A comma delimited list or array of MAC Routine names NOTE: The routine names must either all contain extensions (e.g. myRtn.MAC) or none at all (e.g. myRtn) EXAMPLE: items="MRPtest1,MRPtest2" OR items("MRPtest1")="" items("MRPtest2")="" clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1]
RETURN Value: The number of Cached Queries added to the <class>SYS.PTools.UtilSQLStatements</class> class; Otherwise, return an error message if an error occurred
|
static |
Get the SQLStats-flag that controls whether or not we collect SQL Statistics for each SQL Query execution.
Method: getSQLStatsFlag [SQL: PTools_getSQLStatsFlag] Purpose: This method gets the flag that controls whether or not we collect SQL Statistics for each SQL Query execution
Get the current value of the SQLStats-flag for the given 'flagType'.
The SQLStats-flag (System/Job) controls whether or not SQL Statistics are collected for each SQL Query execution, and which performance statistics to be collected.
The SQLStats-flag is a colon (:) delimited string comprised of the following individual components:
SQLStats-flag={action-flag}:{collect-flag}:{condition-flag}:{condition-value}:{terminate-flag}:{flag-type}
RULES: When (flagType=""), whether to use the SQLStats-flag (System) or the SQLStats-flag (Process/Job) is determined by the following rules: IF {action-flag} (Process/Job) = 0, then use SQLStats-flag (System) ELSE use SQLStats-flag (Process/Job) NOTE: This method has the following additional rule when passed the parameter: flagType="" RULE-G1: If {action-flag}=-1, then return zero (0) for each component-flag of the SQLStats-flag, except for the {flag-type} which is one (1) [indicating a Process/Job Flag setting], as in the following example: write $SYSTEM.SQL.PTools.getSQLStatsFlag("") => "0:0:0::0:1"
To retrieve the actual value for each component-flag of the SQLStats-flag in this example, pass a one (1) for the 'flagType' parameter: write $SYSTEM.SQL.PTools.getSQLStatsFlag(1) => "-1:0:0::0:1"
Invocation: This method can be invoked in the following ways: Object Script: $SYSTEM.SQL.PTools.getSQLStatsFlag(...) SQL: SELECT SYSTEM_SQL.PTools_getSQLStatsFlag(...)
Examples: The following examples shows the use of this method:
#1 Get the current value of the SQLStats-flag for the Job/System Flag based on SQLStats-flag Rules:
set SQLStatsFlag=$SYSTEM.SQL.PTools.getSQLStatsFlag("")
Parameters: flagType - "" = Job/System Flag based on SQLStats-flag Rules [DEFAULT] 0 = System Flag 1 = Process/Job Flag ptInfo - A Pass By Reference information array that returns to the user detailed information in the following format: ptInfo(category,variable)=value Where category = { "current" | "terminate" | ["expired"] | ... } variable = A variable that corresponds to the given 'category'
Example: ptInfo("current","SQLStatsFlag")=The SQLStats-flag value after method execution
RETURN: The current value of the SQLStats-flag; Otherwise, return an error message if an error occurred
|
static |
Get the SQLStats-flag that controls whether or not we collect SQL Statistics about each SQL Query execution for the given 'pid'.
Method: getSQLStatsFlagByPID [SQL: PTools_getSQLStatsFlagByPID] Purpose: This method gets the flag that controls whether or not we collect SQL Statistics about each SQL Query execution for the given 'pid'
Get the current value of the SQLStats-flag for the given 'pid'.
The SQLStats-flag (Process/Job) controls whether or not SQL Statistics are collected for each SQL Query execution, and which performance statistics to be collected.
The SQLStats-flag is a colon (:) delimited string comprised of the following individual components:
SQLStats-flag={action-flag}:{collect-flag}:{condition-flag}:{condition-value}:{terminate-flag}:{flag-type}
NOTE: This method ONLY applies to the SQLStats-flag for the given 'pid' (Process/Job) and NOT the SQLStats-flag for the (System)!
RESTRICTION: This method invocation requires Admin_Operate:Use privilege
Invocation: This method can be invoked in the following ways: Object Script: $SYSTEM.SQL.PTools.getSQLStatsFlagByPID(...) SQL: SELECT SYSTEM_SQL.PTools_getSQLStatsFlagByPID(...)
Examples: The following examples shows the use of this method:
#1 Get the current value of the SQLStats-flag for the Job/System Flag based on SQLStats-flag Rules for PID# 12345:
set SQLStatsFlag=$SYSTEM.SQL.PTools.getSQLStatsFlagByPID(12345)
Parameters: pid - The process ID ($JOB) for which to set the SQLStats-flag [DEFAULT: Current $JOB] ptInfo - A Pass By Reference information array that returns to the user detailed information in the following format: ptInfo(category,variable)=value
NOTE: This method currently returns no 'ptInfo', but is included for future extensibility
RETURN: The current value of the SQLStats-flag; Otherwise, return an error message if an error occurred
|
static |
Get the SQL Statements from the IRIS database.
Method: getSQLStmts [SQL: PTools_getSQLStmts] Replaces: GetSQLStatements (<class>SYS.PTools.SQLUtilities</class>) <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: This method searches for at all of the SQL Statements in a namespace from the following locations based on the parameter values (getCachedQry,getClassMethQry,getClassQry,getRtnQry) and adds information about the statements (e.g. Type, Name, SQLText) to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing:
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.getSQLStmts(...) SQL: CALL SYSTEM_SQL.PTools_getSQLStmts(...) SELECT SYSTEM_SQL.PTools_getSQLStmts(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT Type, Name, MethodName, ImportPackage,
SQLTextExt AS "SQL Text"
FROM %SYS_PTools.UtilSQLStatements
ORDER BY Type, Name
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_getSQLStmts()
OR
SELECT Type, "Class/Routine Name", "Method Name", ImportPackage,
"SQL Text"
FROM %SYS_PTools.UtilSQLAnalysis_getSQLStmts()
NOTE: These queries can be invoked from a number of tools,
such as the SQL Query tool in the 'Management Portal'
or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as
shown below:
>do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLStmts","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] skipSysObj - 0 = Don't skip all System Objects (Classes & Routines) 1 = Skip all System Objects (Classes & Routines) that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Objects that are not defined in the namespace in which this method is invoked 3 = Skip all System Objects defined by InterSystems, even if the object is also defined in the namespace in which this method is invoked NOTE: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] getCachedQry - 1 = Get the SQL Statements from all Cached Queries [DEFAULT: 1] getClassMethQry - 1 = Get the SQL Statements from all of the Class Methods [DEFAULT: 1] getClassQry - 1 = Get the SQL Statements from all of the Class Queries [DEFAULT: 1] getRtnQry - 1 = Get the Embedded SQL Statements from all of the MAC Routines [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1] returnType - 0 = Return a Status code of either $$$OK or $$$ERROR() 1 = Return a $LIST of SQL Statements added to the <class>SYS.PTools.UtilSQLStatements</class> class [DEFAULT: 0]
RETURN Value: Based on the value of the 'returnType' parameter, return one of the following: 0: Return the status of this method; Otherwise, return an error message if an error occurred
1: Return the number of SQL Statements added to the <class>SYS.PTools.UtilSQLStatements</class> class in the following $LIST format; Otherwise, return an error message if an error occurred.
$LIST() pieces: 1) Grand Total of all SQL Query Statements added 2) Total of all cached query Statements added 3) Total of all Class Method Statements added 4) Total of all Class Query Statements added 5) Total of all Routine Statements added
|
static |
Generate a ShowPlan for each query and keep a count of how many times each index is used by each query.
For each of the SQL Statements saved in the <class>SYS.PTools.UtilSQLStatements</class> class, generates a ShowPlan and keeps a count of how many times each index is used by each query, along with the total usage for each index by all queries in the namespace, and store this information in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class.
Method: indexUsage [SQL: PTools_indexUsage] Replaces: IndexUsage SQL: IndexUsage <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: This method uses the SQL Statement data stored in the <class>SYS.PTools.UtilSQLStatements</class> class to generate a ShowPlan for each query, and to keeps a count of how many times each index is used by each query. This index usage count is subsequently stored in the 'UsageCount' field of the <class>SYS.PTools.UtilSQLAnalysisDB</class> class, which can be used to find and remove unneeded indices in addition to being used for other analytical purposes...
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.indexUsage(...) SQL: CALL SYSTEM_SQL.PTools_indexUsage(...) SELECT SYSTEM_SQL.PTools_indexUsage(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_indexUsage()
NOTE: These queries can either be invoked from a number of
tools, such as the SQL Query tool in the 'Management Portal'
or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as show
below:
>do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] getIndices - 1 = Get all the SQL Indexes from the Class Methods in this Namespace and add them to the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for additional processing of this method [DEFAULT: 0*]
RETURN Value: The status from the invocation of this method
|
static |
Identify all queries that perform a JOIN between tables, where their joined-fields use an index that supports the join.
For each of the SQL Statements saved in the <class>SYS.PTools.UtilSQLStatements</class> class, identify all queries that have joins, and determines if there is an index defined to support that join. It ranks the indices available to support the joins from 0 (no index present) to 4 (index fully supports the join). Outer joins require an index in one direction. Inner joins require an index in both directions. The result set only contains rows that have a JoinIndexFlag < 4. JoinIndexFlag=4 means there is an index that fully supports the join; these are not listed.
Method: joinIndices [SQL: PTools_joinIndices] Replaces: JoinIndices SQL: JoinIndices <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: This method uses the SQL Statement data stored in the <class>SYS.PTools.UtilSQLStatements</class> class to pinpoint the queries that perform a JOIN between tables where their joined-fields use an index that supports the join. This method will then ranks the indices available to support the join from 0 (no index present) to 4 (index fully supports the join). Pertinent information about these queries is subsequently stored in the the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for future processing and analysis. It's worth noting that OUTER JOINs require an index in one direction, whereas INNER JOINs require an index in both directions. The result-set stored in the the <class>SYS.PTools.UtilSQLAnalysisDB</class> class only contains rows that have a 'JoinIndexFlag < 4'. Rows that have a 'JoinIndexFlag = 4', which means that there exists an index that fully supports the JOIN, are not stored since they are already fully optimized. The stored queries should be reviewed to determine if an index could be added to the class to satisfy the highest 'JoinIndexFlag' possible:
The 'JoinIndexFlag' property has the following 5 values: 0 - No Match: No index exists to support the fields from the JOIN conditions (Some version of the suggested index should be created to improve this query's performance) 1 - Partial Match: An index exists where its fields contains some of the fields from the JOIN conditions, but not the leading field (This will produce poor performance and for that reason is rarely used) 2 - Contains Match: An index exists where its fields contains all fields from the JOIN conditions, but not the leading fields (This might produce OK performance, but improvements should be made) 3 - Leading Match: An index exists where its leading fields match all fields from the JOIN conditions, but there are additional fields in the index (This will produce OK performance, but improvements can be made) 4 - Exact Match: An index exists where its fields match all fields from the JOIN conditions (This is a fully optimized index)
NOTE: The fields returned by the query's 'Index Needed' could be used to create an index that should help improve performance.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.joinIndices(...) SQL: CALL SYSTEM_SQL.PTools_joinIndices(...) SELECT SYSTEM_SQL.PTools_joinIndices(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT SchemaName, TableName,
SQLPointer->Type, SQLPointer->Name,
IndexName, $LISTTOSTRING(JoinFields) AS "Index Needed",
$LISTTOSTRING(IndexFields) AS "Indexed Fields",
$LISTTOSTRING(JoinFields) AS "JOIN Fields",
JoinIndexFlag AS "Join Index Flag",
ExtentSize, BlockCount AS "Block Count",
SQLPointer->SQLTextExt AS "SQL Text"
FROM %SYS_PTools.UtilSQLAnalysisDB
WHERE OptionName = 'JI'
ORDER BY 1,2
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_joinIndices()
NOTE: This query will return JoinIndexFlag AS "Join Index Flag"
as a numeric value (0-3) as specified above. However,
in order to return more specificity for this field,
one of the following values can be passed to the 2nd
parameter 'indexFlagInfo' of the joinIndices() query:
0 = The Index-Flag Internal Value [DEFAULT]
1 = The Index-Flag Title
2 = The Index-Flag Definition
3 = The Index-Flag as 'Title: Definition'
EXAMPLE:
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_joinIndices(,3)
OR
SELECT SchemaName, TableName, Type, "Class/Routine Name",
IndexName, "Index Needed", "Join Index Flag",
ExtentSize, "Block Count",
"SQL Text"
FROM %SYS_PTools.UtilSQLAnalysis_joinIndices()
#3 Show joined-based tables with less than optimal indexes that support the JOIN specified in the query:
SELECT SchemaName, TableName, $LISTTOSTRING(JoinFields) AS "Index Needed", JoinIndexFlag AS "Join Index Flag", COUNT(*) AS "Query Count" FROM SYS_PTools.UtilSQLAnalysisDB WHERE JoinIndexFlag < 4 and OptionName = 'JI' GROUP BY SchemaName, TableName, IndexFields ORDER BY 4,5 DESC – These tables should be reviewed to see if a better – index can be added to fully support the JOIN conditions
NOTE: These queries can be invoked from a number of tools, such as the SQL Query tool in the 'Management Portal' or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as shown below: >do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] getSQLStmts - 1 = Get all the SQL Statements from InterSystems IRIS locations (Cached Queries, Class Methods, Class Queries, MAC Routines) and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing of this method NOTE: This is an all inclusive call which could be time consuming. The <class>SYS.PTools.UtilSQLStatements</class> class can populated via APIs that offer more precise collection alternatives which are less time consuming [DEFAULT: 0] skipSysObj - 0 = Don't skip all System Objects (Classes & Routines) 1 = Skip all System Objects (Classes & Routines) that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Objects that are not defined in the namespace in which this method is invoked 3 = Skip all System Objects defined by InterSystems, even if the object is also defined in the namespace in which this method is invoked NOTE-1: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) NOTE-2: This only applies when retrieving SQL Statements (getSQLStmts=1) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo("insert-cnt")=The number of rows inserted in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for queries that have joins indexing issues
RETURN Value: The status from the invocation of this method
|
static |
Identify all queries that have outliers, and determines if there is an index defined to support the Outlier Condition.
For each of the SQL Statements saved in the <class>SYS.PTools.UtilSQLStatements</class> class, identify all queries that have outliers, and determines if there is an index defined to support that outlier. It ranks the indices available to support the outlier from 0 (no index present) to 4 (index fully supports the outlier).
Method: outlierIndices [SQL: PTools_outlierIndices] Replaces: N/A Status: New Functionality Purpose: This method uses the SQL Statement data stored in the <class>SYS.PTools.UtilSQLStatements</class> class to pinpoint the queries that have outliers, and determines if there is an index defined to support the Outlier Condition. This method will then ranks the indices available to support the Outlier Condition from 0 (no index present) to 4 (index fully supports the Outlier Condition). Pertinent information about these queries is subsequently stored in the the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for future processing and analysis. While the result-set stored in the the <class>SYS.PTools.UtilSQLAnalysisDB</class> contains rows for all value of the 'OutlierIndexFlag' field, the outlierIndices() Query for this class/table only returns the rows that have the following <where-condition>: 'OutlierIndexFlag < 4'. Rows that have a 'OutlierIndexFlag = 4', which means that there exists an index that fully supports the Outlier Condition, are not returned by the outlierIndices() Query, since they are already fully optimized, however this information can be obtained by directly querying the SYS_PTools.UtilSQLAnalysisDB table. The stored queries should be reviewed to determine if an index could be added to the class to satisfy the highest 'OutlierIndexFlag' possible:
The 'OutlierIndexFlag' property has the following 5 values: 0 - No Match: No index exists to support the fields from the Outlier conditions (Some version of the suggested index should be created to improve this query's performance) 1 - Partial Match: An index exists where its fields contains some of the fields from the Outlier conditions, but not the leading field (This will produce poor performance and for that reason is rarely used) 2 - Contains Match: An index exists where its fields contains all fields from the Outlier conditions, but not the leading fields (This might produce OK performance, but improvements should be made) 3 - Leading Match: An index exists where its leading fields match all fields from the Outlier conditions, but there are additional fields in the index (This will produce OK performance, but improvements can be made) 4 - Exact Match: An index exists where its fields match all fields from the Outlier conditions (This is a fully optimized index)
NOTE: The fields returned by the query's 'IndexFields' could be used to create an index that should help improve performance.
Invocation: This method can be invoked in the following ways: ObjectScript: ##class(SYSTEM.SQL.PTools).outlierIndices(...) SQL: CALL SYSTEM_SQL.PTools_outlierIndices(...) SELECT SYSTEM_SQL.PTools_outlierIndices(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT SchemaName, TableName,
SQLPointer->Type, SQLPointer->Name,
$LISTTOSTRING(IndexFields) As "Index Fields",
JoinIndexFlag As "Join Index Flag",
ExtentSize, BlockCount As "Block Count",
SQLPointer->SQLTextExt AS "SQL Text"
FROM %SYS_PTools.UtilSQLAnalysisDB
WHERE OptionName = 'OI'
ORDER BY 1,2
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_outlierIndices()
NOTE: This query will return OutlierIndexFlag AS
"Outlier Index Flag" as a numeric value (0-3) as
specified above. However, in order to return more
specificity for this field, one of the following
values can be passed to the 2nd parameter
'indexFlagInfo' of the outlierIndices() query:
0 = The Index-Flag Internal Value [DEFAULT]
1 = The Index-Flag Title
2 = The Index-Flag Definition
3 = The Index-Flag as 'Title: Definition'
EXAMPLE:
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_outlierIndices(,3)
OR
SELECT SchemaName, TableName, Type, "Class/Routine Name",
IndexName, "Index Fields", "Bias Outlier",
"Outlier Index Flag", "Outlier Field",
"Outlier Condition", "Outlier Selectivity",
"Outlier WHERE Condition",
ExtentSize, "Block Count",
"SQL Text"
FROM %SYS_PTools.UtilSQLAnalysis_outlierIndices()
#3 Show outlier-based tables with less than optimal indexes that support the Outlier Condition specified in the query:
SELECT SchemaName, TableName, IndexFields As "Index Fields", OutlierIndexFlag AS "Outlier Index Flag", COUNT(*) AS "Query Count" FROM SYS_PTools.UtilSQLAnalysisDB WHERE OutlierIndexFlag < 4 and OptionName = 'OI' GROUP BY SchemaName, TableName, IndexFields ORDER BY 4,5 DESC – These tables should be reviewed to see if a better – index can be added to fully support the Outlier Conditions
NOTE: These queries can be invoked from a number of tools, such as the SQL Query tool in the 'Management Portal' or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as shown below: >do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] getSQLStmts - 1 = Get all the SQL Statements from InterSystems IRIS locations (Cached Queries, Class Methods, Class Queries, MAC Routines) and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing of this method NOTE: This is an all inclusive call which could be time consuming. The <class>SYS.PTools.UtilSQLStatements</class> class can populated via APIs that offer more precise collection alternatives which are less time consuming [DEFAULT: 0] skipSysObj - 0 = Don't skip all System Objects (Classes & Routines) 1 = Skip all System Objects (Classes & Routines) that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Objects that are not defined in the namespace in which this method is invoked 3 = Skip all System Objects defined by InterSystems, even if the object is also defined in the namespace in which this method is invoked NOTE-1: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) NOTE-2: This only applies when retrieving SQL Statements (getSQLStmts=1) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo("insert-cnt")=The number of rows inserted in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for queries that have outliers indexing issues
RETURN Value: The status from the invocation of this method
|
static |
Set the SQLStats-flag that controls whether or not the System collects SQL Statistics about each run of a query.
The following methods are defined in the <class>SYS.PTools.StatsSQL</class> class and are designed to gather performance statistics for SQL Queries. Additional details can be found within the defining class.
Method: setSQLStatsFlag [SQL: PTools_setSQLStatsFlag] Purpose: This method sets the flag that controls whether or not the System collects SQL Statistics about each run of a query
You can invoke different levels of SQL Statistics collection by setting the SQLStats-flag, for the System with this method.
The SQLStats-flag controls whether or not SQL Statistics are collected for each SQL Query execution, and which performance statistics to collect.
The SQLStats-flag is a colon (:) delimited string comprised of the following individual components:
SQLStats-flag={action-flag}:{collect-flag}:{condition-flag}:{condition-value}:{terminate-flag}:{flag-type}
Invocation: This method can be invoked in the following ways: Object Script: $SYSTEM.SQL.PTools.setSQLStatsFlag(...) SQL: SELECT SYSTEM_SQL.PTools_setSQLStatsFlag(...)
Examples: The following examples shows the use of this method:
#1 Turn PTools ON to collects stats for all SQL modules (System):
set oldStats=$SYSTEM.SQL.PTools.setSQLStatsFlag(3)
Parameters: actionFlag - The portion of the SQLStats-flag which is represented by the
1st colon (:) piece, and can have one of the following values: 0 = Query Compilation: Don't generator SQLStats collection code for any Query Modules Query Execution: Don't collect SQLStats for any Query Modules 1 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Don't collect SQLStats for any Query Modules 2 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Collect SQLStats for MAIN Query Module (Start & Stop) 3 = Query Compilation: Generator SQLStats collection code for ALL Query Modules Query Execution: Collect SQLStats for ALL Query Modules collectFlag - The portion of the SQLStats-flag which is represented by the 2nd colon (:) piece, and is a numeric value representing which SQL Performance Statistics/Metrics to collect, with one of the following values: "" = Collect All SQL Performance Metrics [DEFAULT] n = Where n=SUM(MVal) [See Below]
In general, all of the following performance metrics are collected for each SQL module, along with a cumulative value representing all SQL modules, when the SQLStats-flag is turned on:
MVal Metric Name Metric Description
1 Query Execution Time Total number of seconds elapsed 2 Total Global References Total number of global references 4 Total Lines of Code Executed Total number of COS lines executed 8 Total Disk Read Latency Time Total milliseconds spent waiting ==== for Disk Reads 15 ALL Collect all Performance Metrics
This parameter provides a mechanism by which to choose a combination of which performance metrics to collect, by specifying a SUM of the performance metrics MVal numbers (specified above) that you wish to collect.
EXAMPLE #1: The following example represents the collection of 2 performance metrics, 'Query Execution Time' & 'Total Disk Read Latency Time':
MVal Metric Name
1 Query Execution Time
9 Collect both of these performance metrics
By passing 9 for the value of the 'collectFlag' parameter, the sum of the two aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked.
EXAMPLE #2: The following example represents the collection of 3 performance metrics, 'Query Execution Time', 'Total Global References' & 'Total Lines of Code Executed':
MVal Metric Name
1 Query Execution Time 2 Total Global References
7 Collect both of these performance metrics
By passing 7 for the value of the 'collectFlag' parameter, the sum of the three aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked. terminateCond - The portion of the SQLStats-flag which is represented by the 5th colon (:) piece, and is determined by this parameter value. An optional condition to determine when to terminate the SQLStats collection, by turning off the SQLStats-flag (System), or by setting it to a specified reset value. This parameter accepts the following values: 0 No Action [DEFAULT] M:<min>:<raf> Where <min>=# of minutes from 1..n When specified, this value will terminate the SQLStats collection the number of minutes <min> after the current $H Where <raf>=Reset {action-flag} value from 0..3 When specified, this is the value to which the {action-flag} portion of the SQLStats-flag will be set upon expiration If not specified, default <raf> to zero (0) (e.g. "M:120:1" => Terminate 120minutes after the current $H and reset SQLStats-flag/{action-flag} to 1) T:<ts>:<raf> Where <ts>=Timestamp with the format: YYYYMMDD HHMM When specified, this value will terminate the SQLStats collection after the timestamp value Where <raf>=Reset {action-flag} value from 0..3 When specified, this is the value to which the {action-flag} portion of the SQLStats-flag will be set upon expiration If not specified, default <raf> to zero (0) (e.g. "T:20171018 1330:1" => Terminate after 10/18/2017 01:30PM and reset SQLStats-flag/{action-flag} to 1) ptInfo - A Pass By Reference information array that returns to the user detailed information in the following format: ptInfo(category,variable)=value Where category = { "current" | "terminate" | ... } variable = A variable that corresponds to the given 'category'
Example: ptInfo("current","SQLStatsFlag")=The SQLStats-flag value after method execution
RETURN: The value of the SQLStats-flag before setting it to the new value; Otherwise, return an error message if an error occurred
|
static |
Set the flag that controls whether or not to collect SQL Statistics about each run of a query within the given 'ns' (namespace)
Method: setSQLStatsFlagByNS [SQL: PTools_setSQLStatsFlagByNS] Purpose: This method sets the flag that controls whether or not to collect SQL Statistics about each run of a query within the given 'ns' (Namespace)
You can invoke different levels of SQL Statistics collection by setting the SQLStats-flag, for a given 'ns'.
The SQLStats-flag (System) controls whether or not SQL Statistics are collected for each SQL Query execution, and which performance statistics to be collected.
The SQLStats-flag is a colon (:) delimited string comprised of the following individual components:
SQLStats-flag={action-flag}:{collect-flag}:{condition-flag}:{condition-value}:{terminate-flag}:{flag-type}
NOTE: This method ONLY applies to the SQLStats-flag (System) for the given 'namespace' and NOT the SQLStats-flag (Process/Job)!
Invocation: This method can be invoked in the following ways: Object Script: $SYSTEM.SQL.PTools.setSQLStatsFlagByNS(...) SQL: SELECT SYSTEM_SQL.PTools_setSQLStatsFlagByNS(...)
Examples: The following examples shows the use of this method:
#1 Turn PTools ON to collects stats for all SQL modules within the "USER" Namespace:
set oldStats=$SYSTEM.SQL.PTools.setSQLStatsFlagByNS("USER",3)
Parameters: ns - The Namespace ($NAMESPACE) for which to set the SQLStats-flag [REQUIRED] actionFlag - The portion of the SQLStats-flag which is represented by the 1st colon (:) piece, and can have one of the following values: 0 = Query Compilation: Don't generator SQLStats collection code for any Query Modules Query Execution: Don't collect SQLStats for any Query Modules 1 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Don't collect SQLStats for any Query Modules 2 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Collect SQLStats for MAIN Query Module (Start & Stop) 3 = Query Compilation: Generator SQLStats collection code for ALL Query Modules Query Execution: Collect SQLStats for ALL Query Modules collectFlag - The portion of the SQLStats-flag which is represented by the 2nd colon (:) piece, and is a numeric value representing which SQL Performance Statistics/Metrics to collect, with one of the following values: "" = Collect All SQL Performance Metrics [DEFAULT] n = Where n=SUM(MVal) [See Below]
In general, all of the following performance metrics are collected for each SQL module, along with a cumulative value representing all SQL modules, when the SQLStats-flag is turned on:
MVal Metric Name Metric Description
1 Query Execution Time Total number of seconds elapsed 2 Total Global References Total number of global references 4 Total Lines of Code Executed Total number of COS lines executed 8 Total Disk Read Latency Time Total milliseconds spent waiting ==== for Disk Reads 15 ALL Collect all Performance Metrics
This parameter provides a mechanism by which to choose a combination of which performance metrics to collect, by specifying a SUM of the performance metrics MVal numbers (specified above) that you wish to collect.
EXAMPLE #1: The following example represents the collection of 2 performance metrics, 'Query Execution Time' & 'Total Disk Read Latency Time':
MVal Metric Name
1 Query Execution Time
9 Collect both of these performance metrics
By passing 9 for the value of the 'collectFlag' parameter, the sum of the two aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked.
EXAMPLE #2: The following example represents the collection of 3 performance metrics, 'Query Execution Time', 'Total Global References' & 'Total Lines of Code Executed':
MVal Metric Name
1 Query Execution Time 2 Total Global References
7 Collect both of these performance metrics
By passing 7 for the value of the 'collectFlag' parameter, the sum of the three aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked. terminateCond - The portion of the SQLStats-flag which is represented by the 5th colon (:) piece, and is determined by this parameter value. An optional condition to determine when to terminate the SQLStats collection, by turning off the SQLStats-flag (System), or by setting it to a specified reset value. This parameter accepts the following values: 0 No Action [DEFAULT] M:<min>:<raf> Where <min>=# of minutes from 1..n When specified, this value will terminate the SQLStats collection the number of minutes <min> after the current $H Where <raf>=Reset {action-flag} value from 0..3 When specified, this is the value to which the {action-flag} portion of the SQLStats-flag will be set upon expiration If not specified, default <raf> to zero (0) (e.g. "M:120:1" => Terminate 120minutes after the current $H and reset SQLStats-flag/{action-flag} to 1) T:<ts>:<raf> Where <ts>=Timestamp with the format: YYYYMMDD HHMM When specified, this value will terminate the SQLStats collection after the timestamp value Where <raf>=Reset {action-flag} value from 0..3 When specified, this is the value to which the {action-flag} portion of the SQLStats-flag will be set upon expiration If not specified, default <raf> to zero (0) (e.g. "T:20171018 1330:1" => Terminate after 10/18/2017 01:30PM and reset SQLStats-flag/{action-flag} to 1) ptInfo - A Pass By Reference information array that returns to the user detailed information in the following format: ptInfo(category,variable)=value Where category = { "current" | "terminate" | ... } variable = A variable that corresponds to the given 'category'
Example: ptInfo("current","SQLStatsFlag")=The SQLStats-flag value after method execution
RETURN: The value of the SQLStats-flag before setting it to the new value; Otherwise, return an error message if an error occurred
|
static |
Set the SQLStats-flag that controls whether or not to collect SQL Statistics about each run of a query for the given 'pid'.
Method: setSQLStatsFlagByPID [SQL: PTools_setSQLStatsFlagByPID] Purpose: This method sets the flag that controls whether or not to collect SQL Statistics about each run of a query for the given 'pid'
You can invoke different levels of SQL Statistics collection by setting the SQLStats-flag, for a given 'pid'.
The SQLStats-flag (Process/Job) controls whether or not SQL Statistics are collected for each SQL Query execution, and which performance statistics to be collected.
The SQLStats-flag is a colon (:) delimited string comprised of the following individual components:
SQLStats-flag={action-flag}:{collect-flag}:{condition-flag}:{condition-value}:{terminate-flag}:{flag-type}
NOTE: This method ONLY applies to the SQLStats-flag for the given 'pid' (Process/Job) and NOT the SQLStats-flag for the (System)!
RESTRICTION: This method invocation requires Admin_Operate:Use privilege
Invocation: This method can be invoked in the following ways: Object Script: $SYSTEM.SQL.PTools.setSQLStatsFlagByPID(...) SQL: SELECT SYSTEM_SQL.PTools_setSQLStatsFlagByPID(...)
Examples: The following examples shows the use of this method:
#1 Turn PTools ON to collects stats for all SQL modules for PID# 12345:
set oldStats=$SYSTEM.SQL.PTools.setSQLStatsFlagByPID(12345,3)
Parameters: pid - The process ID ($JOB) for which to set the SQLStats-flag [DEFAULT: Current $JOB] actionFlag - The portion of the SQLStats-flag which is represented by the 1st colon (:) piece, and can have one of the following values: -1 = Query Compilation: Turn SQLStats Off for the given 'pid' Query Execution: Turn SQLStats Off for the given 'pid' 0 = Query Compilation: Use the {action-flag} (System) setting Query Execution: Use the {action-flag} (System) setting 1 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Don't collect SQLStats for any Query Modules 2 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Collect SQLStats for MAIN Query Module (Start & Stop) 3 = Query Compilation: Generator SQLStats collection code for ALL Query Modules Query Execution: Collect SQLStats for ALL Query Modules collectFlag - The portion of the SQLStats-flag which is represented by the 2nd colon (:) piece, and is a numeric value representing which SQL Performance Statistics/Metrics to collect, with one of the following values: "" = Collect All SQL Performance Metrics [DEFAULT] n = Where n=SUM(MVal) [See Below]
In general, all of the following performance metrics are collected for each SQL module, along with a cumulative value representing all SQL modules, when the SQLStats-flag is turned on:
MVal Metric Name Metric Description
1 Query Execution Time Total number of seconds elapsed 2 Total Global References Total number of global references 4 Total Lines of Code Executed Total number of COS lines executed 8 Total Disk Read Latency Time Total milliseconds spent waiting ==== for Disk Reads 15 ALL Collect all Performance Metrics
This parameter provides a mechanism by which to choose a combination of which performance metrics to collect, by specifying a SUM of the performance metrics MVal numbers (specified above) that you wish to collect.
EXAMPLE #1: The following example represents the collection of 2 performance metrics, 'Query Execution Time' & 'Total Disk Read Latency Time':
MVal Metric Name
1 Query Execution Time
9 Collect both of these performance metrics
By passing 9 for the value of the 'collectFlag' parameter, the sum of the two aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked.
EXAMPLE #2: The following example represents the collection of 3 performance metrics, 'Query Execution Time', 'Total Global References' & 'Total Lines of Code Executed':
MVal Metric Name
1 Query Execution Time 2 Total Global References
7 Collect both of these performance metrics
By passing 7 for the value of the 'collectFlag' parameter, the sum of the three aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked. ptInfo - A Pass By Reference information array that returns to the user detailed information in the following format: ptInfo(category,variable)=value
NOTE: This method currently returns no 'ptInfo', but is included for future extensibility
RETURN: The value of the SQLStats-flag before setting it to the new value; Otherwise, return an error message if an error occurred
|
static |
Set the SQLStats-flag that controls whether or not this Process/Job collects SQL Statistics about each run of a query.
Method: setSQLStatsFlagJob [SQL: PTools_setSQLStatsFlagJob] Purpose: This method sets the flag that controls whether or not this Process/Job collects SQL Statistics about each run of a query
You can invoke different levels of SQL Statistics collection by setting the SQLStats-flag, for your current Process/Job with this method.
The SQLStats-flag controls whether or not SQL Statistics are collected for each SQL Query execution, and which performance statistics to collect.
The SQLStats-flag is a colon (:) delimited string comprised of the following individual components:
SQLStats-flag={action-flag}:{collect-flag}:{condition-flag}:{condition-value}:{terminate-flag}:{flag-type}
Invocation: This method can be invoked in the following ways: Object Script: $SYSTEM.SQL.PTools.setSQLStatsFlagJob(...) SQL: SELECT SYSTEM_SQL.PTools_setSQLStatsFlagJob(...)
Examples: The following examples shows the use of this method:
#1 Turn PTools ON to collects stats for all SQL modules:
set oldStats=$SYSTEM.SQL.PTools.setSQLStatsFlagJob(3)
Parameters: actionFlag - The portion of the SQLStats-flag which is represented by the 1st colon (:) piece, and can have one of the following values: -1 = Query Compilation: Turn SQLStats Off for this Process/Job Query Execution: Turn SQLStats Off for this Process/Job [-1 ONLY when flagType=1] 0 = Query Compilation: Use the {action-flag} (System) setting Query Execution: Use the {action-flag} (System) setting 1 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Don't collect SQLStats for any Query Modules 2 = Query Compilation: Generator SQLStats collection code for MAIN Query Module (Start & Stop) Query Execution: Collect SQLStats for MAIN Query Module (Start & Stop) 3 = Query Compilation: Generator SQLStats collection code for ALL Query Modules Query Execution: Collect SQLStats for ALL Query Modules collectFlag - The portion of the SQLStats-flag which is represented by the 2nd colon (:) piece, and is a numeric value representing which SQL Performance Statistics/Metrics to collect, with one of the following values: "" = Collect All SQL Performance Metrics [DEFAULT] n = Where n=SUM(MVal) [See Below]
In general, all of the following performance metrics are collected for each SQL module, along with a cumulative value representing all SQL modules, when the SQLStats-flag is turned on:
MVal Metric Name Metric Description
1 Query Execution Time Total number of seconds elapsed 2 Total Global References Total number of global references 4 Total Lines of Code Executed Total number of COS lines executed 8 Total Disk Read Latency Time Total milliseconds spent waiting ==== for Disk Reads 15 ALL Collect all Performance Metrics
This parameter provides a mechanism by which to choose a combination of which performance metrics to collect, by specifying a SUM of the performance metrics MVal numbers (specified above) that you wish to collect.
EXAMPLE #1: The following example represents the collection of 2 performance metrics, 'Query Execution Time' & 'Total Disk Read Latency Time':
MVal Metric Name
1 Query Execution Time
9 Collect both of these performance metrics
By passing 9 for the value of the 'collectFlag' parameter, the sum of the two aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked.
EXAMPLE #2: The following example represents the collection of 3 performance metrics, 'Query Execution Time', 'Total Global References' & 'Total Lines of Code Executed':
MVal Metric Name
1 Query Execution Time 2 Total Global References
7 Collect both of these performance metrics
By passing 7 for the value of the 'collectFlag' parameter, the sum of the three aforementioned performance metrics MVal numbers, the SQLStats PTool application will only collect statistical data for these two performance metrics whenever an SQL Query is invoked. p3 - Placeholder Parameter for future extensibility ptInfo - A Pass By Reference information array that returns to the user detailed information in the following format: ptInfo(category,variable)=value Where category = { "current" | "terminate" | ... } variable = A variable that corresponds to the given 'category'
Example: ptInfo("current","SQLStatsFlag")=The SQLStats-flag value after method execution
RETURN: The value of the SQLStats-flag before setting it to the new value; Otherwise, return an error message if an error occurred
|
static |
This method is used to START the PTools statistics collection.
General Stats Methods
The following methods are defined in the <class>SYS.PTools.Stats</class> class and are designed to gather performance statistics for any type of routine or code block. Additional details can be found within the defining class.
Method: startGeneralStats Replaces: N/A Status: Original Functionality Purpose: This method is used to START the PTools statistics collection
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.startGeneralStats(...) SQL: N/A
Examples: The following examples shows the use of this method:
#1 Start collecting stats to analyze the class 'Populate' method:
do $SYSTEM.SQL.PTools.startGeneralStats($NAMESPACE,"Test","Populate")
do ##class(Sample.Person).Populate(100)
do $SYSTEM.SQL.PTools.stopGeneralStats($NAMESPACE,"Test","Populate")
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: ns - The namespace in which the stats collection is occurring rtn - The routine name for which the stats collection is occurring mod - The module name for which the stats collection is occurring [DEFAULT: 1]
RETURN Value: (NONE)
|
static |
This method is used to STOP the PTools statistics collection.
Method: stopGeneralStats Replaces: N/A Status: Original Functionality Purpose: This method is used to STOP the PTools statistics collection This method INSERTs the stats information into the SYS_PTools.Stats table
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.stopGeneralStats(...) SQL: N/A
Examples: The following examples shows the use of this method:
#1 Stop collecting stats to analyze the class 'Populate' method:
do $SYSTEM.SQL.PTools.startGeneralStats($NAMESPACE,"Test","Populate")
do ##class(Sample.Person).Populate(100)
do $SYSTEM.SQL.PTools.stopGeneralStats($NAMESPACE,"Test","Populate")
Data Storage: ^sqlcq($NAMESPACE,"PTools","db","Stats{C|D|I|S|Z}")
Parameters: ns - The namespace in which the stats collection is occurring rtn - The routine name for which the stats collection is occurring mod - The module name for which the stats collection is occurring [DEFAULT: 1]
RETURN Value: (NONE)
|
static |
Identify all queries that perform a table scan.
For each of the SQL Statements saved in the <class>SYS.PTools.UtilSQLStatements</class> class, identify all queries that do table scans. Table scans should be avoided if at all possible, but a table scan can't always be avoided. However, if a table has a large number of table scans, the indices defined for that table should be reviewed. Often the list of table scans and the list of temp indices will overlap; fixing one will remove the other. The result set lists the tables from largest Block Count to smallest Block Count.
Method: tableScans [SQL: PTools_tableScans] Replaces: TableScans SQL: TableScans <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: This method uses the SQL Statement data stored in the <class>SYS.PTools.UtilSQLStatements</class> class to pinpoint the queries that perform a table scan, which could be over an index or the master map.
Pertinent information about these queries is subsequently stored in the the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for future processing and analysis. For some queries a table scan can't be avoided, but any query that uses such a scan should be reviewed in order to determine if an index could be added for performance optimizations.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.tableScans(...) SQL: CALL SYSTEM_SQL.PTools_tableScans(...) SELECT SYSTEM_SQL.PTools_tableScans(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT SQLPointer->Type As "Routine Type",
SQLPointer->Name As "Routine Name",
SchemaName, TableName, ModuleName,
ExtentSize,
SQLPointer->SQLTextExt AS "SQL Text"
FROM %SYS_PTools.UtilSQLAnalysisDB
WHERE OptionName = 'TS'
ORDER BY ExtentSize DESC
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_tableScans()
OR
SELECT SchemaName, TableName, Type, "Class/Routine Name",
ModuleName, "Map Type" , ExtentSize, "Block Count",
"SQL Text"
FROM %SYS_PTools.UtilSQLAnalysis_tableScans()
NOTE: These queries can be invoked from a number of tools,
such as the SQL Query tool in the 'Management Portal'
or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as
shown below:
>do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] getSQLStmts - 1 = Get all the SQL Statements from InterSystems IRIS locations (Cached Queries, Class Methods, Class Queries, MAC Routines) and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing of this method NOTE: This is an all inclusive call which could be time consuming. The <class>SYS.PTools.UtilSQLStatements</class> class can populated via APIs that offer more precise collection alternatives which are less time consuming [DEFAULT: 0] skipSysObj - 0 = Don't skip all System Objects (Classes & Routines) 1 = Skip all System Objects (Classes & Routines) that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Objects that are not defined in the namespace in which this method is invoked 3 = Skip all System Objects defined by InterSystems, even if the object is also defined in the namespace in which this method is invoked NOTE-1: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) NOTE-2: This only applies when retrieving SQL Statements (getSQLStmts=1) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo("insert-cnt")=The number of rows inserted in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for queries that require a full table scan
RETURN Value: The status from the invocation of this method
|
static |
Identify all queries that build a Temp Index/Table.
For each of the SQL Statements saved in the <class>SYS.PTools.UtilSQLStatements</class> class, identify all queries that build temporary indices to resolve the SQL. Sometimes the use of a temp index is helpful and improves performance, for example building a small index based on a range condition that InterSystems IRIS can then use to read the master map in order. Sometimes a temp index is simply a subset of a different index and might be very efficient. Other times a temporary index degrades performance, for example scanning the master map to build a temporary index on a property that has a condition. This situation indicates that a needed index is missing; you should add an index to the class that matches the temporary index. The result set lists the tables from largest Block Count to smallest Block Count.
Method: tempIndices [SQL: PTools_tempIndices] Replaces: TempIndices SQL: TempIndices <DEP>[DEPRECATED]</DEP> Status: New Method to replicate Backward-Compatible Method it 'Replaces' Purpose: This method uses the SQL Statement data stored in the <class>SYS.PTools.UtilSQLStatements</class> class to pinpoint the queries that are building a Temp Index/Table.
Pertinent information about these queries is subsequently stored in the the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for future processing and analysis. It's worth noting that the results of this method and that of the 'tableScans()' method might have a large overlap. For some queries the creation of a Temp Index/Table can be avoided, but often the creation of a Temp Index/Table is done so to provide optimal data traversal and retrieval. These queries should be reviewed to determine if an index could be added to the class for performance optimizations, because often the structure of the Temp Index/Table is the basis for the creation of a class index to help with query performance.
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.tempIndices(...) SQL: CALL SYSTEM_SQL.PTools_tempIndices(...) SELECT SYSTEM_SQL.PTools_tempIndices(...)
NOTE: This 'SqlProc' method can be invoked with either the CALL-interface or the SELECT-interface. Both interfaces execute the method: the CALL-interface does not return any resulting value, while the SELECT-interface does.
Examples: The following examples provide analytical information produced from the invocation of this method:
#1 Show info from where the SQL Statements were collected:
SELECT %EXACT(Type) AS QueryType, Count(*) AS QueryCount
FROM %SYS_PTools.UtilSQLStatements
GROUP BY Type
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_countSQLStmtTypes()
#2 Show the data collected from the running of this method:
SELECT SchemaName, TableName,
$LISTTOSTRING(IndexFields) As "Index Fields",
$LISTTOSTRING(DataValues) As "Data Fields",
ExtentSize, BlockCount As "Block Count",
SQLPointer->SQLTextExt AS "SQL Text"
FROM %SYS_PTools.UtilSQLAnalysisDB
WHERE OptionName = 'TI'
ORDER BY ExtentSize DESC
OR
SELECT * FROM %SYS_PTools.UtilSQLAnalysis_tempIndices()
OR
SELECT SchemaName, TableName, Type, "Class/Routine Name",
IndexName, "Index Fields", "Data Fields",
ExtentSize, "Block Count",
"SQL Text"
FROM %SYS_PTools.UtilSQLAnalysis_tempIndices()
NOTE: These queries can be invoked from a number of tools,
such as the SQL Query tool in the 'Management Portal'
or via 'SQL Query Shell' within a 'InterSystems IRIS Terminal' as
shown below:
>do $SYSTEM.SQL.Shell()
Data Storage: ^sqlcq($NAMESPACE,"PTools","util","SQLAnlsys","{C|D|I|S}")
Parameters: clearData - 1 = Kill all of the existing data before re-populating with the results of this method invocation [DEFAULT: 1] getSQLStmts - 1 = Get all the SQL Statements from InterSystems IRIS locations (Cached Queries, Class Methods, Class Queries, MAC Routines) and add them to the <class>SYS.PTools.UtilSQLStatements</class> class for additional processing of this method NOTE: This is an all inclusive call which could be time consuming. The <class>SYS.PTools.UtilSQLStatements</class> class can populated via APIs that offer more precise collection alternatives which are less time consuming [DEFAULT: 0] skipSysObj - 0 = Don't skip all System Objects (Classes & Routines) 1 = Skip all System Objects (Classes & Routines) that start with: { % | DeepSee | Ens | HS | INFORMATION{.|_}SCHEMA } 2 = Skip all System Objects that are not defined in the namespace in which this method is invoked 3 = Skip all System Objects defined by InterSystems, even if the object is also defined in the namespace in which this method is invoked NOTE-1: Pass the combination of the specified options if more than one option desired (e.g. 13 => #1 & #3) NOTE-2: This only applies when retrieving SQL Statements (getSQLStmts=1) [DEFAULT: 1] skipInsStmts - 1 = Skip INSERT Statements, as they don't have looping logic [DEFAULT: 1] display - 1 = Display messages while processing method [DEFAULT: 1] ptInfo - A Pass By Reference information array that returns to the user the following details: ptInfo("insert-cnt")=The number of rows inserted in the <class>SYS.PTools.UtilSQLAnalysisDB</class> class for queries that build temporary indices to resolve the SQL.
RETURN Value: The status from the invocation of this method
|
static |
Method: versionSQLAnalysis [SQL: PTools_versionSQLAnalysis] Replaces: N/A Status: New Functionality Purpose: Get the current version for the <class>SYS.PTools.UtilSQLStatements</class> & <class>SYS.PTools.UtilSQLAnalysisDB</class> classes/sections of the Performance Tools (PTools) Application...
Invocation: This method can be invoked in the following ways: ObjectScript: $SYSTEM.SQL.PTools.versionSQLAnalysis(...) SQL: SELECT SYSTEM_SQL.PTools_versionSQLAnalysis(...)
Examples: The following examples shows the use of this method:
#1 Display the UtilSQLAnalysis version to the screen via an InterSystems IRIS Terminal:
write $SYSTEM.SQL.PTools.versionSQLAnalysis() // Simple Version write $SYSTEM.SQL.PTools.versionSQLAnalysis(1) // Full Version
#2 Display the UtilSQLAnalysis version via the SQL Query Page of the Management Portal:
SELECT SYSTEM_SQL.PTools_versionSQLAnalysis() /* Simple Version */ SELECT SYSTEM_SQL.PTools_versionSQLAnalysis(1) /* Full Version */
Data Storage: N/A
Parameters: fullVer - 0 = Display the UtilSQLAnalysis Simple Version [DEFAULT] 1 = Display the UtilSQLAnalysis Full Version
RETURN Value: The UtilSQLAnalysis {Simple | Full} Version
1.9.1