Appendix A: Data Items


Table of data items and definitions

Table A-1 describes the data items available for inclusion in recording session views. The table lists data items in alphabetical order and provides the following information about each one:

Table A-1: Data items and definitions

Data item

Description

Application Execution Class Version: 11.5 and later

Configured execution class, if any, for a given application name. Because of override features, the configured execution class does not necessarily reflect the priority and engine group at runtime. The following notations are used in the monitor:

  • blank – no execution class is configured for this application.

  • execution class name – the execution class configured for the application in general, without consideration for specific logins. (That is, an execution class is configured for the application with null scope.)

  • execution class name followed by asterisk (*) – in addition to the execution class configured for the application in general, additional execution classes are configured for specific logins. (That is, an execution class is configured for the application with null scope and at least one additional execution class is configured for the application with a specific scope.)

  • an asterisk (*) without execution class – no execution class is configured for the application in general, but execution classes are configured for specific logins using this application. (That is, at least one execution class is configured for the application with a specific scope.)

Type: Result

Application Name Version: 11.0 and later

Name of application for which other statistics are being accumulated. Views that contain Application Name only report on processes that are active as of the end of the sample period.

Application name is mutually exclusive with Process ID in a view.

Type: Key

Blocking Process ID Version: 11.0 and later

ID of the process that holds a lock that another process is waiting for, if any. A returned value of zero means that the other process is not blocked.

Type: Result

Cache Efficiency Version: 11.0 and later

The number of cache hits per second per megabyte of a particular data cache.

Type: Result

Cache Hit Pct Version: 11.0 and later

The fraction of the page reads for objects bound to a particular data cache that are satisfied from the cache computed from the following formula:

cache_hits /  (cache_hits + cache_misses) * 100

Type: Result

Cache Hits Version: 11.0 and later

The number of times a page read was satisfied from a particular data cache.

Type: Result

Cache ID Version: 11.0 and later

The ID of a data cache in Adaptive Server version 11.0 or later. Particular database tables and indexes may be bound to a specific data cache, or all objects in a database may be bound to the same data cache. No object may be bound to more than one data cache.

Type: Key

Cache Misses Version: 11.0 and later

Number of times a page read was satisfied from disk rather than from a particular data cache. This data item includes failed attempts to locate pages in the data caches during page allocation. Therefore, the number of physical page reads reported may be overstated. If this occurs, the percentage of data cache misses reported by Cache Hit Pct is understated.

Type: Result

Cache Name Version: 11.0 and later

The name of a data cache. Particular database tables and indexes may be bound to a specific data cache, or all objects in a database may be bound to the same data cache. No object may be bound to more than one cache.

Type: Key

Cache Prefetch Efficiency Version: 11.0 and later

A percentage comparing the count of pages being reused in large I/O buffers (the denominator) to the number of those pages that were ever referenced by Adaptive Server. When a buffer is reused, all of the pages in it are counted as reused. Buffers are reused when there are no free buffers in the pool to accept a new physical read from a database device. The number of reused pages referenced by Adaptive Server divided by the result of the number of pages per buffer multiplied by the number of reused buffers indicates the effectiveness of large I/O fetches.

Regardless of how many buffer pools are configured in a named data cache, Adaptive Server only uses two of them. It uses the 2K buffer pool and the pool configured with the largest-sized buffers. Prefetch effectiveness does not apply to the 2K buffer pool, since 2K grabs are not considered large I/O. Therefore, prefetch effectiveness applies to the largest buffer pool in the cache. For example, if a data cache has pools of buffers sized 2K, 8K, and 16K, the 8K pool is not used, and this metric reflects the effectiveness of large I/O in the 16K buffer pool.

If the ratio is large, then prefetching is effective; otherwise, prefetching is not providing much benefit. This may suggest that a buffer pool should be eliminated (or it may imply that a clustered index on some table is fragmented, and that the index should be dropped and recreated).

Type: Result

Cache Refer and Reuse Version: 11.0 and later

