sp_monitor

Description

Displays statistics about Adaptive Server.

Syntax

sp_monitor syntax is divided by command type for clarity, since many of the types have parameters of their own. The following code paragraph shows the syntax of the stored procedure as a whole, followed by the syntax of each command type interface.

sp_monitor [[connection | statement], [cpu | diskio | elapsed time]]  
	[event, [spid ]]
	[procedure, [dbname, [procname[, summary | detail]]]]
	[enable] [disable] 
	[help], 
	[deadlock][procstack]

Parameters

Examples

Example 1

Reports information about how busy Adaptive Server has been:

sp_monitor

last_run               current_run          seconds 
-------------------    -------------------  --------- 
Jan 29 1987 10:11AM    Jan 29 1987 10:17AM  314

cpu_busy           io_busy     idle 
---------------    ---------   -------------- 
4250(215)-68%      67(1)-0%    109(100)-31% 

packets_received       packets_sent    packet_errors 
----------------       ------------    ------------ 
781(15)                10110(9596)     0(0) 

total_read     total_write total_errors    connections 
-----------    -------------------------   ----------- 
394(67)        5392(53)    0(0)            15(1) 

Example 2

Shows how to display information about connections:

1> sp_monitor "connection"
2> go
spid    LoginName    ElapsedTime  LocksHeld  SQLText  
----    ---------    -----------  ---------  -----------------
12      sa           90300        2          exec get_employee_salaries
27      sa           17700        1          exec get_employee_perks

By default, the output by default is sorted in the descending order of the ElapsedTime.

Example 3

Identifies the connections performing the most physical reads:

1> sp_monitor "connection","diskio"
2> go
spid  LoginName  Physical_Reads  LocksHeld  SQLText 
----  ---------  --------------  ---------  -------------------------- 
12    sa         117             2          exec get_employee_salaries 
27    sa         1               0          exec get_employee_perks 

Example 4

Displays information about each statement:

1> sp_monitor "statement"
2> go
spid   LoginName   ElapsedTime   SQLText
----   ---------   -----------   -------------------------- 
12     sa          100           exec get_employee_salaries 

Example 5

Displays the events each task spent time waiting for and the duration of the wait, reported in descending order of wait times:

1> sp_monitor "event"
2> go
SPID   WaitTime    Description 
------ ----------- ------------------------------------------ 
6      108200      hk: pause for some time 
29     108200      waiting for incoming network data 
10     107800      waiting while allocating new client socket 
15     17100       waiting for network send to complete 
14     5900        waiting for CTLIB event to complete 
14     400         waiting for disk write to complete 
7      200         hk: pause for some time 
7      100         waiting on run queue after yield 
12     100         waiting for network send to complete 

Example 6

Displays event data for spid 14:

1> sp_monitor "event","14"
2> go
WaitTime    Description 
----------- ----------------------------------- 
9000 waiting for CTLIB event to complete 
600 waiting for disk write to complete 
200 waiting for disk write to complete 
100 waiting on run queue after yield 
100 wait for buffer write to complete

Example 7

Provides a summary of most recently run procedures, sorted in descending order of average elapsed time. This example provides historical monitoring information rather than the current state.

1> sp_monitor "procedure"
2> go

Average Procedure Statistics
============================

ProcName       DBName    AvgElapsedTime   AvgCPUTime  AvgWaitTime AvgPhysicalReads AvgLogicalReads AvgPacketsSent NumExecs 
-----------------------------------------------------------------------neworder_remote   tpcc   1833     16    1083     26   96    0     6
neworder_local    tpcc   1394     13    1181     31   122   0     38
tc_startup        tpcc   1220     3     1157     0    3     0     59
delivery          tpcc   1000     0     800      23   49    0     2

Usage

Permissions

The permission checks for sp_monitor are the same whether or not granular permissions is enabled:

• The database owner of sybsystemprocs can execute sp_monitor and can grant execute permission to other users

• The stored procedure is created with execute as owner. The owner is sa. The owner must have mon_role which user sa has by default.

For more information see “Monitoring Tables” Performance and Tuning: Monitoring and Analyzing.

Auditing

Values in event and extrainfo columns from the sysaudits table are:

See also