HP Neoview Workload Management Services Guide HP Part Number: 544806-001 Published: April 2008 Edition: HP Neoview Release 2.
© Copyright 2008 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.......................................................................................................11 Intended Audience................................................................................................................................11 New and Changed Information in This Edition...................................................................................11 Document Organization.......................................................................
Associating Queries With Services............................................................................35 Specifying a Service in a Client Data Source........................................................................................35 Setting the Service in the ODBC Administrator on a Windows Workstation.................................35 Setting the Service in the MXODSN File on a Linux or UNIX Workstation...................................
Considerations.................................................................................................................................63 Examples..........................................................................................................................................63 HOLD Command..................................................................................................................................63 Syntax..................................................................
List of Figures 1-1 1-2 1-3 Execution of Queries Through WMS............................................................................................17 How WMS Handles an Incoming Query......................................................................................18 How WMS Maps a Service to a Query..........................................................................................
List of Tables A-1 A-2 A-3 A-4 A-5 A-6 A-7 A-8 A-9 A-10 A-11 A-12 INFO SERVICE Command Output...............................................................................................64 INFO WMS Command Output.....................................................................................................65 System Status Information............................................................................................................68 System Version Information...............................
About This Document This manual describes how to use the Neoview Workload Management Services (WMS) to perform workload and resource management on a Neoview data warehousing platform. WMS commands enable you to define service levels and resource thresholds, monitor system resources, and manage queries. Intended Audience This manual is intended for customers who are using WMS to manage workload on a Neoview data warehousing platform.
ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. [ ] Brackets Brackets enclose optional syntax items. For example: DATETIME [start-field TO] end-field A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
@script-file Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "{" module-name [, module-name]... "}" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: DAY (datetime-expression) DAY(datetime-expression) If there is no space between two items, spaces are not permitted.
Neoview Management Dashboard Information on using the Dashboard Client, including how to install the Client, Client Guide for Database start and configure the Client Server Gateway (CSG), use the Client windows Administrators and property sheets, interpret entity screen information, and use Command and Control to manage queries from the Client. Neoview Management Dashboard Online Help Context-sensitive help topics that describe how to use the Neoview Management Dashboard Client.
Publishing History Part Number Product Version Publication Date 544357-002 HP Neoview Release 2.0 (beta) April 2007 544587–001 HP Neoview Release 2.2 (beta) August 2007 544806–001 HP Neoview Release 2.3 April 2008 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: pubs.comments@hp.
1 Introducing Neoview Workload Management Services (WMS) The Neoview Workload Management Services (WMS) feature provides the infrastructure to help you manage system and service-level resources for executing queries on a Neoview platform. You can configure service levels in WMS to prioritize and set rules for groups of queries (that is, query workloads) executing on the Neoview platform.
When a query is submitted to the Neoview platform, the NDCS server passes the execution decision making to WMS. Figure 1-2 shows how WMS handles an incoming query. Figure 1-2 How WMS Handles an Incoming Query When handling an incoming query, WMS first checks that WMS is in the active state. WMS is inactive when a user places it on hold by using the HOLD command. For more information, see the “HOLD Command” (page 63).
If the total number of queries in WMS is less than or equal to the limit, WMS maps the query to a service level. WMS maps the query to a service level based on the attribute set by the NDCS server. If you set a service for the client session or the query, WMS executes the query in that service. If you do not set a service for the client session or query, WMS searches for a service name that matches the second part of the client role, such as MGR from ROLE.MGR.
WMS obtains compile-time information about the query from the NDCS server, such as the query ID, CPU time, I/O time, messages time, idle time, total time, and cardinality. At preconfigured intervals, WMS also captures system resource information, such as the CPU busy, memory usage, query cache hits, and disk I/O, and also captures query runtime statistics.
Dashboard Client enables you to suspend (hold) , resume (release), and kill (cancel) queries displayed in the QueryRTS entity. For more information, see the Neoview Management Dashboard Client Guide for Database Administrators.
2 Getting Started • • “Installing and Starting WMS on the Neoview Platform” (page 23) “Installing the Neoview Command Interface (NCI)” (page 23) Installing and Starting WMS on the Neoview Platform If you have Neoview Release 2.3, WMS should already be installed and started on your Neoview platform. If you are an HP support person, see the Neoview Database Support Guide for information about installing and starting WMS on a Neoview platform.
3 Configuring WMS • • • “How Services Work” (page 25) “Configuring User-Defined Services” (page 29) “Configuring the WMS System Configuration” (page 33) How Services Work • • • “What Are Services?” (page 25) “How Service Priorities and System Resource Thresholds Work” (page 25) “Effect of Service-Level Thresholds” (page 29) What Are Services? Service levels are a mechanism in WMS to enable you to prioritize query workloads on a Neoview platform and to partition available workload resources.
higher priority services are currently executing, the queries associated with the lower priority service execute next, provided that the system resource usage has not reached its limits. WMS throttles incoming queries (that is, puts them into a waiting queue) when the system resource usage reaches its limits.
Consider the system resource usage when queries associated with those services request to be executed on the system: Service Name Total Queries CPU Busy Maximum CPU Busy Memory Usage Maximum Memory Usage SERVICE1 80 50% 100% 60% 85% SERVICE2 20 50% 100% 60% 85% SERVICE3 25 50% 100% 60% 85% Because the system resources are within the limits (100% for CPU busy and 85% for memory usage), WMS allows all incoming queries to start executing.
executing first.
queries and then 30 medium-priority SERVICE2 queries in the waiting queue to start executing until the system resources reach their limits: Service Name Total Queries Executing Queries Percentage of All Expected Waiting Queries Executing Queries Percentage Based on Priority Weight SERVICE1 60 0+50=50 50/90 = 56% 56% 60–50=10 SERVICE2 30 0+30=30 30/90 = 33% 33% 30–30=0 SERVICE3 30 10 10/90 = 11% 11% 10 Effect of Service-Level Thresholds For each service level, you can set system resource
• PRIORITY MEDIUM-HIGH • PRIORITY MEDIUM • PRIORITY LOW-MEDIUM • PRIORITY LOW If you do not specify a priority for the service, the default priority is medium. Setting the System Resource Thresholds of the Service You can set these system resource thresholds for the service: • MAX_CPU_BUSY, which is a percentage from zero to 100 of the total CPU busy allowed for the service. This value is an average of CPU busy across all segments in the cluster.
Specify the TEXT option to collect the SQL syntax of queries executing in the service. Client tools, such as NCI and the Neoview Manageability Repository can then use and display this data. If you do not specify TEXT, WMS does not collect any SQL text for the service (that is NO_TEXT). Adding a Comment for the Service You can optionally provide text to describe the service that you are creating.
Changing the EXEC_TIMEOUT, WAIT_TIMEOUT, PLAN, and TEXT parameters does not affect the currently executing or waiting queries associated with the service. However, changing these settings does affect new incoming queries associated with the service. Deleting a Service Use the DELETE SERVICE command to delete a service from the WMS configuration.
For example, in NCI, this INFO SERVICE command displays configuration information for all services in WMS: NS%info service all; SERVICE_NAME SERVICE_PRIORITY MAX_CPU_BUSY MAX_MEM_USAGE ACTIVE_TIME SQL_PLAN SQL_TEXT EXEC_TIMEOUT WAIT_TIMEOUT COMMENT -------------------------------------------------- ---------------- ------------ -------------------------------------------------------------- -------- -------- ------------ --------------------------------------------------------------------------------------
Altering the WMS System Configuration Use the ALTER WMS command to alter the WMS system configuration (that is, the SYSTEM service), which includes the maximum CPU busy, the maximum memory usage, and the refresh interval for query runtime statistics. • For MAX_CPU_BUSY, specify a percentage for the maximum CPU busy of all CPUs on the system. The default value is zero, meaning that WMS uses the internal value of 100 percent.
4 Associating Queries With Services If you do not associate an SQL query with a service, WMS first looks for a service name that matches the second part of the client role, such as MGR in ROLE.MGR. If WMS finds a service name that matches the client role, WMS manages the query in that service. If WMS does not find a service name that matches the client role, WMS manages the query in the default service, HP_DEFAULT_SERVICE.
NOTE: The ODBC Data Source Administrator and WMS support multibyte characters in the service name. For guidelines on using multibyte character sets, see the Neoview Character Sets Administrator's Guide. 1. Select Start→All Programs→HP ODBC 2.0→MS ODBC Administrator. The ODBC Data Source Administrator dialog box appears: 36 2. 3. 4. Under the User DSN tab, select the Data Source for which you want to specify a service. Click Configure.... Enter a name in the Service Name box: 5.
The service name that you set in the ODBC Administrator applies to queries that run in the data source. A service name that is set in a JDBC or ODBC client application or in an NCI session takes precedence over the setting in the ODBC Administrator. Setting the Service in the MXODSN File on a Linux or UNIX Workstation On a Linux or UNIX workstation, you can set the service name for a client data source in the MXODSN file.
For more information about using the JDBC Type 4 driver, see the Neoview JDBC Type 4 Driver Programmer's Reference. Using the SET SERVICE Statement to Associate Queries With a Service SET SERVICE Statement In NCI or in an ODBC or JDBC client application, use the SET SERVICE statement to associate SQL queries with a service. In NCI, in SQL mode only, you can enter SET SERVICE interactively in the command-line interface, or you can put the SET SERVICE statement in a script file that you run in NCI.
SQL>get service; CUR_SERVICE PLAN TEXT -------------------------------------------------- ----------- ----------HP_DEFAULT_SERVICE 0 0 --- SQL operation complete. SQL> For more information about GET SERVICE, see the Neoview SQL Reference Manual.
5 Managing Workload in WMS • • • • “Monitoring System Resources” (page 41) “Monitoring Services and Queries” (page 41) “Managing Services” (page 51) “Managing Queries” (page 52) Monitoring System Resources Using the STATUS WMS Command to Monitor System Resources In NCI, this STATUS WMS command displays information about the state of the system and the system resources: NS%status wms; STATE MAX_CPU_BUSY MAX_MEM_USAGE STATS_INTERVAL DISK_IO DISK_CACHE CPU_BUSY MEM_USAGE --------- ------------ -------------
ACTIVE_TIME The time period during which the service is active and can execute queries. The default is 00:00 through 23:59.
HOLD ACTIVE ACTIVE ACTIVE HOLD HOLD HOLD ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE 3 DATALOADING 0 1 SERVICE2 1 2 SERVICE2 1 3 SERVICE2 0 1 SALESQUERIES 0 2 SALESQUERIES 0 3 SALESQUERIES 0 1 SERVICE3 1 2 SERVICE3 0 3 SERVICE3 1 1 HP_DEFAULT_SERVICE 0 2 HP_DEFAULT_SERVICE 0 3 HP_DEFAULT_SERVICE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 --- WMS operation complete. NS% For the syntax, see the “STATUS Command” (page 66).
0.43943207564842224 0.45029863646618223 0.39207400850312774 1.0 \WMS0102.$Z0DR PC-D530||FASTJDBC 2.1405113621293412 DBA1 458776 0 2008-04-03 18:18:09.613894 2008-04-03 18:18:09.613916 212075561889613916 212075561895388641 MXID01003010491212075562925097818000000004004DBA100_234_S1 EXECUTING SERVICE3 2.1405113621293412 2.4270026755241196 0.43943207564842224 0.45029863646618223 0.39207400850312774 2.1405113621293412 1.0 \WMS0103.$Z0FH PC-D530||FASTJDBC DBA1 589848 1 2008-04-03 18:18:15.
• • • • Use the STATUS QUERIES command to filter query status results according to the query state (for example, waiting, executing, or holding). Use the STATUS QUERIES SERVICE command to filter query status results according to the service and optionally the query state (for example, waiting, executing, or holding).
For example, this STATUS QUERIES SERVICE command displays status information about queries in the SERVICE2 service that are in the executing state: NS%status queries service service2 executing; QUERY_ID EST_MSG_TIME PROCESS_NAME QUERY_STATE SERVICE_NAME EST_COST EST_CPU_TIME EST_IDLE_TIME EST_TOTAL_TIME QUERY_NAME EST_IO_TIME EST_CARDINALITY ROLE_NAME SERVICE_INDEX QUERY_INDEX START_TS ENTRY_TS ENTRY_JTS LAST_UPDATED ---------------------------------------------------------------------------------------
589848 1 2008-04-03 18:18:18.350083 2008-04-03 18:18:18.350125 212075561898350125 212075561898350133 MXID01002010476212075562920218543000000004004DBA100_234_S1 EXECUTING SERVICE2 2.1405113621293412 2.4270026755241196 0.43943207564842224 0.45029863646618223 0.39207400850312774 2.1405113621293412 1.0 \WMS0102.$Z0DN PC-D530||FASTJDBC DBA1 524312 3 2008-04-03 18:18:15.388603 2008-04-03 18:18:15.
Displaying Runtime Statistics of All Queries Use the STATUS QUERIES ALL STATS or STATUS QUERY ALL STATS command to display the runtime statistics of all queries being managed by WMS. NOTE: By default, WMS collects runtime statistics for all executing queries at an interval of five seconds.
INITIAL -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.0 0.0 0 212075561897764939 MXID01002000687212075563079285896000000012114SUPER.SERVICES00_7802_SQL_CUR_3 COMPLETED SELECT_NON_UNIQUE 0 INITIAL -1 0 0 0 0 0 0 0 0 0 0 0 0 0.0 0 212075561895388651 MXID01002010476212075562920218543000000004004DBA100_234_S1 EXECUTING SELECT_NON_UNIQUE INITIAL 0 0 0 0 0 0 0 0 212075561895388651 0 0 0 -1 0 0 0 0 0 0 0 0.0 0 0 0 -1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -1 0 0 0 0 0 0 0.0 0 0 0 0.
Displaying the Query Explain Plan Use the STATUS QUERY PLAN command to display the execution plan of a specific query. For the STATUS QUERY PLAN command to succeed, the output option, PLAN, must be enabled for the service. If the default NO_PLAN is specified for the service, the STATUS QUERY PLAN command does not return a query execution plan.
Managing Services • • • • “Holding All Services” (page 51) “Holding a Service” (page 51) “Releasing All Services” (page 51) “Releasing a Service” (page 51) Holding All Services When you hold all services in WMS, you prevent the waiting queries associated with all the services from being executed. While the services are on hold, WMS allows queries that are currently executing in the services to finish executing, but WMS rejects new incoming queries associated with the services.
For the syntax, see the “RELEASE Command” (page 66). Managing Queries You can manage queries in WMS by using the HOLD, RELEASE, and CANCEL commands. The HOLD command enables you to hold a query that is in the waiting queue, and the RELEASE command enables you to release a holding query and put it back into the waiting queue. You can also kill a waiting or executing query to free system resources by using the CANCEL command.
--- WMS operation complete. NS% For the syntax, see the “CANCEL Command” (page 61). When you cancel a query, you kill the NDCS server that is handling the query.
A WMS Commands Use these commands to configure WMS: • “ADD SERVICE Command” (page 56) • “ALTER SERVICE Command” (page 58) • “ALTER WMS Command” (page 60) • “DELETE SERVICE Command” (page 62) Use these commands to display status information about queries, services, WMS or system resources: • “INFO SERVICE Command” (page 64) • “INFO WMS Command” (page 65) • “STATUS Command” (page 66) Use these commands to manage WMS workload: • “CANCEL Command” (page 61) • “HOLD Command” (page 63) • “RELEASE Command” (page 66
ADD SERVICE Command The ADD SERVICE command adds a service to the WMS configuration on the Neoview platform. Syntax ADD SERVICE service-name [service-attribute[, service-attribute]...
service-threshold output-option comment specifies one of these limits for the service: MAX_CPU_BUSY percentage specifies the maximum CPU busy, as a percentage, of all the CPUs on the system for queries executing in the service. percentage can be a number from 0 through 100. Zero, the default value, means that WMS uses the threshold of the WMS system configuration, if set, or the internal default threshold of 100%.
Considerations • • • Use a unique name for the service. You cannot add a service that already exists. You cannot add a service named SYSTEM or HP_DEFAULT_SERVICE. To execute this command in NS mode in NCI, see “How to Execute WMS Commands in NCI” (page 55). Examples • This command adds a service, DATALOADING, to the WMS configuration.
• PRIORITY MEDIUM • PRIORITY LOW-MEDIUM • PRIORITY LOW If you do not specify a priority, the default is MEDIUM. service-threshold output-option specifies one of these limits for the service: MAX_CPU_BUSY percentage specifies the maximum CPU busy, as a percentage, of all the CPUs on the system for queries executing in the service. percentage can be a number from 0 through 100.
comment TEXT collects the SQL syntax of queries executing in the service so that client tools, such as NCI and the Neoview Manageability Repository, can use and display that data. If not specified, the default is NO_TEXT, meaning that no SQL text is collected. NO_TEXT does not collect the SQL syntax of queries executing in the service. The default is NO_TEXT. is optional text that you can specify to describe the service that you are altering. comment-string cannot exceed 256 characters.
system-threshold specifies one of these limits for the system: MAX_CPU_BUSY percentage specifies the maximum CPU busy, as a percentage, for all the CPUs on the system. percentage can be a number from 0 through 100. Zero, the default value, means that WMS uses the internal value of 100 percent. MAX_MEM_USAGE percentage sets the maximum memory usage, as a percentage, for the entire system. percentage can be a number from 0 through 100.
type specifies one of these options for cancelling queries: QUERIES service-name [ALL] cancels all queries in the specified service. service-name is the name of a user-defined service for managing queries. The service name is not case-sensitive and is always converted to uppercase. WMS supports multibyte characters in the service name. For guidelines on using multibyte character sets, see the Neoview Character Sets Administrator's Guide.
service-name IMMEDIATE is the name of a user-defined service for managing queries. service-name must exist in the WMS configuration but cannot be the SYSTEM service or the HP_DEFAULT_SERVICE. The service name is not case-sensitive and is always converted to uppercase. WMS supports multibyte characters in the service name. For guidelines on using multibyte character sets, see the Neoview Character Sets Administrator's Guide.
Considerations To execute this command in NS mode in NCI, see “How to Execute WMS Commands in NCI” (page 55). Examples • This command suspends all WMS activities and puts WMS in a holding state: HOLD WMS • This command holds all waiting queries in the DATALOADING service: HOLD SERVICE dataloading • This command holds all services on the Neoview platform: HOLD SERVICE ALL • This command holds a specific waiting query: HOLD QUERY MXID0100100050121203677536...
Table A-1 INFO SERVICE Command Output (continued) • Column Name Data Type Description SQL_PLAN VARCHAR(7) PLAN indicates that the query execution plans are collected for display. NO_PLAN indicates that no plans are collected for display. SQL_TEXT VARCHAR(7) TEXT indicates that the SQL syntax of executing queries are collected for display. NO_TEXT indicates that no SQL text is collected for display.
INFO WMS RELEASE Command The RELEASE command releases a query or a set of queries being managed by WMS from the holding state. Syntax RELEASE type type is: { WMS } | { SERVICE { service-name | ALL } } | { QUERY { query-id | ALL } } type specifies one of these options for releasing queries from the holding state: WMS releases WMS from the holding state. SERVICE service-name releases all queries in the specified service from the holding state.
Syntax STATUS type type is: { WMS [VERSION] } | { SERVICE [ ALL | service-name | STATS ] } | { QUERIES [ ALL [ STATS ] | EXECUTING [STATS] | WAITING | HOLDING ] } | { QUERIES SERVICE service-name [EXECUTING | WAITING | HOLDING] } | { QUERIES ROLE {role-name | alias-name} [EXECUTING | WAITING | HOLDING] } | { QUERY ALL STATS | query-id [STATS | PLAN | TEXT] } type specifies one of these items for which to return status information: WMS returns status information about WMS and system resources.
QUERIES ROLE {role-name | alias-name} [state] returns status information about the queries that are associated with a role, such as ROLE.USER, or an alias of a role, such as dba1. If you specify a role, the STATUS command returns only the queries associated with the particular role and not the queries associated with the aliases of the role.For more information, see Table A-8 (page 70). role-name is the name of a user role, which can be a maximum of 17 characters. The role name is case-sensitive.
Table A-4 System Version Information Column Name Data Type Description VERSION_INFO VARCHAR(n) A string of version information for internal WMS processes Table A-5 VERSION_INFO Column String • String Element Example Segment number of the WMS process 01 Process name QSSYNC Component ID 33 Major version number 2 Minor version number 3 Build ID 1 VPROC information T8010N26_15FEB2008_AFC_SYNC_0304 The STATUS SERVICE option returns this status information: Table A-6 Services Status Inform
Table A-7 Statistics for All Services on the System (continued) • Column Name Data Type Description WAITING INT Number of waiting queries for the service across the cluster HOLDING INT Number of holding queries for the service across the cluster The STATUS QUERIES and STATUS QUERY without the STATS, PLAN, or TEXT option return this status information: Table A-8 Query Status Information Column Name Data Type Description QUERY_ID VARCHAR(160) Query identifier QUERY_STATE VARCHAR(9) State of
Table A-9 Numbers of Executing Queries on the System • Column Name Data Type Description SEGMENT INT Segment number TOT_INITIAL INT Number of executing queries in the initialization state for this segment TOT_OPEN INT Number of executing queries in the open state for this segment TOT_EOF INT Number of executing queries in the end-of-file state for this segment TOT_CLOSE INT Number of executing queries in the close state for this segment TOT_DEALLOCATED INT Number of executing queries i
Table A-10 Query Runtime Statistics (continued) 72 Column Name Data Type Description EXEC_STATE VARCHAR(21) — — — — — — — — — — ELAPSED_TIME LARGEINT Elapsed time of query execution ACCESSED_ROWS LARGEINT Number of rows accessed from the tables referenced by the query. This number includes the records examined by the disk process, the file system, and the executor. USED_ROWS LARGEINT Number of rows actually used by the query.
Table A-10 Query Runtime Statistics (continued) • Column Name Data Type Description SQL_HEAP_USED INT Amount, in kilobytes, of the heap type of memory used in the master and ESPs involved in processing the query SQL_CPU_TIME LARGEINT Approximation, in microseconds, of the total CPU time spent in the master and ESPs involved in processing the query EID_SPACE_ALLOC INT Amount, in kilobytes, of the space type of memory allocated in the EID (executor code in DP2 processes) involved in processing th
• This command displays status information for the SALESQUERIES service: STATUS SERVICE salesqueries • This command displays statistics for all the services on the system: STATUS SERVICE STATS • This command displays status information for all the queries on the system: STATUS QUERIES ALL • This command displays runtime statistics information about all the queries on the system: STATUS QUERIES ALL STATS • This command displays status information for all the waiting queries on the system: STATUS QUE
Index A Active period, setting start and end times, 30 ACTIVE state, 42 ACTIVE threshold, syntax of, 57, 59 ACTIVE_TIME description of, 32, 42 setting the value, 30 ADD SERVICE command example of, 29 syntax of, 56 ALTER SERVICE command, syntax of, 58 ALTER WMS command example of, 34 syntax of, 60 C CANCEL command example of, 52 syntax of, 61 Client data source, specifying a service, 35 Client role, 35 COMMENT, 32 Compile-time statistics, examples of, 43, 44 Configuration, WMS, 25 D Data source, specifying
compile-time statistics, 43, 44 execution statistics, 47 explain plan, 50 filtering, 44 holding all queries in a service, 51 all queries in all services, 51 specific query, 52 managing, 52 monitoring, 41 releasing all sets of queries, 51 specific query, 52 specific set of queries, 51 runtime statistics, 48, 49 SQL text, 50 Query plan, 50 Query text, 50 R RELEASE command example of, 51, 52 syntax of, 66 Role, 35 Runtime statistics, 48, 49 S SERVICE_NAME, 32, 41 SERVICE_PRIORITY, 32, 41 Services active peri