The number of pages in buffers were both referenced and reused. This count is employed when determining the efficiency of prefetching buffers (see Cache Prefetch Efficiency). This data item, unlike Cache Prefetch Efficiency, includes activity in the default 2K buffer pool.

See Cache Prefetch Efficiency for a definition of buffer reuse.

Type: Result

Cache Reuse Version: 11.0 and later

The number of pages in buffers that were reused. A large value indicates a high rate of turnover (of buffers in this memory pool), and suggests that the pool may be too small. A zero value suggests that this memory pool may be too large. This data item, unlike Cache Prefetch Efficiency, includes activity in the default 2K buffer pool.

See Cache Prefetch Efficiency for a definition of buffer reuse.

Type: Result

Cache Reuse Dirty Version: 11.0 and later

The number of times that a buffer that was reused had changes that needed to be written. A non-zero value indicates that the wash size is too small.

See Cache Prefetch Efficiency for a definition of buffer reuse.

Type: Result

Cache Size Version: 11.0 and later

The size of a data cache, in megabytes.

Type: Result

Cache Spinlock Contention Version: 11.0 and later

The fraction of the requests for a data cache’s spinlock that were forced to wait.

spinlock_waits / spinlock_requests

Type: Result

Code Memory Size Version: 11.0 and later

Amount of memory in bytes allocated to Adaptive Server.

Type: Result

Connect Time Version: 11.0 and later

Number of seconds elapsed since the process was started or since the session was started, whichever is smaller.

Type: Result

CPU Busy Percent Version: 11.0 and later

Percentage of total server CPU ticks that the Adaptive Server CPU was busy.

Type: Result

CPU Percent Version: 11.0 and later

If used in a view with Process ID, this is the percentage of time a single process was in the Running state over the time all processes were in the Running state.

If used in a view with Application Name, this is the percentage of time the set of processes running a given application were in the Running state over the time all processes were in the Running state.

Type: Result

CPU Time Version: 11.0 and later

If used in a view with no keys, this data item is the total CPU busy time, in seconds, on the server. If used with keys, this data item is the busy time, in seconds, that was used by each process, application, or engine. Process ID and Application Name are mutually exclusive.

Type: Result

CPU Yields Version: 11.0 or later

Number of times that the Adaptive Server yielded to the operating system.

Type: Result

Current Application Name Version: 11.0 and later

The name of the application that is currently executing on a particular process.

Type: Result

Current Engine Version: 11.0 and later

Number of the Adaptive Server engine on which the process was running most recently.

Type: Result

Current Execution Class

Version: 11.5 and later

The name of the execution class under which a process is currently running.

Type: Result

Current Process State Version: 11.0 and later

Current state of a process. See Process State for definitions of the possible states.

Type: Result

Current Stmt Batch ID Version: 11.5 and later

The ID of a particular query batch being executed on a particular process.

Type: Result

Current Stmt Batch Text Version: 11.5 and later

The text of a particular query batch being executed for a particular process. This text may be only an initial substring of the complete text in a query batch. The amount of text stored in this field is determined by the Adaptive Server max SQL text monitored configuration parameter.

Type: Result

Current Stmt Batch Text Byte Offset Version: 11.5 and later

The byte offset to the beginning of a statement within the query batch or stored procedure being executed for a particular process. If both:

Current Stmt Procedure Database ID is equal to 0 and Current Stmt Procedure ID is equal to 0 then the statement is the currently executing SQL statement in the query batch. Otherwise, the statement is the currently executing SQL statement in the stored procedure uniquely identified by these two IDs.

Type: Result

Current Stmt Batch Text Enabled Version: 11.5 and later

Reports whether Adaptive Server (version 11.5 and later) is saving the SQL text of the currently executing query batches and, if so, how much.

Value of 0 = saving SQL text disabled

Value of 1 or more = maximum number of bytes of batch text per server process that can be saved.

Type: Result

Current Stmt Context ID Version: 11.5 and later

The ID that uniquely identifies a stored procedure invocation within a particular query batch being executed for a particular process.

Type: Result

Current Stmt CPU Time Version: 11.5 and later

