RESETPERFSTATS

Resets statistics gathering for a specified persistence and scope. Each of the statistics tables available using the GETPERFSTATS ESSCMD command has a pre-defined persistence and scope. When you issue RESETPERFSTATS without parameters, statistics-gathering is reset for all of the tables.

Collecting and analyzing performance statistics can assist you in determining whether databases are in good running condition, or could use modifications to improve performance.

Syntax

RESETPERFSTATS persistence scope

persistence
[default=long]
  • disable
    Turn off performance-statistics gathering.
  • enable
    Turn on performance-statistics gathering. You might do this when you want to tune the system, change hardware configuration, or monitor I/O. The measurement begins for current processes as soon as you enable it. Any subsequent queries for statistics return measurements spanning from the time of enablement to the time of the query.
  • short
    Reset tables that measure transient events. Short measurements need frequent resetting. You might use this to measure how many x events happened during an operation; for example, how many reads or writes occurred during a calculation? Did the calculation speed up or slow down by a factor of n?
    Examples: Semaphore, Event, Spinlock, and Mutex tables.
  • long (default)
    Reset tables that measure events over the course of the entire session. Long measurements rarely need to be reset. Example: kernel Cache Statistics table.
scope
[default=all]
  • thread
    Reset per-thread statistics tables. There are currently no per-thread tables available in ESSCMD.
    A thread is the scope of one Analytic Services transaction; for example, a load operation. Many threads are at work within Analytic Services processes.
  • db
    Reset per-database statistics tables.
  • server
    Reset per-application statistics tables.
  • all (default)
    Reset all statistics tables: for threads, databases, and applications.

Description

Depending on your database and production needs, you create a statistical measurement profile by resetting the appropriate levels of persistence (length of events to measure) and scope (granularity of the entity to measure).

Notes

This command resets to zero any previously collected statistics of a persistence shorter than or equal to the reset persistence. For example, entering RESETPERFSTATS MEDIUM resets both medium and short statistics tables back to zero.

Example

RESETPERFSTATS ENABLE;
RESETPERFSTATS MEDIUM SERVER;

See Also

GETPERFSTATS

©2004 Hyperion Solutions Corporation. All Rights Reserved.
http://www.hyperion.com