QRYGOVEXECTIME

Sets the maximum amount of time a query can use to retrieve and deliver information before the query is terminated.

Syntax

QRYGOVEXECTIME [appname [dbname]] n

appname—Optional. Applies the query time limit to the application specified. If you specify appname, you must also specify a value for n, or Essbase Server ignores QRYGOVEXECTIME. If you do not specify an application, then you cannot specify a database, and the query time limit applies to all applications and databases on Essbase Server. If you specify a value for appname and do not specify a value for dbname, the query time limit applies to all databases in the specified application.
dbname—Optional. Must be used with appname and n, or Essbase Server ignores QRYGOVEXECTIME. If you specify dbname, appname, and n, the query time limit is applied only to the specified database.
n—Integer specifying the number of seconds that Essbase Server allows a query to run before the query is terminated. The default value is 300 seconds. If you do not specify appname or dbname, the query time limit applies to the entire server.

Description

QRYGOVEXECTIME specifies the maximum amount of time that a query can run before Essbase Server terminates the query (a request for information sent to a database). You can apply this setting to an entire server, to all the databases in a single application, or to a single database.

When a query exceeds the time limit and is terminated, an error message is written to the application log of the application accessed for the query.

Restarting Essbase Server after adding or changing this setting activates the new setting values.

Use QRYGOVEXECTIME to prevent these types of queries:

A long-running query against a database that accesses atrributes at a high level, forcing many dynamic calculations to occur.
A query that uses the "Drill to bottom" option in a large dimension.
A query that uses the "Drill to all levels" option in a a large dimension.

Use QRYGOVEXECTIME, for example, if you have users who try to retrieve so much data in a single query that their query appears to hang for minutes at a time.

Notes

Because the query time setting is evaluated in 10 second increments, the query may actually run nine seconds longer than specified before being terminated.
If you use an invalid value (such as a negative number, a letter, a word, or a special character) for n, the server ignores QRYGOVEXECTIME.
Query governor settings are ignored during data load and calculation. You can leave query governor settings in the configuration file whether you are performing these operations or querying against the data.

Example

QRYGOVEXECTIME Sample Basic 20

Sets 20 seconds as the maximum time that a query can run before being terminated. In this example the restriction applies only to the Basic database in the Sample application.

QRYGOVEXECTIME 45

Sets 45 seconds as the maximum time that a query can run before being terminated. The query time limit applies to all applications and databases on the server.