The amount of time (in seconds) that the currently executing SQL statement has spent in the running state.

Type: Result

Current Stmt Elapsed Time Version: 11.5 and later

The amount of time (in seconds) that the currently executing SQL statement has been running.

Type: Result

Current Stmt Line Number Version: 11.5 and later

The number of the line (within a query batch or stored procedure) that contains the beginning of the currently executing SQL statement for a particular process. The currently executing SQL statement is in the query batch if both Current Stmt Procedure Database ID is equal to 0 and Current Stmt Procedure ID is equal to 0.

Otherwise, the currently executing SQL statement is in the stored procedure uniquely identified by these two IDs.

Type: Result

Current Stmt Locks Granted After Wait Version: 11.5 and later

Number of lock requests by the currently executing SQL statement that were granted after waiting.

Type: Result

Current Stmt Locks Granted Immediately Version: 11.5 and later

Number of lock requests by the currently executing SQL statement that were granted immediately or were not needed (because sufficient locking was already held by the requestor).

Type: Result

Current Stmt Locks Not Granted Version: 11.5 and later

Number of lock requests by the currently executing SQL statement that were denied.

Type: Result

Current Stmt Logical Reads Version: 11.5 and later

Number of data page reads satisfied from cache or from device reads by the currently executing SQL statement.

Type: Result

Current Stmt Number Version: 11.5 and later

The number of the statement (appearing in a query batch or stored procedure) that is the currently executing SQL statement for a particular process. The currently executing SQL statement is in the query batch if both Current Stmt Procedure Database ID is equal to 0 and Current Stmt Procedure ID is equal 0.

Otherwise, the currently executing SQL statement is in the stored procedure uniquely identified by these two IDs.

A value of 0 indicates partial result data for the currently executing SQL statement. In other words, this SQL statement began executing before monitoring began. Performance metrics are available but numbers reflect only the time period since the start of monitoring.

Type: Result

Current Stmt Page I/O Version: 11.5 and later

Number of combined logical page reads and page writes by the currently executing SQL statement.

Type: Result

Current Stmt Physical Reads Version: 11.5 and later

Number of data page reads by the currently executing SQL statement that could not be satisfied from the data cache.

Type: Result

Current Stmt Procedure Database ID Version: 11.5 and later

The database ID of the stored procedure (including triggers, a special kind of stored procedure) that contains the currently executing SQL statement for a particular process. If the currently executing SQL statement is not contained in a stored procedure, this ID is 0.

Type: Result

Current Stmt Procedure Database Name Version: 11.5 and later

The database name of the stored procedure (including triggers, a special kind of stored procedure) that contains the currently executing SQL statement for a particular process. If the currently executing SQL statement is not contained in a stored procedure, this name is “**NoDatabase**”.

Type: Result

Current Stmt Procedure ID Version: 11.5 and later

The ID of the stored procedure (including triggers, a special kind of stored procedure) that contains the currently executing SQL statement for a particular process. If the currently executing SQL statement is not contained in a stored procedure, this ID is 0.

Type: Result

Current Stmt Procedure Name Version: 11.5 and later

The name of the stored procedure (including triggers, a special kind of stored procedure) that contains the currently executing SQL statement for a particular process. If the currently executing SQL statement is not contained in a stored procedure, this name is “**NoObject**”.

Type: Result

Current Stmt Procedure Owner Name Version: 11.5 and later

The owner name of the stored procedure (including triggers, a special kind of stored procedure) that contains the currently executing SQL statement for a particular process. If the currently executing SQL statement is not contained in a stored procedure, this name is “**NoOwner**”.

Type: Result

Current Stmt Procedure Text Version: 11.5 and later

The text of a particular stored procedure (including triggers, a special kind of stored procedure) being executed for a particular process. If both Current Stmt Procedure Database ID is equal to 0 and Current Stmt Procedure ID is equal to 0 then a stored procedure is not currently executing and this text is a null-terminated empty string ("").

If the text is not available (because this stored procedure was compiled and its text was discarded, or because the text is stored in an encrypted format), then this text is a null-terminated empty string ("").

Type: Result

Current Stmt Query Plan Text Version: 11.5 and later

The text of the query plan for a particular query being executed for a particular process.

If the text is not available (because the Adaptive Server has removed this plan from its catalog of query plans), then this text is a null-terminated empty string ("").

Type: Result

Current Stmt Start Time Version: 11.5 and later

The date and time, in the time zone of Adaptive Server, when the currently executing SQL statement began running.

If this SQL statement began running before monitoring began, then this result is the date and time that activity was first encountered for this statement.

Type: Result

Current Stmt Text Byte Offset Version: 11.5 and later

The byte offset to the beginning of a statement within the query batch or stored procedure being executed for a particular process.

If both Current Stmt Procedure Database ID is equal to 0 and Current Stmt Procedure ID is equal to 0 then the statement is the currently executing SQL statement in the query batch. Otherwise, the statement is the currently executing SQL statement in the stored procedure uniquely identified by those two IDs.

Type: Result

Database ID Version: 11.0 and later

Unique identification of a database.

Type: Key

Database Name Version: 11.0 and later

Name of the database.

Type: Result

Deadlock Count Release: 11.0 and later

Number of deadlocks.

Type: Result

Demand Lock Version: 11.0 and later

A character string (Y or N) that indicates whether or not a lock that has been upgraded to demand lock status.

Type: Result

Device Hit Percent Version: 11.0 and later

The fraction of device requests is computed by multiplying the quotient of device hits divided by device misses plus device misses by 100.

Type: Result

Device Hits Version: 11.0 and later

Number of times access to a device was granted.

Type: Result

Device I/O Version: 11.0 and later

Combination of device reads and device writes.

Type: Result

Device Misses Version: 11.0 and later

Number of times access to a device had to wait.

Type: Result

Device Name Version: 11.0 and later

Name of a database device defined in Adaptive Server.

Type: Key

Device Reads Version: 11.0 and later

Number of reads made from a device.

Type: Result

Device Writes Version: 11.0 and later

Number of writes made to a device.

Type: Result

Elapsed Time Version: 11.0 and later

The time increment, in seconds, either from one data refresh to the next (sample) or from the creation of the view to the present (session).

Type: Result

Engine Number Version: 11.0 and later

Number of the Adaptive Server engine.

Type: Key

Host Name Version: 11.0 and later

The name of the host computer that established a particular connection.

Type: Result

Index Logical Reads Release: 11.0 and later

Number of index page reads satisfied from cache and from database devices.

Type: Result

Index Physical Reads Version: 11.0 and later

Number of index page reads that could not be satisfied from the data cache.

Type: Result

Kernel Process ID Version: 11.0 and later

An Adaptive Server process identifier that remains unique over long periods of time.

Type: Key

Kernel Structures Memory Size Version: 11.0 and later

Amount of memory in bytes allocated to the kernel structures.

Type: Result

Large I/O Denied Version: 11.0 and later

The number of times the buffer manager did not satisfy requests (of the optimizer) to load data into a buffer in this data cache by fetching more than one contiguous page from disk at a time.

Type: Result

Large I/O Performed Version: 11.0 and later

The number of times the buffer manager satisfied requests (of the optimizer) to load data into a buffer in this data cache by fetching more than one contiguous page from disk at a time.

Type: Result

Large I/O Requested Version: 11.0 and later

The number of times the optimizer made requests (of the buffer manager) to load data into a buffer in this data cache by fetching more than one contiguous page from disk at a time.

Type: Result

Lock Count

Version: 11.0 and later

Number of locks.

Type: Result

Lock Hit Percent

Version: 11.0 and later

Percentage of successful requests for locks.

Type: Result

Lock Result Version: 11.0 and later

Result of a logical lock request. Lock result values are:

  • 1 – Granted immediately

  • 2 – Not needed; requestor already held a sufficient lock

  • 3 – Waited; requestor waited

  • 4 – Did not wait; lock was not available immediately and the requestor did not want the lock request to be queued

  • 5 – Deadlock; requestor selected as deadlock victim

  • 6 – Interrupted; the lock request was interrupted by attention condition

Type: Key

Lock Results Summarized Version: 11.0 and later

Lock results summarized at a granted or not granted level.

  • 1 – The lock result summary granted is composed of the lock results: granted, not needed, and waited.

  • 2 – The lock result summary not granted is composed of the lock results: did not wait, deadlock, and interrupted.

Type: Key

Lock Status Version: 11.0 and later

Current status of a lock which includes lock status values:

  • 1– Held and blocking

  • 2 – Held and not blocking

  • 3 – Requested and blocked

  • 4 – Requested and not blocked

Type: Key

Lock Status Count

Version: 11.0 and later

Number of locks in each lock status. This is a snapshot value.

Type: Result

Lock Type Version: 11.0 and later

Adaptive Server protects tables or data pages currently used by active transactions by locking them. Adaptive Server employs the following lock types:

  • 1 – Exclusive table lock

  • 2 – Shared tablelock

  • 3 – Exclusive intent lock

  • 4 – Shared intent lock

  • 5 – Exclusive page lock

  • 6 – Shared page lock

  • 7 – Update page lock

Type: Key

Locks Being Blocked Count Version: 11.0 and later

Number of locks being blocked by this process that holds this “held_and_blocking” lock.

Type: Result

Locks Granted Immediately Version: 11.5 and later

Number of locks that were granted immediately, without having to wait for another lock to be released.

Type: Result

Locks Granted After Wait Version: 11.5 and later

Number of locks that were granted after waiting for another lock to be released.

Type: Result

Locks Not Granted Version: 11.5 and later

Number of locks that were requested but not granted.

Type: Result

Log Contention Percent Version: 11.0 and later

The percentage of times, of the total times when a user log cache was flushed into the transaction log, that it had to wait for the log semphore.

A high percentage may indicate that the user log cache size should be increased.

Type: Result

Logical Page Reads Version: 11.0 and later

Number of data page reads per unit of time, whether satisfied from cache or from a database device.

Type: Result

Login Name Version: 11.0 and later

Login name associated with Adaptive Server processes.

Type: Result

Most Active Device I/O Version: 11.0 and later

Number of combined reads and writes against the device with the most activity during a given time interval.

Type: Result

Most Active Device Name Version: 11.0 and later

Name of the device with the largest number of combined reads and writes during a given time interval.

Type: Result

Net Bytes Received Version: 11.0 and later

Number of network bytes received.

Type: Result

Net Bytes Sent Version: 11.0 and later

Number of network bytes sent.

Type: Result

Net Default Packet Size Version: 11.0 and later

Default network packet size.

Type: Result

Net I/O Bytes Version: 11.0 and later

Total number of network bytes sent and received.

Type: Result

Net Max Packet Size Version: 11.0 and later

Configured maximum size for a network packet.

Type: Result

Net Packet Size Received Version: 11.0 and later

Average size of network packets received.

Type: Result

Net Packet Size Sent Version: 11.0 and later

Average size of network packets sent.

Type: Result

Net Packets Received Version: 11.0 and later

Number of network packets received.

Type: Result

Net Packets Sent Version: 11.0 and later

Number of network packets sent.

Type: Result

Number of Engines Version: 11.0 and later

Number of engines configured for Adaptive Server.

Type: Result

Number of Processes Version: 11.0 and later

Number of processes currently running on Adaptive Server, or, if used with the key Application Name, the number of processes currently running a given application.

Type: Result

Object ID Version: 11.0 and later

ID of a database object. The object returned is either a database table, a stored procedure, or a temporary table.

Object IDs might be negative numbers. The object IDs that Adaptive Server assigns to temporary tables can be positive or negative.

Type: Key

Object Name Version: 11.0 and later

Database object name. The string **TempObject** is reported for temporary tables.

Type: Result

Object Type Version: 11.0 and later

Type of database object:

  • 0 – None

  • 1 – Stored procedure (including triggers)

  • 2 – Table

Type: Result

Owner Name Version: 11.0 and later

Name of an objects’s owner.

Type: Result

Page Cache Size Version: 11.0 and later

Amount of memory in bytes allocated for the page cache.

Type: Result

Page Hit Percent Version: 11.0 and later

Percentage of times that a data page read could be satisfied from cache without requiring a physical page read.

Type: Result

Page I/O Version: 11.0 and later

Combined total of logical page reads and page writes.

Type: Result

Page Number Version: 11.0 and later

Data page number for a particular lock or lock request.

Type: Key

Page Writes Version: 11.0 and later

Number of pages written to a database device.

Type: Result

Physical Page Reads Version: 11.0 and later

Number of data page reads that could not be satisfied from the data cache.

Type: Result

Procedure Buffer Size Version: 11.0 and later

Amount of memory in bytes allocated for the procedure buffer.

Type: Result

Procedure CPU Time Version: 11.0 and later

Number of seconds of CPU time spent executing a stored procedure.

Type: Result

Procedure Database ID Version: 11.0 and later

Database ID of the active stored procedure.

Type: Key

Procedure Database Name Version: 11.0 and later

Database name of the active stored procedure.

Type: Key

Procedure Elapsed Time Version: 11.0 and later

Number of seconds elapsed during a stored procedure execution. All statistic types valid with this data item report time in units of seconds. For example, “Procedure Elapsed Time”, “Average for Session” reports the average number of elapsed seconds per procedure execution.

Type: Result

Procedure Execution Class Version: 11.5 and later

Configured execution class, if any, for a given stored procedure.

Type: Result

Procedure Execution Count Version: 11.0 and later

Number of times a stored procedure, or a line in a stored procedure, was executed.

Type: Result

Procedure Header Size Version: 11.0 and later

Amount of memory in bytes allocated for the procedure header.

Type: Result

Procedure Hit Percent Version: 11.0 and later

Percentage of times that a procedure execution found the procedure’s query plan in procedure cache and available for use.

Type: Result

Procedure ID Version: 11.0 and later

Active stored procedure. Active indicates the top-level stored procedure was called.

Type: Key

Procedure Line Number Version: 11.0 and later

Stored procedure line number.

Type: Key

Procedure Line Text Version: 11.0 and later

Entire text of the stored procedure.

Type: Result

Procedure Logical Reads Version: 11.0 and later

Number of requests to execute a stored procedure, whether satisfied from procedure cache or with a read from sysprocedures.

Type: Result

Procedure Name Version: 11.0 and later

Name of the active stored procedure.

Type: Result.

Procedure Owner Name Version: 11.0 and later

Name of the owner of the active stored procedure.

Type: Result

Procedure Physical Reads Version: 11.0 and later

Number of requests to execute a stored procedure, for which a read from sysprocedures was necessary.

Type: Result

Procedure Statement Number Version: 11.0 and later

Statement number within a stored procedure. A single stored procedure line can contain one or more statements.

Type: Key

Process ID Version: 11.0 and later

Adaptive Server process identification number. Views that contain Process ID only report on processes that are active as of the end of the sample period. Process ID is mutually exclusive with Application Name in a view.

Type: Key

Process State Version: 11.0 and later

Process state:

  • 0 – None.

  • 1 – Alarm Sleep.Waiting on an alarm.

  • 2 – Background. Adaptive Server process executing.

  • 3 – Bad Status. Undetermined error condition.

  • 4 – Infected. Tagged by Adaptive Server as unprocessable.

  • 5 – Lock Sleep. Waiting on a lock acquisition.

  • 6 – Received Sleep. Waiting on a network read.

  • 7 – Runnable. Waiting to run according to priority and availability of CPU.

  • 8 – Running. Executing.

  • 9 – Send Sleep. Waiting on a network send.

  • 10 – Sleeping. Paused for any other reason not listed here, such as: waiting on device I/O (physical reads) or waiting for client activity.

  • 11 – Stopped. Process terminated.

  • 12 – Terminating. Process terminating.

  • 13 – Unknown. Process state undeterminable.

  • 14 – Remote I/O. Waiting on a remote (OMNI) server to complete an operation.

  • 15 – Synch Sleep. Waiting to synchronize with some other server process(es) that are working in parallel to execute a given query.

Type: Key

Process State Count Version: 11.0 and later

Number of processes in a particular state.

Type: Result

Rows Deleted Version: 11.0 and later

Number of rows deleted from a database table.

Type: Result

Rows Deleted Deferred Version: 11.0 and later

Number of rows deleted from a database table in deferred mode.

Type: Result

Rows Deleted Direct Version: 11.0 and later

Number of rows deleted from a database table in direct mode.

Type: Result

Rows Inserted Version: 11.0 and later

Insertions into a database table.

Type: Result

Rows Inserted Clustered Version: 11.0 and later

Insertions into database tables with clustered indexes.

Type: Result

Rows Inserted Heap Version: 11.0 and later

Insertions into database tables without clustered indexes.

Type: Result

Rows Updated Version: 11.0 and later

Updates to a database table.

Type: Result

Rows Updated Deferred Version: 11.0 and later

Updates that require two steps to complete. First, records for deleting the existing entry and inserting the new entry are written to the log, but only the deletes are actually performed on the data pages. In the second step, the log is rescanned and the insert operations performed on the data pages.

Type: Result

Rows Updated Direct Version: 11.0 and later

The sum of expensive, in-place, and not-in-place updates (everything except updates deferred).

Type: Result

Rows Updated Expensive Version: 11.0 and later

A type of direct update that deletes a row from its original location and inserts it in a new location.

Rows Updated In Place Version: 11.0 and later

A type of direct update that does not require rows to move on a data page.

Type: Result

Rows Updated Not In Place Version: 11.0 and later

A type of direct update that does not require the updated row to move, but because the length of the updated row changes, other rows on the data page are moved. Also known as cheap updates.

Type: Result

Select Statements

Version: 11.0 and later

Number of SELECT or OPEN CURSOR statements.

Type: Result

Server Structures Size Version: 11.0 and later

Amount of memory in bytes allocated for the Adaptive Server structures.

Type: Result

SQL Server Name Version: 11.0 and later

Name of the Adaptive Server that is being monitored as specified by the -S parameter in the start-up command for the Monitor Server being used.

Type: Result

SQL Server Version Version: 11.0 and later

Version of the Adaptive Server that is being monitored. For more information, see the global @@version variable in the Transact-SQL User’s Guide.

Type: Result

Thread Exceeded Max Version: 11.5 and later

The number of times a query plan was adjusted at runtime because of attempting to exceed the configured limit of threads in the server-wide worker thread pool in Adaptive Server version 11.5 and later.

Type: Result

Thread Exceeded Max Percent Version: 11.5 and later

The percentage of time a query plan was adjusted at runtime because of attempting to exceed the configured limit of threads in the server-wide worker thread pool in Adaptive Server version 11.5 and later.

Type: Result

Thread Max Used Version: 11.5 and later

The maximum number of threads from the server-wide worker thread pool which were concurrently in use on the server.

Type: Result

Time Waited on Lock Version: 11.0 and later

Amount of time (in seconds) that a lock request has been waiting.

Type: Result

Timestamp Version: 11.0 and later

In recording session views and in playback views when summarization_level is raw, the date and time on the Adaptive Server when the recording session data was gathered.

In playback views, when summarization_level is actual, entire, or a user-defined interval, the time is converted to the time zone of Historical Server.

For more information, see the getdate() function in the Transact-SQL User’s Guide.

Type: Result

Timestamp Datim Version: 11.0 and later

In recording session views and in playback views when summarization_level is raw, the date and time on the Adaptive Server when the recording session data was gathered, returned in a CS_DATETIME structure. For more information, see the getdate() function in the Transact-SQL User’s Guide.

In playback views, when summarization_level is actual, entire, or a user-defined interval, the time is converted to the time zone on Historical Server.

Type: Result

Transactions Version: 11.0 and later

Total number of committed Transact-SQL statement blocks delimited by a begin transaction and commit transaction statement.

Type: Result