IBM Tivoli Composite Application Manager for Microsoft

Applications: Microsoft SQL Server Agent

Version 6.3

User’s Guide



SC23-8880-06
IBM Tivoli Composite Application Manager for Microsoft
Applications: Microsoft SQL Server Agent
Version 6.3

User’s Guide



SC23-8880-06
 Note
Before using this information and the product it supports, read the information in “Notices” on page 405

This edition applies to version 6.3 of IBM Tivoli Composite Application Manager for Microsoft Applications:
Microsoft SQL Server Agent (product number 5724-U17) and to all subsequent releases and modifications until
otherwise indicated in new editions.
© Copyright IBM Corporation 2005, 2012.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Figures
1. The Configure Database Agents window 23 2. The Database Server Properties window 24

© Copyright IBM Corp. 2005, 2012 iii

iv Microsoft SQL Server agent: User’s Guide
Tables
1. When data is collected and cache duration for 24. Trace log files for troubleshooting agents 272
attribute groups . . . . . . . . . . . 6 25. Problems and solutions for installation and
2. Key aspects of data gathering for attribute configuration on UNIX and Windows systems 278
groups . . . . . . . . . . . . . . 9 26. Problems and solutions for installation and
3. Data that is accessed by attribute groups that configuration of the Microsoft SQL Server
gather data from operating system or agent . . . . . . . . . . . . . . 280
Microsoft SQL Server files. . . . . . . . 13 27. General problems and solutions for
4. Additional authorization . . . . . . . . 21 uninstallation . . . . . . . . . . . 285
5. Names and descriptions of configuration 28. SQL Server problems and solutions . . . . 286
settings for each interface . . . . . . . . 26 29. General agent problems and solutions 287
6. Interfaces for starting and stopping the 30. Remote deployment problems and solutions 296
Microsoft SQL Server agent locally and 31. Workspace problems and solutions . . . . 297
remotely . . . . . . . . . . . . . 36 32. Specific situation problems and solutions 301
7. Cross-linked workspaces within the SQL 33. Problems with configuring situations that you
Server agent . . . . . . . . . . . . 58 solve in the Situation Editor . . . . . . 302
8. Capacity planning for historical data logged 34. Problems with configuration of situations that
by the Microsoft SQL Server agent . . . . 223 you solve in the Workspace area . . . . . 303
9. User ID and password combinations 240 35. Problems with configuration of situations that
10. Index and table updates . . . . . . . . 247 you solve in the Manage Tivoli Enterprise
11. Index and table updates . . . . . . . . 249 Monitoring Services window . . . . . . 304
12. Index and table updates . . . . . . . . 251 36. Take Action commands problems and
13. Top Processes by CPU report . . . . . . 258 solutions . . . . . . . . . . . . . 304
14. Server Transactions Details report . . . . . 259 37. Tivoli Common Reporting for Microsoft SQL
15. Wait Time and Requests of Locks report 260 Server agent problems and solutions . . . . 305
16. Space Utilization by Database report 261 38. Time periods and suffixes for summary tables
17. Free Space Availability report . . . . . . 262 and views. . . . . . . . . . . . . 309
18. Database Status Availability report . . . . 263 39. Additional columns to report summarization
19. CPU Utilization report . . . . . . . . 264 information . . . . . . . . . . . . 310
20. Processes Details report . . . . . . . . 265 40. Overview of attribute groups to event classes
21. Server Lock Details report . . . . . . . 266 and slots . . . . . . . . . . . . . 314
22. Servers with Most Failed Jobs report 267
23. Information to gather before contacting IBM
Software Support . . . . . . . . . . 269

© Copyright IBM Corp. 2005, 2012 v

vi Microsoft SQL Server agent: User’s Guide
Contents
Figures . . . . . . . . . . . . . . . iii Availability Replicas and Database Information
workspace . . . . . . . . . . . . . . 46
Tables . . . . . . . . . . . . . . . v Availability Replicas Status workspace . . . . 46
Databases Information workspace . . . . . . 46
Database Mirror Detail workspace . . . . . . 46
Chapter 1. Overview of the agent . . . . 1 Device Detail workspace . . . . . . . . . 47
IBM Tivoli Monitoring . . . . . . . . . . . 2 Enterprise Database Mirror Detail workspace . . 47
New in this release . . . . . . . . . . . . 2 Enterprise Database Summary workspace . . . 47
Components of the IBM Tivoli Monitoring Enterprise Errorlog Alerts workspace . . . . . 47
environment . . . . . . . . . . . . . . 4 Enterprise Log Shipping Database Details
Agent Management Services . . . . . . . . . 5 workspace . . . . . . . . . . . . . . 47
User interface options . . . . . . . . . . . 5 Enterprise Processes Summary workspace . . . 47
Microsoft SQL Server agent data collection . . . . 6 Enterprise Server Locking workspace . . . . . 47
Collection processes . . . . . . . . . . . 6 Enterprise Servers Overview workspace . . . . 48
Attribute groups that gather data from Microsoft Enterprise Server Statistics workspace . . . . 48
SQL Server SELECT statements and stored Enterprise Server Summary workspace . . . . 48
procedures . . . . . . . . . . . . . . 8 Errorlog Alerts workspace . . . . . . . . 48
Attribute groups that gather data from operating Filegroup Detail workspace . . . . . . . . 48
system or MS SQL Server files . . . . . . . 13 FileTable Detail workspace . . . . . . . . 49
Job Detail workspace . . . . . . . . . . 49
Chapter 2. Agent installation and Job Summary workspace . . . . . . . . . 49
configuration . . . . . . . . . . . . 15 Lock Resource Type Summary workspace . . . 49
Installing language packs . . . . . . . . . . 15 Log and Space Information workspace . . . . 49
Windows systems . . . . . . . . . . . 15 Log Shipping Database Details workspace . . . 49
UNIX or Linux systems . . . . . . . . . 16 Log Shipping Error Details workspace . . . . 49
Prerequisites checking . . . . . . . . . . . 16 Log Shipping Job Details workspace . . . . . 50
Running as a non-administrator user . . . . . . 17 MS SQL Server Historical Summarized
Agent-specific installation and configuration . . . 18 Availability workspace. . . . . . . . . . 50
Granting permissions . . . . . . . . . . 19 MS SQL Server Historical Summarized
Local configuration . . . . . . . . . . . 23 Availability Daily workspace . . . . . . . 50
Local environment variables . . . . . . . . 32 MS SQL Server Historical Summarized
Remote configuration . . . . . . . . . . 34 Availability Hourly workspace . . . . . . . 51
Reconfiguration . . . . . . . . . . . . 35 MS SQL Server Historical Summarized
Starting and stopping the Microsoft SQL Server Availability Weekly workspace . . . . . . . 51
agent . . . . . . . . . . . . . . . 35 MS SQL Server Historical Summarized Capacity
Setting up the Microsoft SQL Server agent in a workspace . . . . . . . . . . . . . . 52
cluster environment . . . . . . . . . . 36 MS SQL Server Historical Summarized Capacity
Daily workspace. . . . . . . . . . . . 52
Chapter 3. Workspaces reference . . . 41 MS SQL Server Historical Summarized Capacity
Hourly workspace . . . . . . . . . . . 52
Predefined workspaces . . . . . . . . . . 42
MS SQL Server Historical Summarized Capacity
Additional Availability Database Details
Weekly workspace . . . . . . . . . . . 53
workspace . . . . . . . . . . . . . . 44
MS SQL Server Historical Summarized
Additional Database Details workspace . . . . 44
Performance workspace . . . . . . . . . 53
Analysis Services Data Mining Statistics
MS SQL Server Historical Summarized
workspace . . . . . . . . . . . . . . 44
Performance Daily workspace . . . . . . . 53
Analysis Services Memory Statistics workspace 44
MS SQL Server Historical Summarized
Analysis Services Storage Engine Query
Performance Hourly workspace . . . . . . 53
Processing workspace . . . . . . . . . . 44
MS SQL Server Historical Summarized
Analysis Services Rows Processing workspace . . 44
Performance Weekly workspace . . . . . . 54
Availability Database Information workspace . . 45
MS SQL Server Overview. . . . . . . . . 54
Availability Groups Information workspace. . . 45
Process Holding Lock SQL Text workspace . . . 54
Availability Groups Information In Cluster
Processes workspace . . . . . . . . . . 54
workspace . . . . . . . . . . . . . . 45
Server Batch Statistics workspace . . . . . . 55
Availability Replicas Information workspace . . 46
Server Configuration workspace . . . . . . 55
Server Detail workspace . . . . . . . . . 55

© Copyright IBM Corp. 2005, 2012 vii

 Services Detail workspace . . . . . . . . 55 MS SQL Enterprise Log Shipping DB Details
Server Locking workspace . . . . . . . . 55 attributes . . . . . . . . . . . . . . 144
Server Statistics workspace . . . . . . . . 56 MS SQL Error Event Details attributes . . . . 145
Server Summary workspace . . . . . . . . 56 MS SQL Filegroup Detail attributes . . . . . 146
SQL Server CPU Bottleneck workspace . . . . 56 MS SQL FileTable Detail attributes . . . . . 147
SQL Server Disk Space and Logon Statistics . . 56 MS SQL Individual Queries Details attributes 148
SQL Server Integration Service Details workspace 56 MS SQL Integration Service Details attributes 151
SQL Server Logical Disk Bottleneck workspace 56 MS SQL Job Detail attributes . . . . . . . 152
SQL Server Memory Bottleneck workspace . . . 57 MS SQL Job Summary attributes . . . . . . 156
SQL Server Physical Disk Bottleneck workspace 57 MS SQL Lock Conflict Detail attributes . . . . 158
SQL Server Service Broker Information MS SQL Lock Detail attributes. . . . . . . 159
workspace . . . . . . . . . . . . . . 57 MS SQL Lock Resource Type Summary
SQL Server Transactions Summary workspace . . 57 attributes . . . . . . . . . . . . . . 162
SQL Text for Process ID workspace . . . . . 58 MS SQL Lock Summary attributes . . . . . 163
Table Detail workspace . . . . . . . . . 58 MS SQL Log Shipping DB Details attributes . . 165
Table Information workspace . . . . . . . 58 MS SQL Log Shipping Errors attributes. . . . 166
Cross-linked workspaces . . . . . . . . . 58 MS SQL Log Shipping Jobs Detail attributes . . 166
MS SQL Memory Manager attributes . . . . 167
Chapter 4. Attributes reference . . . . 59 MS SQL Problem Detail attributes . . . . . 170
Attributes in each attribute group . . . . . . . 59 MS SQL Problem Summary attributes . . . . 171
MS SQL Additional Database Details attributes 60 MS SQL Process Detail attributes . . . . . . 172
MS SQL Additional Availability Database Details MS SQL Process Summary attributes . . . . 176
attributes . . . . . . . . . . . . . . 62 MS SQL Remote Servers attributes . . . . . 178
MS SQL Analysis Services Data Mining attributes 63 MS SQL Resource Pool Stats attributes . . . . 179
MS SQL Analysis Services MDX Processing MS SQL Running Queries Details attributes . . 181
attributes . . . . . . . . . . . . . . 65 MS SQL Service Broker Activation attributes . . 185
MS SQL Analysis Services Memory Statistics MS SQL Service Broker Statistics attributes . . 186
attributes . . . . . . . . . . . . . . 69 MS SQL Service Broker Transport attributes . . 188
MS SQL Analysis Services Rows Processing MS SQL Services Detail attributes . . . . . 190
attributes . . . . . . . . . . . . . . 77 MS SQL Server Detail attributes . . . . . . 192
MS SQL Analysis Services Storage Engine Query MS SQL Server Properties attributes . . . . . 195
attributes . . . . . . . . . . . . . . 78 MS SQL Server Summary attributes . . . . . 198
MS SQL Availability Database Details attributes 85 MS SQL Server Transactions Summary attributes 203
MS SQL Availability Database Details In Cluster MS SQL Statistics Detail attributes . . . . . 205
attributes . . . . . . . . . . . . . . 90 MS SQL Statistics Summary attributes . . . . 206
MS SQL Availability Database Statistics attributes 91 MS SQL Table Detail attributes . . . . . . 208
MS SQL Availability Database Summary MS SQL Table Summary attributes . . . . . 210
attributes . . . . . . . . . . . . . . 93 MS SQL Text attributes . . . . . . . . . 212
MS SQL Availability Groups Details attributes . . 96 MS SQL Workload Group Stats attributes . . . 213
MS SQL Availability Groups Details In Cluster VMS SQL Remote Servers attributes . . . . . 215
attributes . . . . . . . . . . . . . . 99 VMS SQL Server Enterprise View attributes . . 217
MS SQL Availability Group Listener Details
attributes . . . . . . . . . . . . . . 101 Chapter 5. Situations reference. . . . 227
MS SQL Availability Groups Summary attributes 103 Predefined situations . . . . . . . . . . . 228
MS SQL Availability Replicas Details attributes 105 Situation descriptions. . . . . . . . . . . 230
MS SQL Availability Replicas Details In Cluster MS_SQL_Block_Critical . . . . . . . . . 230
attributes . . . . . . . . . . . . . . 109 MS_SQL_Block_Warning . . . . . . . . 230
MS SQL Availability Replicas Statistics attributes 110 MS_SQL_Cache_Ave_FreePage_Crit . . . . . 230
MS SQL Availability Replicas Status attributes 112 MS_SQL_Cache_Ave_FreePage_Warn . . . . 230
MS SQL Availability Replicas Status Summary MS_SQL_Cache_Hit_Ratio_Crit . . . . . . 230
attributes . . . . . . . . . . . . . . 115 MS_SQL_Cache_Hit_Ratio_Warn . . . . . . 230
MS SQL Batch Stats attributes . . . . . . . 118 MS_SQL_Cache_Max_FreePage_Crit . . . . . 230
MS SQL Blocked Queries Details attributes . . 119 MS_SQL_Cache_Max_FreePage_Warn . . . . 230
MS SQL Configuration attributes . . . . . . 121 MS_SQL_Client_Cnt_Pct_Used_Crit . . . . . 230
MS SQL Database Detail attributes . . . . . 122 MS_SQL_Client_Cnt_Pct_Used_Warn . . . . 230
MS SQL Database Mirroring attributes . . . . 131 MS_SQL_Collection_Status_Warning. . . . . 230
MS SQL Database Summary attributes . . . . 135 MS_SQL_CPU_Critical . . . . . . . . . 231
MS SQL Device Detail attributes . . . . . . 136 MS_SQL_CPU_Warning . . . . . . . . . 231
MS SQL Enterprise Database Mirroring MS_SQL_DB_Error_Status . . . . . . . . 231
attributes . . . . . . . . . . . . . . 140 MS_SQL_DB_Freespace_Critical . . . . . . 231
MS_SQL_DB_Join_State_Warn . . . . . . . 231

viii Microsoft SQL Server agent: User’s Guide

MS_SQL_DB_Space_Pct_Used_Warn. . . . . 231 MS_SQL_Total_Locks_Warning . . . . . . 237
MS_SQL_DB_Space_Pct_Used_Crit . . . . . 231
MS_SQL_DB_Num_Errors_Warning . . . . . 231 Chapter 6. Take Action commands
MS_SQL_DB_Freespace_Warning . . . . . . 231 reference . . . . . . . . . . . . . 239
MS_SQL_DB_Status_Crit . . . . . . . . 231
Predefined Take Action commands . . . . . . 239
MS_SQL_DB_Suspect_Crit . . . . . . . . 231
Database Check-up and Tune-up action . . . 240
MS_SQL_DB_Sync_Health_Crit . . . . . . 231
Dump Database action . . . . . . . . . 241
MS_SQL_DB_Sync_State_Warn . . . . . . 231
Dump Transaction Log action . . . . . . . 244
MS_SQL_Device_Free_PCT_Warning . . . . 231
Rebuild Fragmented Indexes action . . . . . 246
MS_SQL_Error_Event_Warning . . . . . . 232
Refresh Query Optimizer Statistics action . . . 248
MS_SQL_Error_Warning. . . . . . . . . 232
Start SQL Server action . . . . . . . . . 249
MS_SQL_ErrorLog_Size_Warning. . . . . . 232
Stop SQL Server action . . . . . . . . . 250
MS_SQL_Failed_Jobs_Crit . . . . . . . . 232
Update Space Usage Information action . . . 250
MS_SQL_Fragmentation_Crit . . . . . . . 232
MS_SQL_Fragmentation_Warn . . . . . . 232
MS_SQL_Group_Role_Crit . . . . . . . . 232 Chapter 7. Policies reference. . . . . 253
MS_SQL_IOERR_Startup_Warning . . . . . 232 Predefined policies . . . . . . . . . . . 253
MS_SQL_IO_Disk_Errors_Crit . . . . . . . 232 Policy descriptions . . . . . . . . . . . 253
MS_SQL_IOError_Curintvl_Warning. . . . . 232 MS_SQL_DB_free_space_critical . . . . . . 253
MS_SQL_Log_Freespace_Critical . . . . . . 232
MS_SQL_Log_Freespace_Warning . . . . . 232 Chapter 8. Tivoli Common Reporting
MS_SQL_Log_Shipping_Status_Err . . . . . 233 for the monitoring agent . . . . . . 255
MS_SQL_Log_Shipping_Warning . . . . . . 233 Cognos-based report packages. . . . . . . . 255
MS_SQL_Log_Space_Pct_Used_Crit . . . . . 233 Prerequisites. . . . . . . . . . . . . 255
MS_SQL_Log_Space_Pct_Used_Warn . . . . 233 Importing Cognos report packages . . . . . 257
MS_SQL_Log_Suspend_Warning . . . . . . 233 Cognos data models and reports . . . . . . 258
MS_SQL_LogonPct_Crit . . . . . . . . . 233
MS_SQL_LogonPct_Warning . . . . . . . 233 Chapter 9. Troubleshooting . . . . . 269
MS_SQL_Long_Running_Transaction_Warning 233
Gathering product information for IBM Software
MS_SQL_Mirror_Failover_Critical . . . . . 233
Support . . . . . . . . . . . . . . . 269
MS_SQL_Mirror_Lagging_Warning . . . . . 233
Built-in troubleshooting features . . . . . . . 269
MS_SQL_Mirror_Suspended_Warning . . . . 233
Problem classification. . . . . . . . . . . 270
MS_SQL_Network_Read_Rate_Crit . . . . . 234
Trace logging . . . . . . . . . . . . . 270
MS_SQL_Network_Read_Rate_Warn . . . . 234
Overview of log file management . . . . . 270
MS_SQL_Network_Write_Rate_Crit . . . . . 234
Examples of trace logging . . . . . . . . 270
MS_SQL_Network_Write_Rate_Warn . . . . 234
Principal trace log files . . . . . . . . . 271
MS_SQL_Num_Process_Blocked_Crit . . . . 234
Enabling detailed tracing in the collector trace log 274
MS_SQL_Num_Process_Blocked_Warn . . . . 234
Option one: modify the settings file . . . . . 274
MS_SQL_Oldest_Transaction_Crit . . . . . 234
Option two: modify environment variables . . 274
MS_SQL_Proc_Buffs_Used_Crit . . . . . . 235
RAS trace parameters . . . . . . . . . . 275
MS_SQL_Proc_Buffs_Used_Warn . . . . . . 235
Setting RAS trace parameters by using the GUI 275
MS_SQL_Proc_Cache_Active_Crit . . . . . 235
Manually setting RAS trace parameters. . . . 276
MS_SQL_Proc_Cache_Active_Warn . . . . . 235
Problems and workarounds . . . . . . . . 277
MS_SQL_Proc_Cache_Used_Crit . . . . . . 235
Installation and configuration troubleshooting 277
MS_SQL_Proc_Cache_Used_Warn . . . . . 236
Troubleshooting for SQL Server . . . . . . 286
MS_SQL_Process_Blocked_Warning . . . . . 236
Agent troubleshooting . . . . . . . . . 287
MS_SQL_Process_Infected_Warning . . . . . 236
Troubleshooting for remote deployment . . . 296
MS_SQL_Processes_Bad_Warning . . . . . 236
Workspace troubleshooting . . . . . . . . 297
MS_SQL_Processes_Stop_Warning . . . . . 236
Situation troubleshooting . . . . . . . . 301
MS_SQL_ProcessLockSleep_Warning . . . . 236
Take Action command troubleshooting . . . . 304
MS_SQL_ProcessOthSleep_Warning . . . . . 236
Tivoli Common Reporting troubleshooting . . 305
MS_SQL_Rem_Serv_Stat_Critical . . . . . . 236
Support information . . . . . . . . . . . 307
MS_SQL_Repl_Latency_Crit . . . . . . . 236
MS_SQL_Repl_Latency_Warn . . . . . . . 236
MS_SQL_Replica_Join_State_Warn . . . . . 236 Appendix A. Upgrading for warehouse
MS_SQL_Replica_Role_Health_Crit . . . . . 236 summarization . . . . . . . . . . . 309
MS_SQL_Replica_Sync_Health_Warn . . . . 237 Tables in the warehouse . . . . . . . . . . 309
MS_SQL_Replicas_Conn_State_Crit . . . . . 237 Effects on summarized attributes . . . . . . . 309
MS_SQL_Status_Critical . . . . . . . . . 237 Upgrading your warehouse with limited user
MS_SQL_Status_Inactive . . . . . . . . 237 permissions . . . . . . . . . . . . . . 310
MS_SQL_Total_Locks_Critical . . . . . . . 237

Contents ix
Appendix B. Event mapping . . . . . 313 Configuring the Tivoli Event Integration Facility
(EIF) probe to enrich events . . . . . . . 396
Appendix C. Discovery Library Creating a service in Tivoli Business Service
Manager . . . . . . . . . . . . . . 397
Adapter for the Microsoft SQL Server Creating a data source mapping for each data
agent . . . . . . . . . . . . . . . 385 source . . . . . . . . . . . . . . . 397
DLA data model class types represented in CDM 385 Configuring additional IBM Tivoli Monitoring
DLA data model classes for Microsoft SQL Server web services. . . . . . . . . . . . . 398
agent . . . . . . . . . . . . . . . . 385 Viewing data in the Tivoli Enterprise Portal . . 398
SqlServer class . . . . . . . . . . . . 386
SqlServerDatabase class . . . . . . . . . 387 Appendix E. Documentation library 399
SqlServerTable class . . . . . . . . . . 388
Prerequisite publications. . . . . . . . . . 399
SqlServerProcess class . . . . . . . . . 390
Related publications . . . . . . . . . . . 400
TMSAgent class . . . . . . . . . . . 391
Other sources of documentation . . . . . . . 400

Appendix D. Integration with Tivoli Accessibility . . . . . . . . . . . . 403

Business Service Manager . . . . . 395
Components for integrating with Tivoli Business
Notices . . . . . . . . . . . . . . 405
Service Manager . . . . . . . . . . . . 395
Trademarks . . . . . . . . . . . . . . 407
Tasks to integrate the agent with Tivoli Business
Service Manager . . . . . . . . . . . . 396
Installing the Discovery Library Toolkit on the Index . . . . . . . . . . . . . . . 409
Tivoli Business Service Manager . . . . . . 396

x Microsoft SQL Server agent: User’s Guide

Chapter 1. Overview of the agent
The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft SQL Server Agent
provides you with the capability to monitor Microsoft SQL Server. You can also use the agent to take
basic actions with the Microsoft SQL Server.

IBM® Tivoli® Monitoring is the base software for the Microsoft SQL Server agent.

The Microsoft SQL Server agent monitors the following functions:

v Availability and resources
v Performance
v Error and event log
v Historical data

Features of the monitoring agent

The Microsoft SQL Server agent offers a central point of management for distributed databases. The
monitoring agent provides a comprehensive means for gathering exactly the information you need to
detect problems early and prevent them. Information is standardized across all systems so you can
monitor hundreds of servers from a single workstation. You can easily collect and then analyze specific
information using the Tivoli Enterprise Portal interface.

The Microsoft SQL Server agent is an intelligent, remote monitoring agent that resides on managed
systems. It assists you in anticipating trouble and warns system administrators when critical events take
place on systems. With the Microsoft SQL Server agent, database and system administrators can set
threshold levels as desired and can set flags to alert them when the system reaches these thresholds.

This monitoring agent provides the following benefits:

v Simplifies application and system management by managing applications, operating systems, and
resources across your environment.
v Increases profits by providing you with real-time access to reliable, up-to-the-minute data that allows
you to make faster, better-informed operating decisions.
v Scales and ports to new Windows operating systems.
v Improves system performance by letting you integrate, monitor, and manage your system, network,
console, and mission-critical applications. The monitoring agent sends an alert when conditions on the
system network meet threshold-based conditions. These alerts notify your system administrator to limit
and control database usage. You can view data gathered by monitoring agents in reports and charts for
the status of your distributed database systems.
v Enhances efficiency by monitoring different Microsoft SQL Server versions on separate systems and
networks from a single PC screen. Depending on your configuration, you can collect and monitor data
across systems. The monitoring agent gathers and filters status information at the managed system
rather than at the hub, eliminating unnecessary data transmission and sending only data that is
relevant to changes in status conditions. The Microsoft SQL Server agent helps you to monitor and to
gather the consistent, accurate, and timely information you need to effectively perform your job.

© Copyright IBM Corp. 2005, 2012 1

IBM Tivoli Monitoring
IBM Tivoli Monitoring provides a way to monitor the availability and performance of all the systems in
your enterprise from one or several designated workstations. It also provides useful historical data that
you can use to track trends and to troubleshoot system problems.

You can use IBM Tivoli Monitoring to achieve the following tasks:
v Monitor for alerts on the systems that you are managing by using predefined situations or custom
situations.
v Establish your own performance thresholds.
v Trace the causes leading to an alert.
v Gather comprehensive data about system conditions.
v Use policies to take actions, schedule work, and automate manual tasks.

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. You can use the
consolidated view of your environment as seen in the Tivoli Enterprise Portal to monitor and resolve
performance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” on page 399 for complete
information about IBM Tivoli Monitoring and the Tivoli Enterprise Portal.

New in this release

For version 6.3 of the Microsoft SQL Server agent, the following enhancements have been made since
version 6.2.3, including the fix packs:
v Additional supported operating systems as listed in the Prerequisites topic for the Microsoft SQL
Server agent in the IBM Tivoli Composite Application Manager for Microsoft Applications Information
Center
v New attribute groups:
– MS SQL Analysis Services Data Mining
– MS SQL Analysis Services MDX Processing
– MS SQL Analysis Services Memory Statistics
– MS SQL Analysis Services Rows Processing
– MS SQL Analysis Services Storage Engine Query
– MS SQL Availability Database Details
– MS SQL Availability Database Details In Cluster
– MS SQL Availability Database Statistics
– MS SQL Availability Database Summary
– MS SQL Availability Groups Details attributes
– MS SQL Availability Groups Details In Cluster
– MS SQL Availability Group Listener Details
– MS SQL Availability Groups Summary
– MS SQL Availability Replicas Details
– MS SQL Availability Replicas Details In Cluster
– MS SQL Availability Replicas Statistics
– MS SQL Availability Replicas Status
– MS SQL Availability Replicas Status Summary
– MS SQL Blocked Queries Details
– MS SQL Running Queries Details

2 Microsoft SQL Server agent: User’s Guide

 – MS SQL FileTable Detail
– MS SQL Individual Queries Details
– MS SQL Running Queries Details
– MS SQL Service Broker Activation
– MS SQL Service Broker Statistics
– MS SQL Service Broker Transport
– MS SQL Server Transactions Summary
– MS SQL Table Summary
– MS SQL Additional Database Details
– MS SQL Additional Availability Database Details
– MS SQL Server Properties
v Modified attribute groups:
– MS SQL Server Summary
– MS SQL Statistics Summary
– MS SQL Job details
– MS SQL Table Detail
– MS SQL Lock Detail
– MS SQL Server Detail
– MS SQL Device Detail
– MS SQL Server Properties
– MS SQL Table Detail
– MS SQL Filegroup Detail
v New navigator items:
– AlwaysOn
– Services
v New workspaces:
– SQL Server Transactions Summary
– Availability Groups Information
– Availability Replicas Status
– Availability Database Information
– Availability Replicas Information
– Additional Availability Database Details
– Availability Replicas and Database Information
– SQL Server Service Broker Information
– SQL Server Integration Service Details
– Services Detail
– Table Information
– Analysis Services Data Mining Statistics
– Analysis Services Memory Statistics
– Analysis Services Storage Engine Query Processing
– Analysis Services Rows Processing
– Query Details
– Individual Queries Details
– FileTable Detail
– Additional Database Detail

Chapter 1. Overview of the agent 3

 – Availability Groups Information In Cluster
v New predefined situations:
– MS_SQL_Replica_Join_State_Warn
– MS_SQL_DB_Join_State_Warn
– MS_SQL_Group_Role_Crit
– MS_SQL_DB_Sync_Health_Crit
– MS_SQL_Replicas_Conn_State_Crit
– MS_SQL_Replica_Role_Health_Crit
– MS_SQL_Replica_Sync_Health_Warn
– MS_SQL_DB_Sync_State_Warn
v New environment variables:
– COLL_JOB_DISABLED
– COLL_KOQFGRPD_MAX_ROW
– COLL_KOQDEVD_MAX_ROW
– COLL_KOQDBD_INTERVAL
– COLL_DBD_FRENAME_RETRY_CNT
v Support for handling multilingual error log file in the MS SQL Problem Detail attribute group
v New koqErrConfg.ini file, which is saved at candle_home\TMAITM6 directory for a 32-bit agent, and at
candle_home\TMAITM6_x64 for a 64-bit agent
v New Cognos® data models and Cognos-based reports
v Added the self-describing agent support for the monitoring agent to generate agent support files as
part of the agent image
v Added the prerequisites checking utility to verify prerequisites before the agent is installed or
upgraded
v Integration with Tivoli Business Service Manager V6.1 or later
v Updated koq.baroc file to support Tivoli Enterprise Console® event mapping

Components of the IBM Tivoli Monitoring environment

After you install and set up the Microsoft SQL Server agent, you have an environment that contains the
client, server, and monitoring agent implementation for Tivoli Monitoring.

This Tivoli Monitoring environment contains the following components:

Tivoli Enterprise Portal client
The portal has a user interface based on Java™ for viewing and monitoring your enterprise.
Tivoli Enterprise Portal Server
The portal server is placed between the client and the Tivoli Enterprise Monitoring Server and
enables retrieval, manipulation, and analysis of data from the monitoring agents. The Tivoli
Enterprise Portal Server is the central repository for all user data.
Tivoli Enterprise Monitoring Server
The monitoring server acts as a collection and control point for alerts received from the
monitoring agents, and collects their performance and availability data. The Tivoli Enterprise
Monitoring Server is also a repository for historical data.
Tivoli Enterprise Monitoring Agent, Microsoft SQL Server agent
This monitoring agent collects data and distributes the data to the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal, Tivoli Data Warehouse, and Tivoli
Integrated Portal.
Multiple copies of this agent can run on the same system.

4 Microsoft SQL Server agent: User’s Guide

IBM Tivoli Netcool/OMNIbus
Tivoli Netcool/OMNIbus is an optional component and the recommended event management
component. The Netcool/OMNIbus software is a service level management (SLM) system that
delivers real-time, centralized monitoring of complex networks and IT domain events. Event
information is tracked in a high-performance, in-memory database and presented to specific users
through individually configurable filters and views. The software includes automation functions
that you can use to perform intelligent processing on managed events. You can use this software
to forward events for Tivoli Monitoring situations to Tivoli Netcool/OMNIbus.
IBM Tivoli Enterprise Console
The Tivoli Enterprise Console is an optional component that acts as a central collection point for
events from various sources, including events from other Tivoli software applications, Tivoli
partner applications, custom applications, network management platforms, and relational
database systems. You can view these events through the Tivoli Enterprise Portal (by using the
event viewer), and you can forward events from Tivoli Monitoring situations to the Tivoli
Enterprise Console component. If you do not already use Tivoli Enterprise Console and need an
event management component, you can choose to use IBM Tivoli Netcool/OMNIbus.
IBM Tivoli Common Reporting
Tivoli Common Reporting is a separately installable feature available to users of Tivoli software
that provides a consistent approach to generating and customizing reports. Some individual
products provide reports that are designed for use with Tivoli Common Reporting and have a
consistent look and feel.
IBM Tivoli Application Dependency Discovery Manager (TADDM)
TADDM delivers automated discovery and configuration tracking capabilities to build application
maps that provide real-time visibility into application complexity.
IBM Tivoli Business Service Manager
The Tivoli Business Service Manager component delivers real-time information to help you
respond to alerts effectively based on business requirements. Optionally, you can use this
component to meet service-level agreements (SLAs). Use the Tivoli Business Service Manager
tools to help build a service model that you can integrate with Tivoli Netcool/OMNIbus alerts or
optionally integrate with data from an SQL data source. Optional components provide access to
data from other IBM Tivoli applications such as Tivoli Monitoring and TADDM.

Agent Management Services

You can use IBM Tivoli Monitoring Agent Management Services to manage the Microsoft SQL Server
agent. These services are available in the following IBM Tivoli Monitoring OS agents: Windows, Linux,
and UNIX. The services are designed to keep the Microsoft Active Directory agent available, and to
provide information about the status of the product to the Tivoli Enterprise Portal. IBM Tivoli Monitoring
V6.2.2, Fix Pack 2 or later provides support for Agent Management Services. For more information about
Agent Management Services, see the IBM Tivoli Monitoring Administrator's Guide, "Agent Management
Services" chapter.

User interface options

Installation of the base software and other integrated applications provides the following interfaces that
you can use to work with your resources and data:
Tivoli Enterprise Portal user interface
The client interface is a graphical user interface (GUI) based on Java on a Windows or Linux
workstation. You can run the Tivoli Enterprise Portal as a desktop application or a browser
application. The browser application is automatically installed with the Tivoli Enterprise Portal
Server. The desktop application is installed using the Tivoli Monitoring installation media or with

Chapter 1. Overview of the agent 5

 Java Web Start. Tivoli Enterprise Portal Server. To start the Tivoli Enterprise Portal browser client
in your Internet browser, enter the URL for a specific Tivoli Enterprise Portal browser client
installed on your Web server.
Command line interface
You can use IBM Tivoli Monitoring commands to manage the Tivoli Monitoring components and
their configuration. There are also commands that you can run at the Tivoli Enterprise Console
event server or the Tivoli Netcool/OMNIbus ObjectServer to configure event synchronization for
enterprise situations.
Manage Tivoli Enterprise Monitoring Services window
The window for the Manage Tivoli Enterprise Monitoring Services utility is used for configuring
the agent and starting Tivoli services not already designated to start automatically.
IBM Tivoli Enterprise Console
An event management application that integrates system, network, database, and application
management to help ensure the optimal availability of an IT service for an organization.

Microsoft SQL Server agent data collection

This section provides information about how the monitoring agent collects data, including the following
topics:
v “Collection processes”
v “Attribute groups that gather data from Microsoft SQL Server SELECT statements and stored
procedures” on page 8
v “Attribute groups that gather data from operating system or MS SQL Server files” on page 13

Collection processes
The Microsoft SQL Server agent gathers data when it is requested by a workspace refresh, a situation
sampling of attributes, or historical data collection. At that time, the monitoring agent gathers all
attributes in the attribute groups that make up a workspace or situation. The default refresh or sampling
intervals do not put a significant load on the system or the Microsoft SQL Server as it gathers the data.
Most of the attributes gathered by the Microsoft SQL Server agent come from monitoring data provided
by Windows Performance Monitor (Perfmon). This data is acquired though the use of requests for
Perfmon data and SQL database SELECT statements. The Perfmon and SQL data are gathered on a
defined cycle while most other attributes are gathered on demand when requested through a workspace
refresh, a situation sampling of attributes, or historical data collection. Other attribute groups contain data
that is collected from system information or external Microsoft SQL Server data such as the database
instance log. This data is primarily gathered on demand, as it is requested. The Microsoft SQL Server
agent attempts to lessen the possibility of over sampling by maintaining a cache of attribute data for a set
length of time. If the data is sampled within a shorter duration than the interval set for the cache, the
cache data is considered fresh and the collector does not acquire new data.

Table 1 provides information about when the attribute data is gathered (on demand or cyclically) and the
cache duration for each Microsoft SQL Server agent attribute group.
Table 1. When data is collected and cache duration for attribute groups
When data is collected (cycle time
Attribute group or on demand) Cache duration in seconds
MS SQL Batch Stats Every 180 seconds No caching
MS SQL Configuration On demand 90
MS SQL Database Detail On demand 10
MS SQL Database Mirroring On demand No caching
MS SQL Database Summary Every 180 seconds No caching

6 Microsoft SQL Server agent: User’s Guide

Table 1. When data is collected and cache duration for attribute groups (continued)
When data is collected (cycle time
Attribute group or on demand) Cache duration in seconds
MS SQL Device Detail On demand No caching
MS SQL Enterprise Log Shipping DB On demand No caching
Details
MS SQL Filegroup On demand No caching
MS SQL Job Detail Every 180 seconds No caching
MS SQL Job Summary On demand No caching
MS SQL Lock Conflict Detail On demand No caching
MS SQL Lock Detail On demand No caching
MS SQL Lock Resource Type Summary Every 300 seconds No caching
MS SQL Lock Summary On demand No caching
MS SQL Log Shipping DB Details On demand No caching
MS SQL Log Shipping Errors On demand No caching
MS SQL Log Shipping Jobs Detail On demand No caching
MS SQL Memory Manager On demand No caching
MS SQL Problem Detail Every 180 seconds No caching
MS SQL Process Detail On demand 10
MS SQL Process Summary Every 180 seconds No caching
MS SQL Problem Summary Every 180 seconds No caching
MS SQL Remote Servers Every 60 seconds No caching
MS SQL Resource Pool Stats On demand No caching
MS SQL Server Detail On demand 60
MS SQL Server Enterprise View On demand No caching
MS SQL Server Summary Every 180 seconds No caching
MS SQL Services Detail On demand No caching
MS SQL Statistics Detail On demand 300
MS SQL Statistics Summary Every 60 seconds No caching
MS SQL Table Detail On demand 120
MS SQL Text On demand No caching
MS SQL Workload Group Stats On demand No caching
VMS SQL Remote Servers On demand No caching
VMS SQL Server Enterprise View On demand No caching
MS SQL Server Transaction Summary On demand 10
MS SQL Service Broker Activation On demand 10
MS SQL Service Broker Statistics On demand 10
MS SQL Service Broker Transport On demand 10
MS SQL Table Summary On demand 120
MS SQL Integration Service Details On demand No caching
MS SQL Analysis Services Data Mining On demand No caching
MS SQL Analysis Services Memory On demand No caching
statistics

Chapter 1. Overview of the agent 7

Table 1. When data is collected and cache duration for attribute groups (continued)
When data is collected (cycle time
Attribute group or on demand) Cache duration in seconds
MS SQL Analysis Services Storage Engine On demand No caching
Query
MS SQL Analysis Services MDX On demand No caching
Processing
MS SQL Analysis Services Rows On demand No caching
Processing
MS SQL Running Queries Details On demand 30
MS SQL Individual Queries Details On demand 30
MS SQL Blocked Queries Details On demand 10
MS SQL FileTable Detail On demand 120
MS SQL Additional Database Details On demand 60
MS SQL Availability Groups Details On demand 60
MS SQL Availability Replicas Details On demand 60
MS SQL Availability Replicas Status On demand 60
MS SQL Availability Replicas Status On demand 60
Summary
MS SQL Availability Groups Summary On demand 60
MS SQL Availability Replicas Statistics On demand 60
MS SQL Availability Database Details On demand 60
MS SQL Availability Database Statistics On demand 60
MS SQL Availability Database Summary On demand 60
MS SQL Availability Group Listener On demand 60
Details
MS SQL Availability Groups Details In On demand 60
Cluster
MS SQL Availability Replicas Details In On demand 60
Cluster
MS SQL Availability Database Details In On demand 60
Cluster
MS SQL Additional Availability Details On demand 60
MS SQL Server Properties On demand 10

The Microsoft SQL Server agent maintains long-running processes for the monitoring agent that
communicates with the Tivoli Enterprise Monitoring Server and the collector that drives data collection.
Short-running processes are used to access system data, access database instance log file data, issue and
process the output of Microsoft SQL Server stored procedures, and perform other database instance
interactions.

Attribute groups that gather data from Microsoft SQL Server SELECT
statements and stored procedures
Some of the attribute groups gather data from the data that is returned by Microsoft SQL Server SELECT
statements, stored procedures, or both. Table 2 on page 9 provides information about how each attribute
group collects data (SELECT statements or stored procedures). The table also provides the following
information:

8 Microsoft SQL Server agent: User’s Guide

v For attribute groups that use SELECT statements to gather data, the number of individual SELECT
statements issued for the group and the tables that are accessed are listed.
v For attribute groups that use stored procedures to gather data, the names of the stored procedures are
listed.
Table 2. Key aspects of data gathering for attribute groups
Attribute group Primary Number of Tables accessed Name of stored
collection SELECT procedures
mechanism statements
issued
MSSQL Batch Stats Perfmon 0 None None
MSSQL Server SELECT and 5 sysprocesses, sysjobhistory serverproperty
Summary Perfmon ('processid'), DBCC
MSSQL Server Detail SELECT and 5 sysprocesses, sysjobhistory serverproperty
Perfmon ('processid'), DBCC
MSSQL Database SELECT and 4 sysdatabases, sysfiles sp_replcounters
Summary Perfmon
MSSQL Database SELECT and 4 sysdatabases, sysfiles sp_replcounters
Detail Perfmon
MSSQL Database SELECT and 2 sys.database_mirroring None
Mirroring Perfmon
MSSQL Device Detail SELECT and 4 sysfiles, sysdevices, sysusages, None
Perfmon spt_values
MSSQL Enterprise SELECT 1 log_shipping_monitor_ None
Log Shipping DB primary, log_shipping_monitor_
Details history_detail, log_shipping_
monitor_secondary
MSSQL Lock Detail SELECT 2 syslockinfo, sysobjects None
MSSQL Lock Conflict SELECT 1 sysprocesses None
Detail
MSSQL Log SELECT 1 log_shipping_monitor_ None
Shipping DB Details primary, log_shipping_
monitor_history_detail,
log_shipping_
monitor_secondary
MSSQL Log SELECT 1 log_shipping_ None
Shipping Errors monitor_error_detail
MSSQL Log SELECT 1 log_shipping_monitor_ None
Shipping Jobs Detail history_detail, sysjobhistory
MSSQL Text SELECT 1 sysprocesses None
MSSQL Process SELECT 2 sysprocesses None
Summary
MSSQL Process SELECT 3 sysprocesses None
Detail
MSSQL Statistics SELECT 1 @@cpu_busy, @@io_busy, None
Summary @@idle, @@connections,
@@pack_sent, @@pack_received,
@@packet_errors, @@total_read,
@@total_write, @@total_errors,

Chapter 1. Overview of the agent 9

Table 2. Key aspects of data gathering for attribute groups (continued)
Attribute group Primary Number of Tables accessed Name of stored
collection SELECT procedures
mechanism statements
issued
MSSQL Statistics SELECT 1 @@cpu_busy, @@io_busy, None
Detail @@idle, @@connections,
@@pack_sent, @@pack_received,
@@packet_errors, @@total_read,
@@total_write, @@total_errors,
MSSQL Remote SELECT 1 sysservers None
Servers
MSSQL Resource Perfmon 0 None None
Pool Stats
MSSQL SELECT 1 sysconfigurations, None
Configuration sysscurconfigs, sysconfigures
MSSQL Server SELECT 1 sysprocesses, sysjobhistory, None
Enterprise View syslockinfo
MSSQL Lock SELECT and 16 syslockinfo None
Summary Perfmon
MSSQL Memory Perfmon 0 None None
Manager
MSSQL Job SELECT 3 syscategories, sysjobs,
Summary sysjobhistory
MSSQL Job Detail SELECT 3 syscategories, sysjobs,
sysjobhistor
MSSQL Filegroup SELECT and 2 sysdatabases, sysfiles None
Detail Perfmon
MSSQL Lock Perfmon 0 None None
Resource Type
Summary
MSSQL Workload Perfmon 0 None None
Group Stats
MS SQL Server Perfmon 0 None None
Transaction
Summary
MS SQL Service Perfmon 0 None None
Broker Activation
MS SQL Service Perfmon 0 None None
Broker Statistics
MS SQL Service Perfmon 0 None None
Broker Transport
MS SQL Table SELECT 3 sys.tables, sysindexes, None
Summary sys.dm_db_
index_physical_stats,
sys.dm_db_
partition_stats
MS SQL Integration Perfmon 0 None None
Service Details
MS SQL Analysis Perfmon 0 None None
Services Data Mining

10 Microsoft SQL Server agent: User’s Guide

Table 2. Key aspects of data gathering for attribute groups (continued)
Attribute group Primary Number of Tables accessed Name of stored
collection SELECT procedures
mechanism statements
issued
MS SQL Analysis Perfmon 0 None None
Services Memory
Statistics
MS SQL Analysis Perfmon 0 None None
Services Storage
Engine Query
MS SQL Analysis Perfmon 0 None None
Services MDX
Processing
MS SQL Analysis Perfmon 0 None None
Services Rows
Processing
MS SQL Running SELECT 1 sys.dm_exec_requests, None
Queries Details sys.dm_exec_sessions,
sys.dm_exec_sql_text
MS SQL Individual SELECT 1 sys.dm_exec_ None
Queries Details connections, sys.dm_exec_
requests, sys.dm_exec_sessions,
sys.dm_exec_sql_text
MS SQL Blocked SELECT 3 sys.dm_os_sys_info, None
Queries Details sys.configurations,
sys.dm_exec_
query_stats,
sys.dm_exec_requests,
sys.dm_exec_sql_text,
sys.dm_exec_
plan_attributes
MS SQL FileTable SELECT 3 sys.databases, sys.filetables, None
Detail sysindexes,
sys.dm_filestream_non_
transacted_handles
MS SQL Additional SELECT 1 sys.databases, sys.database_ None
Database Details filestream_options
MS SQL Availability SELECT 3 sys.availability_groups, None
Groups Details sys.dm_hadr_
availability_group_states,
sys.dm_hadr_
database_replica_states,
sys.dm_hadr_
availability_replica_
states, sys.availability_replicas
MS SQL Availability SELECT 2 sys.availability_replicas, None
Replicas Details sys.availability_groups,
sys.dm_hadr_
availability_group_
states

Chapter 1. Overview of the agent 11

Table 2. Key aspects of data gathering for attribute groups (continued)
Attribute group Primary Number of Tables accessed Name of stored
collection SELECT procedures
mechanism statements
issued
MS SQL Availability SELECT 2 sys.dm_hadr_ None
Replicas Status availability_replica_
states, sys.availability_groups,
sys.dm_hadr_
database_replica_states
MS SQL Availability SELECT 2 sys.dm_hadr_ None
Replicas Status availability_replica_
Summary states, sys.availability_groups,
sys.dm_hadr_database_
replica_states
MS SQL Availability SELECT 3 sys.availability_groups, None
Groups Summary sys.dm_hadr_
availability_group_
states, sys.dm_hadr_
database_replica_
states, sys.dm_hadr_
availability_replica_
states, sys.availability_replicas
MS SQL Availability Perfmon 0 None None
Replicas Statistics
MS SQL Availability SELECT 1 dm_hadr_database_ None
Database Details replica_states,
sys.availability_groups
MS SQL Availability Perfmon 0 None None
Database Statistics
MS SQL Availability SELECT 1 dm_hadr_database_ None
Database Summary replica_states,
sys.availability_groups
MS SQL Availability SELECT 1 sys.availability_group_ None
Group Listener listener_ip_addresses,
Details sys.availability_group_
listenerssavg_list,
sys.availability_groups
MS SQL Availability SELECT 1 sys.availability_groups_ None
Groups Details In cluster
Cluster
MS SQL Availability SELECT 1 sys.dm_hadr_ None
Replicas Details In availability_replica_
Cluster cluster_states, sys.availability
_groups_cluster, sys.dm_hadr_
availability_replica_
cluster_nodes,
MS SQL Availability SELECT 1 sys.dm_hadr_database_ None
Database Details In replica_cluster_states,
Cluster sys.availability_
databases_cluster,
sys.availability_groups_
cluster

12 Microsoft SQL Server agent: User’s Guide

Table 2. Key aspects of data gathering for attribute groups (continued)
Attribute group Primary Number of Tables accessed Name of stored
collection SELECT procedures
mechanism statements
issued
MS SQL Additional SELECT 1 sys.dm_hadr_database_ None
Availability Database replica_states, sys.dm_hadr_
Details availability_replica_states
MS SQL Server SELECT 1 SERVERPROPERTY None
Properties

Attribute groups that gather data from operating system or MS SQL

Server files
Table 3 contains information about the attribute groups that gather data from the operating system or
Microsoft SQL Server files.
Table 3. Data that is accessed by attribute groups that gather data from operating system or Microsoft SQL Server
files
Attribute group Data accessed
MS SQL Error Event Details MS SQL server error log file
MS SQL Problem Summary MS SQL server error log file
MS SQL Problem Detail MS SQL server error log file
MS SQL Services Detail Windows Services API
MS SQL Integration Details Windows Services API
MS SQL Analysis service Data Mining Windows Services API
MS SQL Analysis Service Memory Statistics Windows Services API
MS SQL Analysis Service Storage Engine Query Windows Services API
MS SQL Analysis Service MDX Processing Windows Services API
MS SQL Analysis Service Rows Processing Windows Services API

Chapter 1. Overview of the agent 13

14 Microsoft SQL Server agent: User’s Guide
Chapter 2. Agent installation and configuration
Agent installation and configuration requires the use of the IBM Tivoli Monitoring Installation and Setup
Guide and agent-specific installation and configuration information.

To install and configure Microsoft SQL Server agent, use the procedures for installing monitoring agents
in the IBM Tivoli Monitoring Installation and Setup Guide along with the agent-specific installation and
configuration information.

If you are installing silently by using a response file, see "Performing a silent installation of IBM Tivoli
Monitoring" in the IBM Tivoli Monitoring Installation and Setup Guide.

With the self-describing agent capability, new or updated IBM Tivoli Monitoring agents using IBM Tivoli
Monitoring V6.2.3 or later can become operational after installation without having to perform additional
product support installation steps. To take advantage of this capability, see "Enabling self-describing agent
capability at the hub monitoring server" in the IBM Tivoli Monitoring Installation and Setup Guide. Also, see
"Self-describing monitoring agents" in the IBM Tivoli Monitoring Administrator's Guide.

Installing language packs

You can install language packs for your agent support files on the Tivoli Enterprise Monitoring agent and
the Tivoli Enterprise Portal Server. There are separate procedures for installing language packs on
Windows and on UNIX or Linux systems.

Before you begin

Ensure that you have installed the product in English before you install a language pack for the agent
support files on the Tivoli Enterprise Monitoring Server, and the Tivoli Enterprise Portal Server.

Windows systems
This section contains the procedure for installing a language pack on Windows operating systems.

Procedure
1. Double-click lpinstaller.bat in the language pack CD to start the installation program.
2. Select the language of the installer and click OK.
3. Click Next on the Introduction panel.
4. Click Add/Update and click Next.
5. Select the folder in which the National Language Support package (NLSPackage) files are located.

Note: Usually the NLSPackage files are located in the nlspackage folder where the executable installer
is located.
6. Select the language support for the agent of your choice and click Next.

Note: You can select multiple languages by pressing the Ctrl key.
7. Select the languages that you want to install and click Next.
8. Examine the installation summary page and click Next to start the installation.
9. Click Finish after the installation completes.
10. Restart the Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Eclipse Help Server if any of
these components are installed.

© Copyright IBM Corp. 2005, 2012 15

UNIX or Linux systems
This section contains the procedure for installing a language pack on UNIX or Linux operating systems.

Procedure
1. Run the following command to create a temporary directory on the computer. Ensure that the full
path of the directory does not contain any spaces:
mkdir dir_name
2. Mount the language pack CD to the temporary directory that you have created.
3. Run the following command to start the installation program:
cd dir_name
lpinstall.sh ITM Home Directory

where ITM Home Directory is the location where you have installed IBM Tivoli Monitoring. Usually it
is /opt/IBM/ITM for AIX® and Linux systems.
4. Select the language of the installer and click OK.
5. Click Next on the Introduction panel.
6. Click Add/Update and click Next.
7. Select the folder in which the National Language Support package (NLSPackage) files are located.

Note: Usually, the NLSPackage files are located in the nlspackage folder where the installer
executable is located.
8. Select the language support for the agent of your choice and click Next.

Note: You can select multiple languages by pressing the Ctrl key.
9. Select the languages that you want to install and click Next.
10. Examine the installation summary page and click Next to start the installation.
11. Click Finish after the installation completes.
12. Restart the Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Eclipse Help Server if any of
these components are installed.

Prerequisites checking
The prerequisite checker utility verifies whether all the prerequisites that are required for the agent
installation are met. The prerequisite checker creates a log file that contains a report of all the
prerequisites checks when the prerequisite checker was run.

For the Microsoft SQL Server agent, the prerequisite checker verifies the following requirements:
v Memory
v Disk
v Operating systems
Additionally, the prerequisite checker verifies whether the user, who installs the agent, is a member of the
Administrators group.

For detailed information about installation prerequisites, see the Prerequisites topic for the agent in the
IBM Tivoli Composite Application Manager for Microsoft Applications Information Center
(http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/
welcome_msapps63.html).

You can run the prerequisite checker in stand-alone mode or remotely. For more information about the
prerequisite checker, see "Prerequisite Checking for IBM Tivoli Monitoring Agents" in the IBM Tivoli
Monitoring Installation and Setup Guide.

16 Microsoft SQL Server agent: User’s Guide

Running as a non-administrator user
This section provides information about running the Microsoft SQL Server agent as a non-administrator
user.

About this task

The Microsoft SQL Server agent can run as non-administrator. However, some functionality might not be
available. This process supports Domain Users only.

Procedure
1. Start Windows application Active Directory Users and Computers and create a domain user.
v Make sure that the new user is a member of the Domain Users group.
v Make sure that the SQL Server that you monitor is a member of Domain Computers.
2. Add the newly created domain user in the SQL Server Login user group. The domain user must have
sysadmin SQL Server role permissions on the SQL Server.
3. Log on to the SQL Server with a domain administrator account.
4. Use File Systems, to give the Modify permission to every drive that the Microsoft SQL Server agent
accesses and propagate permissions to all subdirectories. Complete the following steps to propagate
permissions:
a. Go to My Computer.
b. Right-click the drive.
c. Click the Security tab.
d. Add the newly created user.
e. Give modify permissions to the newly created user.
f. Click OK. This procedure takes a few minutes to apply permissions throughout the file system.
5. By using the Windows Registry, grant read access to HKEY_LOCAL_MACHINE, and propagate settings.
Complete the following steps to propagate settings:
a. Right-click the HKEY_LOCAL_MACHINE directory and select Permissions.
b. Add the newly created user.
c. Select the newly created user.
d. Select the Allow Read check box.
e. Click OK. This procedure takes a few minutes to propagate through the entire
HKEY_LOCAL_MACHINE tree.
6. By using the Windows Registry, grant the agent-specific registry permissions according to the
following list:
v If you installed a 32-bit agent on a 32-bit operating system, grant full access to the
HKEY_LOCAL_MACHINE\SOFTWARE\Candle directory, and then propagate the settings.
v If you installed a 32-bit agent on a 64-bit operating system, grant full access to the
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Candle directory, and then propagate the settings.
v If you installed a 64-bit agent on a 64-bit operating system, grant full access to the
HKEY_LOCAL_MACHINE\SOFTWARE\Candle directory, and then propagate the settings.
Complete the following steps to propagate settings:
a. Right-click the directory for which you have granted full access and select Permissions.
b. Add the newly created user.
c. Select the newly created user.
d. Select the Allow Full Control check box.
e. Click OK. This procedure takes a few minutes to propagate through the entire
HKEY_LOCAL_MACHINE\SOFTWARE\Candle tree.

Chapter 2. Agent installation and configuration 17

 7. Add a new Domain User to the Performance Monitor Users group.
8. Verify that Domain Users are members of the Users group.
9. Grant the following permissions to the Windows directory while running as a non-administrator
user:
v If a 32-bit agent is installed on a 32-bit operating system, grant read and write access to the
OS_installation_drive:\Windows\system32 directory
v If a 32-bit agent is installed on a 64-bit operating system, grant read and write access to the
OS_installation_drive:\Windows\SysWOW64 directory
v If a 64-bit agent is installed on a 32-bit or a 64-bit operating system, grant read and write access to
the OS_installation_drive:\Windows\system32 directory

Note: You do not need to grant the permissions to the Windows directory if you are using Windows
Server 2008, Windows Server 2008 R2, and Windows Server 2012.
10. Grant the following permissions to the SQL Server data file and log file:
v The default data file path is SQLServer_root_dir\DATA, where SQLServer_root_dir is the root
directory of the SQL Server instance. For example, if the root directory of the SQL Server instance
is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL, the data file path is C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
v The default log file path is SQLServer_root_dir\LOG, where SQLServer_root_dir is the root directory
of the SQL Server instance. For example, if the root directory of the SQL Server instance is
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL, the log file path is C:\Program
Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG.
11. Grant full permissions to the Candle_Home directory. The default path is C:\IBM\ITM.
12. Restart the SQL Server to ensure that local security permissions are applied.
13. Change the logon settings for the SQL Server agent services to the non-administrator user by
completing the following steps:
a. Click Start > Administrative Tools > Services.
b. Right-click the Monitoring Agent For SQL Server instance_name, and click Properties. The SQL
Service Properties window opens.
c. Click the Log On tab.
d. Click This account and type the user name.
e. In the Password and Confirm Password fields, enter the password, and click OK.
f. Repeat steps b - e for the Monitoring Agent For SQL Server Collector instance_name, where
instance_name is the Microsoft SQL Server instance name.

Agent-specific installation and configuration

When performing the steps to install and configure the Microsoft SQL Server agent as described in the
IBM Tivoli Monitoring Installation and Setup Guide, "Installing monitoring agents," use the agent-specific
configuration information provided in this chapter.

You can install and configure the Microsoft SQL Server agent locally or remotely by using a GUI or
command line.

Agent-specific information is provided for the following procedures:

v “Granting permissions” on page 19
v “Local configuration” on page 23
– “Using the Manage Tivoli Enterprise Monitoring Services window” on page 23
– “Silent installation” on page 32
v “Local environment variables” on page 32

18 Microsoft SQL Server agent: User’s Guide

v “Remote configuration” on page 34
v “Reconfiguration” on page 35
v “Configuration settings” on page 25
v “Starting and stopping the Microsoft SQL Server agent” on page 35
v “Setting up the Microsoft SQL Server agent in a cluster environment” on page 36

Never attempt to start the monitoring agent until you have completed the configuration steps appropriate
to the installation of the monitoring agent.

Granting permissions
If the Microsoft SQL Server agent is configured to Windows authentication, the monitoring agent will
access the Microsoft SQL Server using the run-as user ID, otherwise the monitoring agent will use the
configured Microsoft SQL Server user ID. Further reference in this section to Microsoft SQL Server user
ID or SQL Server ID refers to either the run-as user ID or the Microsoft SQL Server user ID.

The Microsoft SQL Server user ID must have access to the Microsoft SQL Server agent. The procedure
described in this section includes creating a Microsoft SQL Server user ID and granting permission to the
new user ID, which is the minimum authority required.

The SQL Server ID used to configure this monitoring agent must have the following SQL Server
authorities:
v Required authorization roles
– Database roles: Public access is required for each database that is being monitored.
– Server roles: No special Server Role is required.
v Optional authorization roles
Each Take Action command has a separate set of authorization roles that are required for the SQL
Server credentials to pass to the Take Action command. These authorities are listed for each Take
Action command in Chapter 6, “Take Action commands reference,” on page 239.

The monitored attributes in Table 4 on page 20 require additional authorization for the SQL Server ID
used to configure the Microsoft SQL Server agent. If you want to monitor any of these attributes,
configure the SQL Server ID used by the monitoring agent with the corresponding authorization.

Chapter 2. Agent installation and configuration 19

Table 4. Additional authorization
Navigation item,
Attribute group workspace, view Situation Authorization
MS SQL Job Detail Navigator item: Jobs None predefined
Server Role: Server
Workspace: Job Detail AdministratorsThis
View: Job Status, Job Detail authorization enables data
collection for all SQL Server
Navigator item: Jobs
MS SQL Job Summary jobs.
Workspace: Job Summary
—OR—
View: Running Job Current
Interval, Job Summary Database Role (msdb
database): publicAn SQL
Server Agent proxy account
must be defined. The agent
can collect job data only on
the jobs that this SQL
Server ID owns.

—OR—

Database Role (msdb

database):
SQLAgentUserRole (SQL
Server 2005 only)The agent
can collect job data only on
the jobs that this SQL
Server ID owns.

—OR—

Database Role (msdb

database):
SQLAgentReaderRole
(SQL Server 2005 only)The
agent can collect job data
on all SQL Server jobs.

—OR—

Database Role (msdb

database):
SQLAgentOperatorRole
(SQL Server 2005 and
2008)The agent can collect
job data on all SQL Server
jobs.
MS SQL Lock Detail Navigator item: Server None predefined VIEW SERVER STATE
Locking permission is required on
MS SQL Lock Summary the SQL Server
Workspace: Server Locking,
Lock Detail
View: Log Detail, Lock
Detail

20 Microsoft SQL Server agent: User’s Guide

MS SQL Server Detail Navigator item: Servers v MS_SQL_Proc_Buffs
Database Role: db_owner
Workspace: Server Detail _Active_Warn
(on default database
View: Server Detail-Status, v MS_SQL_Proc_Buffs associated with the SQL
Server Detail-Statistics _Active_Crit Server ID)
v MS_SQL_Proc_Buffs
_Used_Warn —OR—
v MS_SQL_Proc_Buffs Server Role: System
_Used_Crit Administrator
v MS_SQL_Proc_Cache
_Active_Warn
v MS_SQL_Proc_Cache
_Active_Crit
v MS_SQL_Proc_Cache
_Used_Warn
v MS_SQL_Proc_Cache
_Used_Crit
MS SQL Server Summary Navigator item: Servers None predefined VIEW SERVER STATE
permission is required on
Workspace: Server
the SQL Server
Summary
View: CPU Utilization,
Server Summary
MS SQL Statistics Summary Navigator item: Servers v MS_SQL_Client_Cnt VIEW SERVER STATE
_Pct_Used_Crit permission is required on
Workspace: Server Statistics
the SQL Server
View: Statistics Summary v MS_SQL_Client_Cnt
Chart view, IO Summary, _Pct_Used_Warn
Statistic Summary table v MS_SQL_IOERR
view _Startup_Warning
v MS_SQL_IOError
_Curintvl_Warning
v MS_SQL_LogonPct
_Crit
v MS_SQL_LogonPct
_Warning
v MS_SQL_Network
_Read_Rate_Crit
v MS_SQL_Network
_Read_Rate_Warn
v MS_SQL_Network
_Write_Rate_Crit
v MS_SQL_Network
_Write_Rate_Warn
v MS_SQL_Pct
_IO_Warning

Chapter 2. Agent installation and configuration 21

 MS SQL Table Detail Navigator item: Databases v MS_SQL_Fragmentatio Database Role: db_owner
n_Warn (for each database)
Workspace: Table Detail
View: Table Detail, v MS_SQL_Fragmentation —OR—
Fragmentation (greater than _Crit
30%) by Index Name v MS_SQL_Opt_Stats Server Role: System
_Age_Warn Administrator
v MS_SQL_Opt_Stats —OR—
_Age_Crit
VIEW DATABASE STATE
and VIEW SERVER STATE
permissions are required on
the SQL Server

Granting permissions for SQL Server 2005, 2008, and 2012

Before installing the Microsoft SQL Server agent, you must grant permissions for the Microsoft SQL
Server.

Before you begin

Ensure that you have the Database administrator authorization role to grant permissions. If you are
configuring the Microsoft SQL Server agent locally, complete this procedure between the steps for
installing and configuring the monitoring agent. If you are configuring the Microsoft SQL Server agent
remotely, complete this procedure after installing and configuring the monitoring agent.

Perform the appropriate installation procedures in the IBM Tivoli Monitoring Installation and Setup Guide

Procedure
1. Click Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.
2. In the Tree tab, select Logins in the Security folder (Console Root > WindowsName > Security >
Logins).
3. Right-click Logins and select New Login.
4. Select the General Folder option and type the SQL Server user ID if you are using SQL Server
authentication. Type the Windows user ID if you are using Windows authentication.
5. Select one of the following authentication methods:
v SQL Server
v Windows
6. Type a password in the Password field if you are using the SQL Server authentication method.
7. Select the User Mapping option.
8. In the Specify which databases can be accessed by this login area, select the check box for each
database that you currently have to give permission to each selected database.
9. Select the Server Roles option.
10. If you are running a Take Action command, you might need additional authority. See the Take
Action command descriptions in “Predefined Take Action commands” on page 239.
11. Click OK to display the Confirm Password window.
12. Retype the password that you typed for the user ID.
13. Click OK to display the new user ID in the Logins list.

22 Microsoft SQL Server agent: User’s Guide

What to do next

Configure the Microsoft SQL Server agent to start the monitoring agent and begin monitoring your
Microsoft SQL Server application.

Local configuration
If you are installing and configuring locally, use the steps in the IBM Tivoli Monitoring Installation and
Setup Guide, "Installing monitoring agents." Also, use the agent-specific configuration information in this
section and in Table 5 on page 26 for the Manage Tivoli Enterprise Monitoring Services window.

Using the Manage Tivoli Enterprise Monitoring Services window

Use the Configure Database Agents window to select the database that you want to monitor.

Figure 1. The Configure Database Agents window

In the Configure Database Agents window, select the server that you want to monitor from the Database
Servers Available list, and move the server to the Server to Monitor list. The Database Server Properties
window opens.

Chapter 2. Agent installation and configuration 23

Figure 2. The Database Server Properties window

The following fields are populated in the Database Server Properties window:
v Server Name

24 Microsoft SQL Server agent: User’s Guide

v Database Version
v Home Directory
v Error Log File

The following fields in the Database Server Properties window are optional:
v Windows Authentication
v Support Long Lived Database Connections
v Extended Parms
v Include
v Day(s) Frequency
v Weekly Frequency
v Monthly Frequency
v Collection Start Time

If you do not select the Windows Authentication field, you must enter your login and password in the
Login and Password fields by using only ASCII characters. You can use the Extended Parms field to
enable or disable the data collection for the Table Detail attribute group. To disable data collection for the
Table Detail attribute group, type koqtbld in the Extended Parms field. Click OK to see the Configure
Database Agents window. Click OK in the Configure Database Agents window to complete the
configuration process.

You can specify a daily, weekly, or monthly frequency for the collection of the MS SQL Table Detail
attribute group.

You can select the Table Detail Continuous Collection checkbox to enable continuous collection of the
MS SQL Table Detail attribute group. If you select the Table Detail Continuous Collection check box,
you must enter a value in the Interval Between Two Continuous Collection (in min.) field.

Configuration settings: Table 5 on page 26 contains a list of the configuration settings for each of the
interfaces where you can specify these settings and a description of each setting.

Chapter 2. Agent installation and configuration 25

Table 5. Names and descriptions of configuration settings for each interface
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
Server Name Database INSTANCE=InstanceName Name of the SQL If the SQL Server instance
Server Server instance that is being monitored is the default
Instance to be monitored. SQL Server instance and the
Name1 host name is popcorn, enter
Use the host name if popcorn in this field.
the SQL Server being
monitored is the If the SQL Server instance
default instance; being monitored is a named
otherwise use the instance with the instance name
instance name. of mysqlserver and the host
name is popcorn, enter
The name must be mysqlserver in this field.
short enough to fit
within the total
managed system
name, which must be
between 2 and 32
characters in length.
Login Database DBSETTINGS.db_login SQL Server user ID to
Server User =UserId be used to connect to
Id1 the SQL Server.

See “Granting
permissions” on page
19 for more
information.

Login is required only

when Windows
Authentication
parameter is set to
False.

Use only ASCII

characters.
Password Password1 DBSETTINGS.db Password for the SQL
_password=Password Server user ID

Password is required
only when Windows
Authentication
parameter is set to
False.

Use only ASCII

characters.

26 Microsoft SQL Server agent: User’s Guide

Table 5. Names and descriptions of configuration settings for each interface (continued)
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
Home Database DBSETTINGS.db Install directory Server The default home directory
Directory Server Home _home=HomeDirPath instance monitored. path for the default SQL Server
Directory 2005 instance is C:\Program
Path1 Files\Microsoft SQL
Server\MSSQL.

A named SQL Server 2005

instance has a default home
directory path in the format
C:\Program Files\Microsoft
SQL Server\
MSSQL$instance_name, where
instance_name is the SQL
Server instance name.
Error Log Database DBSETTINGS.db Fully qualified location The default error log path for
File Server Error _errorlog=ErrorlogPath and name of the SQL the default SQL Server 2005
Log File1 Server Error Log instance is C:\Program
Files\Microsoft SQL
Server\MSSQL\LOG\ERRORLOG.

A named SQL Server 2005

instance has a default error log
path in the format C:\Program
Files\Microsoft SQL
Server\MSSQL$instance_name\
LOG\ERRORLOG, where
instance_name is the SQL
Server instance name.
Right-click _WIN32_STARTUP The ID and passwords The following tacmd command
the agent Use this _.Username must have Windows property, explicitly sets the user
instance, account2 If and_WIN32_STARTUP Administrator ID for the monitoring agent to
and select selecting this _.Password—or— authority for the the LocalSystem account:_WIN32
Change option, _WIN32_STARTUP system on which the _STARTUP_.LocalSystem=1.
Startup... to complete the _.LocalSystem monitoring agent is to
set the ID following run. When setting the _WIN32
under which fields as _STARTUP_.LocalSystem
the agent described: See “Granting property, the _WIN32_STARTUP
instance is to v Account: ID permissions” on page _.InteractWithDesktop
run under 19 for information property must also be set.
which the about the required
agent user ID permissions.
instance is
The LocalSystem
to run
account is the default
v Password ID used by the
and monitoring agent.
Confirm
password:
password

Chapter 2. Agent installation and configuration 27

Table 5. Names and descriptions of configuration settings for each interface (continued)
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
Windows Windows DBSETTINGS.db Enables or disables DBSETTINGS.db_winauth=1
Authentic- Authentic- _winauth= 1/0 Windows
ation ation Authentication —OR–
DBSETTINGS.db_winauth=0
Support Support Long DBSETTINGS.db Enables or disables DBSETTINGS.db_lldbconn=1
Long Lived Lived _lldbconn= 1/0 long lived database
Database Database connections The —OR–
Connections Connections following Take Action
commands do not use DBSETTINGS.db_lldbconn=0
Long Lived Database
Connections:
v Database Check-up
and Tune-up
v Dump Database
v Dump Transaction
Log
v Rebuild Fragmented
Indexes
v Refresh Query
Optimizer Statistics
v Update Space Usage
Information
The following attribute
groups do not use
Long Lived Database
Connections:
v MS SQL Text
v MS SQL Filegroup
Detail
v MS SQL Server
Summary
Extended Extended DBSETTINGS.db Disables capture of
Parms Parms _extparms="KOQTBLD" Table Detail attributes

28 Microsoft SQL Server agent: User’s Guide

Table 5. Names and descriptions of configuration settings for each interface (continued)
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
Include Database DBSETTINGS.db_include
names to Use this feature to Examples of filters:
include filter databases that
you want to monitor. Case 1: % usage

To specify database Example:

filter, you must first @@%m%
select a separator. A
separator is a character Output: All the databases that
that distinguishes a have the character m in their
database name or names are filtered.
database expression
from the other Case 2: _ usage
database name or
database expression. Example:
@@____
While selecting a
separator, ensure that Output: All the databases that
database names and are of length four characters are
database expression do filtered.
not contain the
character that you Case 3: [] usage
choose as a separator.
You must not use the Example:
wildcard characters @@[m]___
that are typically used
in the T-SQL query Output: All the databases of
(for example, %, _, [ ], length four characters and
^, -) if they are used in whose names start with the
the database names or character m are
database filtered.(Continued on the next
expression.(Continued page.)
on the next page.)

Chapter 2. Agent installation and configuration 29

Table 5. Names and descriptions of configuration settings for each interface (continued)
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
Include Database DBSETTINGS.db_include
names to When specifying Case 4: [^] usage
(Continued) include database filter:
Example:
v Database names
must start with a @@[^m]%
separator.
v Database expression Output: All the databases (of
must start with two any length) except those whose
separators. names start with the character
m are filtered.
Note: Database
expression is a valid Case 5: Wrong input
expression that can be
used in the LIKE part Example:
of the T-SQL query. @%m%
However, you cannot
use the T-SQL ESCAPE Output: None of the databases
clause while specifying are filtered.
the database
expression.The Case 6: Default
following workspaces
are affected by Example: Field left blank (No
database filter: query is typed)
v Database Output: All the databases are
Information filtered.
v Enterprise Database
Summary Case 7: Mixed patterns
v Device Detail Example:
v Table Detail @@[m-t]_d%
v Filegroup Detail
Output: All the databases (of
any length) whose names start
with the characters m, n, o, p,
q, r, s, t, followed by any
character, with the character d
in the third place are filtered.
Day(s) Table Detail DBSETTINGS.db_tbld Use this feature to DBSETTINGS.db_tbld_daily=1
Frequency Collection _daily define the frequency of
Day(s) collecting data of Table
Frequency3 Detail attributes. The
values can be from
zero to 31.
Weekly Table Detail DBSETTINGS.db_tbld Use this feature to DBSETTINGS.db_tbld_weekly=1
Frequency Collection _weekly specify a particular
Weekly day for collecting data
Frequency3 for Table Detail
attributes. The values
can be from zero to
seven.

30 Microsoft SQL Server agent: User’s Guide

Table 5. Names and descriptions of configuration settings for each interface (continued)
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
Monthly Table Detail DBSETTINGS.db_tbld Use this feature to DBSETTINGS.db_tbld_monthly=5
Frequency Collection _monthly define the data
Monthly collection of Table
Frequency3 Detail attributes on a
particular day of the
month. The possible
values are 1, 2, 3, and
so on.
Collection Collection DBSETTINGS.db_tbld The possible values DBSETTINGS.db
Start Time Start Time _coll_stime_hour are zero to 23. The _tbld_coll_stime_hour=1
Hour default value is zero.
Collection DBSETTINGS.db_tbld The possible values DBSETTINGS.db
Start Time _coll_stime_minute are from zero to 59. _tbld_coll_stime_minute=59
Minute The default value is
zero.
Table Detail Enable/ DBSETTINGS.db_tbldconcoll Use this feature for the DBSETTINGS.db_tbldconcoll=1
Continuous Disable continuous
Collection Continuous background collection
Collection for of Table Detail data.
Table Detail
Interval Interval time DBSETTINGS.db_tbldcoll Specify the time for DBSETTINGS.db_tbldcoll
Between between two _time the interval between _time=10
Two collection in two collections in
Continuous minutes minutes. The
Collection minimum interval
(in min.) time is 3 minutes.

You can select the

Interval Between Two
Continuous Collection
(in min.) check box or
you can use
Scheduling to specify
continuous collection
of the Table Detail
attribute group. If you
use the Between Two
Continuous Collection
(in min.) check box,
you must specify the
time interval for
collection. If you use
Scheduling to specify
the collection of the
Table Detail attribute
group, the minimum
time interval is 1 day.

Chapter 2. Agent installation and configuration 31

Table 5. Names and descriptions of configuration settings for each interface (continued)
Interfaces where configuration settings are specified
Manage
Tivoli
Enterprise
Monitoring Tivoli
Services Enterprise
window Portal tacmd command line Description Examples
1
v Database Server Properties tab
2
v Agent tab Run as area
3
v The agent collects the data at the time interval for which data collection occurs frequently. For example, if you
specify all three Table Details Collection configuration settings (Day, Weekly, and Monthly), the agent starts the
data collection according to the following conditions:
– If Day(s) Frequency ≤ 7, the Day(s) Frequency settings are selected, and the Weekly and Monthly Frequency
settings are ignored.
– If Day(s) Frequency > 7, the Weekly Frequency settings are selected, and the Day(s) and Monthly Frequency
settings are ignored.

Configuring local environment variables

You can configure local environment variables to change the behavior of the Microsoft SQL Server agent.

Procedure
1. In the Manage Tivoli Enterprise Monitoring Services window, from the Actions menu, click Advanced
> Edit Variables.
2. In the Tivoli Enterprise Monitoring Server: Override Local Variable Settings window, click Add.
3. In the Add Environment Setting Override window, enter the variable and the corresponding value.

Note: See “Local environment variables” to view the list of environment variables that you can
configure.

Silent installation
If you are performing a silent installation using a response file, see the IBM Tivoli Monitoring Installation
and Setup Guide, "Performing a silent installation of IBM Tivoli Monitoring."

Local environment variables

You can change the behavior of the Microsoft SQL Server agent by configuring local environment
variables.

Variables for checking SQL Server service availability

To check the availability of the SQL Server service, add the following environment variables:
v COLL_MSSQL_RETRY_INTERVAL: This variable provides the retry interval (in minutes) to check the SQL
Server service status. If value is less than or equal to zero, then the variable takes the default value of 1
minute.
v COLL_MSSQL_RETRY_CNT: This variable provides the number of retries that the SQL Server agent makes to
check whether SQL Server service is started or not. If the SQL Server service is not started after the
number of retries then collector stops working. If value is less than or equal to zero, then the variable
takes the default value of infinity.

Variables for monitoring the SQL Server error log file

To monitor the MS SQL Error Event Details attribute group, you can add the following environment
variables:
v COLL_ERRORLOG_STARTUP_MAX_TIME: This variable provides the time interval (T) for error collection before
agent startup. The default value is 0 minutes. This variable can take the following values:

32 Microsoft SQL Server agent: User’s Guide

 T=0 The agent starts monitoring the error log file from the time the agent starts or is restarted. The
agent does not read the errors that were logged in the error log file before the agent was
started.
T=1 The agent monitors the error log file according to the following values that are set for the
COLL_ERRORLOG_STARTUP_MAX_EVENT_ROW variable, which is represented by R.
– If R < 0, the agent starts monitoring the error log file from the time the agent starts or is
restarted.
– If R = 1, the agent monitors all the errors that are logged in the error log file.
– If R > 1 and the agent is installed for the first time, the agent monitors the error log file until
R errors are monitored. If R > 1 and the agent is restarted, the agent monitors all the
previously missed R errors.
T>1 The agent monitors all previous errors that were logged up to T minutes from the time the
agent starts or is restarted. The agent monitoring also depends on the following values that
you set for the COLL_ERRORLOG_STARTUP_MAX_EVENT_ROW variable:
– If R ≤ 0, the agent starts monitoring the error log file from the time the agent starts or is
restarted.
– If R = 1, the agent monitors the error log file for all the errors that are logged up to T
minutes.
– If R > 1, the agent monitors not more than R errors that are logged in last T minutes.
v COLL_ERRORLOG_STARTUP_MAX_EVENT_ROW: This variable provides the maximum number of errors that
must be processed at agent startup. The default value is 0. This variable can take the following values:
R=0 The agent starts monitoring the error log file from the time the agent starts or restarts. The
agent does not read errors that were created in the error log file before the agent was started.
R=1 The agent monitors the errors that were logged in the last T minutes from the time the agent
starts or restarts.
R > 1 The agent monitors R errors logged in the last T minutes.
v COLL_ERRORLOG_MAX_EVENT_ROW: This variable provides the number of error rows to be displayed on the
Tivoli Enterprise Portal. The default value is 50. This variable can take the following values:
X=0 The agent does not display error logs on the Tivoli Enterprise Portal.
X>0 The agent displays X error rows on the Tivoli Enterprise Portal.

Variable for query timeout interval

To set the query timeout interval for the SQL Server agent, use the QUERY_TIMEOUT variable. This
environment variable defines the maximum amount of time (in seconds) that the SQL Server agent waits
to receive a response for a query that is sent to the SQL Server. The value for this variable must be less
than 45 seconds. However, if you set the value for this variable as 0 seconds, the SQL Server agent waits
indefinitely to receive a response from the SQL Server. If the SQL Server agent accesses a large number of
locked databases, the value for this variable must preferably be in the range of 10 - 20 seconds. If the
query is not processed within the set timeout interval, the SQL Server agent skips the timed out query
and moves to the next query in the queue. The agent does not display data on the Tivoli Enterprise
Portal for the query that has timed out.

Variable for viewing information about enabled jobs

To view information about enabled jobs, use the COLL_JOB_DISABLED environment variable. If you set the
value of this variable as 1, the Microsoft SQL Server agent does not display information about disabled
jobs. If you do not specify this variable, you can view information about enabled and disabled jobs.

Variable for limiting rows in MS SQL Filegroup Detail attribute group

To limit the number of rows the that the collector service fetches for the MS SQL Filegroup Detail
attribute group, use the COLL_KOQFGRPD_MAX_ROW environment variable. This environment variable defines
the maximum number of rows that the collector service fetches for the Filegroup Detail attribute group.

Chapter 2. Agent installation and configuration 33

You can use this environment variable to modify the default limit of maximum rows in the koqcoll.ctl
file. Complete the following steps to modify the default limit:
1. Specify the maximum number of rows for KOQFGRPD in the koqcoll.ctl file.
2. Add the COLL_KOQFGRPD_MAX_ROW environment variable, and ensure that the value of this variable is
the same as the value that you have specified in the koqcoll.ctl file.

If the value in the koqcoll.ctl file is less than the value that is specified in the COLL_KOQFGRPD_MAX_ROW
environment variable, the value in the koqcoll.ctl file is treated as the value for the maximum number
of rows.

If the value in the koqcoll.ctl file is greater than the value that is specified in the
COLL_KOQFGRPD_MAX_ROW environment variable, the value in the COLL_KOQFGRPD_MAX_ROW environment
variable is treated as the value for the maximum number of rows.

Variable for limiting rows in MS SQL Device Detail attribute group

To limit the number of rows that the collector service fetches for the MS SQL Device Detail attribute
group, use the COLL_KOQDEVD_MAX_ROW environment variable. This environment variable defines the
maximum number of rows that the collector service fetches for the Device Detail attribute group. You can
use this environment variable to modify the default limit of maximum rows in the koqcoll.ctl file.
Complete the following steps to modify the default limit:
1. Specify the maximum number of rows for KOQDEVD in the koqcoll.ctl file.
2. Add the COLL_KOQDEVD_MAX_ROW environment variable, and ensure that the value of this variable is the
same as the value that you have specified in the koqcoll.ctl file.

If the value in the koqcoll.ctl file is less than the value that is specified in the COLL_KOQDEVD_MAX_ROW
environment variable, the value in the koqcoll.ctl file is treated as the value for the maximum number
of rows.

If the value in the koqcoll.ctl file is greater than the value that is specified in the COLL_KOQDEVD_MAX_ROW
environment variable, the value in the COLL_KOQDEVD_MAX_ROW environment variable is treated as the value
for the maximum number of rows.

Variables for enhancing collection for MS SQL Database Detail attribute group
To enhance the MS SQL Database Detail attribute group collection, you can use the following
environment variables:
v COLL_KOQDBD_INTERVAL: This environment variable enables you to specify a time interval (in minutes)
between two consecutive collections of the MS SQL Database Detail attribute group.
v COLL_DBD_FRENAME_RETRY_CNT: This environment variable enables you to specify the number of attempts
that can be made to move the %COLL_HOME%_tmp_%COLL_VERSION%_%COLL_SERVERID%_%COLL_SERVERID
%__DBD_TEMP file to the %COLL_HOME%_tmp_%COLL_VERSION%_%COLL_SERVERID%_%COLL_SERVERID%__DBD_PREV
file.

Remote configuration
If you are installing and configuring remotely, use the steps in the IBM Tivoli Monitoring Installation and
Setup Guide, "Deploying non-OS agents." Also, use the agent-specific configuration information in this
section and in Table 5 on page 26 for the following interfaces:
v Tivoli Enterprise Portal
v tacmd command line

Using the Tivoli Enterprise Portal

To deploy this monitoring agent remotely using the command line, use the procedure, “Deploying
through the portal,” in the IBM Tivoli Monitoring Installation and Setup Guide.

34 Microsoft SQL Server agent: User’s Guide

In the New Managed System Configuration window, use the settings in Table 5 on page 26 for the Tivoli
Enterprise Portal Database Server Properties tab and the Agent tab Run as information.

Using the tacmd command line

To deploy this monitoring agent remotely using the command line, use the procedure, “Deploying
through the command line,” in the IBM Tivoli Monitoring Installation and Setup Guide. Also, use the
agent-specific configuration information in Table 5 on page 26 for the tacmd addSystem command. The
IBM Tivoli Monitoring Command Reference has complete information about the tacmd addSystem command.

Use the -t or --type TYPE parameter to specify the Microsoft SQL Server agent that you are configuring:
OQ.

Specify the properties with the -p or -property option.

For example:
tacmd addSystem -t OQ -n Primary:myhostname:NT -p
DBSETTINGS.db_login=sa
DBSETTINGS.db_password=sapwd
DBSETTINGS.db_home="C:\Program Files\Microsoft SQL Server\MSSQL"
DBSETTINGS.db_errorlog="C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG"
DBSETTINGS.db_winauth=1
DBSETTINGS.db_lldbconn=0
DBSETTINGS.db_include=#master##temp%
INSTANCE=MyServer
DBSETTINGS.db_winauth=1
DBSETTINGS.db_tbld_weekly=1
DBSETTINGS.db_tbld_coll_stime_hour=23
DBSETTINGS.db_tbld_coll_stime_minute=59

The parameters in the example are shown on separate lines for clarity. When typing the command, type
all of the parameters on one line.

Reconfiguration
If you need to reconfigure the Microsoft SQL Server agent, ensure that the steps for installing the
monitoring agent in the IBM Tivoli Monitoring Installation and Setup Guide are completed.

Local reconfiguration
If you are reconfiguring an instance locally, use the Manage Tivoli Enterprise Monitoring Services
window. See Table 5 on page 26 for the configuration settings.

Remote reconfiguration
If you are reconfiguring remotely, use one of the following interfaces:
v tacmd command line
Use the configureSystem command. See the IBM Tivoli Monitoring Command Reference Guide for
complete information about this command.
When reconfiguring, enter the information for the property that you are changing as well as the
INSTANCE property.
v Tivoli Enterprise Portal

See Table 5 on page 26 for the configuration settings.

Starting and stopping the Microsoft SQL Server agent

Table 6 on page 36 shows which interfaces you can use on Windows operating systems locally or
remotely to start the monitoring agent.

Chapter 2. Agent installation and configuration 35

Table 6. Interfaces for starting and stopping the Microsoft SQL Server agent locally and remotely
Local Remote

v Manage Tivoli Enterprise Monitoring Services v Tivoli Enterprise Portal

v tacmd startAgent v tacmd startAgent
v tacmd stopAgent v tacmd stopAgent
v tacmd restartAgent v tacmd restartAgent

Manage Tivoli Enterprise Monitoring Services

Enter only ASCII characters in the fields for the Manage Tivoli Enterprise Monitoring Services window.

Tivoli Enterprise Portal

See the "Working with monitoring agents," "Starting and stopping a monitoring agent" in the IBM Tivoli
Monitoring Administrator's Guide for information about using the Tivoli Enterprise Portal to start or stop
the monitoring agent.

tacmd command line

In the following examples, the tacmd command is used to start, stop, or restart the Microsoft SQL Server
agent instances that are configured for the Microsoft SQL Server on Windows operating systems, where
myhostname is the host name of the computer where the monitoring agent is running.
v Local
– tacmd startAgent -t oq
– tacmd stopAgent -t oq
– tacmd restartAgent -t oq
v Remote
– tacmd stopagent -t oq -m InstanceName:hostname:MSS
– tacmd startagent -t oq -m InstanceName:hostname:MSS
– tacmd restartagent -t oq -m InstanceName:hostname:MSS

The command for restarting the monitoring agent remotely can be tacmd restartagent -t oq -n
INST1:ESX1-PG3-2:MSS, where INST1 is the Microsoft SQL Server agent instance name, and ESX1-PG3-2 is
the host name of the computer where the monitoring agent is running.

For information about using the tacmd commands, see the IBM Tivoli Monitoring Command Reference.

Setting up the Microsoft SQL Server agent in a cluster environment

To use this monitoring agent in a Microsoft Cluster Server environment requires special configuration.

The IBM Tivoli Monitoring Installation and Setup Guide contains an overview of clustering. The information
provided here is specifically for installing and setting up the Microsoft SQL Server agent in a Microsoft
Cluster Server environment.

The SQL Server and the Microsoft SQL Server agent both support multiple instances running on the same
node. One agent does not interfere with another while running on the same node.

When the SQL Resource Group is moved from node to node, the server down situation event fires. This
event is caused by the Microsoft SQL Server agent coming online faster than the SQL Server. When the
SQL Server comes online the event clears.

Do not use the Start and Stop Take Action commands for the Microsoft SQL Server agent because they
conflict with the actions taken by the cluster server.

36 Microsoft SQL Server agent: User’s Guide

Requirements
You can set up a cluster environment for the following versions of the Microsoft SQL Server:
v Microsoft SQL Server 2005
v Microsoft SQL Server 2008
v Microsoft SQL Server 2008 R2
v Microsoft SQL Server 2012

In addition to installing and setting up the Microsoft SQL Server agent, the following additional steps are
required for the cluster environment:
v Setting CTIRA_HOSTNAME to a common value for all monitoring agents (usually the cluster name)
v Setting CTIRA_HIST_DIR to a common disk location if history is stored at the monitoring agents (if
history for the Microsoft SQL Server agent is configured to be stored at the monitoring agent)
v Creating a monitoring agent cluster resource in the Resource Group of the Virtual Server 3

On Windows systems, IBM Tivoli Monitoring requires that monitoring agents are installed in the same
directory path as the OS agent. Therefore, each node in a cluster must have installed all monitoring
agents (on the nodes system disk) that are required to support the cluster applications that can run on
that cluster node.

Installing and configuring the monitoring agent

This section contains the procedure for installing the Microsoft SQL Server agent on each node of a
cluster where it is possible the Microsoft Virtual Servers to run.

Procedure
1. Setting CTIRA_HOSTNAME
v Because there can be multiple instances of the Microsoft SQL Server agent, each instance must be
configured with a CTIRA_HOSTNAME. Set the CTIRA_HOSTNAME environment variable to the name of the
Microsoft Cluster Server cluster for all monitoring agents running in that cluster. By setting the
CTIRA_HOSTNAME for all agents in the cluster to the same name, you can navigate to all of the
monitoring agents for that cluster in the Tivoli Enterprise Portal.
v When deciding on the value for CTIRA_HOSTNAME, consider that the managed system name is
comprised of three parts: CTIRA_SUBSYSTEM_ID, CTIRA_HOSTNAME, and CTIRA_NODETYPE. Also, the name
is limited to 31 characters. By default for the Microsoft SQL Server Agent, CTIRA_NODETYPE is set to
MSS, and CTIRA_SUBSYSTEM_ID is set to the Microsoft SQL Virtual Server name. The
CTIRA_SUBSYSTEM_ID is used to distinguish the multiple instances of the Microsoft SQL Server agent.
2. Setting CTIRA_HIST_DIR
v If history for the Microsoft SQL Server agent is configured to be stored at the monitoring agent,
each instance of the monitoring agent must be configured with common CTIRA_HIST_DIR that points
to a shared disk directory.
v If history is stored at the Tivoli Enterprise Management Server, setting CTIRA_HIST_DIR is not
required. Storing history at the Tivoli Enterprise Management Server puts a higher burden on that
server.
3. Setting COLL_HOME
If you want to collect data for attribute groups that use configuration files at a shared location, and
these files are used by multiple cluster nodes, set the COLL_HOME variable to X:\shared-location,
where X is a shared drive that is accessible to the cluster nodes. For example, you can set the value
for the COLL_HOME variable when you are defining the configuration settings for the MS SQL Table
Detail attribute group or MS SQL Error Event Details attribute group.
4. Creating a monitoring agent cluster resource
v Set each Microsoft SQL Server agent startup parameter to manual so the cluster resource can
control the starting and stopping of the monitoring agent.

Chapter 2. Agent installation and configuration 37

 v After these parameters are set for each Microsoft SQL Server agent, instance cluster resources to
control the monitoring agents must be created. Each Microsoft SQL Server agent is comprised of
two Windows Services: KOQAGENTx and KOQCOLLx, where x is the agent instance number.

Example

Examples of Windows Services names:

v Monitoring Agent for Microsoft SQL Server – SQLTEST
v Monitoring Agent for Microsoft SQL Server – Collector SQLTEST
v Monitoring Agent for Microsoft SQL Server – SQLTEST2
v Monitoring Agent for Microsoft SQL Server – Collector SQLTEST2

Creating a resource
This section contains the procedure for creating a resource for the Windows Server 2003 operating system.

Procedure
1. Click Start > Administrative Tools > Cluster Administrator.
2. Select the group for the Instance that is being worked > SQLTEST.
3. Right-click the group, and then click New > Resource.
4. In the New Resource window, complete the fields as follows:
Name: KOQAGENT0
Description: resource_description
Resource type: Generic Service
Group: SQLTEST
5. In the Possible Owners window, accept the default of all Available Nodes.
6. In the Dependencies window, do not add any dependencies on history disk.
7. In the Generic Service Parameters window, complete the fields as follows:
Service name: KOQAGENT0
Start Parameters: -Hkey “KOQ\610\SQLVS1”
8. Click Finish.
9. Click Advanced.
10. Clear the Affect the group check box.
11. Right-click the group, and then click New > Resource.
12. Complete the following information:
Name: KOQCOLL_instance_name
Resource Type: Generic Service
Group: SQLTEST
13. In the Possible Owners window, accept the default of all Available Nodes.
14. In the Dependencies window, do not add any dependencies on history disk.
15. In the Generic Service Parameters window, complete the fields as follows:
Name: KOQCOLLinstance_name
Start Parameters: -Hkey “KOQ\610\SQLVS1”
16. Click Finish.
17. Click Advanced.
18. Clear the Affect the group check box.
19. Bring the two agent resources online.
20. Repeat these steps for the other instances of the monitoring agent in the cluster environment.

38 Microsoft SQL Server agent: User’s Guide

Creating a service
This section contains the procedure for creating a service for Windows 2008 systems.

Procedure
1. Click Start > Administrative Tools > Failover Cluster Management.
2. Expand Failover Cluster Management.
3. Expand Services and Applications and right-click the SQL instance that you want to configure.
4. Click Add a resource > Generic Service. The New Resource Wizard opens.
5. On the Select Service page, select Monitoring Agent for Microsoft SQL Server, and click Next.

Note: To add the Microsoft SQL Server- Collector service, select Monitoring Agent for Microsoft
SQL Server- Collector service on the Select Service page, and click Next.
6. On the Confirmation page, check the details, and click Next.
7. On the Summary page, click Finish.
8. Right-click the service that you have added, and click Properties.
9. In the Dependencies tab, select SQL Server or Monitoring Agent for Microsoft SQL Sever from the
Resources list.
10. Click Apply > OK.
11. Right-click the service that you created, and click Bring this resource online.

Making configuration changes

After control of the agent cluster resource is given to the cluster server, you must take the agent cluster
resource offline to make configuration changes or edit the agent variables on the node from which the
agent cluster resource runs. If the agent cluster resource is not offline when the agent config utility
attempts to take the agent offline, the cluster server notices that the monitoring agent went offline and
attempts to bring the monitoring agent back online. When finished with the configuration changes for the
monitoring agent, bring the agent cluster resource back online.

Chapter 2. Agent installation and configuration 39

40 Microsoft SQL Server agent: User’s Guide
Chapter 3. Workspaces reference
A workspace is the working area of the Tivoli Enterprise Portal application window. The Navigator tree
contains a list of the workspaces provided by the agent.

About workspaces

Use the Navigator tree to select the workspace you want to see. As part of the application window, the
status bar shows the Tivoli Enterprise Portal Server name and port number to which the displayed
information applies and the ID of the current user.

When you select an item in the Navigator tree, a default workspace is displayed. When you right-click a
Navigator item, a menu that includes a Workspace item is displayed. The Workspace item contains a list
of workspaces for that Navigator item. Each workspace has at least one view. Some views have links to
other workspaces. You can also use the Workspace Gallery tool as described in the Tivoli Enterprise Portal
User's Guide to open workspaces.

The workspaces in the Navigator are displayed in a Physical view that shows your enterprise as a
physical mapping or a dynamically populated logical view that is agent-specific. You can also create a
Logical view. The Physical view is the default view.

This monitoring agent provides predefined workspaces. You cannot modify or delete the predefined
workspaces, but you can create new workspaces by editing them and saving the changes with a different
name.

When multiple instances of the monitoring agent are defined on a system, the top-level node becomes
Microsoft Active Directory. The Microsoft Active Directory workspace is undefined at this node. A
subnode for each instance is created called Instance:Hostname:OQ. A workspace that is called
Instance:Hostname:OQ is associated with the instance node. This workspace is comparable to the Microsoft
Active Directory workspace.

A table view within a workspace corresponds to a group of attributes; the columns in the table view
show some or all the attributes available in the attribute group.

Additional information about workspaces

For more information about creating, customizing, and working with workspaces, see "Using workspaces"
in the Tivoli Enterprise Portal User's Guide.

For a list of the predefined workspaces for this monitoring agent and a description of each workspace,
see “Predefined workspaces” on page 42 and the information about each individual workspace.

Some attribute groups for this monitoring agent might not be represented in the predefined workspaces
or views for this agent. For a full list of the attribute groups, see “Attributes in each attribute group” on
page 59.

© Copyright IBM Corp. 2005, 2012 41

Predefined workspaces
When you install the Microsoft SQL Server agent, you receive a collection of predefined workspaces. The
predefined workspaces display data collected on an interval basis.

You can use the predefined workspaces in the Microsoft SQL Server agent for the following purposes:
v Analyze the performance of your system.
v Identify problems and bottlenecks.
v Obtain the information you need to tune your system.
v Evaluate how your tuning decisions affect the performance of your system.

In most cases, a predefined workspace has an attribute group that contains attributes similar to the
columns in the predefined workspace. You can use these values to build your own workspaces and to
create your own situations.

The Microsoft SQL Server agent provides predefined workspaces, which are organized by Navigator item.
v Microsoft SQL Server Navigator item
This Navigator item is available only when more than one Microsoft SQL Server agent instance is
configured and running on the same system.
v SQL Server instance name Navigator item
This Navigator item is available only when more than one Microsoft SQL Server agent instance is
configured and running on the same system.
– MS SQL Server Overview workspace
– Enterprise Servers Overview workspace
v Microsoft SQL Server - SQL Server instance name Navigator item
This Navigator item is available only when exactly one Microsoft SQL Server agent instance is
configured and running on the system.
– MS SQL Server Overview workspace
– Enterprise Servers Overview workspace
v AlwaysOn Navigator item
– Availability Database Information workspace
– Availability Groups Information workspace
– Availability Groups Information In Cluster workspace
– Availability Replicas and Database Information workspace
– Availability Replicas Information workspace
– Availability Replicas Status workspace
– Additional Availability Database Details workspace
v Databases Navigator item
– Additional Database Details workspace
– Databases Information workspace
- Log and Space Information workspace
– Enterprise Database Summary workspace
– FileTable Detail workspace
– Device Detail workspace
– Table Detail workspace
– Filegroup Detail workspace
– Database Mirror Detail workspace
– Enterprise Database Mirror Detail workspace

42 Microsoft SQL Server agent: User’s Guide

 – Log Shipping Error Details
– Log Shipping Job Details
– Log Shipping Database Details
– Enterprise Log Shipping Database Details
v Errorlog Alerts Navigator item
– Enterprise Errorlog Alerts workspace
– Errorlog Alerts workspace
v Jobs Navigator item
– Job Summary workspace
– Job Detail workspace
v Server Locking Navigator item
– Enterprise Server Locking workspace
– Server Locking workspace
- Process Holding Lock SQL Text workspace
- SQL Text for Process ID workspace
- Lock Resource Type Summary workspace
v Processes Navigator item
– Enterprise Processes Summary workspace
– Processes Information workspace
- SQL Text for Process ID workspace
v Servers Navigator item
– Enterprise Server Statistics workspace
– Enterprise Server Summary workspace
– Server Statistics workspace
– Server Summary workspace
- Server Configuration workspace
– Server Detail workspace
– Services Detail workspace
– Server Batch Statistics workspace
v Services Navigator item
– Services Details workspace
– SQL Server Integration Service Details workspace
– Analysis Services Data Mining Statistics workspace
– Analysis Services Memory Statistics workspace
– Analysis Services Storage Engine Query Processing workspace
– Analysis Services Rows Processing workspace

The Microsoft SQL Server agent has following composite workspaces:

v SQL Server CPU Bottleneck workspace
v SQL Server Disk Space and Logon Statistics
v SQL Server Logical Disk Bottleneck workspace
v SQL Server Memory Bottleneck workspace
v SQL Server Physical Disk Bottleneck workspace

Chapter 3. Workspaces reference 43

Additional Availability Database Details workspace
Additional Availability Database Details is a predefined workspace that contains the Additional
Availability Database Details table view. This view displays additional information about the availability
databases that are available on an SQL Server instance.

Additional Database Details workspace

Additional Database Details workspace is a predefined workspace that displays information about the
databases that are available in the SQL Server version 2012 or later. The predefined workspace contains
the Additional Database Details table view that displays information about the databases that are
available in the SQL Server version 2012 or later.

Analysis Services Data Mining Statistics workspace

Analysis Services Data Mining Statistics is a predefined workspace that displays statistical information
about the data mining feature of the SQL Server Analysis Services. The predefined workspace contains
the following views:
v Total Data Mining Processing bar chart that displays statistics about the total predictions, total queries,
and total rows.
v Data Mining Processing bar chart that displays statistics about the number of predictions per second,
number of queries per second, and number of rows per second.
v Data Mining Statistics table view that displays statistics about the data mining queries.

Analysis Services Memory Statistics workspace

Analysis Services Memory Statistics is a predefined workspace that displays statistical information about
the memory that is used by the SQL Server Analysis Services. The predefined workspace contains the
following views:
v Memory Limits Statistics bar chart that displays the memory that is currently used by the SQL Server
Analysis Services. This view also displays the upper and lower limits of the amount of memory that
can be used by the SQL Server Analysis Services.
v Background Cleaner Memory Statistics view that displays the amount of background cleaner memory
that is currently used, and the amount of shrinkable and non-shrinkable memory that is known to the
background cleaner.
v Analysis Services Memory Statistics table view that displays statistics about the memory that is used
by the SQL Server Analysis Services.

Analysis Services Storage Engine Query Processing workspace

Analysis Services Storage Engine Query Processing is a predefined workspace that displays statistical
information about the dimension queries and the storage engine queries that are processed by the SQL
Server Analysis Services. The predefined workspace contains the following views:
v Dimension Queries Statistics bar chart that displays the following information:
– The number of dimension queries that are currently processed
– The total number of dimension queries that have been processed since the server was started
v Analysis Services Storage Engine Query Processing table view that displays the statistical information
about storage engine query processing.
v Analysis Services MDX Processing table view that displays the metrics of MDX processing.

Analysis Services Rows Processing workspace

Analysis Services Rows Processing is a predefined workspace that displays the summary of the rows that
are processed by the SQL Server Analysis Services. The predefined workspace contains the following
views:
v Rows Processing Per Second bar chart that displays the following information:

44 Microsoft SQL Server agent: User’s Guide

 – The rate at which rows are converted per second
– The rate at which rows are read per second
– The rate at which rows are written per second
v Total Rows Processing bar chart that displays the following information:
– The total number of rows that are converted per second
– The total number of rows that are read per second
– The total number of rows that are written per second

Availability Database Information workspace

Availability Database Information is a predefined workspace that provides information about the
availability databases that are available on an SQL Server instance. The predefined workspace contains
the following views:
v Availability Database Summary table view that displays a summary of all the databases in the
availability groups that are available on an SQL Server instance.
v Availability Database Details table view that displays the details of all the availability databases that
are available on an SQL Server instance.
v Availability Database Statistics table view that displays the detailed information about the statistics of
all the availability databases that are available on an SQL Server instance.

This workspace provides a cross-link to the Additional Availability Database Details workspace.

Availability Groups Information workspace

Availability Groups Information is a predefined workspace that provides information about the
availability groups that are available on an SQL Server instance. This workspace is supported for SQL
Server 2012, or later. The predefined workspace contains the following views:
v Availability Groups Details table view that displays information about each availability group that is
available on an SQL Server instance.
v Availability Groups Summary table view that displays a summary of the availability groups that are
available on an SQL Server instance.
v Availability Groups Listener table view that displays information about the availability group listener
of all the availability groups that are hosted by the local SQL Server instance.

The Availability Groups Details view provides a cross-link to the Availability Replicas and Database
Information workspace.

Availability Groups Information In Cluster workspace

Availability Groups Information In Cluster is a predefined workspace that provides information about the
availability groups that are available in a Windows Service Failover Clustering (WSFC) cluster. This
workspace is supported for SQL Server 2012 Enterprise Edition, or later. The predefined workspace
contains the following views:
v Availability Groups Details In Cluster table view that displays information about all the availability
groups that are available in a WSFC cluster.
v Availability Replicas Details In Cluster table view that displays information about all the availability
replicas on all the nodes of a WSFC cluster.
v Availability Database Details In Cluster table view that displays information about all the availability
databases that are available in a WSFC cluster.

The Availability Groups Details view provides a cross-link to the Availability Replicas and Database
Information workspace.

Chapter 3. Workspaces reference 45

Availability Replicas Information workspace
Availability Replicas Information is a predefined workspace that provides information about the
availability replicas that are available on an SQL Server instance. The predefined workspace contains the
following views:
v Availability Replicas Details table view that displays the details of all the availability replicas that are
available in all the availability groups in an SQL Server instance..
v Availability Replicas Statistics table view that displays the statistics of all the availability replicas that
are available in all the availability groups in an SQL Server instance, except the local replica.

Availability Replicas and Database Information workspace

Availability Replicas and Database Information is a predefined workspace that provides information
about the availability replicas and databases that are available on an SQL Server instance. The predefined
workspace contains the following views:
v Availability Replicas Details table view that displays the details of all the availability replicas that are
available on a local server instance.
v Availability Replicas Status table view that displays the status of all the availability replicas that are
available on a local server instance.
v Availability Database Details table view that displays the details of all the availability databases that
are available on an SQL Server instance.

Availability Replicas Status workspace

Availability Replicas Status is a predefined workspace that provides a summary of the status of the
availability replicas that are available on an SQL Server instance. The predefined workspace contains the
following views:
v Availability Replicas Status Summary table view that displays a summary of the status of all the
availability replicas that are available on an SQL Server instance.
v Availability Replicas Status table view that displays the details of all the availability replicas that are
available on an SQL Server instance.

Databases Information workspace

Databases Information is a predefined workspace that displays information about the databases for the
server. The predefined workspace contains the following views:
v Databases Summary table view that displays summary information for the databases (such as the error
status and the options being used in your environment)
v Databases Summary bar chart that displays data from selected columns from the Databases Summary
table view (such as the minimum percentages of freespace in the database and the error log)
v Databases Detail table view that displays specific information for a database (such as the name of the
database and the owner)
v Database Detail bar chart that displays data from selected columns in the Database Detail table view
(such as the percentages of freespace in the database and log)

This workspace provides a cross-link to the Availability Replicas Information workspace.

Database Mirror Detail workspace

Database Mirror Detail is a predefined workspace that provides details about the database mirrors. The
predefined workspace contains the following views:
v Database Mirrors view that displays the database mirrors that are created on this instance
v Database Mirror Detail view that displays statistics related to each database mirror

46 Microsoft SQL Server agent: User’s Guide

Device Detail workspace
Device Detail is a predefined workspace that provides details about the SQL Server devices. The
predefined workspace contains the following views:
v Device Free Space Percent view that displays a bar chart of the percent free space on a device
v Device Detail view that displays statistics related to each device

Enterprise Database Mirror Detail workspace

Enterprise Database Mirror Detail is a predefined workspace that provides details about the database
mirrors for all the servers. The predefined workspace contains the following views:
v Transaction Delay view that shows a bar chart of the transaction delays of mirrors
v Enterprise Database Mirrors view that shows information about all database mirrors

Enterprise Database Summary workspace

Enterprise Database Summary is a predefined workspace that displays an overview of SQL server
database activity. The predefined workspace contains the following views:
v Databases Summary table view that displays summary information for the databases (such as the error
status and the options being used in your environment)
v Percent Data Freespace bar chart showing the percentage of freespace in the database from the column
in the Database Summary table view

Enterprise Errorlog Alerts workspace

Enterprise Errorlog Alerts is a predefined workspace that displays an overview of information about the
error log for each SQL server in your environment. The predefined workspace contains the following
views:
v Alert Summary table view with overview information (such as the size of the error log)
v Alert Summary bar chart showing the total number of errors from the column in the Alert Summary
table view

Enterprise Log Shipping Database Details workspace

Enterprise Log Shipping Database Details is a predefined workspace that provides detailed information
about Log Shipping Databases for the enterprise. The predefined workspace contains the following views:
v Enterprise Threshold Exceeded bar chart that displays information about the number of times the
threshold exceeded
v Enterprise Log Shipping Database Details table that displays the database details

Enterprise Processes Summary workspace

Enterprise Process Summary is a predefined workspace that displays overview information about the
processes for the SQL server. The predefined workspace contains the following views:
v Process Summary table view that displays information about the processes (such as the number of
processes and the statuses)
v CPU Percent that displays information from selected columns in the Server Summary table view
v Processes Blocked bar chart that displays the number of processes blocked by locks

Enterprise Server Locking workspace

Enterprise Server Locking is a predefined workspace that displays overview information about locks for
all the SQL servers in your environment. The predefined workspace contains the following views:
v Server Locking table view with overview information (such as the total number of locks)

Chapter 3. Workspaces reference 47

v Server Locking bar chart that displays information about selected columns in the Server Locking table
view (such as the total number of locks and the total number of processes being blocked by those
locks)

Enterprise Servers Overview workspace

Enterprise Servers Overview is a predefined workspace that displays an overview of the health of every
Microsoft SQL server. The predefined workspace contains the following views:
v CPU Percent bar chart view that displays the Microsoft SQL server CPU percentage usage for every
monitored Microsoft SQL server
v Lock Analysis bar chart view that displays the total number of locks and the total number of processes
blocked (waiting for a lock) for every monitored Microsoft SQL server
v Statistics Summary bar chart view that displays the number of physical reads and writes for every
monitored Microsoft SQL server

Enterprise Server Statistics workspace

Enterprise Server Statistics is a predefined workspace that displays statistical information about the SQL
servers in your environment. The predefined workspace contains the following views:
v Server Statistics table that displays the statistical information (such as the physical reads per second)
v Server Statistics bar chart that displays information from selected columns in the Server Statistics table
view (such as the physical reads and writes per second)

Enterprise Server Summary workspace

Enterprise Server Summary is a predefined workspace that displays an overview of activity for your SQL
servers. The predefined workspace contains the following views:
v Server Summary table view that displays summary information about the SQL servers (such as the
name and status)
v Remote Servers table view that displays summary information about the remote SQL servers (such as
the name and status)
v CPU Utilization bar chart that displays information from selected columns in the Server Summary table
view

Errorlog Alerts workspace

Errorlog Alerts is a predefined workspace that displays information about the error log alerts. The
predefined workspace contains the following views:
v Alerts Summary table view that displays summary information for the error logs (such as the size of
the error log and the number of errors during the interval)
v Alert Summary bar chart that displays information about selected columns in the table view that
displays summary information
v Alerts Detail table view that displays specific information for an error (such as the severity level of the
error)

Filegroup Detail workspace

Filegroup Detail is a predefined workspace that provides details about the SQL Server database file
groups. The predefined workspace contains the following views:
v Filegroup Sizes view that displays a bar chart of the sizes of the file groups
v Filegroup Detail view that displays statistics for each file group

48 Microsoft SQL Server agent: User’s Guide

FileTable Detail workspace
FileTable Detail workspace is a predefined workspace that displays information about the tables that are
configured as FileTables in the SQL Server. The predefined workspace contains the FileTable Detail table
view that displays information about each FileTable that is available in the SQL Server.

Job Detail workspace

Job Detail is a predefined workspace that provides details about the SQL Server jobs. The predefined
workspace contains the following views:
v Job Status view that displays the status of all jobs
v Job Detail view that displays statistic information about all jobs

Job Summary workspace

Job Summary is a predefined workspace that provides summary details about the SQL Server jobs. The
predefined workspace contains the following views:
v Running Jobs Current® Interval view that displays a bar chart of the number of jobs that are currently
running
v Job Summary view that displays job statistics

Lock Resource Type Summary workspace

Lock Resource Type Summary is a predefined workspace that provides details about the SQL Server lock
summary by resource type. The predefined workspace contains the following views:
v Lock Requests per Second by Resource Type view that displays a bar chart for lock requests per second
v Lock Resource Type Summary view that displays statistics of lock resource types

Log and Space Information workspace

Log and Space Information is a predefined workspace that displays information about the transaction log,
space being used, and devices for the selected database. The predefined workspace contains the following
views:
v Log and Space Information table view that displays information about the transaction log and space
usage (such as the size of the log and the number of devices)
v Data and Log Size bar chart that displays data from selected columns in the Log and Space
Information table view (such as the size a freespace for the database and log)
v Devices table view that displays information for the devices (such as the name, type, and size of the
device)
v Device Size bar chart that displays data from selected columns in the Devices table view (such as the
size and percentage of free space for the device)

Log Shipping Database Details workspace

Log Shipping Database Details is a predefined workspace that provides details about log shipping
databases. The predefined workspace contains the following views:
v Threshold Exceeded bar chart that displays information about the number of times threshold exceeded
v Log Shipping Database Details table that displays information about log shipping databases

Log Shipping Error Details workspace

Log Shipping Error Details is a predefined workspace that provides details about log shipping job errors.
The predefined workspace contains the following views:
v Job Completion Status bar chart that displays the number of error records
v Log Shipping Errors table that displays log shipping error details

Chapter 3. Workspaces reference 49

Log Shipping Job Details workspace
Log Shipping Job Details is a predefined workspace that provides details about log shipping jobs. The
predefined workspace contains the following views:
v Job Completion Status bar chart that displays information about the number of jobs that ended in the
error state
v Log Shipping Job Details table that displays log shipping job details

MS SQL Server Historical Summarized Availability workspace

The MS SQL Server Historical Summarized Availability workspace shows the availability information by
server averaged over the number of months that you specify in the Time Span dialog. This workspace
consists of the following three views:
v Availability by Server (average over months), which shows the average percentage of time that the
system has been available since startup, grouped by server instance
v Problem Summary Over Time by Server (average over months), which shows individual averages that
include the following information, high and total, per server:
– Error messages
– Error messages with a severity of 17 or higher
– Error messages with a severity level of less than 17 that have occurred
v Client Usage by Server (average over months), which shows the following information per server:
– Average percentage of maximum user connections that are in use
– Average percentage of client workstation connections in use

MS SQL Server Historical Summarized Availability Daily workspace

The MS SQL Server Historical Summarized Availability Daily workspace shows the availability
information, client usage, problem summary, database summary, and process summary information by
day for a managed server. This workspace consists of the following five views:
v Availability (daily), which shows the percentage of time that the system has been available since
startup, summarized by day
v Client Usage (daily), which shows the following information, summarized by day:
– Average percentage of maximum user connections in use
– Average percentage of client workstation connections in use
v Problem Summary (daily), which shows the following information, high and total, summarized by day:
– Error messages
– Error messages with a severity of 17 or higher
– Error messages with a severity level of less than 17 that have occurred
v Database Summary (daily), which shows information about databases on the managed server,
summarized by day. The information includes the maximum and average statistics information for the
following types of databases:
– Databases in read-only status
– Databases in DBO-only status
– Databases that can be accessed by only one user at a time
– Databases that have errors
v Process Summary (daily), which shows the following maximum and average statistics information,
summarized by day:
– Percentages of blocked processes
– Percentages of stopped processes
– Percentages of processes in lock sleep

50 Microsoft SQL Server agent: User’s Guide

MS SQL Server Historical Summarized Availability Hourly workspace
The MS SQL Server Historical Summarized Availability Hourly workspace shows the availability
information, client usage, problem summary, database summary, and process summary information by
hour for a managed server. This workspace consists of the following five views:
v Availability (hourly), which shows the percentage of time that the system has been available since
startup, summarized by hour
v Client Usage (hourly), which shows the following information, summarized by hour:
– Average percentage of maximum user connections in use
– Average percentage of client workstation connections in use
v Problem Summary (hourly), which shows the following information, high and total, summarized by
hour:
– Error messages
– Error messages with a severity of 17 or higher
– Error messages with a severity level of less than 17 that have occurred
v Database Summary (hourly), which shows information about databases on the managed server,
summarized by hour. The information includes the maximum and average statistics information for the
following types of databases:
– Databases in read-only status
– Databases in DBO-only status
– Databases that can be accessed by only one user at a time
– Databases that have errors
v Process Summary (hourly), which shows the following maximum and average statistics information,
summarized by hour:
– Percentages of blocked processes
– Percentages of stopped processes
– Percentages of processes in lock sleep

MS SQL Server Historical Summarized Availability Weekly workspace

The MS SQL Server Historical Summarized Availability Weekly workspace shows the availability
information, client usage, problem summary, database summary, and process summary information by
week for a managed server. This workspace consists of the following five views:
v Availability (weekly), which shows the percentage of time that the system has been available since
startup, summarized by week
v Client Usage (weekly), which shows the following information, summarized by week:
– Average percentage of maximum user connections in use
– Average percentage of client workstation connections
v Problem Summary (weekly), which shows the following information, high and total, summarized by
week:
– Error messages
– Error messages with a severity of 17 or higher
– Error messages with a severity level of less than 17 that have occurred
v Database Summary (weekly), which shows information about databases on the managed server,
summarized by week. The information includes the maximum and average statistics information for
the following types of databases:
– Databases in read-only status
– Databases in DBO-only status
– Databases that can be accessed by only one user at a time

Chapter 3. Workspaces reference 51

 – Databases that have errors
v Process Summary (weekly), which shows the following maximum and average statistics information,
summarized by week:
– Percentages of blocked processes
– Percentages of stopped processes
– Percentages of processes in lock sleep

MS SQL Server Historical Summarized Capacity workspace

The MS SQL Server Historical Summarized Capacity workspace shows the percentage of system
resources used for the time span that you specify in the Time Span dialog. This workspace consists of the
following three views:
v Freespace by Server (average over months), which shows the average of the lowest percentage of free
space in the database and the average of the lowest percentage of free space in the transaction log
during the time span that you specify in the Time Span dialog
v CPU Usage by Server (average over months), which shows the percentage of CPU usage for the
following during the time span that you specify in the Time Span dialog:
– SQL server
– I/O operations
– All processes on the host
v Lock Capacity by Server (average over months), which shows the total number of locks that can still be
taken out and the number of locks that are blocking other processes during the time span that you
specify in the Time Span dialog

MS SQL Server Historical Summarized Capacity Daily workspace

The MS SQL Server Historical Summarized Capacity Daily workspace shows the percentage of system
resources used, summarized by day. This workspace consists of the following four views:
v Freespace (daily), which shows the average of the lowest percentage of free space in the database and
the average of the lowest percentage of free space in the transaction log, summarized by day
v Freespace by Database (daily), which shows the minimum percentage of free space in the database and
the minimum percentage of free space in the transaction log for the database, summarized by day
v CPU Usage (daily), which shows the percentage of CPU usage for the following, summarized by day:
– SQL server
– I/O operations
– All processes on the host
v Lock Capacity (daily), which shows the total number of locks that can still be taken out and the
number of locks that are blocking other processes, summarized by day

MS SQL Server Historical Summarized Capacity Hourly workspace

The MS SQL Server Historical Summarized Capacity Hourly workspace shows the percentage of system
resources used, summarized by hour. This workspace consists of the following four views:
v Freespace (hourly), which shows the average of the lowest percentage of free space in the database and
the average of the lowest percentage of free space in the transaction log, summarized by hour
v Freespace by Database (hourly), which shows the minimum percentage of free space in the database
and the minimum percentage of free space in the transaction log for the database, summarized by hour
v CPU Usage (hourly), which shows the percentage of CPU usage for the following, summarized by
hour:
– SQL server
– I/O operations
– All processes on the host

52 Microsoft SQL Server agent: User’s Guide

v Lock Capacity (hourly), which shows the total number of locks that can still be taken out and the
number of locks that are blocking other processes, summarized by hour

MS SQL Server Historical Summarized Capacity Weekly workspace

The MS SQL Server Historical Summarized Capacity Weekly workspace shows the percentage of system
resources used, summarized by week. This workspace consists of the following four views:
v Freespace (weekly), which shows the average of the lowest percentage of free space in the database
and the average of the lowest percentage of free space in the transaction log, summarized by week
v Freespace by Database (weekly), which shows the minimum percentage of free space in the database
and the minimum percentage of free space in the transaction log for the database, summarized by
week
v CPU Usage (weekly), which shows the percentage of CPU usage for the following, summarized by
week:
– SQL server
– I/O operations
– All processes on the host
v Lock Capacity (weekly), which shows the total number of locks that can still be taken out and the
number of locks that are blocking other processes, summarized by week

MS SQL Server Historical Summarized Performance workspace

The MS SQL Server Historical Summarized Performance workspace shows the average cache information
and resources for the time span that you specify in the Time Span dialog. This workspace consists of the
following three views:
v Cache Hit Ratio by Server (average over months), which shows the ratio of data cache hits to total
requests, indicating the effectiveness of the data cache during the time span that you specify in the
Time Span dialog
v Cache Buffers by Server (average over months), which shows the number of cache buffers in the free
buffer pool and the average number of buffers that the LazyWriter scanned when searching the data
cache for an unused buffer to replenish the free buffer pool during the specified time period
v Cache Size (KB) by server (average over months), which shows the number of kilobytes (KB) allocated
for the data cache as well as the number of kilobytes (KB) allocated for the procedure cache during the
specified time period

MS SQL Server Historical Summarized Performance Daily workspace

The MS SQL Server Historical Summarized Performance Daily workspace shows the cache information
and resources, summarized by day. This workspace consists of the following three views:
v Cache Hit Ratio (daily), which shows the average, minimum, and maximum ratios of data cache hits to
total requests, indicating the effectiveness of the data cache, summarized by day
v Cache Buffers by Server (daily), which shows the average, minimum, and maximum numbers of cache
buffers in the free buffer pool and average, minimum, and maximum numbers of buffers that the
LazyWriter scanned when searching the data cache for an unused buffer to replenish the free buffer
pool, summarized by day
v Cache Size (KB) by server (daily), which shows the average, minimum, and maximum number of
kilobytes (KB) allocated for the data cache as well as the average, minimum, and maximum number of
kilobytes (KB) allocated for the procedure cache, summarized by day

MS SQL Server Historical Summarized Performance Hourly workspace

The MS SQL Server Historical Summarized Performance Hourly workspace shows the cache information
and resources, summarized by hour. This workspace consists of the following three views:

Chapter 3. Workspaces reference 53

v Cache Hit Ratio (hourly), which shows the average, minimum, and maximum ratios of data cache hits
to total requests, indicating the effectiveness of the data cache, summarized by hour
v Cache Buffers by Server (hourly), which shows the average, minimum, and maximum numbers of
cache buffers in the free buffer pool and average, minimum, and maximum numbers of buffers that the
LazyWriter scanned when searching the data cache for an unused buffer to replenish the free buffer
pool, summarized by hour
v Cache Size (KB) by server (hourly), which shows the average, minimum, and maximum number of
kilobytes (KB) allocated for the data cache as well as the average, minimum, and maximum number of
kilobytes (KB) allocated for the procedure cache, summarized by hour

MS SQL Server Historical Summarized Performance Weekly workspace

The MS SQL Server Historical Summarized Performance Weekly workspace shows the cache information
and resources, summarized weekly. This workspace consists of the following three views:
v Cache Hit Ratio (weekly), which shows the average, minimum, and maximum ratios of data cache hits
to total requests, indicating the effectiveness of the data cache, summarized by week
v Cache Buffers by Server (weekly), which shows the average, minimum, and maximum numbers of
cache buffers in the free buffer pool and average, minimum, and maximum numbers of buffers that the
LazyWriter scanned when searching the data cache for an unused buffer to replenish the free buffer
pool, summarized by week
v Cache Size (KB) by server (weekly), which shows the average, minimum, and maximum number of
kilobytes (KB) allocated for the data cache as well as the average, minimum, and maximum number of
kilobytes (KB) allocated for the procedure cache, summarized by week

MS SQL Server Overview

MS SQL Server Overview is a predefined workspace that displays an overview of the health of the
Microsoft SQL server. The predefined workspace contains the following views:
v CPU Percent bar chart view that displays the Microsoft SQL server CPU percentage usage
v Cache Utilization bar chart view that displays the data cache and procedure cache sizes
v Errorlog Alerts bar chart view that displays error message counts, including the total number of error
messages and a count of the high severity error messages
v Percent Freespace bar chart view that displays the minimum database data free space percentage and
minimum database log free space percentage for the Microsoft SQL server
v Processes Summary bar chart view that displays counts of various Microsoft SQL server processes by
type, including the total number of Microsoft SQL server processes, blocked Microsoft SQL server
processes, stopped Microsoft SQL server processes, and infected Microsoft SQL server processes

Process Holding Lock SQL Text workspace

Process Holding Lock SQL Text workspace is a predefined workspace that displays information about a
process that has a lock on the database. Part of the information displayed is the SQL command that the
process is executing. You access this workspace from the Server Locking workspace. The predefined
workspace contains the following views:
v Event Console view
v Process Holding Lock SQL Text table view that displays detailed information about the process that
has a lock on the database such as the Client Process ID, Process Status, and Total CPU Time (Sec.).

Processes workspace
Processes is a predefined workspace that displays information about the processes for SQL servers. The
predefined workspace contains the following views:
v Process Summary table view that displays information about the processes (such as the number of
processes and the statuses)

54 Microsoft SQL Server agent: User’s Guide

v CPU Percent bar chart that displays data from selected columns in the Process Summary table view
(such as the percentages of CPU being used by the system and the application)
v Process Summary bar chart that displays data from selected columns in the Process Summary table
view (such as the total processes and total processes blocked)
v Process Detail table view that displays information about specific processes (such as the usage and
time)

Server Batch Statistics workspace

Server Batch Statistics is a predefined workspace that displays information about batch requests that are
sent to the SQL Server. The predefined workspace contains the following views:
v Server Batch Statistics table view that displays information about batch requests, such as batch requests
sent to the SQL Server per second and the number of failed auto-parameterization attempts per second
v Rate of Batch Request plot chart view that displays the status of batch requests that are sent to the SQL
Server per second

Server Configuration workspace

Server Configuration is a predefined workspace that displays information about the configuration of the
SQL servers. The predefined workspace contains the following views:
v Server Summary table view that displays summary information about the SQL servers (such as the
name and status)
v Cache Utilization bar chart that displays data from selected columns in the Server Summary table view
(such as the size of the caches for data and procedures)
v Server Options table view that displays performance information about the selected server (such as the
status and the size of the data and procedure caches)
v Server Configuration table view that displays information about specific configuration values (such as
the name and value for the parameter)

Server Detail workspace

Server Detail is a predefined workspace that gives the status of the SQL Server. The predefined
workspace contains the following views:
v Server Detail – Status view that displays the status of the SQL Server
v Server Detail – Statistics view that displays statistics of the SQL Server

Services Detail workspace

Services Detail is a predefined workspace that provides details and the status of the SQL Server Windows
services. The predefined workspace contains the following views:
v Situation Event Console view that displays all events on the server
v Services Details view that displays information about each SQL service

Server Locking workspace

Server Locking is a predefined workspace that displays information about the locks for SQL servers. The
predefined workspace contains the following views:
v Lock Conflict table view that displays information about the locks conflicts (such as the type of lock
and the ID of the process holding the lock)
v Lock Detail table view that displays information about specific locks (such as the type of lock and the
cursor associated with the lock)

Chapter 3. Workspaces reference 55

Server Statistics workspace
Server Statistics is a predefined workspace that displays statistical information for SQL servers. The
predefined workspace contains the following views:
v Statistics Summary table view that displays summary statistics for the SQL servers (such as the number
of active connections)
v Statistics Summary bar chart and IO Summary bar chart that display data from selected columns in the
Statistics Summary table view
v Statistics Detail table view that displays each statistic for the selected SQL server (such as the name of
the statistic and the average, current, minimum, and maximum value for the statistic)

Server Summary workspace

Server Summary is a predefined workspace that displays an overview of the SQL server activity for your
environment. The predefined workspace contains the following views:
v Server Summary table view that displays summary information about the SQL Server (such as the
name and status)
v CPU Utilization bar chart view that displays data from selected columns in the Server Summary table
(such as the percentage of CPU being used by the server)
v Server Properties table view that displays the properties of the SQL Server

SQL Server CPU Bottleneck workspace

SQL Server CPU Bottleneck is a composite workspace that displays real-time data about the SQL Server
process CPU utilization for all the SQL Server nodes. This workspace contains the following views:
v SQL Server Process User Time Percent view that displays the user time and the privileged time (in
percentage) used by the SQL Server process.
v Total CPU Time Percent view that displays the total user time, the privileged time, and the processor
time (in percentage) of the CPU.

SQL Server Disk Space and Logon Statistics

SQL Server Disk Space and Logon Statistics is a composite workspace that displays information about the
amount of available free space and active logons for all the SQL Server instances. This workspace
contains the following views:
v Minimum Percentage Data and Log Freespace Availability view that displays the minimum percentage
of free space that is available on the disk for all the SQL Server instances.
v Server Logon Details view that displays the current active logons and average number of active logons
for all the SQL Server instances.

SQL Server Integration Service Details workspace

SQL Server Integration Service Details is a predefined workspace that displays information about the
integration service pipeline for the current instance of the SQL Server. This workspace contains the
following views:
v Integration Service Pipeline Buffer Statistics view that displays a bar chart of the flat buffer memory
and the private buffer memory statistics about the integration service pipeline.
v Integration Service Pipeline Details view that displays a table with detailed information about the
integration service pipeline.

SQL Server Logical Disk Bottleneck workspace

SQL Server Logical Disk Bottleneck workspace is a composite workspace that displays the current logical
disk activities. This workspace contains the following views:
v Logical Disk Read/Write Percent view that displays the details about the percentage of time that is
spent by the logical disk in servicing read and write requests.

56 Microsoft SQL Server agent: User’s Guide

v Disk Queue Length view that displays the details about the total number of pending requests on the
logical disk.
v Disk Space view that displays the details about the disk volume.

SQL Server Memory Bottleneck workspace

SQL Server Memory Bottleneck is a composite workspace that displays the memory and the processor
utilization of the SQL Server. This workspace contains the following views:
v SQL Server Process Memory Utilization view that displays the memory used by the SQL Server.
v SQL Server Processor Utilization Percent view that displays the percentage of CPU time that the SQL
Server process uses, and the percentage of CPU time that the other processes on the host use.
v Memory Pages to be Written per Sec view that displays the number of memory buffers that are written
by the lazy writer per second, and the number of pages that are flushed to the disk per second by the
checkpoint.
v Cache Hit Ratio view that displays the current ratio of the number of data cache hits to the number of
total requests.
v Stolen Pages view that displays the details about the number of pages that are used for miscellaneous
server purposes.

SQL Server Physical Disk Bottleneck workspace

SQL Server Physical Disk Bottleneck is a composite workspace that displays the current physical disk
activities. This workspace contains the following views:
v Physical Disk Read/Write Percent view that displays details about the percentage of time that is spent
by the physical disk in servicing read and write requests.
v Disk Queue Length view that displays the details about the number of pending requests on a physical
disk including the requests that are currently in service.
v Physical Disk Average Read/Write per Sec view that displays the average number of read and write
requests that are serviced on the physical disk per second.

SQL Server Service Broker Information workspace

SQL Server Service Broker Information is a predefined workspace that displays information about Service
Broker activation, Service Broker statistics, and Service Broker transport. This workspace contains the
following views:
v Service Broker Activation Details view that displays the details of the Service Broker activation of each
database in an SQL Server instance.
v Service Broker Statistics view that displays a summary of the Service Broker statistics.
v Service Broker Transport view that displays the summary of the activities that are related to the Server
Broker transport.

SQL Server Transactions Summary workspace

SQL Server Transactions Summary is a predefined workspace that displays the summary of all the
transactions on the SQL Server since the server was started. The predefined workspace contains the
following views:
v Total Active Transactions Statistics view that displays a bar chart of the number of the total active
transactions, total non-snapshot transactions, and total snapshot transactions in the SQL Server.
v Version Store Unit Statistics view that displays a bar chart of the details about the version store unit
count, the version store unit creation, and the version store unit truncation in the SQL Server.
v Server Transaction Summary view that displays the summary of the transaction statistics in the SQL
Server.

Chapter 3. Workspaces reference 57

SQL Text for Process ID workspace
SQL Text for Process ID is a predefined workspace that displays information about the SQL text string for
the selected process. The predefined workspace contains the following views:
v SQL text table view that displays detailed information about the SQL text strings (such as the total
CPU time)
v Event Console view

Table Detail workspace

Table Detail is a predefined workspace that provides details about the SQL Server database tables. The
predefined workspace contains the following views:
v Fragmentation (greater than 30%) by Index Name view that displays a bar chart of the fragmentation
for each index
v Table Detail view that displays statistics for each table

Table Information workspace

Table Information is a predefined workspace that provides details about the SQL Server database tables.
The predefined workspace contains the following views:
v Fragmentation (greater than 30%) by Index Name view that displays a bar chart of the fragmentation
for each index.
v Table Detail view that displays the detailed information for each table in the current instance of the
SQL Server.
v Table Summary view that displays the summarized information of all the tables in the current instance
of the SQL Server.

Cross-linked workspaces
This section contains cross-links within the SQL Server agent navigator items and workspaces. The
following table contains source, target, and filtering criteria for the cross-linked workspaces.
Table 7. Cross-linked workspaces within the SQL Server agent
Source Source
navigator workspace Source view
item name name Target navigator item Target workspace name Filter
AlwaysOn Availability Availability AlwaysOn Additional Availability N/A
Database Database Database Details
Information Details
AlwaysOn Availability Availability AlwaysOn Availability Replicas and N/A
Groups Groups Details Database Information
Information

58 Microsoft SQL Server agent: User’s Guide

Chapter 4. Attributes reference
Attributes are organized into attribute groups. Attributes in an attribute group relate to a single object
such as an application, or to a single kind of data such as status information.

Attributes in a group can be used in queries, query-based views, situations, policy workflows, take action
definitions, and launch application definitions. Chart or table views and situations are two examples of
how attributes in a group can be used:
v Chart or table views
Attributes are displayed in chart and table views. The chart and table views use queries to specify
which attribute values to request from a monitoring agent. You use the Properties editor to apply filters
and set styles to define the content and appearance of a view based on an existing query.
v Situations
You use attributes to create situations that monitor the state of your operating system, database, or
application. A situation describes a condition you want to test. When you start a situation, the values
you assign to the situation attributes are compared with the values collected by the Microsoft SQL
Server agent and registers an event if the condition is met. You are alerted to events by indicator icons
that are displayed in the Navigator.

Additional information about attributes

For more information about using attributes and attribute groups, see the Tivoli Enterprise Portal User's
Guide.

For a list of the attributes groups, a list of the attributes in each attribute group, and descriptions of the
attributes for this monitoring agent, refer to the Attributes in each attribute group section in this chapter.

Attributes in each attribute group

This monitoring agent contains the following attribute groups:
v MS SQL Batch Stats
v MS SQL Configuration
v MS SQL Database Detail
v MS SQL Database Mirroring
v MS SQL Database Summary
v MS SQL Device Detail
v MS SQL Enterprise Database Mirroring
v MS SQL Enterprise Log Shipping DB Details
v MS SQL Filegroup Detail
v MS SQL Job Detail
v MS SQL Job Summary
v MS SQL Lock Conflict Detail
v MS SQL Lock Detail
v MS SQL Lock Resource Type Summary
v MS SQL Lock Summary
v MS SQL Log Shipping DB Details
v MS SQL Log Shipping Errors

© Copyright IBM Corp. 2005, 2012 59

v MS SQL Log Shipping Jobs Detail
v MS SQL Memory Manager
v MS SQL Problem Detail
v MS SQL Problem Summary
v MS SQL Process Detail
v MS SQL Process Summary
v MS SQL Remote Servers
v MS SQL Resource Pool Stats
v MS SQL Server Detail
v MS SQL Server Summary
v MS SQL Services Detail
v MS SQL Statistics Detail
v MS SQL Statistics Summary
v MS SQL Table Detail
v MS SQL Text
v MS SQL Workload Group Stats
v VMS SQL Remote Servers
v VMS SQL Server Enterprise View

IBM Tivoli Monitoring provides other attribute groups that are available to all monitoring agents, for
example Universal Time and Local Time. The attributes in these common attribute groups are
documented in the Tivoli Enterprise Portal Help.

The following sections contain descriptions of the Microsoft SQL Server agent attribute groups, which are
listed alphabetically. Each description contains a list of attributes in the attribute group.

Note: If all attributes in an attribute group contain the values Not Collected, Not Applicable or No Data,
during the execution of the historical data collection (HDC), the .hdr file is not created for the attribute
group, and HDC data is not visible for the attribute group.

MS SQL Additional Database Details attributes

The MS SQL Additional Database Details attribute group contains attributes that provide information
about the database details for SQL Server 2012 Enterprise Edition, or later. This attribute group provides
information about database details in addition to the MS SQL Database Details attribute group.

Containment Indicates whether containment is enabled for the database. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.
No Containment 1 The database is not contained.
Partial Containment 2 The database is partially contained.
Full Containment 3 The database is fully contained.

Database ID The database ID. The following values are valid:

60 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.

Database Name The name of the database. The value format is an alphanumeric string, for example,
KOQ3. Each database name is unique. The SQL Server also assigns each database a unique identification
number. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_Applicable The value is not supported for SQL Server
2008 or earlier.

Filestream Directory Name The name of the filestream directory. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_Applicable The value is not supported for SQL Server
2008 or earlier.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Non Transactional Access Level The level of non-transactional access for the database. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.
ReadOnly 1 The level of non-transactional access for
the database is read-only access.
Full Access 2 The level of non-transactional access for
the database is full access.
In Transition to ReadOnly 3 The level of non-transactional access for
the database is in transition to read-only
access.
In Transition to Off 4 The level of non-transactional access for
the database is in transition to off.

Originnode The key for the table view in the format serverid:hostname:MSS.

Server The name of the SQL Server.

Chapter 4. Attributes reference 61

MS SQL Additional Availability Database Details attributes
MS SQL Additional Availability Database Details attribute group provides additional information about
the availability databases that are hosted by the SQL Server instance. This attribute group is supported
for SQL Server 2012 Enterprise Edition, or later.

Database Name The name of the availability database. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not applicable.

Filestream Sent Rate (KB Per Sec) The rate (in KB per second) at which filestream data is sent to the
secondary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not applicable.
No Data -3 No data is collected.

Group Database ID The ID of the availability group database. The following values are valid:

External value Internal value Description

Not Applicable Not_applicable The value is not applicable.
Not Collected Not_collected The value cannot be collected.
No Data nodata No data is collected.

Group ID The ID of the availability group to which the availability database belongs. The following
values are valid:

External value Internal value Description

Not Applicable Not_applicable The value is not applicable.
Not Collected Not_collected The value cannot be collected.
No Data nodata No data is collected.

Hub Timestamp The time when data is inserted at the hub.

Log Bytes Sent Rate (KB Per Sec) The rate (in KB per second) at which log records are currently being
sent to the secondary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not applicable.
No Data -3 No data is collected.

Log Send Queue Size (KB) The amount of log bytes (in KB) in the log files of the primary database that
has not been sent to the secondary replica. The following values are valid:

62 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not applicable.
No Data -3 No data is collected.

Originnode The key for the table view in the format serverid:hostname:MSS.

Redo Queue Size (KB) The amount of log bytes (in KB) that is not yet redone in the log files of the
secondary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not applicable.
No Data -3 No data is collected.

Redo Rate (KB Per Sec) The rate (in KB per second) at which log records are being redone. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not applicable.
No Data -3 No data is collected.

Role Indicates whether a replica is currently a primary or secondary replica. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not applicable.
No Data -3 No data is collected.
Resolving 1 The replica is recovering from a failover.
Primary 2 The replica is a primary replica.
Secondary 3 The replica is a secondary replica.
Invalid 4 The availability group that is associated
with the database is offline.

Server The name of the SQL Server.

MS SQL Analysis Services Data Mining attributes

The MS SQL Analysis Services Data Mining attribute group provides detailed information about the data
mining of the SQL Server Analysis Services.

Cases Per Sec The rate at which cases are currently processed. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 63

Concurrent Data Mining Queries The number of data mining queries that are currently being processed.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Current Models Processing The number of SQL Server Analysis Services Data Mining models that are
currently being processed. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Hub Timestamp The time when data is inserted at the hub.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Predictions Per Sec The rate at which predictions that are generated in data mining queries. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Queries Per Sec The rate at which data mining queries are generated. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Rows Per Sec The number of rows that are currently processed per second for a data mining prediction
query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Server The name of the SQL Server. The value format is an alphanumeric string with a maximum of 30
characters.

Total Predictions The number of data mining prediction queries that are currently received by the server.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Queries The number of data mining queries that are currently received by the server. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

64 Microsoft SQL Server agent: User’s Guide

Total Rows The number of rows that are currently returned by data mining queries. The following value
is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Analysis Services MDX Processing attributes

The MS SQL Analysis Services MDX Processing attribute group provides a summary of data that is
processed by Multidimensional Expressions (MDX).

Current Evaluation Nodes The approximate number of evaluation nodes that are currently built by the
MDX execution plans. This number includes active evaluation nodes and cached evaluation nodes. This
attribute is not supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Current Cached Evaluation Nodes The approximate number of cached evaluation nodes that are
currently built by the MDX execution plans. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Hub Timestamp The time when data is inserted at the hub.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Server The name of the SQL Server.

Total Autoexist The number of times that the Autoexist operation is currently performed. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Bulk Mode Evaluation Nodes The number of bulk-mode evaluation nodes that are currently built
by the MDX execution plans. This attribute is not supported on SQL Server 2005. The following values
are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Chapter 4. Attributes reference 65

Total Cached Bulk Mode Evaluation Nodes The number of cached bulk-mode evaluation nodes that are
currently built by the MDX execution plans. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Cached Other Evaluation Nodes The number of cached evaluation nodes that are currently built by
the MDX execution plans, and that are not storage engine evaluation plans or bulk-mode evaluation
plans. This attribute is not supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Cached Storage Engine Evaluation Nodes The number of cached storage engine evaluation nodes
that are currently built by the execution plans. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Calculation Cache Registered The number of calculation caches that are currently registered. This
attribute is supported only on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Calculations Covered The number of evaluation nodes that are currently built by the MDX
execution plans. This number includes active evaluation nodes and cached evaluation nodes. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Cell By Cell Evaluation Nodes The number of cell-by-cell evaluation nodes that are currently built
by the MDX execution plans. This attribute is not supported on SQL Server 2005. The following values
are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

66 Microsoft SQL Server agent: User’s Guide

Total Cell By Cell Hits In Cache of Evaluation Nodes The number of cell-by-cell hits that currently
occurred in the evaluation nodes cache. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Cell By Cell Misses In Cache of Evaluation Nodes The number of cell-by-cell misses that currently
occurred in the evaluation nodes cache. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Cells Calculated The number of cell properties that are currently calculated. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Evaluation Nodes Calculations at Same Granularity The number of evaluation nodes with
calculations that have identical granularity level as that of the evaluation nodes. This attribute is not
supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Evaluation Nodes Covered Single Cell The number of evaluation nodes that are currently built by
the MDX execution plans, and that covered only one cell. This attribute is not supported on SQL Server
2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Evictions Of Evaluation Nodes The number of evaluation nodes that are currently evicted because
of collisions. This attribute is not supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total EXISTING Operators The number of times that the EXISTING set operation is currently performed.
The following value is valid:

Chapter 4. Attributes reference 67

External value Internal value Description
Not Collected -1 The value cannot be collected.

Total Flat Cache Inserts The number of cell values that are currently inserted into the flat calculation
cache. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Hash Index Hits In Cache Of Evaluation Nodes The number of hits in the evaluation nodes cache
that are currently satisfied by the hash index. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total NonEmpty Algorithms The number of times a NonEmpty algorithm is currently used. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total NonEmpty Algorithms For Calculated Members The number of times that the NonEmpty
algorithm currently looped through the calculated members. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total NonEmpty Unoptimized Algorithms The number of times that a NonEmpty algorithm that is not
optimized is currently used. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Recomputes The number of cells that are currently computed again because of an error. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Sonar Subcubes The number of subcubes that are currently generated by the query optimizer. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

68 Microsoft SQL Server agent: User’s Guide

Total Storage Engine Evaluation Nodes The number of storage engine evaluation nodes that are
currently built by the MDX execution plans. This attribute is not supported on SQL Server 2005. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Subcube Hits In Cache Of Evaluation Nodes The number of subcube hits that are currently
present in the evaluation nodes cache. This attribute is not supported on SQL Server 2005. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Subcube Misses In Cache Of Evaluation Nodes The number of subcube misses that are currently
present in the evaluation nodes cache. This attribute is not supported on SQL Server 2005. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

MS SQL Analysis Services Memory Statistics attributes

The MS SQL Analysis Services Memory Statistics attribute group provides information about memory
that is used by the SQL Server Analysis Services.

Aggregation Map Files The current number of aggregation map files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Aggregate Cache (KB) The amount of memory that is currently allocated to the file cache. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Cleaner Balance Per Sec The rate at which balance and shrink operations are performed. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Cleaner Current Price The current price of memory in dollars per byte and per unit of time. This price is
normalized to 1000. The following value is valid:

Chapter 4. Attributes reference 69

External value Internal value Description
Not Collected -1 The value cannot be collected.

Cleaner Memory Non-Shrinkable (KB) The amount of memory that cannot be purged by the
background cleaner. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Cleaner Memory Shrinkable (KB) The amount of memory that can be purged by the background
cleaner. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Cleaner Memory (KB) The sum of shrinkable memory and the amount of non-shrinkable memory that is
currently known to the background cleaner. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Cleaner Memory Shrunk KB Sec The rate at which the cleaner memory is shrunk. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Dimension Index (Hash) Files The current number of dimension index (hash) files. The following value
is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Dimension Property Files The current number of dimension property files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Dimension String Files The current number of dimension string files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Fact Aggregation Files The current number of fact aggregation files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

70 Microsoft SQL Server agent: User’s Guide

Fact Data Files The current number of fact data files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Fact String Files The current number of fact string files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Clock Pages Examined Per Sec The rate at which the background cleaner examines the filestore
clock pages and considers the pages for eviction. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Clock Pages HaveRef Per Sec The rate at which the background cleaner examines the filestore
clock pages that have a reference number because they are currently used. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Clock Pages Valid Per Sec The rate at which the background cleaner examines the filestore
clock pages that are valid for eviction. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Page Faults Per Sec The rate at which filestore page faults are generated. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore (KB) The amount of memory that is currently allocated to the filestore. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore KB Reads Per Sec The rate at which filestore operations are read. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 71

Filestore KB Writes Per Sec The rate at which filestore operations are written. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Memory Pinned (KB) The amount of filestore memory that is currently pinned. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Reads Per Sec The rate at which filestore pages are read. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Filestore Writes Per Sec The rate at which filestore pages are written. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, it is
available for reports, queries, and workspaces.

In-Memory Map File (KB) The current size of the in-memory map file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Map File (KB) Per Sec The rate at which write operations occur in the in-memory map file.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Other File (KB) The current size of the in-memory other file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Other File (KB) Per Sec The rate at which write operations occur in the in-memory other file.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

72 Microsoft SQL Server agent: User’s Guide

In-Memory Property File (KB) The current size of the in-memory property file. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Property File KB Per Sec The rate at which write operations occur in the in-memory
property file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory String File (KB) The current size of the in-memory string file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory String File KB Per Sec The rate at which write operations occur in the in-memory string file.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Aggregation Map File (KB) The current size of the in-memory aggregation map file. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Aggregation Map File KB Per Sec The rate at which write operations occur in the
in-memory aggregation map file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Dimension Index (Hash) File (KB) The current size of the in-memory dimension index
(hash) file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Dimension Index (Hash) File KB Per Sec The rate at which write operations occur in the
in-memory dimension index (hash) file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 73

In-Memory Fact Aggregation File (KB) The current size of the in-memory fact aggregation file. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Fact Aggregation File KB Per Sec The rate at which write operations occur in the in-memory
fact aggregation file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Fact Data File (KB) The current size of the in-memory fact data file. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Fact Data File KB Per Sec The rate at which write operations occur in the in-memory fact
data file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Fact String File (KB) The current size of the in-memory fact string file. The following value
is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

In-Memory Fact String File (KB) Per Sec The rate at which write operations occur in the in-memory fact
string file. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Map Files The current number of map files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Memory Limit High (KB) The highest memory limit that is specified in the configuration file. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

74 Microsoft SQL Server agent: User’s Guide

Memory Limit Low (KB) The lowest memory limit that is specified in the configuration file. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Memory Usage (KB) The amount of memory that is used by the server to calculate the cleaner memory
price. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Other Files The current number of other files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Page Pool 1 Alloc (KB) The amount of memory that is borrowed from the 64 KB page pool. This
memory is distributed to other parts of the server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Page Pool 1 Lookaside (KB) The amount of memory that is currently available in the 1 KB lookaside list.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Page Pool 64 Alloc (KB) The amount of memory that is borrowed from the system. This memory is
distributed to other parts of the server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Page Pool 64 Lookaside (KB) The amount of memory that is currently available in the 64 KB lookaside
list. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Page Pool 8 Alloc (KB) The amount of memory that is currently borrowed from the 64 KB page pool.
The memory is distributed to other parts of the server. The following value is valid:

Chapter 4. Attributes reference 75

External value Internal value Description
Not Collected -1 The value cannot be collected.

Page Pool 8 Lookaside (KB) The amount of memory that is currently available in the 8 KB lookaside list.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Aggregation Map File (KB) The potential size of the in-memory aggregation map
files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Dimension Index (Hash) File (KB) The potential size of the in-memory dimension
index (hash) files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Dimension Property File (KB) The potential size of the in-memory dimension
property files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Dimension String File (KB) The potential size of the in-memory dimension string
files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Fact Aggregation File (KB) The potential size of the in-memory fact aggregation
files. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Fact Data File (KB) The potential size of the in-memory fact data files. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Fact String File (KB) The potential size of the in-memory fact string files. The
following value is valid:

76 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.

Potential In-Memory Map File (KB) The potential size of the in-memory map files. The following value
is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Potential In-Memory Other File (KB) The potential size of the in-memory other files. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Quota (KB) The current amount of memory quota. A memory quota is also referred to as a memory
grant or memory reservation. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Quota Blocked The number of requests for memory quota that are currently blocked until some memory
quotas are freed. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Server The name of the SQL Server.

Total Filestore I/O Errors The current number of filestore I/O errors. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Filestore I/O Errors Per Sec The rate at which filestore I/O errors occur. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Analysis Services Rows Processing attributes

The MS SQL Analysis Services Rows Processing attribute group provides a summary of the rows that are
processed by the SQL Server Analysis Services.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Chapter 4. Attributes reference 77

Hub Timestamp The time when data is inserted at the hub.

Rows Converted Per Sec The rate at which rows are converted during processing per second. The
following value is valid.

External value Internal value Description

Not Collected -1 The value cannot be collected.

Rows Read Per Sec The rate at which rows are read from all the relational databases per second. The
following value is valid.

External value Internal value Description

Not Collected -1 The value cannot be collected.

Rows Written Per Sec The rate at which rows are written to the database during processing. The
following value is valid.

External value Internal value Description

Not Collected -1 The value cannot be collected.

Server The name of the SQL Server.

Total Rows Converted The number of rows that are currently converted during processing. The
following value is valid.

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Rows Read The number of rows that are currently read from all the relational databases. The
following value is valid.

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Rows Written The number of rows that are currently written to the database during processing.
The following value is valid.

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Analysis Services Storage Engine Query attributes

The MS SQL Analysis Services Storage Engine Query attribute group provides the summary of statistics
that are related to the storage engine query processing feature of the SQL Server Analysis Services.

Aggregation Hits Per Sec The rate of aggregation hits. This attribute is not supported on SQL Server
2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

78 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Applicable -2 The attribute is not supported.

Aggregation Lookups Per Sec The rate of aggregation lookups. This attribute is not supported on SQL
Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Average Time Per Query The average time in milliseconds that is taken to respond to each query that
was answered since the last counter measurement. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Bytes Sent Per Sec The number of bytes that are currently sent by the server to the clients per second in
response to queries. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Calculation Cache Hits Per Sec The number of calculation hits per second. The calculation cache
includes global, session, and query scope calculation caches. This attribute is not supported on SQL
Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Calculation Cache Lookups Per Sec The number of calculation cache lookups per second. The calculation
cache includes global, session, and query scope calculation caches. This attribute is not supported on SQL
Server 2005. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Current Dimension Queries The number of dimension queries that are currently being processed. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Current Measure Group Queries The number of measure group queries that are currently being worked
on. The following value is valid:

Chapter 4. Attributes reference 79

External value Internal value Description
Not Collected -1 The value cannot be collected.

Current Pyramid Operations The number of pyramid operations that are currently in progress. This
attribute is supported only on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Data Bytes Per Sec The number of bytes that are currently read per second from the data file. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Data Reads Per Sec The number of logical read operations that are currently using the data file per
second. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Dimension Cache Hits Per Sec The number of dimension cache hits per second. This attribute is not
supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Dimension Cache Lookups Per Sec The rate of dimension cache lookups. This attribute is not supported
on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Dimension Queries Per Sec The rate at which dimension queries are processed. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Flat Cache Hits Per Sec The rate of flat cache hits. The flat cache includes global, session, and query
scope flat caches. This attribute is not supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

80 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Applicable -2 The attribute is not supported.

Flat Cache Lookups Per Sec The rate of flat cache lookups. The flat cache includes global, session, and
query scope flat caches. This attribute is not supported on SQL Server 2005. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Filter Rows Included Per Sec The number of rows that are included per second in the last query that
was processed. This attribute is supported only on SQL Server 2005. The following values valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Filter Rows Excluded Per Sec The number of rows that are excluded per second in the last query that
was processed. This attribute is supported only on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Filtered Rows Per Sec The rate at which rows are currently filtered. This attribute is supported only on
SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Index Bytes Per Sec The number of bytes that are currently read from the index files per second. This
attribute is supported only on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Index Reads Per Sec The number of logical read operations that are currently using the index files per
second. This attribute is supported only on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Chapter 4. Attributes reference 81

Hub Timestamp The time when data is inserted at the hub.

Map Bytes Per Sec The number of bytes that are currently read from the map file per second. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Map Reads Per Sec The number of logical read operations that are currently using the map file per
second. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Measure Group Cache Hits Per Sec The rate of group cache hits. This attribute is not supported on SQL
Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Measure Group Lookups Per Sec The rate of measure group cache lookups. This attribute is not
supported on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Measure Group Queries Per Sec The rate of measure group queries that are sent to the server. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Network Round Trips Per Sec The rate of network round trips. The network round trips include all
communication between the client and the server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Persisted Cache Hits Per Sec The rate of persisted cache hits. Persisted caches are created by the MDX
script cache statement. This attribute is not supported on SQL Server 2005. The following values are
valid:

82 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Persisted Cache Lookups Per Sec The rate of persisted cache lookups. Persisted caches are created by the
MDX script cache statement. This attribute is not supported on SQL Server 2005. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Queries Answered Per Sec The rate at which queries are currently answered. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Pyramid Operations Per Sec The rate at which pyramid operations are currently started. This attribute is
supported only on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Queries From Cache Direct Per Sec The rate at which queries are answered directly from the cache. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Queries From Cache Filtered Per Sec The rate at which queries are answered by filtering the existing
cache entry. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Queries From Files Per Sec The rate at which queries are answered from files. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Rows Read Per Sec The number of rows that are currently read by the server per second. This attribute
is supported only on SQL Server 2005. The following values are valid:

Chapter 4. Attributes reference 83

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Rows Sent Per Sec The rate at which rows are sent by the server to the clients. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Server The name of the SQL Server.

Total Dimension Queries The current number of dimension queries. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Measure Group Queries The current number of measure group queries. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Network Round Trips The current number of network round trips. The network round trips
include all communication between the client and the server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Pyramid Operations The current number of pyramid operations. This attribute is supported only
on SQL Server 2005. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The attribute is not supported.

Total Queries Answered The current number of queries that are answered. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Queries From Cache Direct The number of queries that are currently derived from the cache for
every partition. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

84 Microsoft SQL Server agent: User’s Guide

Total Queries From Cache Filtered The number of queries that are currently answered by filtering the
existing cache entries. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Queries From File The number of queries that are currently answered from files. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Rows Sent The number of rows that are currently sent by the server to the clients. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Bytes Sent The number of bytes that are currently sent by the server to the clients in response to
queries. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Availability Database Details attributes

The MS SQL Availability Database Details attribute group provides information about the availability
databases that are hosted by the SQL Server instance. This attribute group is supported for SQL Server
2012 Enterprise Edition, or later.

Database ID The ID of the availability database that is hosted by the SQL Server instance. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Database Name The name of the availability database that is hosted by the SQL Server instance. The
following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Database State Indicates the current state of the availability database. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Chapter 4. Attributes reference 85

External value Internal value Description
No Data -3 No data is collected.
Online 1 The database is available for access.
Restoring 2 The database is currently unavailable
because of one of the following reasons:
v One or more files of the primary group
are being restored.
v One or more secondary files are being
restored offline.
Recovering 3 The database is currently unavailable and
is being recovered. If the database
recovery is successful, the database state
changes to Online. If the database recovery
fails, the database state changes to Suspect.
Recovery Pending 4 The database is currently unavailable
because of one of the following reasons:
v Some files are missing.
v The database cannot start because of
system resource limitations.
Suspect 5 The database is currently unavailable
because of the following reasons:
v The primary file group is damaged.
v Database cannot be recovered during
the SQL Server startup.
Emergency 6 The database is currently in the single-user
mode, and is being repaired or restored.
The following actions are completed when
the database is in the Emergency mode:
v The database is marked read-only.
v Logging is disabled.
v Access is limited to the members of the
sysadmin fixed server role.
Offline 7 The database is not available for access.

Group Database ID The ID of the availability group database that is hosted by the SQL Server instance.
The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group ID The ID of the availability group to which the availability database belongs. The following
values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

86 Microsoft SQL Server agent: User’s Guide

Group Name The name of the availability group to which the availability database belongs. The
following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Hub Timestamp The time when data is inserted at the hub.

Local Indicates whether the availability replica is hosted by the local SQL Server instance. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
No 1 The replica is not hosted by the local
instance.
Yes 2 The replica is hosted by the local instance.

Originnode The key for the table view in the format serverid:hostname:MSS.

Replica ID The ID of the availability replica. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Role Indicates whether the availability database is a primary or a secondary database. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Resolving 1 The system is trying to gather information
about the role of the database.
Primary 2 The database is the primary database.
Secondary 3 The database is the secondary database.
Invalid 4 The availability group that is associated
with the database is offline.

Server The name of the SQL Server.

Suspend Reason The reason for a database to enter the suspended state. The following values are valid:

Chapter 4. Attributes reference 87

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected. This enum is shown
if the database is not suspended.
Suspend From User 1 The reason for the database to be
suspended is Suspend From User.
Suspend From Partner 2 The reason for the database to be
suspended is Suspend From Partner.
Suspend From Redo 3 The reason for the database to be
suspended is Suspend From Redo.
Suspend From Apply 4 The reason for the database to be
suspended is Suspend From Apply.
Suspend From Capture 5 The reason for the database to be
suspended is Suspend From Capture.
Suspend From Restart 6 The reason for the database to be
suspended is Suspend From Restart.
Suspend From Undo 7 The reason for the database to be
suspended is Suspend From Undo.
Suspend From Revalidation 8 The reason for the database to be
suspended is Suspend From Revalidation.

Synchronization Health Indicates the health of the availability database replica. The replica is healthy if
the synchronized and the asynchorinzed replicas are in the Synchronized state. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Not Healthy 1 The synchronization health of the database
replica that is hosted on the SQL Server
instance is not healthy.
Partially Healthy 2 The synchronization health of the database
replica that is hosted on the SQL Server
instance is partially healthy.
Healthy 3 The synchronization health of the database
replica that is hosted on the SQL Server
instance is healthy.

Synchronization State The current synchronization state of the availability database replica. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

88 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Synchronizing 1 On a primary database, this value
indicates that the database is not ready to
synchronize the transaction log with the
secondary database.
On a secondary database, this value
indicates that the database is not
synchronizing because of one of the
following reasons:
v The database has not started log
synchronization.
v The database is being suspended.
v The database is going through the
transition state during the startup.
v The database role is changing.
Synchronizing 2 On a primary replica, this value indicates
that the database is ready to accept a scan
request from the secondary database.
On a secondary replica, this value
indicates that an active data movement is
in progress.
Synchronized 3 On a primary replica, this value indicates
that at least one secondary database is
synchronized, and is available as a target
for a failover without data loss.
On a secondary replica, this value
indicates that all secondary databases are
synchronized with the corresponding
primary databases.
Reverting 4 Indicates that the availability database
replica is in the Reverting state.
Note: If the availability database replica is
forced to shut down when the replica is in
the Reverting state, you may not be able
to start the replica again.
Initializing 5 Indicates that the availability database
replica is in the Initializing state.
Note: If the availability database replica is
forced to shut down when the replica is in
the Initializing state, you may not be able
to start the replica again.

Synchronized Commit Indicates whether the transaction commit is synchronized with the database
replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Not Synchronized 1 The transaction commit is not
synchronized with the database replica.
Synchronized 2 The transaction commit is synchronized
with the database replica.

Chapter 4. Attributes reference 89

MS SQL Availability Database Details In Cluster attributes
The MS SQL Availability Database Details In Cluster attribute group provides detailed information about
the health of the availability databases in each availability group on the Windows Server Failover
Clustering (WFSC) cluster even if the availability database is not hosted by the local SQL Server instance.
This attribute group is supported for SQL Server 2012 Enterprise Edition, or later.

Database Name The name of the availability database. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

Failover Ready Indicates whether the secondary database is synchronized with the primary database. The
following values are valid:

Not Collected -1 The value cannot be collected.

Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Not Ready 1 The secondary database is not
synchronized with the primary database.
Ready 2 The secondary database is synchronized
with the primary database.

Group Database ID The availability group database ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group ID The availability group ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The availability group name. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

90 Microsoft SQL Server agent: User’s Guide

Hub Timestamp The time when data is inserted at the hub.

Join State Indicates whether the availability database on the availability replica is joined to the
availability group. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.
No Data -3 No data is collected.
Not Joined 1 The availability database is not joined to
the availability group.
Joined 2 The availability database is joined to the
availability group.

Originnode The key for the table view in the format serverid:hostname:MSS.

Replica ID The replica ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Secondary Suspension Pending Indicates whether the database is pending suspension after a forced
failover. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
No 1 The secondary database is not pending
suspension.
Yes 2 The secondary database is pending
suspension.

Server The name of the SQL Server.

MS SQL Availability Database Statistics attributes

MS SQL Availability Database Statistics attribute group provides information about the availability
database statistics. This attribute group is supported for SQL Server 2012 Enterprise Edition, or later.

Database Name The name of the availability database. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Chapter 4. Attributes reference 91

File Bytes Received Per Sec The amount of filestream data that is currently being received per second.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Hub Timestamp The time when data is inserted at the hub.

Log Bytes Received Per Sec The amount of log bytes that is currently being received per second. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Log Send Queue (KB) The amount of log bytes (in KB) that has been sent by the primary replica, but has
not been received by the secondary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Mirrored Write Transaction Per Sec The number of transactions that have been written to the mirrored
database in the last second, and are waiting for the logs to be sent to the mirrored database to complete
the commit operation. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Originnode The key for the table view in the format serverid:hostname:MSS.

Recovery Queue The number of log records that are in the recovery queue because they are not redone.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Redo Blocked Per Sec The number of times that the redo operation is currently being blocked per
second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

92 Microsoft SQL Server agent: User’s Guide

Redo Bytes Remaining (KB) The amount of log bytes (in KB) that has not completed the redo phase. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Redone Bytes Per Sec The amount of log bytes that was redone on the secondary database in the last
second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Server The name of the SQL Server.

Total Log Requiring Undo (KB) The amount of log data (in KB) that must be undone. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Undo Log Remaining (KB) The amount of log data (in KB) that remains to be undone. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

MS SQL Availability Database Summary attributes

The MS SQL Availability Database Summary attribute group provides a summary of the information
about availability databases that are hosted by the SQL Server instance. This attribute group is supported
for SQL Server 2012 Enterprise Edition, or later.

Originnode The key for the table view in the format serverid:hostname:MSS.

Max Unsynchronized Databases The maximum number of the availability databases that have been
unsynchronized since the agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Hub Timestamp The time when data is inserted at the hub.

Max Non Healthy Databases The maximum number of the availability databases that have been
non-healthy since the agent startup. The following values are valid:

Chapter 4. Attributes reference 93

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Max Non Synchronized Commit Database Replicas The maximum number of availability database
replicas on which the transaction commit operation has not been synchronized since the agent startup.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Max Non-Online Databases The maximum number of databases that have not been online since the
agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Non Healthy Databases The minimum number of the availability databases that have been
non-healthy since the agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Non Synchronized Commit Database Replicas The minimum number of availability database
replicas on which the transaction commit operation has not been synchronized since the agent startup.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Non-Online Databases The minimum number of databases that have not been online since the
agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Unsynchronized Databases The minimum number of the availability databases that have been
unsynchronized since the agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

94 Microsoft SQL Server agent: User’s Guide

Server The name of the SQL Server.

Total Non Healthy Databases The total number of the availability databases that have been non-healthy
since the agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Non Synchronized Commit Database Replicas The total number of availability database replicas
on which the transaction commit operation has not been synchronized since the agent startup. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Non-Online Databases The total number of databases that have not been online since the agent
startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Databases The total number of availability databases that are hosted by the SQL Server instance.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Primary Databases The total number of primary availability databases that are hosted by the SQL
Server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Secondary Databases The total number of secondary availability databases that are hosted by the
SQL Server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Chapter 4. Attributes reference 95

Total Unsynchronized Databases The total number of availability databases that have been
unsynchronized since the agent startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

MS SQL Availability Groups Details attributes

The MS SQL Availability Groups attribute group provides details about the availability groups that are
hosted by the local SQL Server instance. This attribute group is supported for SQL Server 2012 Enterprise
Edition, or later.

Note: In this attribute group, the Primary Replica ID is blank if the SQL query returns the NULL value.

Backup Preference The preferred location to perform backup operations on the availability databases that
are available in the availability group. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Primary Replica 1 The backup operation is performed on the
primary replica.
Secondary Replica 2 The backup operation is performed on the
secondary replica.
Primary Replica acceptable if no 3 The backup operation is performed on the
Secondary Replica Available primary replica if a secondary replica is
not available.
No Preference 4 No preference is specified for performing
backup operations.

Database Count The total number of databases that are connected to the availability group. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

Failure Condition The condition level that is specified for triggering an automatic failure of the
availability group. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
SQL Service Down or Group Lease 1 An automatic failure is triggered if the
Expired SQL service is down, or the group lease
has expired.

96 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Health check timeout Threshold 2 An automatic failure is triggered when the
Group Exceeded availability group exceeds the health check
timeout threshold.
Critical SQL Server Internal Errors 3 An automatic failure is triggered when the
system encounters critical SQL Server
internal errors.
SQL Server Internal Errors 4 An automatic failure is triggered when the
system encounters SQL Server internal
errors.
Unsolvable Deadlock or 5 An automatic failure is triggered when the
Exhaustion of SQL Engine system encounters an unsolvable deadlock
or the exhaustion of the SQL engine.

Group ID The ID of the availability group to which the replica belongs. The value format is an
alphanumeric string with a maximum of 128 characters. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The name of the availability group to which the replica belongs. The value format is an
alphanumeric string with a maximum of 384 characters. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Group Role Indicates whether the local server instance is a primary or a secondary replica. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Resolving 1 The system is trying to gather information
about the role of the replica.
Primary 2 The replica is a primary replica.
Secondary 3 The replica is a secondary replica.
Invalid 4 The availability group that is associated
with the replica is offline.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Chapter 4. Attributes reference 97

Last Group Role Indicates whether the local server instance is a primary or a secondary replica for the
availability group in the last sample. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Resolving 1 The replica is recovering from a failover.
Primary 2 The replica is a primary replica.
Secondary 3 The replica is a secondary replica.
Invalid 4 The availability group that is associated
with the replica is offline.

Local Replica Recovery Health The recovery health status of the replica that is hosted by the local SQL
Server instance in the availability group. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
In Progress 1 The replica is recovering from a failover.
Online 2 The replica is online.

Originnode The key for the table view in the format serverid:hostname:MSS.

Primary Replica The name of the primary replica. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Primary Replica ID The ID of the primary replica. The format is an alphanumeric string with a
maximum of 128 characters. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Secondary Replicas Count The number of secondary replicas in the availability group. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

98 Microsoft SQL Server agent: User’s Guide

Server The name of the SQL Server.

Synchronization Health A summary of the synchronization health of all the replicas in the availability
group. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Not Healthy 1 All the replicas in the availability group
are not healthy.
Partially Healthy 2 At least one replica in the availability
group is not healthy.
Healthy 3 All the replicas in the availability group
are healthy.

Wait Timeout (ms) The duration (in milliseconds) that the system waits for a response from the SQL
Server instance before the nstance is assumed to be slow or not responding. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

MS SQL Availability Groups Details In Cluster attributes

The MS SQL Availability Groups Details In Cluster attribute group provides information about each
availability group in the Windows Server Failover Clustering (WFSC) cluster even if the local SQL Server
instance is not a part of any availability group in the WFSC cluster. This attribute group is supported for
SQL Server 2012 Enterprise Edition, or later.

Backup Preference The preferred location that is specified for performing backup operations on the
availability database. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Primary Replica 1 The primary replica is specified as the
preferred location for performing backup
operations on the availability database.
Secondary Replica 2 The secondary replica is specified as the
preferred location for performing backup
operations on the availability database.
Primary Replica acceptable if no 3 The primary replica is specified as the
Secondary Replica Available location for performing backup operations
on the availability database if no
secondary replica is available.

Chapter 4. Attributes reference 99

External value Internal value Description
No Preference 4 No preferred location is specified for
performing backup operations on the
availability database.

Cluster Resource ID The WSFC cluster resource ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Failure Condition The value that indicates when an automatic failover occurs. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
SQL Service Down or Group Lease 1 An automatic failover occurs when the
Expired SQL service is down, or the group lease
has expired.
Health Check Timeout Threshold 2 An automatic failover occurs when the
Group Exceeded health check timeout threshold of the
availability group has been exceeded.
Critical SQL Server Internal Errors 3 An automatic failover occurs because
critical SQL Server internal errors are
detected.
SQL Server Internal Errors 4 An automatic failover occurs because SQL
Server internal errors are detected.
Unsolvable Deadlock or 5 An automatic failover occurs because one
Exhaustion of SQL Engine of the following conditions exists:
v The worker threads of the SQL engine
are exhausted
v An unsolvable deadlock exists

Group ID The availability group ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The availability group name. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

100 Microsoft SQL Server agent: User’s Guide

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

Hub Timestamp The time when data is inserted at the hub.

Originnode The key for the table view in the format serverid:hostname:MSS.

Resource Group ID The WSFC cluster resource group ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_Applicable The value is not supported.
No Data nodata No data is collected.

Server The name of the SQL Server.

Wait Timeout (ms) The duration (in milliseconds) that the system waits for the sp_server_diagnostics
stored procedure to return the health information of the SQL Server instance before the server instance is
assumed to be slow or not responding. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

MS SQL Availability Group Listener Details attributes

The MS SQL Availability Group Listener Details attribute group provides information about the
availability group listeners of all the availability groups that are hosted by the local SQL Server instance.
This attribute group is supported for SQL Server 2012 Enterprise Edition, or later.

Originnode The key for the table view in the format serverid:hostname:MSS.

Group ID The availability group ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The availability group name. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

Chapter 4. Attributes reference 101

Hub Timestamp The time when data is inserted at the hub.

Is Conformant Indicates whether the IP address of the availability groups listener is conformant. An IP
address is conformant if one of the following conditions exists:
v The IP configuration is created by the T-SQL statement.
v The IP configuration is created outside of the SQL Server, but the IP configuration can be modified by
the T-SQL statement.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.
No Data -3 No data is collected.
No 1 The IP address of the availability groups
listener is not conformant.
Yes 2 The IP address of the availability groups
listener is conformant.

Is DHCP Indicates whether the IP address of the availability groups listener is configured by the
Dynamic Host Configuration Protocol (DHCP). The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.
No Data -3 No data is collected.
No 1 The IP address of the availability groups
listener is not configured by the DHCP.
Yes 2 The IP address of the availability groups
listener is configured by the DHCP.

Listener IP Address The IP address of the availability group listener. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Listener Name The name of the availability group listener. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

102 Microsoft SQL Server agent: User’s Guide

Listener Subnet IP The IP address of the subnet to which the availability group listener belongs. The
following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Listener ID The resource ID of the availability group listener in the WSFC cluster. The following values
are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Port The TCP port number of the availability group listener. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected. This value indicates
that the listener is configured outside the
SQL Server and the port number of the
listener is not added to the availability
group

Server The name of the SQL Server.

State The state of the availability group listener in the WSFC cluster. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported for SQL Server
2008 or earlier.
No Data -3 No data is collected.
Offline 1 The availability group listener is offline.
Online 2 The availability group listener is online.
Online Pending 3 The availability group listener is being
brought online.
Failed 4 The availability group listener could not
be brought online and has failed.

MS SQL Availability Groups Summary attributes

The MS SQL Availability Groups Summary attribute group provides a summary of the availability groups
that are hosted by the local SQL Server instance. This attribute group is supported for SQL Server 2012
Enterprise Edition, or later.

Chapter 4. Attributes reference 103

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Max Non Healthy Groups The maximum number of availability groups in which at least one availability
replica that is hosted by the SQL Server instance has not been healthy since the agent startup. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Max Non Online Local Replica Groups The maximum number of availability groups in which at least
one availability replica that is hosted by the SQL Server instance has not been online since the agent
startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Non Healthy Groups The minimum number of availability groups in which at least one availability
replica that is hosted by the SQL Server instance has not been healthy since the agent startup. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Non Online Local Replica Groups The minimum number of availability groups in which at least
one availability replica that is hosted by the SQL Server instance has not been online since the agent
startup. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Originnode The key for the table view in the format serverid:hostname:MSS.

Server The name of the SQL Server.

Total Groups The total number of availability groups that are available on the SQL Server instance in the
current interval. The following values are valid:

External value Internal value Description

Not Applicable Not_applicable The value is not applicable.
Not Collected Not_collected The value is not supported.

104 Microsoft SQL Server agent: User’s Guide

Total Non Healthy Groups The total number of availability groups that are currently not healthy in the
current interval. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Non Online Local Replica Groups The total number of availability groups in which at least one
availability replica that is hosted by the SQL Server instance is not online in the current interval. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Primary Role Group The total number of availability groups in which the SQL Server instance is
the primary replica in the current interval. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Secondary Role Group The total number of availability groups in which the SQL Server instance is
the secondary replica in the current interval. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

MS SQL Availability Replicas Details attributes

The MS SQL Availability Replicas Details attribute group provides details about the availability replicas
in each availability group. This attribute group is supported for SQL Server 2012 Enterprise Edition, or
later.

Availability Mode Indicates whether the availability replica is running in the synchronous-commit mode
or the asynchronous-commit mode. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Asynchronous Commit 1 The availability replica is running in the
asynchronous-commit mode.
Synchronous Commit 2 The availability replica is running in the
synchronous-commit mode.

Backup Priority The priority that is specified to perform backup operations on the replica. The following
values are valid:

Chapter 4. Attributes reference 105

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

Note: The value of this attribute is displayed as 0 if you select the Exclude Replica check box while
configuring an availability replica.

Create Date The date when the replica was created. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Note: This attribute shows No Data if the SQL Server query returns the NULL value.
The format is MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL Server on
Friday, January 25, 2002 at 8:00 a.m.

Endpoint URL The database mirroring endpoint that is specified by the user. The value format is an
alphanumeric string. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Failover Mode Indicates whether the failover mode of the availability replica is manual or automatic. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Manual 2 The failover mode of the replica is manual.
Automatic 1 The failover mode of the replica is
automatic.

106 Microsoft SQL Server agent: User’s Guide

Group ID The ID of the availability group to which the replica belongs. The value format is an
alphanumeric string. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The name of the availability group to which the replica belongs. The value format is an
alphanumeric string. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Hub Timestamp The time when data is inserted at the hub.

Modify Date The date when the replica was last modified. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Note: This attribute shows No Data if the SQL Server query returns the NULL value.

Originnode The key for the table view in the format serverid:hostname:MSS.

Owner SID The security identifier (SID) of the external owner of the replica. The following values are
valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Primary Connection Type Indicates the type of connection that is allowed for a primary replica. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
All 3 All types of connections are allowed.
Read Write 4 Connections with read/write access are
allowed.

Chapter 4. Attributes reference 107

Replica ID The ID of the replica. The value format is an alphanumeric string. The following values are
valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Replica Server Name The server and instance name of the location that hosts the replica. The following
values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Role Indicates whether a replica is currently a primary or secondary replica. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Resolving 1 The replica is recovering from a failover.
Primary 2 The replica is a primary replica.
Secondary 3 The replica is a secondary replica.
Invalid 4 The availability group that is associated
with the replica is offline.

Secondary Connection Type Indicates the type of connection that is allowed for a secondary replica. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
No 1 No connections are allowed.
Read Only 2 Connections with read-only access are
allowed.
All 3 All types of connections are allowed.

Server The name of the SQL Server.

Session Timeout The duration (in seconds) that the replica waits to receive a message from another
replica before assuming that the connection between the primary and the secondary replica has failed.
The following values are valid:

108 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

MS SQL Availability Replicas Details In Cluster attributes

The MS SQL Availability Replicas Details In Cluster attribute group provides detailed information about
each availability replica in the Windows Server Failover Clustering (WFSC) cluster. This attribute group is
supported for SQL Server 2012 Enterprise Edition, or later.

Cluster Node The name of the cluster node where the availability replica is located. The following values
are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

Group ID The availability group ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The availability group name. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

Hub Timestamp The time when data is inserted at the hub.

Join State Indicates whether the availability replica is joined to the availability group in the WSFC
cluster. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Not Joined 1 The availability replica is not joined to the
availability group.

Chapter 4. Attributes reference 109

External value Internal value Description
Joined As Stand Alone Instance 2 The availability replica is joined to the
availability group as a stand-alone failover
cluster instance.
Joined As Failover Cluster Instance 3 The availability replica is joined to the
availability group as a cluster instance.

Originnode The key for the table view in the format serverid:hostname:MSS.

Replica Server Name The server and instance name of the location where the availability replica is
hosted. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Note: If no data has been collected from the query for this attribute, the value of this attribute is
displayed as blank on the Tivoli Enterprise Portal.

Replica ID The availability replica ID. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Server The name of the SQL Server.

MS SQL Availability Replicas Statistics attributes

The MS SQL Availability Replicas Statistics attribute group provides information about the statistics of the
availability replicas that are available in the AlwaysOn availability group, which is currently hosted on
the SQL Server instance. This attribute group is supported for SQL Server 2012 Enterprise Edition, or
later.

Bytes Received Per Sec The number of bytes that are currently being received from the availability
replica per second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Bytes Sent Per Sec The number of bytes that are currently being sent per second from the primary
replica to the secondary replica, or from the secondary replica to the primary replica. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

110 Microsoft SQL Server agent: User’s Guide

Bytes Sent To Transport Per Sec The number of bytes that are currently being sent per second through
the network from the primary replica to the secondary replica, or from the secondary replica to the
primary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Flow Control Per Sec The number of flow control operations that have been currently initiated per
second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Flow Control Time (ms) The time (in milliseconds) that the log stream messages waited to send the flow
control information to the availability database. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Hub Timestamp The time when data is inserted at the hub.

Instance Name The name of the local SQL Server instance. The following value is valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Messages Sent To Transport Per Sec The number of AlwaysOn messages that are currently being sent
per second through the network from the primary replica to the secondary replica, or from the secondary
replica to the primary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Originnode The key for the table view in the format serverid:hostname:MSS.

Received Messages Per Sec The number of AlwaysOn messages that are currently being received from
the primary replica per second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Chapter 4. Attributes reference 111

Resent Messages Per Sec The number of AlwaysOn messages that are currently being resent to the
availability replica per second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Sent Messages Per Sec The number of AlwaysOn messages that are currently being sent to the
availability replica per second. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Server The name of the SQL Server.

MS SQL Availability Replicas Status attributes

The MS SQL Availability Replicas Status attribute group provides details about the status of the replicas
in each availability group. This attribute group is supported for SQL Server 2012 Enterprise Edition, or
later.

If the SQL Server instance is a primary replica in an availability group, the MS SQL Availability Replicas
Status Summary attribute group displays the details of all the replicas that are present in all the
availability groups. However, if the SQL Server instance is a secondary replica in an availability group,
the MS SQL Availability Replicas Status Summary attribute group displays the details of only those
replicas that are hosted by the local instance.

Connection State The current connection state of the availability replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Disconnected 1 The availability replica is not connected.
Connected 2 The availability replica is connected.

Group ID The ID of the availability group to which the replica belongs. The value format is an
alphanumeric string with a maximum of 64 characters. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Group Name The name of the availability group to which the replica belongs. The following values are
valid:

112 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Hub Timestamp The time when data is inserted at the hub.

Last Connect Error Number The last connection error number. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

Local Indicates whether the replica is hosted by the local instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
No 1 The replica is not hosted by the local
instance.
Yes 2 The replica is hosted by the local instance.

Operational State The current operational state of the availability replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Pending Failover 1 A failover is being processed for this
availability group.
Pending 2 The primary replica currently cannot
process any requests because no database
worker threads are available to process the
requests.
Online 3 The availability replica is currently online.
Offline 4 The availability replica is currently offline.
Failed 5 The availability replica cannot process any
requests.
Failed No Quorum 6 The local server instance node does not
have quorum.
Invalid 7 The availability group that is associated
with the replica is offline.

Note: This attribute shows the value No Data on the replica that is not local.

Originnode The key for the table view in the format serverid:hostname:MSS.

Chapter 4. Attributes reference 113

Recovery Health Indicates whether the databases that are connected to the availability group are online
or are being recovered after a failover. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
In Progress 1 At least one database that is connected to
the availability group is not online.
Online 2 All databases that are connected to the
availability group are online.

Note: This attribute shows the value No Data on the replica that is not local.

Replica ID The ID of the replica. The value format is an alphanumeric string with a maximum of 64
characters. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.
No Data nodata No data is collected.

Role Indicates whether the replica is a primary or a secondary replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Resolving 1 The system is gathering information about
the role of the availability replica.
Primary 2 The replica is a primary replica.
Secondary 3 The replica is a secondary replica.
Invalid 4 The availability group that is associated
with the replica is offline.

Server The name of the SQL Server.

Synchronization Health The synchronization state of all the databases that are connected to the
availability group on the availability replica. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Not Healthy 1 The synchronization health of all the
replicas that are connected to the
availability group is not healthy.

114 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Partially Healthy 2 The synchronization health of at least one
replica that is connected to the availability
group is not healthy.
Healthy 3 The synchronization health of all the
replicas that are connected to the
availability group is healthy.

Total Databases The total number of databases that are hosted by the availability replica. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.

MS SQL Availability Replicas Status Summary attributes

The MS SQL Availability Replicas Status Summary attribute group provides a summary of the status of
availability replicas in all the availability groups that are hosted on the local server instance. This
attribute group is supported for SQL Server 2012 Enterprise Edition, or later.

If the SQL Server instance is a primary replica in an availability group, the MS SQL Availability Replicas
Status Summary attribute group displays the details of all the replicas that are present in all the
availability groups. However, if the SQL Server instance is a secondary replica in an availability group,
the MS SQL Availability Replicas Status Summary attribute group displays the details of only those
replicas that are hosted by the local instance.

Hub Timestamp The time when data is inserted at the hub.

Max Non Healthy Replicas The maximum number of replicas that have not been healthy since the agent
startup in all the availability groups that are hosted on the local server instance. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Max Disconnected Replicas The maximum number of replicas that have been disconnected since the
agent startup in all the availability groups that are hosted on the local server instance. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Max Local Failed Replicas The maximum number of local replicas that have failed since the agent
startup in all the availability groups that are hosted on the local server instance. The following values are
valid:

Chapter 4. Attributes reference 115

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Max Secondary Replicas The maximum number of secondary replicas that have been connected since the
agent startup in all the availability groups that are hosted on the local server instance. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Non Healthy Replicas The minimum number of replicas that have not been healthy since the agent
startup in all the availability groups that are hosted on the local server instance. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Disconnected Replicas The minimum number of replicas that have been disconnected since the
agent startup in all the availability groups that are hosted on the local server instance. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Local Failed Replicas The minimum number of local replicas that have failed since the agent startup
in all the availability groups that are hosted on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Min Secondary Replicas The minimum number of secondary replicas that have been connected since the
agent startup in all the availability groups that are hosted on the local server instance. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Originnode The key for the table view in the format serverid:hostname:MSS.

Server The name of the SQL Server.

116 Microsoft SQL Server agent: User’s Guide

Total Non Healthy Replicas The total number of non-healthy replicas in all the availability groups that
are hosted on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Connected Replicas The total number of connected replicas in all the availability groups that are
hosted on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Disconnected Replicas The total number of disconnected replicas in all the availability groups that
are hosted on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Local Failed Replicas The total number of local replicas that failed in all the availability groups that
are hosted on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Local Replicas The total number of local replicas in all the availability groups that are hosted on
the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Primary Replicas The total number of primary replicas in all the availability groups that are hosted
on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Secondary Replicas The total number of secondary replicas in all the availability groups that are
hosted on the local server instance. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 117

External value Internal value Description
Not Applicable -2 The value is not supported.

MS SQL Batch Stats attributes

The MS SQL Batch Stats attribute group contains attributes that you can use to monitor detailed
information about batch requests.

Auto-Param Attempts Per Sec The number of auto-parameterization attempts per second. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Batch Requests Per Sec The number of Transact-SQL command batch requests received per second. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Failed Auto-Params Per Sec The number of failed auto-parameterization attempts per second. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Forced Parameterization Per Sec The number of successful forced parameterization attempts per second.
The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Originnode The key for the table view of the format serverid:hostname:MSS.

Safe Auto-Params Per Sec The number of safe auto-parameterization attempts per second. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Server The name of the SQL Server.

Server Attention Rate The number of attentions per second. An attention is a request by the client to end
the currently running request. The following values are valid:

118 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.

Server Compilations Per Sec The number of server compilations per second. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Server Re-Compilations Per Sec The number of times the server recompiles per second. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Unsafe Auto-Params Per Sec The number of unsafe auto-parameterization attempts per second. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Blocked Queries Details attributes

The MS SQL Blocked Queries Details attribute group contains attributes that provide information about
the queries that are currently blocked on the SQL Server.

Blocked Database Name (Unicode) The name of the database against which the blocked query is
currently being run. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocked User Name (Unicode) The name of the user who has run the blocked SQL query. The following
value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocked Query Text The SQL text of the query that is currently blocked on the SQL Server. The following
value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocked Session ID The session ID that is blocking the query that is currently being run on the SQL
Server. The following value is valid:

Chapter 4. Attributes reference 119

External value Internal value Description
Not Collected -1 The value cannot be collected.

Blocked Parent Query Text The SQL text of the parent of the blocking query. The value format is an
alphanumeric string with a maximum of 2048 characters. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocking Query Text The SQL text of the query blocks one or more than one queries on the SQL Server.
The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocking Reason The reason for blocking the query. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocking Resource The resource for which the query is currently blocked on the SQL Server. The
following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Blocking Session ID The ID of the session that is currently blocking the execution of a query on the SQL
Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Blocking User Name The login name of the user who ran the blocking query. The following value is
valid:

External value Internal value Description

No Data nodata No data is collected.

Hub Timestamp The time when data is inserted at the hub.

Originnode The key for the table view in the format serverid:hostname:MSS.

Server The name of the SQL Server.

Total Wait Time (Sec) The total wait time (in seconds) since the query has been blocked on the SQL
Server. The following value is valid:

120 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.

MS SQL Configuration attributes

The MS SQL Configuration attribute group contains attributes that you can use to monitor the
configuration of a SQL server.

Config Parameter The name of the configuration parameter. The value format is an alphanumeric string
with a maximum of 30 characters; for example, Partition group. The sysconfigures and syscurconfigs
system tables store the configuration parameters. Use the parameter name to track the performance of a
particular configuration parameter.

Config Value The value for the configuration parameter. The value format is an alphanumeric string with
a maximum of 12 characters; for example, 1000. The value was initially specified in the sysconfigures
system table. Monitor this value to track its effect on performance, and to compare the initial setting to
the maximum, minimum, and run values.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Maximum Value The maximum value that can be specified for the configuration parameter. The value
format is an alphanumeric string with a maximum of 12 characters; for example, 2147483647.

Minimum Value The minimum value that can be specified for the configuration parameter. The value
format is an alphanumeric string with a maximum of 12 characters; for example, 1.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Parm Type The type of configuration parameter. If the configuration parameter is dynamic, a server
restart is not required. The following values are also valid:

External value Internal value Description

Dynamic 1 Configuration parameter is dynamic.
Static 0 Configuration parameter is static.
Advanced 2 Configuration parameter is advanced.
Dynamic_and_Advanced 3 Configuration parameter is dynamic and
advanced.
Unknown -1 Configuration parameter is unknown.

Run Value The value the SQL server is using for the configuration parameter. The value format is an
alphanumeric string with a maximum of 12 characters; for example, 1000.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

Chapter 4. Attributes reference 121

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

MS SQL Database Detail attributes

The MS SQL Database Detail attribute group contains attributes that you can use to monitor the
performance and usage of MS SQL database.

Accessible Access validation of the database. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Yes 0 The database is accessible.
No 1 The database is not accessible.

Note: When the database is in offline, restoring, or transition state, the value of this attribute is displayed
as No.

Active Transactions The number of active transactions for the database. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Aggregate Database Freespace (MB) The total amount of freespace (in MB) that is available in all the
data files and on the storage device. The value format is a decimal number with two decimal places
allowed. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Aggregate Database Freespace Pct The percentage of the total amount of freespace that is available in all
the data files and on the storage device out of the total space allowed. The value format is a decimal
number with two decimal places allowed. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Data File Names The names of all physical files for data that make up this database.

122 Microsoft SQL Server agent: User’s Guide

Data Files Freespace (MB) The amount of freespace (in MB) that is available in all the data files. The
value format is a decimal number with two decimal places allowed. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Data Freespace The number of megabytes (MB) of free space for the database. The value includes the
megabytes of free data only. The value does not include the free space available in the database. The
value format is a decimal number with two decimal places allowed; for example, 10.00. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Data Freespace Percent The percentage of maximum available free space for the database. The value
format is a percentage with two decimal places allowed; for example, 20.00. The product calculates this
percentage from the maximum available free space for the database and the amount of space already
allocated for the database. Consider using the alter database command to expand the database size. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Note: Calculating value for this attribute depends on the database file space configuration options that
you specify when creating a database. Depending on these options, the SQL Server agent uses a different
algorithm to calculate the data freespace percent.

Option one: Database created with the dynamic growth option

This algorithm considers the hard disk drive freespace for calculation.

Formula for calculation:

Data Freespace Percent = (DB freespace/DB max size) X 100

Where:
v DB freespace is the total free space on all hard disk drives that contain the database files
v DB max size = total allocated database file size + database freespace

Option two: Database created with a fixed maximum size and the database grows dynamically till the
maximum limit is reached.

This algorithm considers the maximum size of the database for calculation.

Formula for calculation:

Data Freespace Percent = (DB freespace/DB max size) X 100

Where:
v DB freespace = (DB max size - DB current size)
v DB max size and DB current size read from the sysfiles table

Chapter 4. Attributes reference 123

Option three: Database created with the no growth option

This algorithm differs from the first two options. The database maximum size is the initial file size of the
database at the time of database creation. The freespace is the freespace in the database file. In the first
two options, reports freespace is derived from the physical hard disk drive space.

Formula for calculation:

Data Freespace Percent = (DB freespace/DB max size) X 100

Where:
v DB freespace = unallocated database pages in the database file
v DB max size and DB current size read from the sysfiles table

Data Size The number of megabytes (MB) allocated for the data only segments of the database. The
value format is a decimal number with two decimal places allowed; for example, 50.00. The following
value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Database Growth Percent The percentage of growth for the database from the last sample to the current
sample. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Database Name The name of the database. The value format is an alphanumeric string with a maximum
of 30 characters; for example, KOQ3. Each database name is unique. The SQL server also assigns each
database its own identification number. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Database Maximum Growth Size The maximum size to which the database can grow in MB. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Database Name (Unicode) The name of the database. Valid values include text strings with a maximum
of 384 bytes; for example, KOQ3. Each database name is unique. The SQL server also assigns each
database its own identification number.

Database Space Percent Used The amount of space (in megabytes) used in the database as a percentage
of total space allowed. Use this attribute to warn you when you need to extend the database. If you run
out of space, you can no longer use the database. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

124 Microsoft SQL Server agent: User’s Guide

Database State Reports the database state. The possible values for this attribute are:

Value Description
Online Database is available for access.
Offline Database is unavailable.
Restoring One or more files of the primary filegroup are being restored,
or one or more secondary files are being restored offline.
Recovering Database is being recovered.
Recovery Pending SQL Server has encountered a resource-related error during
recovery.
Suspect At least the primary filegroup is suspect and might be
damaged.
Emergency User has changed the database and set the status to
Emergency.

When the agent fails to collect data, the following value is displayed:

External value Internal value Description

No Data nodata No data is collected.

Database Status Reports when the database is unavailable. If a database is offline, you cannot access it.
Use this attribute to warn that the database has become unavailable. When the database is in transition
state, the database status is displayed as Available. The following values are valid:

External value Internal value Description

Available 0 The database is available.
Not Available 1 The database is not available.

DB ID The ID for the database. The value format is an alphanumeric string with a maximum of 12
characters; for example, 2156. This value is stored in the sysdatabases table. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

DB Owner The SQL server-assigned user ID for the owner of the database. The value format is an
alphanumeric string with a maximum of 8 characters; for example, DBO. Use the create database
command to establish this identifier.

DB Owner (Unicode) The SQL server-assigned user ID for the owner of the database. Valid values
include text strings with a maximum of 72 bytes. Use the create database command to establish this
identifier.

DBO Only Access Indicates whether the database has a status of DBO only. The following value is valid:

External value Internal value Description

No No Database can be accessed by
authorized users.
Yes Yes Database has a status of DBO only.

Chapter 4. Attributes reference 125

Dump Tran Date The timestamp that indicates the date on which the dump transaction command was
last executed for the database. The dump transaction command copies the uncommitted transactions in
the transaction log. Refer to this date to determine when the latest backup of the transaction log was
made. This attribute value may not be available for the SQL Server to capture. The format is
YYYYMMDD, where:

YYYY Year
MM Month
DD Day

For example, 20020501 indicates May 1, 2002. The following value is valid:

External value Internal value Description

Not Collected nodata The value cannot be collected.

Error Status Indicates whether the database has an error status. A database with an error status has a
status of suspect, crashed, or recovery. Check the status bits in the sysdatabases table to determine the
cause of the error. Use the database consistency checker (dbcc) to verify the database integrity. The
following values are valid:

External value Internal value Description

No No Database does not have an error
status.
Yes Yes Database has an error status.

Free Space Accounting Suppressed Indicates whether the free space accounting option is disabled for the
database. The no-free-space-actg option turns off free space accounting on non-log segments only.
Information about free space is inaccurate when free space accounting is turned off. Use the
no-free-space-actg option and the checkpoint command to speed recovery. No time is needed to count
free space for non-log segments. The following values are valid:

External value Internal value Description

No No Free space accounting is enabled.
Yes Yes Free space accounting is disabled.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Last Database Size The database size in MB from the previous sample. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Log Bytes Flushed per Sec The number of bytes of the log file that are flushed for the current interval.
The following value is valid:

126 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value cannot be collected.

Log File Names The names of all physical files for logs that make up this database.

Log Freespace The number of megabytes (MB) of free space in the transaction log for the database. The
value includes the number of megabytes of free space on the log only partitions. The value format is a
decimal number with two decimal places allowed; for example, 8.00. Various types of transactions, such
as mass updates and bulk copying in can involve extensive logging. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Log Freespace Percent The percentage of free space in the transaction log for the database. The value
format is a percentage with two decimal places allowed; for example, 20.00. Various types of transactions,
such as mass updates and bulk copying in can involve extensive logging. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Log Growths The total number of times the database transaction log is expanded since the SQL Server
was started. The format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Log Maximum Growth Size The maximum size to which the log can grow in MB. The following value is
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Log Size The number of megabytes (MB) allocated for the transaction log for the database. The value
includes the number of megabytes allocated for the transaction log on the log only partitions. The value
format is a decimal number with two decimal places allowed; for example, 500. The appropriate size for
a transaction log depends on how the database is used. Several factors, such as the number of
transactions, type of transactions, and number of users, effect sizing. Evaluate the need to truncate the
transaction log to prevent it from filling up. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Log Space Percent Used The percentage of the transaction log that is full. When the log has filled up all
of its allocated space, transactions that require logging are rejected. Use this attribute to set an alert based
on a percent full threshold, then spawn a task to dump or truncate the transaction log or to do both. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 127

Long Running Transaction Name The long running transaction name. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Long Running Transaction Process ID The longest running transaction. The Long running transactions
are transactions that are open for longer than the LongRunningTransColl standard collector parameter.
The format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Long Running Transaction Time Per Sec The time for which the longest running transaction is active (in
seconds). The format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

No CKPT After Recovery Indicates whether a record for the checkpoint is added to the transaction log
when the database is recovered. The following values are valid:

External value Internal value Description

No No No CKPT After Recovery option is
disabled.
Yes Yes No CKPT After Recovery option is
enabled.

Oldest Open Transaction The age (in minutes) of the oldest open transaction in the database transaction
log. Use this attribute to determine up to which point in time the transaction log can be truncated and
backed up. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Page Verify The option that identifies and notifies incomplete I/O transactions that have occurred
because of disk I/O errors. The following values are valid:

External value Internal value

NONE 0
TORN PAGE DETECTION 1
CHECKSUM 2
Not collected -1

128 Microsoft SQL Server agent: User’s Guide

Read Only Access Indicates whether the database has a status of read only. The following value is valid:

External value Internal value Description

No No Database is read and write database.
Yes Yes Database has a status of read-only.

Recovery Model The method used to maintain the transaction log. The three types of recovery models
include Simple, Full, and Bulk-logged. The following values are valid:

External value Internal value

FULL 1
BULK LOGGED 2
SIMPLE 3
Not collected -1

Replicated Transaction Rate The rate per second at which transactions have been read out of the
publication database transaction log and delivered to the distribution database. Use this attribute to
discover if there are any bottlenecks in the replication process. Bottlenecks cause delays in the published
transactions reaching the subscriber database. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Replicated Transactions The number of transactions in the publication database transaction log that are
marked for replication but have not yet been delivered to the distribution database. Use this attribute to
discover if there are any bottlenecks in the replication process. Bottlenecks cause delays in the published
transactions reaching the subscriber database. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Replication Latency The number of milliseconds between the time a transaction marked for replication is
entered into the publication database transaction log and the time it is read out of the log and delivered
to the distribution database. Use this attribute to discover if there are any bottlenecks in the replication
process. Bottlenecks cause delays in the published transactions reaching the subscriber database. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour

Chapter 4. Attributes reference 129

mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Select Into Bulkcopy Enabled Indicates whether the select into/bulkcopy option is enabled for the
database. The following values are valid:

External value Internal value Description

No No Select Into/Bulkcopy option is
disabled.
Yes Yes Select Into/Bulkcopy option is
enabled.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters. For example, CFS_SVR5.

Single User Access Indicates whether the database has a status of single user. A database with a status of
single user can only be accessed by one user at a time. The following values are valid:

External value Internal value Description

No No Database can be accessed by multiple
users.
Yes Yes Database has a status of single user.

Suspect Database Reports whether a database is marked as suspect. Use this attribute to warn you that a
database cannot be loaded. The following values are valid:

External value Internal value

True 0
False 1

Table Count The number of tables that exist in the database. The value format is an integer. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Devices The number of devices allocated for the database. The value format is an integer in the
range 1-128; for example, 4. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

130 Microsoft SQL Server agent: User’s Guide

Transactions per Second The number of transactions started for the database per second for the current
interval. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Write Transactions per sec The number of transactions written to the database and committed in the last
second. The format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Database Mirroring attributes

The MS SQL Database Mirroring attribute group provides information about the database mirroring
objects.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express® Edition.

Bytes Received Per Sec The number of bytes received per second. The format is an integer. The following
values are also valid:

External value Internal value

Not Collected -1

Bytes Sent Per Sec The number of bytes sent per second. The format is an integer. The following values
are also valid:

External value Internal value

Not Collected -1

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Log Bytes Received Per Sec The number of bytes of log received per second. The format is an integer.
The following values are also valid:

External value Internal value

Not Collected -1

Log Bytes Redone From Cache Per Sec The number of log bytes redone from the Database Mirroring log
cache per second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Chapter 4. Attributes reference 131

Log Bytes Sent From Cache Per Sec The number of log bytes sent from the Database Mirroring log cache
in the last second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Bytes Sent Per Sec The number of log bytes sent per second. The format is an integer. The following
values are also valid:

External value Internal value

Not Collected -1

Log Compressed Bytes Rcvd Per Sec The number of compressed log bytes received in the last second.
The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Compressed Bytes Sent Per Sec The number of compressed log bytes sent in the last second. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Harden Time The number of milliseconds the log blocks waited to be hardened to disk in the last
second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Remaining For Undo The total number of log bytes (in KB) that remain to be scanned by the new
mirror server after failover. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Scanned For Undo The total number of log bytes (in KB) that are scanned by the new mirror server
after failover. The format is an integer. The following values are also valid:

132 Microsoft SQL Server agent: User’s Guide

External value Internal value
Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Send Flow Control Time The time (in milliseconds) awaited by the log stream messages for the send
flow control in the last second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Send Queue The total number of megabytes of log that are not sent to the mirror server. The format
is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Mirror Name The name of the database. The following values are valid:

External value Internal value Description

No Data nodata The value could not be collected.

Mirrored Write Transactions Per Sec The number of transactions (that waited for log to be sent to the
mirror) written to the mirrored database in the last second. The format is an integer. The following values
are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Mirroring Role The current role of the local database in the database mirroring session. The format is an
integer. The following values are also valid:

External value Internal value

Not Collected -1
Mirror 0
Principal 1

Mirroring State The state of the mirror database. The format is an integer. The following values are also
valid:

External value Internal value

Not Collected -1
Suspended 0
Disconnected 1

Chapter 4. Attributes reference 133

External value Internal value
Synchronizing 2
Pending Failover 3
Synchronized 4

Originnode The key to this table of the format serverid:hostname:MSS.

Pages Sent Per Sec The number of pages sent per second. The format is an integer. The following values
are also valid:

External value Internal value

Not Collected -1

Receives Per Sec The number of mirroring messages received per second. The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1

Redo Bytes Per Sec The number of bytes of log redone by the mirror database per second. The format is
an integer. The following values are also valid:

External value Internal value

Not Collected -1

Redo Queue The number of megabytes that redo on the mirror database is behind the hardened log. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Sample Timestamp The time when data is collected.

Send Receive Ack Time The time (in milliseconds) awaited by the messages to receive an
acknowledgment from the partner. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Sends Per Sec The number of sends initiated per second at the time of monitoring interval. The format is
an integer. The following values are also valid:

External value Internal value

Not Collected -1

Server The name of the SQL Server.

134 Microsoft SQL Server agent: User’s Guide

Synchronization State The state of synchronization (is failover possible). The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1
Failover not possible 0
Failover possible 1

Transaction Delay The time (in milliseconds) awaited by the transaction termination to receive an
acknowledgment. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

MS SQL Database Summary attributes

The MS SQL Database Summary attribute group contains attributes that you can use to monitor summary
information about SQL server databases.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data that IBM Tivoli
Monitoring for Microsoft SQL Server collects about each SQL server. New data becomes available if a
new interval has occurred and data has been refreshed at the CMS hub.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Minimum Pct Data Freespace The lowest percentage of free space in data only and data and log
segments on a device allocated to a database. The value format is a percentage with two decimal places
allowed; for example, 5.00. The amount of space needed by the database depends on its anticipated
activity. Set alerts for abnormal conditions. Evaluate the possibility of adding more space to the database.

Minimum Pct Log Freespace The lowest percentage of free space in log only and data and log segments
on a device allocated for the database transaction log. The value format is a percentage with two decimal
places allowed; for example, 5.00. The amount of space needed by the transaction log depends on the
type and quantity of the transactions and the frequency of backups. Set alerts for abnormal conditions.
Evaluate the possibility of expanding the log.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day

Chapter 4. Attributes reference 135

YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters. For example: CFS_SVR5.

Total Databases The number of databases for the SQL server. The value format is an integer; for example,
10.

Total DBs DBO Only The number of databases with a status of DBO only. A database with a status of
database owner can be accessed only by users with DBO authority. The value format is an integer; for
example, 5.

Total DBs in Error The number of databases with an error status. A database with an error status is a
database with a status of suspect, crashed, or recovery. The value format is an integer; for example, 2.

Total DBs No Free Space Accounting The number of databases that have the free space accounting
option disabled. The value format is an integer; for example, 5.

Total DBs Read Only The number of databases with a status of read only. The value format is an integer;
for example, 5.

Total DBs Single User The number of databases with a status of single user. A database with a status of
single user can be accessed by only one user at a time. The value format is an integer; for example, 2.

MS SQL Device Detail attributes

The MS SQL Device Detail attribute group contains attributes that you can use to monitor the usage and
performance of devices.

Autogrowth Indicates whether the autogrowth feature is enabled for a device. If the autogrowth feature
is enabled, the maximum file size is displayed as restricted or unrestricted. The following values are
valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Disabled 0 The autogrowth feature is disabled.
Restricted 1 The growth is restricted.
Unrestricted 2 The growth is unrestricted.

Autogrowth Unit Indicates the unit of file growth. If the autogrowth feature is enabled for a device, the
file growth value is displayed either in a percentage or MB. The following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Not Applicable -2 The value is not supported.
Percentage 1 The file growth is displayed in percentage.

136 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
MB 2 The file growth is displayed in MB.

Autogrowth Value Indicates the growth value of a file. The following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Not Applicable -2 The value is not supported.

Database Name The name of the database. The value format is alphanumeric string with a maximum 30
characters; for example, KOQ3. Each database name is unique. The SQL server also assigns each database
its own identification number. The following values are also valid:

External value Internal value Description

No Data nodata No data is collected.

Database Name (Unicode) The Database name. Valid values include text strings with a maximum of 384
bytes. The following values are also valid:

External value Internal value Description

No Data nodata No data is collected.

Device Free Space The number of megabytes (MB) of free space on a device. The value format is a
decimal with two decimal places allowed; for example, 10.00. Adequate space is required to support
database and system administration activities. Set alerts for abnormal conditions. Refer to this value when
estimating space needed for tables, indexes, logs, and system administration. The following values are
also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Device Free Space Percent The percentage of free space on the device. The value format is a percentage
with two decimal places allowed; for example, 15.00. Adequate space is required to support database and
system administration activities. Set alerts for abnormal conditions. Refer to this value when estimating
space needed for tables, indexes, logs, and system administration. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Device Name The name of the device allocated for the database. The value format is an alphanumeric
string with a maximum of 64 characters; for example, DATA_1. The logical name of the device is stored
in the name column of the sysdevices table. Use the device name in storage-management commands.

Device Name (Unicode) The Device name. Valid values include text strings with a maximum of 384
bytes.

Device Size The number of megabytes (MB) on the device. The value format is an integer; for example,
20. Use this value when analyzing the amount of free space. The following values are also valid:

Chapter 4. Attributes reference 137

External value Internal value Description
Not Collected -1 The value could not be collected.

Option 1 for calculation :Autogrowth is enabled and has unrestricted growth This algorithm considers
the hard disk drive freespace for calulation

Disk size = Total free space on all hard disk drives that contain the database files

Device Size = Disk size + Total database file size

Device Freespace = Device Size - Current allocated space of database file

Device Freespace Percent = (Device Freespace / Device Size) X 100

Option 2 for calculation: Autogrowth is enabled and has restricted growth This algorithm considers the
maximum size of the database and hard disk drive free space for calculation.

Device maximum size = The restricted maximum size allocated to the database file

Disk size = Total free space on all hard disk drives that contain the database files

Condition (a): If device maximum size < Disk size

Device Size = Device maximum size
Device Freespace = Device Size - Current allocated space of database file
Device Freespace Percent = (Device Freespace / Device Size) X 100

Condition (b): if Device maximum size > Disk size

Device Size = Disk size
Device Freespace = Device Size - Current allocated space of database file
Device Freespace Percent = (Device Freespace /Device Size) X 100

Option 3 for calculation: Autogrowth disabled The database maximum size is the initial file size of the
database at the time of database creation.

Device max size = Initial file size of the database at the time of database creation.

Device Size = Device maximum size

Device Freespace = Device Size - Current allocated space of database file

Device Freespace Percent = (Device Freespace / Device Size) X 100

Device Type Indicates the type of device allocated for the database. The following values are also valid:

External value Internal value Description

Log file 1 Indicates that the device stores the
transaction log for the database.
Database file 2 Indicates that the device stores data for the
database.
For future use 3 Indicates that the device supports future
compatibility.

138 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Full text 4 Indicates that the device supports a
full-text catalog.
FILESTREAM 5 Indicates that the device is a FILESTREAM
device.
Not collected -1 The value could not be collected.

The value indicates the type of data that is stored on the device. Databases are frequently spread across
several devices due to size, performance, and recoverability issues.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Mirror Device Name The name of the mirror device for the database. The value format is an
alphanumeric string with a maximum of 64 characters; for example, /dev/rsd2g. The mirror device
duplicates the contents of a primary device. Refer to the logical and physical names of the device that is
being mirrored. The following values are also valid:

External value Internal value Description

Not applicable N/A The value is not supported.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Physical Device Name The name of the physical device allocated for the database. The value format is an
alphanumeric string with a maximum of 30 characters; for example, DATA_1.

Physical Device Name (Unicode) The Name of the physical device. Valid values include text strings with
a maximum of 192 bytes.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Chapter 4. Attributes reference 139

Server Version The version of the SQL Server. The value format is the version in the format w.x.y.z; for
example, 10.0.2531.0.

Server Version (Superceded) The version of the SQL Server. The value format is the version in the format
x.y.z; for example, 10.0.253.

Note: For the complete version of the SQL Server, see the Server Version attribute.

MS SQL Enterprise Database Mirroring attributes

The MS SQL Enterprise Database Mirroring attribute group provides information about the database
mirroring objects.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Bytes Received Per Sec The number of bytes received per second. The format is an integer. The following
values are also valid:

External value Internal value

Not Collected -1

Bytes Sent Per Sec The number of bytes sent per second. The format is an integer. The following values
are also valid:

External value Internal value

Not Collected -1

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Log Bytes Received Per Sec The number of log bytes received per second. The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1

Log Bytes Redone From Cache Per Sec The number of log bytes redone from the Database Mirroring log
cache per second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Bytes Sent From Cache Per Sec The number of log bytes sent from the Database Mirroring log cache
in the last second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

140 Microsoft SQL Server agent: User’s Guide

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Bytes Sent Per Sec The number of log bytes sent per second. The format is an integer. The following
values are also valid:

External value Internal value

Not Collected -1

Log Compressed Bytes Rcvd Per Sec The number of compressed log bytes received in the last second.
The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Compressed Bytes Sent Per Sec The number of compressed log bytes sent in the last second. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Harden Time The time (in milliseconds) awaited by the log blocks to be hardened to the disk in the
last second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Remaining For Undo The total number of log bytes (in KB) that remain to be scanned by the new
mirror server after failover. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Scanned For Undo The total number of log bytes (in KB) that are scanned by the new mirror server
after failover. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Chapter 4. Attributes reference 141

Log Send Flow Control Time The time (in milliseconds) awaited by the log stream messaged for send
flow control in the last second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Log Send Queue The total number of megabytes of log that are not sent to the mirror server. The format
is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Mirror Name The name of the database. The following values are valid:

External value Internal value Description

No Data nodata The value could not be collected.

Mirrored Write Transactions Per Sec The number of transactions (that waited for log to be sent to the
mirror) written to the mirrored database in the last second. The format is an integer. The following values
are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Mirroring Role The current role of the local database in the database mirroring session. The format is an
integer. The following values are also valid:

External value Internal value

Not Collected -1
Mirror 0
Principal 1

Mirroring State The state of the mirror database. The format is an integer. The following values are also
valid:

External value Internal value

Not Collected -1
Suspended 0
Disconnected 1
Synchronizing 2
Pending Failover 3
Synchronized 4

Originnode The key to this table of the format serverid:hostname:MSS.

142 Microsoft SQL Server agent: User’s Guide

Pages Sent Per Sec The number of pages sent per second. The format is an integer. The following values
are also valid:

External value Internal value

Not Collected -1

Receives Per Sec The number of mirroring messages received per second. The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1

Redo Bytes Per Sec The number of bytes of log redone by the mirror database per second. The format is
an integer. The following values are also valid:

External value Internal value

Not Collected -1

Redo Queue The number of megabytes that redo on the mirror database is behind the hardened log. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Sample Timestamp The time when data is collected.

Send Receive Ack Time The time (in milliseconds) awaited by the messages to receive an
acknowledgment from the partner. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Note: This attribute is not supported on the SQL Server 2005 Enterprise Edition.

Sends Per Sec The number of sends initiated per second at the time of monitoring interval. The format is
an integer. The following values are also valid:

External value Internal value

Not Collected -1

Server The name of the SQL Server.

Synchronization State The state of synchronization (is failover possible). The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1
Failover not possible 0
Failover possible 1

Chapter 4. Attributes reference 143

Transaction Delay The time (in milliseconds) awaited by the transaction termination to receive an
acknowledgment. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

MS SQL Enterprise Log Shipping DB Details attributes

The MS SQL Enterprise Log Shipping DB Details attribute group provides detailed information about log
shipping databases.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Database ID The ID of the primary or secondary database for the log shipping configuration.

Database Name The name of the database.

Hub Timestamp The time when data is inserted at the hub.

Last File Processed The absolute path of the most recent transaction log backup or restore.

Last File Processed Time The date and time at which the file is processed. The format is YY/MM/DD
HH:mm, where:

YY Year
MM Month
DD Day
HH Hour
mm Minute

Message The job completion message text.

Originnode The key to this table of the format serverid:hostname:MSS.

Sample Timestamp The time when data is collected.

Server The name of the SQL Server.

Server Type Indicates whether the server is primary or secondary. The format is an integer. The following
values are also valid:

External value Internal value

Primary 0
Secondary 1

Source The source of the error message or event.

Threshold The number of minutes allowed to elapse between backup or restore operations before an
alert is generated.

144 Microsoft SQL Server agent: User’s Guide

Threshold Exceeded Indicates whether the threshold is exceeded or not. The format is an integer. The
following values are valid:

External value Internal value

No 0
Yes 1

MS SQL Error Event Details attributes

The MS SQL Error Event Details attribute group provides detailed information about the selected errors
in the SQL Server error log. The data is collected at the time that the error occurred. This attribute group
is an event-type attribute group.

Error ID The ID of the error message. The value format is an integer. For example, 2520. The errors with
text that are not numbered are written to the SQL Server message logs.

Error SPID The ID of the session in which the event has occurred. This attribute is available for reports,
queries, and workspaces, but not for situations.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time at which data was inserted in the hub. This attribute is available for reports,
queries, and workspaces, but not for situations.

Message Age The number of minutes that have elapsed since the error occurred. The format is an integer,
for example, 2. Use this attribute to help identify the current messages.

Message Issuer The source of the error message. The value format is an alphanumeric string with a
maximum of 8 characters, for example, JSMITH.

Message Text (Unicode) The message text. This attribute is available for reports, queries, and workspaces,
but not for situations.

Message Timestamp The timestamp that indicates the date and time at which the error occurred. The
format is MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the agent collected data from the SQL Server on January 25,
2002 at 8:00 a.m.

Originnode The key for the table view. The format is serverid:hostname:MSS. This attribute is available
for reports, queries, and workspaces, but not for situations.

Sample Timestamp The timestamp that indicates the date and time at which the agent collected sample
data for the SQL Server. The format is MM/DD/YY HH:mm:SS, where:

Chapter 4. Attributes reference 145

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the agent collected the data from the SQL Server on
January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server. The value format is an alphanumeric string with a maximum of 32
characters. For example, CFS_SVR.

Severity Level The severity level of the error.

SQL State Code The value that represents state of the SQL Server when the error occurred. The value
format is an integer. For example, 37.

MS SQL Filegroup Detail attributes

The MS SQL Filegroup Detail attribute group provides details about the filegroups for each database in
the SQL Server instance.

Database Name The name of the database.

Filegroup ID The filegroup identification number.

Filegroup Max Growth Size The maximum amount of space (in MB) that the filegroup can grow to.

Filegroup Name The name of the filegroup.

Filegroup Size The size of the filegroup in MB.

Filegroup Space Percent Used The amount of space (in MB) used in the filegroup as a percentage of total
space allowed.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day

146 Microsoft SQL Server agent: User’s Guide

YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server.

MS SQL FileTable Detail attributes

The MS SQL FileTable Detail attribute group contains attributes that provide information about each
FileTable in the SQL Server.

Database ID The database ID. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

FileTable Directory The name of the directory of the FileTable. The following values are valid:

External value Internal value Description

No Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

FileTable Enabled Indicates whether the FileTable data is available for non-transactional access. The
following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.
No 1 FileTable data is not enabled for
non-transactional access.
Yes 2 FileTable data is enabled for
non-transactional access.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Originnode The key for the table view in the format serverid:hostname:MSS.

Server The name of the SQL Server.

Table ID The table ID. The following values are valid:

Chapter 4. Attributes reference 147

External value Internal value Description
Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Table Name The table name. The value format is an alphanumeric string with a maximum of 30
characters. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value cannot be collected.
Not Applicable Not_applicable The value is not supported.

Total Non Transactional Handles Opened The total number of non-transactional file handles that are
currently open and that are associated with the FileTable. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

MS SQL Individual Queries Details attributes

The MS SQL Individual Queries Details attribute group contains attributes that provide information about
each query in the query batch that is currently running on the SQL Server.

Average CPU Time (Sec) The average CPU time (in seconds) that is taken to run an SQL query. The
following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Average Logical Reads The average number of logical read operations that are completed by an SQL
query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Average Logical Writes The average number of logical write operations that are completed by an SQL
query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Average Physical Reads The average number of physical read operations that are completed by an SQL
query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

148 Microsoft SQL Server agent: User’s Guide

Database Name (Unicode) The name of the database against which the SQL query is running on the SQL
Server. The following value is valid:

External value Internal value Description

No Data nodata The value cannot be collected.

Hub Timestamp The time when data is inserted at the hub.

Last Execution Time The time when an SQL query was last run on the SQL Server. The following value
is valid:

External value Internal value Description

No Data nodata The value cannot be collected.

The format is MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL Server on
Friday, January 25, 2002 at 8:00 a.m.

Max CLR Time (Sec) The maximum common language runtime (CLR, in seconds) that is used for a
single execution of an SQL query inside the .NET framework CLR. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Max CPU Time (Sec) The maximum CPU time (in seconds) that is used for a single execution of an SQL
query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Max Logical Reads The maximum number of logical read operations that are completed by a single
execution of an SQL query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Max Logical Writes The maximum number of logical write operations that are completed by a single
execution of an SQL query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 149

Max Physical Reads The maximum number of physical read operations that are completed by a single
execution of an SQL query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Max Waiting Time (Sec) The maximum waiting time (in seconds) that is taken by a single execution of
an SQL query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Originnode The key for the table view in the format serverid:hostname:MSS.

Query Execution Count The total number of times an SQL query has been run since the query was last
compiled. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Query Hash The query hash of an SQL query. The value format is an alphanumeric string with a
maximum of 2048 characters. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

This attribute, with the Session ID attribute, is used to create the primary key.

Query Text The SQL text of a query in an SQL query batch. The following value is valid:

External value Internal value Description

No Data nodata The value cannot be collected.

Server The name of the SQL Server.

Session ID The ID of the session in which the query is run. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

SQL Handle The SQL handle of the query. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Total CPU Time (Sec) The total amount of CPU time (in seconds) that is used by all the executions of an
SQL query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

150 Microsoft SQL Server agent: User’s Guide

Total Percent CPU Used The percentage of the available CPU memory that is used for executing an SQL
query. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Total Percent Waiting The percentage of total wait operations that are completed when an SQL query is
run. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

MS SQL Integration Service Details attributes

The MS SQL Integration Service Details attribute group provides details about the SQL Server integration
service pipeline for an instance of the SQL Server.

Buffer In Use The number of buffers that are currently used for the pipeline. The following value is
valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Buffer Memory (MB) The amount of memory in MB that is currently allocated to the buffers that are in
the pipeline. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Buffer Spooled The number of buffers that are currently spooled to disk. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Flat Buffers In Use The number of flat memory buffers that are currently used for the pipeline. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Flat Buffer Memory The amount of memory that is currently allocated to flat memory buffers. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Chapter 4. Attributes reference 151

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, it is
available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Private Buffer Memory The amount of memory that is currently allocated to private transformation
buffers. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Private Buffers In Use The number of private transformation buffers that are currently used for the
pipeline. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Server The name of the SQL Server.

Total Rows Read The total number of rows that are currently being read from all data sources. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Rows Written The total number of rows that are currently being written to all data destinations.
The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

MS SQL Job Detail attributes

The MS SQL Job Detail attribute group contains attributes that you can use to monitor SQL Server jobs.

Current Execution Status The current execution status of the job. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Current Execution Step The current step that is being executed in the job. The value format is an
alphanumeric string with a maximum of 128 characters. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

152 Microsoft SQL Server agent: User’s Guide

Current Retry Attempt The current number of retry attempts that are done on a step of a running job.
The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Current Status The current job status. A job is in one of the following states:

External value Internal value

Executing 1
Waiting_for_thread 2
Between_retries 3
Idle 4
Suspended 5
Performing_completion_actions 7
Unknown -1

Enabled Whether or not the job is enabled to run. The following values are valid:

External value Internal value

No 0
Yes 1
Unknown -1

Job Type The type of the job. The following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Local Job 1 The job is run on a local server.
Multiserver 2 The job is run on multiple servers.
No Target Server 3 No target server is defined for the
job.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Job Category ID Job category ID for the job. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Job Category Name Job category name for the job.

Chapter 4. Attributes reference 153

Job Description The description of the job. The value format is an alphanumeric string with a maximum
of 512 characters. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Job Duration The amount of time it took for the job to complete (in seconds). The following value is
valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Job Error Code Error code for the last completion of the job. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Job Execution Duration The time (in seconds) that has elapsed since the job started. The following values
are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Not Applicable -2 The value is not supported.

Jobs ID The SQL Server job ID.

Jobs Name The SQL Server job name.

Job Owner The name of the owner of the job. The value format is an alphanumeric string with a
maximum of 128 characters. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Job Status Current status of the job. The following values are valid:

External value Internal value

Failed 0
Succeeded 1
Retry 2
Canceled 3
In-progress In-progress
Unknown 5 or -1

Last Run Outcome The last job execution status. The following values are valid:

154 Microsoft SQL Server agent: User’s Guide

External value Internal value
Failed 0
Succeeded 1
Canceled 3
Unknown 5 or -1

Last Run Timestamp The timestamp of last job execution. If the job has not been run at all, the Last Run
Timestamp value is 'N/P' (Not Present). If there is an error retrieving the job information, the Last Run
Timestamp value is 'N/P'.

Next Run Timestamp The timestamp of the next scheduled job execution. If a job is not scheduled to
run, its Next Run Timestamp is 'N/C' (Not Configured). If there is an error retrieving the job information,
the Next Run Timestamp values is 'N/P'(Not Present).

Notify Level Eventlog The value that indicates when a notification event must be sent to the Microsoft
Windows application log. The following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Never 0 The notification must not be sent to
the Microsoft application log.
When a job succeeds 1 The notification must be sent to the
Microsoft application log when a job
succeeds.
When the job fails 2 The notification must be sent to the
Microsoft application log when a job
fails.
When the job completes 3 The notification must be sent to the
Microsoft application log when a job
is complete, regardless of the
outcome of the job.

Number of Steps The current number of steps in the job. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour

Chapter 4. Attributes reference 155

mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server.

Start Step ID The step identifier from where the execution of the job starts. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Number The version number of the job. The version number is automatically updated every
time that the job is modified. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

MS SQL Job Summary attributes

The MS SQL Job Summary attribute group contains attributes that you can use to monitor jobs.

Active Jobs The number of active jobs since the agent was started. The format is an integer. The
following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Failed Jobs The number of failed jobs since the SQL Server agent was started. The format is an integer.
The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Jobs Failed Current Interval The number of failed jobs for the current sample interval. The following
values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Jobs Failed Since Startup The number of failed jobs since the agent was started.

156 Microsoft SQL Server agent: User’s Guide

Job Success Rate The rate at which jobs are successful since the agent was started. The format is an
integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Max Jobs Failed Interval Maximum number of failed jobs across all samples since the agent was started.

Max Running Jobs Interval Maximum number of running jobs across all samples since the agent was
started.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Queued Jobs The number of jobs in a queue since the agent was started. The format is an integer. The
following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Running Jobs Current Interval The number of running jobs for the current sample interval. The
following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server.

Successful Jobs The number of successful jobs since the agent was started. The format is an integer. The
following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Chapter 4. Attributes reference 157

MS SQL Lock Conflict Detail attributes
The MS SQL Lock Conflict Detail attribute group contains attributes that you can use to monitor detailed
information about a selected lock conflict.

Blocking Process ID The identifier for the process that is blocking a request for a lock. The value format
is an alphanumeric string with a maximum of 8 characters; for example, 12. Some blocking processes can
become stranded. Investigate situations in which a process is being blocked for an extended period of
time. For more information on a blocking process, query the sysprocesses and use the sp-lock procedure.

Client Group ID The group ID of the user executing the process. This value does not apply to Microsoft
SQL Server version 7. The value format is an alphanumeric string with a maximum of 8 characters; for
example, ACCT_1.

Client User ID ID of the user who executed the command. The value format is an alphanumeric string
with a maximum of 8 characters.

Database ID ID of the database that is locked. The value format is an integer.

Database Name The name of the database. The value format is an alphanumeric string with a maximum
of 30 characters; for example, KOQ3. Each database name is unique. The SQL server also assigns each
database its own identification number.

Database Name (Unicode) The name of the database. Valid values include text strings with a maximum
of 384 bytes.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Requestor Process ID The ID of the blocked process. The value format is an alphanumeric string with a
maximum of 16 characters; for example, 21.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

158 Microsoft SQL Server agent: User’s Guide

Server The number of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Server User ID The ID of the server user. The value format is an alphanumeric string with a maximum
of 8 characters.

MS SQL Lock Detail attributes

The MS SQL Lock Detail attribute group contains attributes that you can use to monitor detailed
information about lock contention by lock type.

Database ID The ID of the database that is locked. The value format is an integer. The following values
are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Database Name The name of the database that is locked. The value format is an alphanumeric string
with a maximum of 16 characters; for example, DB12.

Database Name (Unicode) The name of the locked database.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Lock Request Status Enumeration that identifies the Lock Request Status. The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1
Granted 1
Converting 2
Waiting 3

Lock Resource Type E Enumeration that identifies the Lock Resource Type. The format is an integer. The
following values are also valid:

External value Internal value

NULL_Resource 1
Database 2
File 3
Index 4
Table 5
Page 6
Key 7
Extent 8

Chapter 4. Attributes reference 159

External value Internal value
RID 9
Application 10
Metadata 11
Heap_or_Btree 12
Allocation_Unit 13

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Page Number The page number of the table being locked. The value format is an integer. The following
values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Process Holding Lock The ID of the process holding the lock. The value format is an integer. The
following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example CFS_SVR5.

Table Name The name of the table being locked. The value format is an alphanumeric string with a
maximum of 16 characters.

Table Name (Unicode) Name of Table being locked. Valid values include text strings with a maximum of
384 bytes.

Total Locks The total number of locks for the server. The value format is an integer. The following value
is valid:

160 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value could not be collected.

Total Lock Conflicts The total number of processes that are involved in lock conflicts. The value format
is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Type Indicates the type of lock on the resource that is being requested. The following values are also
valid:

External value Internal value Description

No Data nodata No data is collected.
Unknown Unknown The value is unknown.

and

Value Description
NULL
Sch-S Schema stability
Sch-M Schema modification
IS Intent Shared
SIU Shared Intent Update
IS-S Intent Shared-Shared
IX Intent Exclusive
SIX Shared Intent Exclusive
S Shared
U Update
IIn-Nul Intent Insert-NULL
IS-X Intent Shared-Exclusive
IU Intent Update
IS-U Intent Shared-Update
X Exclusive
BU Used by bulk operations
UIX Update Intent Exclusive
RangeS-S Shared Key-Range and Shared Resource
RangeS-U Shared Key-Range and Update Resource
RangeI-N Insert Key-Range and Null Resource
RangeI-S Key-Range conversion lock
RangeI-U Key-Range conversion lock
RangeI-X Key-Range conversion lock
RangeX-S Key-Range conversion lock
RangeX-U Key-Range conversion lock

Chapter 4. Attributes reference 161

Value Description
RangeX-X Exclusive Key-Range and Exclusive Resource

MS SQL Lock Resource Type Summary attributes

The MS SQL Lock Resource Type Summary attribute group provides information about locks on
individual resource types.

Average Wait Time Locks The average amount of wait time (in milliseconds) for each lock request that
resulted in a wait.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Lock Requests per Second The number of new locks and lock conversions per second requested from the
lock manager. This value is calculated on an interval, and does not reflect a total value.

Lock Resource Type An enumeration of the resources that the SQL Server can lock. The following values
are also valid:

External value Internal value

NULL_Resource 1
Database 2
File 3
Index 4
Table 5
Page 6
Key 7
Extent 8
RID 9
Application 10
Metadata 11
Heap_or_Btree 12
Allocation_Unit 13
Object 14
OibTrackTbl 15

Lock Timeouts per Second The number of lock requests per second that timed out, including requests
for NOWAIT locks.

Lock Wait Time The total wait time (in milliseconds) for locks in the last second.

Number Deadlocks per Second The number of Deadlocks per second for the current sample interval.

162 Microsoft SQL Server agent: User’s Guide

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server.

MS SQL Lock Summary attributes

The MS SQL Lock Summary attribute group contains attributes that you can use to monitor the number
of database locks that are currently open.

Exclusive Extent Locks The number of granted Exclusive Extent locks.

Exclusive Intent Locks The number of granted Exclusive Intent locks.

Exclusive Locks The number of granted Exclusive locks.

Exclusive Page Locks The number of granted Exclusive Page locks.

Exclusive Table Locks The number of granted Exclusive Table locks.

Extent Locks The number of granted Extent locks.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Intent Locks The number of granted Intent locks.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Page Locks The number of granted Page locks.

Pct Max Locks The percentage of locks on resources of the maximum number of locks allowed by the
SQL server. The value format is a percentage with two decimal places allowed; for example, 10.00. Setting

Chapter 4. Attributes reference 163

a higher limit for the maximum number of locks does not impair performance. If your operations exceed
the number of available locks, you can increase this limit. This attribute is not available for use in
situations or for historical data collection. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Server Enterprise View attribute group. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server.

Shared Intent Locks The number of granted Shared Intent locks.

Shared Locks The number of granted Shared locks.

Shared Page Locks The number of granted Shared Page locks.

Shared Table Locks The number of granted Shared Table locks.

Table Locks The number of granted Table locks.

Table Lock Escalations per Sec The number of times that the locks on a table were escalated.

Total Lock Conflicts The total number of processes involved in lock conflicts. The value format is an
integer. This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group. The following
value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Update Extent Locks The number of granted Update Extent locks.

Update Page Locks The number of granted Update Page Locks.

164 Microsoft SQL Server agent: User’s Guide

MS SQL Log Shipping DB Details attributes
The MS SQL Log Shipping DB Details attribute group provides detailed information about log shipping
databases.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Database ID The ID of the primary or secondary database for the log shipping configuration.

Database Name The name of the database.

Hub Timestamp The time when data is inserted at the hub.

Last File Processed The absolute path of the most recent transaction log backup or restore.

Last File Processed Time The date and time at which the file is processed. The format is YY/MM/DD
HH:mm, where:

YY Year
MM Month
DD Day
HH Hour
mm Minute

Message The job completion message text.

Originnode The key to this table of the format serverid:hostname:MSS.

Sample Timestamp The time when data is collected.

Server The name of the SQL Server.

Server Type Indicates whether the server is primary or secondary. The format is an integer. The following
values are also valid:

External value Internal value

Primary 0
Secondary 1

Source The source of the error message or event.

Threshold The number of minutes allowed to elapse between backup or restore operations before an
alert is generated.

Threshold Exceeded Indicates whether the threshold is exceeded or not. The format is an integer. The
following values are valid:

External value Internal value

No 0
Yes 1

Chapter 4. Attributes reference 165

MS SQL Log Shipping Errors attributes
The MS SQL Log Shipping Errors attribute group provides detailed information about log shipping
errors.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Agent Type The type of log shipping job. The following values are also valid:

External value Internal value

Backup 0
Copy 1
Restore 2

Database ID The ID of the primary or secondary database for the log shipping configuration.

Database Name The name of the database.

Error Source The source of the error message or event.

Hub Timestamp The time when data is inserted at the hub.

Log Time The date and time at which the record is created. The format is YY/MM/DD HH:mm, where:

YY Year
MM Month
DD Day
HH Hour
mm Minute

Message The job completion message text.

Originnode The key to this table of the format serverid:hostname:MSS.

Sample Timestamp The time when data is collected.

Sequence Number An incremental number that indicates the correct order of information for errors that
span multiple records.

Server The name of the SQL Server.

MS SQL Log Shipping Jobs Detail attributes

The MS SQL Log Shipping Jobs Detail attribute group provides detailed information about log shipping
jobs.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Agent Type The type of log shipping job. The format is an integer. The following values are also valid:

External value Internal value

Backup 0

166 Microsoft SQL Server agent: User’s Guide

External value Internal value
Copy 1
Restore 2

Database ID The ID of the primary or secondary database for the log shipping configuration.

Note: For jobs that do not have an associated database, the value for the Database ID attribute is
displayed as -1.

Database Name The name of the database.

Hub Timestamp The time when data is inserted at the hub.

Job Name The log shipping job name.

Job Status The status of the session. The following values are also valid:

External value Internal value

Starting 0
Running 1
Success 2
Error 3
Warning 4

Log Time The date and time at which the record is created. The format is YY/MM/DD HH:mm, where:

YY Year
MM Month
DD Day
HH Hour
mm Minute

Message The job completion message text.

Originnode The key to this table of the format serverid:hostname:MSS.

Sample Timestamp The time when data is collected.

Server The name of the SQL Server.

Session ID The primary ID for backup or the secondary ID for copy or restore.

MS SQL Memory Manager attributes

The MS SQL Memory Manager attribute group provides information about the memory usage.

Connection Memory The total amount of dynamic memory the server is using for maintaining
connections in megabytes. The format is an integer. The following values are also valid:

Chapter 4. Attributes reference 167

External value Internal value
Not Collected -1

Granted Workspace Memory The total amount of memory granted to running processes. This memory is
used for the hash, sort, and create index operations in megabytes. The format is an integer. The following
values are also valid:

External value Internal value

Not Collected -1

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Lock Blocks The current number of lock blocks that are in use on the server. Refreshed periodically. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Lock Blocks Allocated The current number of allocated lock blocks. The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1

Lock Memory The total amount of dynamic memory the server is using for locks in megabytes. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Lock Owner Blocks The number of lock owner blocks that are in use on the server. The blocks are
refreshed periodically. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Lock Owner Blocks Allocated The current number of allocated lock owner blocks. The format is an
integer. The following values are also valid:

External value Internal value

Not Collected -1

168 Microsoft SQL Server agent: User’s Guide

Maximum Workspace Memory The total amount of memory granted to running processes. This memory
is used primarily for the hash, sort, and create index operations in megabytes. The format is an integer.
The following values are also valid:

External value Internal value

Not Collected -1

Memory Grants Outstanding The current number of processes that have successfully acquired a
workspace memory. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Memory Grants Pending The current number of processes waiting for a workspace memory grant. The
format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Optimizer Memory The total amount of dynamic memory the server is using for query optimization in
megabytes. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Originnode The key to this table of the format serverid:hostname:MSS.

Sample Timestamp The time when data is collected.

Server The name of the SQL Server.

SQL Cache Memory The total amount of dynamic memory the server is using for the dynamic SQL
cache in megabytes. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Target Server Memory The total amount of dynamic memory the server is willing to consume in
megabytes. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Total Server Memory The total amount of dynamic memory the server is currently consuming in
megabytes. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Chapter 4. Attributes reference 169

MS SQL Problem Detail attributes
The MS SQL Problem Detail attribute group contains attributes that you can use to display detailed
information about a selected error.

Error ID The ID of the error message. The value format is an integer; for example, 2520. The unnumbered
errors with text explanations are written to the SQL server message logs.

Error SPID The ID of the session on which the event occurred. This attribute is not available for use in
situations. Otherwise, this attribute is available to use like any other attribute, for example it is available
for reports, queries, and workspaces.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Message Age The number of minutes that have elapsed since the error occurred. The value format is an
integer; for example, 2. Monitor this value to track current messages.

Message Issuer The source of the error message. The value format is an alphanumeric string with a
maximum of 8 characters; for example, JSMITH.

Message Text The message text. This attribute is not available for use in situations. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces.

Message Text (Unicode) The message text. This attribute is not available for use in situations. Otherwise,
this attribute is available to use like any other attribute, for example it is available for reports, queries,
and workspaces.

Message Timestamp The timestamp that indicates the date and time the error occurred. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

170 Microsoft SQL Server agent: User’s Guide

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR.

Severity Level Indicates the severity level of the error.

SQL State Code The SQL state value for the error message. The value format is an integer; for example,
37.

MS SQL Problem Summary attributes

The MS SQL Problem Summary attribute group contains attributes that you can use to monitor summary
information about SQL server errors.

Age of Last Error The number of minutes that have elapsed since the last error message occurred. The
value format is an integer; for example, 2.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data that IBM Tivoli
Monitoring for Microsoft SQL Server collects about each SQL server. New data becomes available if a
new interval has occurred and data has been refreshed at the CMS hub.

Error Log Size The number of bytes in the error log file. The value format is an integer; for example,
50000.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Maximum Sev Current Interval The error message of the highest severity level encountered during the
current interval. The value format is an integer in the range 10 through 24; for example, 19.

Maximum Sev Level The level of highest severity encountered since the SQL server started. The value
format is an integer in the range 10 through 24; for example, 22.

Maximum Sev Timestamp The timestamp that indicates the date and time the error message with the
highest severity level occurred. The format is MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year

Chapter 4. Attributes reference 171

HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Total Error Messages The number of error messages that have occurred since the SQL server was started.
The value format is an integer; for example, 3.

Total Errors Current Interval The number of error messages that occurred during the current interval.
The value format is an integer; for example, 1.

Total Errors High Sev The number of error messages with a severity level of 17 or higher that have
occurred since the SQL server was started. The value format is an integer; for example, 2.

Total Errors Other The number of error messages with a severity level of less than 17 that have occurred
since the SQL server was started. The value format is an integer; for example, 3.

MS SQL Process Detail attributes

The MS SQL Process Detail attribute group contains attributes that you can use to monitor detailed
information about a selected SQL server process.

Blocking Process ID The identifier for the process that is blocking a request for a lock. The value format
is an alphanumeric string with a maximum of 8 characters; for example, 12. Some blocking processes can
become stranded. Investigate situations in which a process is being blocked for an extended period of
time. For more information on a blocking process, query the sysprocesses and use the sp-lock procedure.
The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

172 Microsoft SQL Server agent: User’s Guide

Client Group ID The group ID of the user executing the process. This value does not apply to Microsoft
SQL Server version 7. The value format is an alphanumeric string with a maximum of 8 characters; for
example, ACCT_1. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Client Host Name The name of the host for the client. The value format is an alphanumeric string with a
maximum of 16 characters; for example, Rocket. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Client Process ID The ID the client assigned to the process. The value format is an alphanumeric string
with a maximum of 16 characters; for example, amc_2236. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Client User ID The ID of the user executing the process. The value format is an alphanumeric string with
a maximum of 8 characters; for example, J_Kelly. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Command The name of the command being executed by the process. The value format is an
alphanumeric string with a maximum of 16 characters; for example, CREATE VIEW. The following value
is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Command (Unicode) The name of the executing command. The value format is an alphanumeric string
with a maximum of 48 bytes. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Current CPU Percent Used Relative percent of the CPU used by this SQL Server process compared to all
other SQL Server processes. The value format is a percentage with two decimal places allowed; for
example, 80.00. This dynamic information is from the sysprocesses table. Set alerts for processes using an
abnormal amount of CPU, relative to all other SQL Server processes. The following value is valid:

External Value Internal Value Description

Not Collected -1 The value could not be collected.

Database Name The name of the database. The value format is an alphanumeric string with a maximum
of 30 characters; for example, KOQ3. Each database name is unique. The SQL server also assigns each
database its own identification number. The following value is valid:

Chapter 4. Attributes reference 173

External Value Internal Value Description
Not Collected nodata The value could not be collected.

Database Name (Unicode) The database name. The value format is an alphanumeric string with a
maximum of 384 bytes. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Duration How long, in seconds, the process has been running. The following value is valid:

External Value Internal Value Description

Not Collected -1 The value could not be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Login Name ID used by the process to log into the SQL Server. The value format is an alphanumeric
string with a maximum of 30 characters. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

NT User User name associated with the process. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

OS Process ID The Microsoft Windows thread ID. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Process ID The ID of the process. The value format is an alphanumeric string with a maximum of 10
characters; for example, 42168. The following value is valid:

External Value Internal Value Description

Not Collected -1 The value could not be collected.

174 Microsoft SQL Server agent: User’s Guide

Process Status Indicates the status of the process. The following values are valid:

Value Description
Alarm sleep Process is waiting for an alarm.
Background Process is a Microsoft SQL Server process.
Bad status Process has errors.
Infected Process is infected.
Lock sleep Process is waiting for a lock to be released.
Log suspend Process is suspended by the log transaction.
Recv sleep Process is waiting for a network read.
Runnable Process is in the queue.
Running Process is running.
Sleeping Process is sleeping.
Stopped Process is stopped.
Send sleep Process is waiting on a network send.
Dormant Process is resetting.
Not Collected The value could not be collected.

Program Name The name of the program (front-end module) for the process. The value format is an
alphanumeric string with a maximum of 16 characters; for example, ISQL. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Program Name (Unicode) The Program Name. The value format is an alphanumeric string with a
maximum of 384 bytes. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Chapter 4. Attributes reference 175

Server User ID The SQL server-assigned ID for the user executing the process. The value format is an
alphanumeric string with a maximum of 8 characters; for example, S. The following value is valid:

External Value Internal Value Description

Not Collected nodata The value could not be collected.

Total CPU Time The amount of CPU time, in seconds, the process has used on the host since the process
started. The value format is an integer; for example, 60. This value is based on the statistics collected by
the SQL server. Use this value to check for processes that use abnormal amounts of CPU time. The
following value is valid:

External Value Internal Value Description

Not Collected -1 The value could not be collected.

Total Disk IO The number of accesses to hard disk since the process started. The value includes accesses
to hard disk for physical reads and physical writes. The value format is an integer; for example, 10. The
following value is valid:

External Value Internal Value Description

Not Collected -1 The value could not be collected.

Total Memory Alloc KB The number of KB allocated for this process, based on the number of pages in
the procedure cache. A negative number indicates that the process is freeing memory allocated by another
process. The following value is valid:

External Value Internal Value Description

Not Collected -1 The value could not be collected.

MS SQL Process Summary attributes

The MS SQL Process Summary attribute group contains attributes that you can use to monitor summary
information about processes.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data that IBM Tivoli
Monitoring for Microsoft SQL Server collects about each SQL server. New data becomes available if a
new interval has occurred and data has been refreshed at the CMS hub.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

176 Microsoft SQL Server agent: User’s Guide

Percent Processes Bad The percentage of processes with a status of bad. The value format is a percentage
with two decimal places allowed; for example, 2.00. This value is based on information from the
sysprocesses table. Bad processes are often associated with a process ID problem.

Percent Processes Blocked The percentage of processes that are being blocked. The value format is a
percentage with two decimal places allowed; for example, 4.00. This value is based on information from
the sysprocesses table. The value includes all processes currently in a waiting state.

Percent Processes Infected The percentage of processes with a status of infected. The value format is a
percentage with two decimal places allowed; for example, 2.00. This value is based on information from
the sysprocesses table. An infected process is associated with a serious error condition.

Percent Processes Locksleep The percentage of processes with a status of locksleep. The value format is a
percentage with two decimal places allowed; for example, 10.00. This value is based on information from
the sysprocesses table. The processes are waiting to obtain locks on resources.

Percent Processes Othersleep The percentage of processes with a status of alarm sleep, recv sleep, send
sleep, or sleeping. The value format is a percentage with two decimal places allowed; for example, 10.00.

Percent Processes Sleeping The percentage of processes with a status of sleep. The value format is a
percentage with two decimal places allowed; for example, 20.00. This value is based on information from
the sysprocesses table.

Percent Processes Stopped The percentage of processes with a status of stopped. The value format is a
percentage with two decimal places allowed; for example, 2.00. This value is based on information from
the sysprocesses table.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Server CPU Percent Application The percentage of CPU time the SQL server application processes are
using on the host. The value format is a percentage with two decimal places allowed; for example, 20.00.

Server CPU Percent System The percentage of CPU time the SQL server processes are using on the host.
The value format is a percentage with two decimal places allowed; for example, 25.00.

Total Log Suspend The number of processes with a status of log suspend. A process with a status of log
suspend is a process that cannot complete until there is free space in the transaction log. The value
format is an integer; for example, 1.

Chapter 4. Attributes reference 177

Total Other Sleep The number of processes with a status of othersleep. The value format is an integer;
for example, 2.

Total Processes The number of processes. The value includes background processes, processes for
applications, and user processes. The value format is an integer; for example, 50. This value includes
background processes, processes for applications, and user processes.

Total Processes Bad The number of processes with a status of bad. The value format is an integer; for
example, 1.

Total Processes Blocked The number of processes that are being blocked. The value format is an integer;
for example, 2.

Total Processes Infected The number of processes with a status of infected. A process with a status of
infected is a process that cannot be completed. The value format is an integer; for example, 1.

Total Processes Locksleep The number of processes with a status of locksleep. A process with a status of
locksleep is a process waiting for a lock on a resource to be released. The value format is an integer; for
example, 5.

Total Processes Stopped The number of processes with a status of stopped. The value format is an
integer; for example, 1.

MS SQL Remote Servers attributes

The MS SQL Remote Servers attribute group contains attributes that you can use to monitor summary
information about remote SQL servers.

Connection Level The connection level for the remote SQL server. The value format is an integer; for
example, 3. If the SQL server is not a Microsoft SQL Server Secure SQL server, the value is 0.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data that IBM Tivoli
Monitoring for Microsoft SQL Server collects about each SQL server. New data becomes available if a
new interval has occurred and data has been refreshed at the CMS hub. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Network Name The name of the network for the remote SQL server. The value format is an
alphanumeric string with a maximum of 16 characters; for example, REM_NET.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

178 Microsoft SQL Server agent: User’s Guide

Remote Server ID The ID of the remote SQL server. The value format is an alphanumeric string with a
maximum of 12 characters; for example, SERV_ID.

Remote Server Name The name of the remote SQL server. The value format is an alphanumeric string
with a maximum of 12 characters; for example, REM_SVR5.

Remote Server Status The status of the remote SQL server. The server status is displayed as Unknown
when the collector process of the SQL Server agent is not running. The server status is displayed as
Inactive when the collector process of the SQL Server agent is running, but the SQL Server is not
responding to the request. The following values are valid:

External value Internal value Description

Active Active SQL server is active.
Inactive Inactive SQL server status is inactive.
Unknown Unknown SQL server status is unknown.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

MS SQL Resource Pool Stats attributes

The MS SQL Resource Pool Stats attribute group provides statistics associated with resource pools.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Active Memory™ Grant Amount The total amount of granted memory in megabytes in the resource pool.
The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Active Memory Grants Count The count of memory grants that are assigned to pool workers. The
format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Chapter 4. Attributes reference 179

Cache Memory Target The current memory target for cache memory in megabytes. The format is an
integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Compile Memory Target The current memory target for compile memory in megabytes. The format is an
integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

CPU Control Effect Percent The effect of the resource governor on the resource pool calculated as (CPU
Usage Percent)/(CPU Usage Percent without RG). The format is an integer. The following values are also
valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

CPU Usage Percent The system CPU Usage by all requests in the specified instance of the performance
object. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

CPU Usage Target Percent The target value of CPU Usage Percent for the resource pool based on the
configuration settings and the system load. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Max Memory The maximum amount of memory in megabytes the resource pool can have based on the
settings and the server state. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Memory Grant Timeouts Per Sec The number of query memory grant timeouts per second occurring in
the resource pool. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

180 Microsoft SQL Server agent: User’s Guide

Memory Grants Per Sec The number of query memory grants per second occurring in the resource pool.
The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key to this table of the format serverid:hostname:MSS.

Pending Memory Grants Count The number of queries waiting for memory grants in the resource pool.
The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Query Exec Memory Target The current memory target for query execution in megabytes. The format is
an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Resource Pool Name The resource governor resource pool name. The following values are valid:

External value Internal value Description

No Data nodata The value could not be collected.

Sample Timestamp The time when data is collected.

Server The name of the SQL Server.

Target Memory The target amount of memory in megabytes the resource pool tries to attain based on the
settings and the server state. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Used Memory The used amount of memory in megabytes in the resource pool. The format is an integer.
The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

MS SQL Running Queries Details attributes

The MS SQL Running Queries Details attribute group contains attributes that provide information about
the queries that are currently running on the SQL Server.

Blocking Session ID The ID of the session that is currently blocking the execution of a query on the SQL
Server. The following value is valid:

Chapter 4. Attributes reference 181

External value Internal value Description
Not Collected -1 The value cannot be collected.

Client Host Name The name of the client workstation that is associated with the SQL query that is
currently running on the SQL Server. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Command Type The type of command that is currently being processed by the SQL Server. The following
value is valid:

External value Internal value Description

No Data nodata No data is collected.

CPU Time (Sec) The CPU time (in seconds) of the SQL query that is currently running on the SQL
Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Database Name (Unicode) The name of the database against which the SQL query is currently running
on the SQL Server. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Granted Query Memory The number of pages that are currently allocated to the execution of a query.
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Hub Timestamp The time when data is inserted at the hub.

Login Name The name that is used to log on to the SQL Server on which the query is currently running.
The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Originnode The key for the table view in the format serverid:hostname:MSS.

Percent Work Complete The percentage of completed work for the database command that is currently
running. The name of the command that is currently running is displayed in the Command Type
attribute. The following list displays the database commands:
v ALTER INDEX REORGANIZE
v AUTO_SHRINK option with ALTER DATABASE

182 Microsoft SQL Server agent: User’s Guide

v BACKUP DATABASE
v DBCC CHECKDB
v DBCC CHECKFILEGROUP
v DBCC CHECKTABLE
v DBCC INDEXDEFRAG
v DBCC SHRINKDATABASE
v DBCC SHRINKFILE
v RECOVERY
v RESTORE DATABASE
v ROLLBACK
v TDE ENCRYPTION
The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Program Name The name of the client program that initiated the request, which is currently running on
the SQL Server. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Query Start Time The time when the query arrived on the SQL Server. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

The format is MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL Server on
Friday, January 25, 2002 at 8:00 a.m.

Query Status The status of the SQL query that is currently running on the SQL Server. The following
values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Background 1 The query is running at the background.
Running 2 The query is currently running.
Runnable 3 The query can be run.
Sleeping 4 The query is currently inactive.

Chapter 4. Attributes reference 183

External value Internal value Description
Suspended 5 The query is currently suspended.

Query Reads The number of query read operations completed by the SQL query that is currently
running on the SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Query Writes The number of query write operations completed by the SQL query that is currently
running on the SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Row Count The number of rows returned to the client by the SQL query that is currently running on the
SQL Server. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Running Query Text The SQL text of the query that is currently running on the SQL Server. The value
format is an alphanumeric string with a maximum of 2048 characters. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Server The name of the SQL Server.

Session ID The session ID of the query that is currently running on the SQL Server. The following value
is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

SQL Handle The SQL handle of the query that is currently running on the SQL Server. The following
value is valid:

External value Internal value Description

No Data nodata No data is collected.

Total Elapsed Time (Sec) The total time (in seconds) that has elapsed since the SQL query arrived on the
SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

184 Microsoft SQL Server agent: User’s Guide

MS SQL Service Broker Activation attributes
The MS SQL Service Broker Activation attribute group monitors the details of the Service Broker
activation for each database in an SQL Server instance.

Total Tasks Started The total number of activated tasks that are currently started. The following value is
valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Database Name (Unicode) The name of the database in the Unicode format.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, this
attribute is available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Server The name of the SQL Server. The value is an alphanumeric string with a maximum of 30
characters.

Stored Procedure Invoked Per Sec The number of stored procedures that are currently called per second.

External value Internal value Description

Not Collected -1 The value could not be collected.

Task Limit Reached Per Sec The number of times that the task limit that is currently activated for a
queue has been reached per second.

External value Internal value Description

Not Collected -1 The value could not be collected.

Tasks Aborted Per Sec The number of activated tasks that are currently ended per second. The following
value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Tasks Started Per Sec The number of activated tasks that are currently being started per second. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Task Limit Reached The number of times that the task limit that is currently activated for a queue
has been reached. The following value is valid:

Chapter 4. Attributes reference 185

External value Internal value Description
Not Collected -1 The value could not be collected.

MS SQL Service Broker Statistics attributes

The MS SQL Service Broker Statistics attribute group displays the summary of the Service Broker
statistics.

Broker Transaction Rollbacks The current number of transactions related to the Service Broker that have
been rolled back. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Enqueued Local Messages Per Sec The number of messages per second from local endpoints that are
currently being delivered into the queues. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Enqueued Transport Messages Per Sec The number of messages from the transport that are being
delivered into the queues per second. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Enqueued Messages Per Sec The number of messages from local endpoints and the transport that are
currently delivered into the queues per second.

Forwarded Messages Discarded Per Sec The number of forwarded messages that are currently discarded
per second because of memory limits for forwarded messages, age limits, and so on. The following value
is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Forwarded Pending Messages The number of forwarded messages that are currently in the queue, and
that are not yet sent.

External value Internal value Description

Not Collected -1 The value could not be collected.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, this
attribute is available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

186 Microsoft SQL Server agent: User’s Guide

Server The name of the SQL Server. The value is an alphanumeric string with a maximum of 30
characters.

SQL Receives Per Sec The number of SQL RECEIVE commands that are processed per second by the
Service Broker. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

SQL Sends Per Sec The number of SQL SEND commands that are processed per second by the Service
Broker. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Enqueued Local Messages The total number of message fragments from the local endpoints that
are currently being delivered into the queues. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Enqueued Messages The total number of message fragments from the local endpoints and the
transport that are currently being delivered into the queues. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Enqueued Transport Messages The total number of messages from the transport that are currently
delivered into the queues. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Forwarded Messages The total number of forwarded messages from the local endpoints and the
transport that are currently being sent. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Forwarded Messages Discarded The total number of forwarded messages that are currently
discarded because of memory limits for forwarded messages, age limits, and so on. The following value
is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total SQL Receives The total number of SQL RECEIVE commands that are currently processed by the
Service Broker. The following value is valid:

Chapter 4. Attributes reference 187

External value Internal value Description
Not Collected -1 The value could not be collected.

Total SQL Sends The total number of SQL SEND commands that are currently processed by the Service
Broker. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

MS SQL Service Broker Transport attributes

The MS SQL Service Broker Transport attribute group monitors the details of the Service Broker transport
for the SQL Server.

Average Size Message Fragments Received The average byte size of the message fragments that are
received by the transport receive I/O operations. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Average Size Message Fragments Sent The average byte size of the message fragments that are sent by
the transport send I/O operations. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Current Message Fragments for Send I/O The number of message fragments that are to be read by the
transport send I/O operations that are currently running. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Current Bytes for Receive I/O The number of bytes that are to be read by the transport receive I/O
operations that are currently running. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Current Bytes for Send I/O The number of buffer bytes that are to be read by the transport send I/O
operations that are currently running. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, this
attribute is available for reports, queries, and workspaces.

188 Microsoft SQL Server agent: User’s Guide

Message Fragment Received Per Sec The number of message fragments that are currently received per
second in the transport receive I/O operations. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Message Fragments Sent Per Sec The number of message fragments that are currently sent per second in
the transport send I/O operations. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Pending Bytes For Receive I/O The number of bytes that are currently present in the completed
transport receive I/O operations whose message fragments are not yet sent to the queue, or are not yet
discarded. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Pending Bytes for Send I/O The current number of buffer bytes of the message fragments that are being
sent to the queue, and that are ready to be sent by the transport send I/O operations. The following
value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Pending Message Fragments for Receive I/O The current number of message fragments that are received
by transport receive I/O operations, and that are not yet sent to the queue or are not yet discarded. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Pending Message Fragments for Send I/O The current number of message fragments that are being sent
to the queue, and that are ready to be sent through the transport layer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Receive I/Os Per Sec The current number of transport receive I/O operations per second. A transport
receive I/O might contain more than one message fragment. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Chapter 4. Attributes reference 189

Send I/Os Per Sec The current number of transport send I/O operations per second. A transport send
I/O operation might contain more than one message fragment. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Server The name of the SQL Server. The value is an alphanumeric string with a maximum of 30
characters.

Total Open Connection Count The total number of transport connections that are currently open. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

MS SQL Services Detail attributes

The MS SQL Services Detail attribute group provides details about the services that make up the SQL
Server.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL Server.

Service Name The service name for the SQL Server.

Service State Current service state. The following values are also valid:

190 Microsoft SQL Server agent: User’s Guide

External value Internal value
Stopped 0
Start Pending 1
Stop Pending 2
Running 3
Continue Pending 4
Pause Pending 5
Paused 6
Unknown -1

Service Start Mode Defined start mode for the service. The following values are also valid:

External value Internal value

Automatic 1
Manual 2
Disabled 3
Unknown -1

Service Status Current service status. The following values are also valid:

External value Internal value

OK 0
Error 1
Degraded 2
Unknown 3
Pred Fail 4
Starting 5
Stopping 6
Service 7

Service Type The service type for this service to the Microsoft SQL Server. The following values are also
valid:

External value Internal value

SQLServer 1
SQLAgent 2
DTC 3
Analysis_OLAP 4
Search 5
ADHelper 6
Browser 7
DTS 8
SQLWriter 9

Chapter 4. Attributes reference 191

External value Internal value
Report 10
Distributed Replay Controller 11
Distributed Replay Client 12
Unknown -1

MS SQL Server Detail attributes

The MS SQL Server Detail attribute group contains attributes that you can use to monitor detailed
information about a selected SQL server.

Current Locks The number of current locks for the SQL server. The value format is an integer; for
example, 73.

Data Cache Size The number of kilobytes (KB) allocated for the data cache memory. The SQL server uses
the data cache to store data and index pages. The value format is an integer; for example, 1000. The cache
is sometimes referred to as the buffer cache.

Error Log Name The name of the file that contains the error log for the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, SQL_Error_Log. The error log
tracks fatal and kernel errors. It also contains startup and system information. Check the error log for
message content and details. This attribute is not available for use in situations. Otherwise, this attribute
is available to use like any other attribute, for example it is available for reports, queries, and workspaces.

Error Log Name (Unicode) The name of the file that contains the error log for the SQL server (Unicode).
Valid values include text strings with a maximum of 392 characters. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Error Log Size The number of bytes in the error log file. The value format is an integer; for example,
50000. The error log contains the fatal error and kernel error messages issued by the SQL server.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Max Locks Allowed The maximum number of allowable locks. The value format is an integer; for
example, 2000. This value is a configuration parameter.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

OS Type The operating system for the SQL server. The value format is an alphanumeric string; for
example, AIX. The following values are valid:

External value Internal value Description

No Data nodata No data is collected.

192 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Windows Srv 2008 Win2008 The operating system is Windows Server
2008.
Windows Srv 2003 Win2003 The operating system is Windows Server
2003.
Windows Srv 2000 Win2000 The operating system is Windows Server
2000.
Windows NT WinNT The operating system is Windows NT.
Windows Srv 2012 Win2012 The operating system is Windows Server
2012.
Windows Srv 2008 R2 Win8R2 The operating system is Windows Server
2008 R2.

OS Version The version of the operating system for the SQL server. The value format is the version in
the format version.release; for example, 2.5.

Percent Max Locks The percentage of locks on resources of the maximum number of locks allowed by
the SQL server. The value format is a percentage with two decimal places allowed; for example, 10.00.
Setting a higher limit for the maximum number of locks does not impair performance. If your operations
exceed the number of available locks, you can increase this limit.

Procedure Buffers Percent Active The percentage of slots with a procedure that is currently executing.
Use this attribute to see how much of the cache these procedures use in relation to the cache size as a
whole. The value format is an integer.

Procedure Buffers Percent Used The percentage of slots that have a procedure in them. A procedure
buffer is considered used when it is associated with a procedure cache entry. A used procedure buffer can
be active or not active. Use this attribute to see how much of the cache is being used by currently
compiled procedures in relation to the cache size as a whole. The value format is an integer.

Procedure Buffers Total The number of procedure buffers that are in the procedure cache. This number is
a fixed number based on the procedure cache that is allocated. Use this attribute to see how much of the
cache currently executing procedures use in relation to the cache size as a whole. The value format is an
integer.

Procedure Cache Pages The number of pages that are allocated for the procedure cache. The SQL server
uses the procedure cache to compile queries and store procedures that are compiled. The value format is
an integer; for example 1000.

Procedure Cache Percent The percentage of cache memory the SQL server uses for the procedure cache.
This value does not apply to Microsoft SQL Server version 7. The value format is a percentage with two
decimal places allowed; for example, 20.00.

Note: This attribute is deprecated from the SQL Server agent V6.2.1.1.

Procedure Cache Percent Active The total size of the procedure cache in pages. The size of the procedure
cache can fluctuate depending on the activity of other database server processes that might require
procedure cache slots, such as query plans. Use the attribute to see the current size of the procedure
cache. The value format is an integer.

Procedure Cache Percent Used The percentage of the procedure cache that has procedures in it. Use this
attribute to see how much of the cache currently executing procedures use in relation to the cache size as
a whole. The value format is an integer.

Chapter 4. Attributes reference 193

Procedure Cache Size The number of kilobytes (KB) that are allocated for the procedure cache. The SQL
server uses the procedure cache to compile queries and store procedures that are compiled. The value
format is an integer; for example 1000.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Server Status Indicates the status of the SQL server. The server status is displayed as Unknown when the
collector process of the SQL Server agent is not running. The server status is displayed as Inactive when
the collector process of the SQL Server agent is running, but the SQL Server is not responding to the
request. The following values are valid:

External value Internal value Description

Active Active or 1 SQL server is active.
Inactive Inactive SQL server status is inactive.
Unknown Unknown or 0 SQL server status is unknown.

Server Type The type of SQL server. The value format is an alphanumeric string; for example, SQL
Server.

Server Version The version of the SQL Server. The value format is the version in the format w.x.y.z; for
example, 10.0.2531.0.

Server Version (Superceded) The version of the SQL Server. The value format is the version in the format
x.y.z; for example, 10.0.253.

Note: For the complete version of the SQL Server, see the Server Version attribute.

Startup Timestamp The timestamp that indicates the date and time the SQL server was started. The
format is YYY/MM/DD HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

194 Microsoft SQL Server agent: User’s Guide

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Time Since Startup The number of minutes that have elapsed since the SQL server was started. The
value format is an integer; for example, 360.

MS SQL Server Properties attributes

The MS SQL Server Properties attribute group contains attributes that you can use to monitor the
properties of the SQL Server.

Collation The name of the default collation for the server. The value format is a string. The following
value is valid:

External value Internal value Description

Not Collected Not_collected The value could not be collected.

Collation ID The identification number of this SQL Server collation. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Edition The installed product edition of this instance of the SQL Server. The following value is valid:

External value Internal value Description

Not Collected Not_collected The value could not be collected.

Edition ID The identification number that represents the installed product edition of this instance of the
SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Engine Edition The database engine edition of the instance of the SQL Server that is currently installed.
The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

FileStream Level The current level of FileStream support that is enabled for the SQL Server instance. The
following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Not Applicable -2 The value is not supported.
Disabled 1 FileStream support is disabled.
Transactional Access 2 FileStream support is enabled for
transactional access.
Local Full Access 3 FileStream support is enabled only for
local full access.

Chapter 4. Attributes reference 195

External value Internal value Description
Local and Remote Full Access 4 FileStream support is enabled for local and
remote full access.

FileStream Share Name The Windows share name where the FileStream data is stored. The value format
is an alphanumeric string. The following values are valid:

External value Internal value Description

Not Collected Not_collected The value could not be collected.
Not Applicable Not_applicable The value is not supported.

HADR Manager Status Indicates whether the HADR manager for the AlwaysOn availability group has
started. The value format is an integer. The following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Not Applicable -2 The value is not supported.
No Data -3 No data is collected.
Communication Pending 1 The communication with the HADR
manager is pending, and the HADR
manager has not started.
Running 1 The HADR manager is running.
Failed 2 The HADR manager has failed.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, this
attribute is available for reports, queries, and workspaces.

Is Clustered Indicates whether the SQL Server instance is configured in the Windows Server Failover
Clustering (WSFC) cluster. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
No 1 The SQL Server instance is not configured
in a failover cluster.
Yes 2 The SQL Server instance is configured in a
failover cluster.

Is HADR Enabled Indicates whether the AlwaysOn Availability Group feature is enabled on the SQL
Server instance. The value format is an integer. The following values are valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
No Applicable -2 The attribute is not supported.
No Data -3 No data is collected.
No 1 The AlwaysOn Availability Group feature
is not enabled on the SQL Server instance.

196 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Yes 2 The AlwaysOn Availability Group feature
is enabled on the SQL Server instance.

Is Integrated Security Only The server is in the integrated security mode. The value format is an integer.
The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
No 1 The SQL Server is not in the integrated
security mode.
Yes 2 The SQL Server is in the integrated
security mode.

Is Single User The server is currently in the single-user mode, in which only a single user can connect to
the server. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
No 1 The SQL Server is not in the single-user
mode.
Yes 2 The SQL Server is in the single-user mode.

License Type The mode of this instance of the SQL Server. The mode can be per-seat or per-processor.
The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Num licenses The number of client licenses that are currently registered for this instance of the SQL
Server if the SQL Server is in the per-seat mode. The number of processors that are currently licensed for
this instance of the SQL Server if the SQL Server is in the per-processor mode. The following value is
valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Physical NetBIOS Name The NetBIOS name of the machine where this instance of the SQL Server is
currently running. The following value is valid:

External value Internal value Description

Not Collected Not_collected The value could not be collected.

Chapter 4. Attributes reference 197

Product Level The level of the version of this instance of the SQL Server, for example, the original release
version and the service pack version. The following value is valid:

External value Internal value Description

No Data nodata The value could not be collected.
CTP 1 The level of the version of the SQL Server
is CTP.
RTM 2 The level of the version of the SQL Server
is RTM.
SP1 3 The level of the version of the SQL Server
is SP1.
SP2 4 The level of the version of the SQL Server
is SP2.
SP3 5 The level of the version of the SQL Server
is SP3.
SP4 6 The level of the version of the SQL Server
is SP4.
SP5 7 The level of the version of the SQL Server
is SP5.
SP6 8 The level of the version of the SQL Server
is SP6.
SP7 9 The level of the version of the SQL Server
is SP7.
SP8 10 The level of the version of the SQL Server
is SP8.
SP9 11 The level of the version of the SQL Server
is SP9.
SP10 12 The level of the version of the SQL Server
is SP10.

Qualified Server Name The name of the qualified SQL Server instance in the format hostname:SQL
server instance. For the default SQL Server instance, the format is hostname. The value format is an
alphanumeric string with a maximum of 128 characters. The following value is valid:

External value Internal value Description

Not Collected Not_collected The value could not be collected.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters.

Server Version The version of the SQL Server. The value format is the version in the format w.x.y.z; for
example, 10.0.2531.0.

MS SQL Server Summary attributes

The MS SQL Server Summary attribute group contains attributes that you can use to monitor summary
information for SQL servers.

Cache Average Free Scan The average number of buffers scanned by the LazyWriter when the
LazyWriter searches the data cache for an unused buffer to replenish the free buffer pool. If Microsoft

198 Microsoft SQL Server agent: User’s Guide

SQL Server must read a large number of buffers to find a free one, server performance might degrade. A
low value indicates optimal performance. The value format is an integer.

Cache Free Buffers The current number of cache buffers in the free buffer pool. Use this attribute as an
alert when the number of buffers is getting low. A low number of free buffers might degrade server
performance. The value format is an integer. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Cache Hit Ratio The current ratio of data cache hits to total requests. Use this attribute to check the
effectiveness of the data cache. For optimal performance, the returned value must be approximately 95%
or greater. The value format is an integer.

Cache Maximum Free Page Scan The maximum value for the number of buffers scanned by the
LazyWriter when the LazyWriter searches the data cache for an unused buffer to replenish the free buffer
pool. Use this attribute to check the effectiveness of the data cache. The value format is an integer.

Checkpoint Pages per Sec The number of pages flushed to disk per second by a checkpoint or other
operation that require all dirty pages to be flushed.

Collection Status Indicates the status of the data collector on a remote node. The data collector is the part
of the product that collects information about the SQL server. The following values are also valid:

External value Internal value Description

Inactive Inactive Data collector is inactive.
Unknown Unknown Data collector is unknown.
Active Active Data collector is active.

CPU Idle Delta The difference in the CPU Idle between the current and the previous samples.

CPU Idle Sec The time (in seconds) that the SQL Server has been idle since it was last started. The value
is in seconds even though the column name would imply milliseconds.

CPU Percent Idle The percentage of time that a database server has been idle during the current
monitoring interval. Use this attribute to gauge how much of the CPU resource the database server uses
so that you can allocate resources more efficiently. Also, you can use this attribute to determine how
resource-intensive certain operations are. The value format is an integer.

CPU Usage Delta The difference in the CPU Usage between the current and the previous samples.

CPU Usage Sec The time (in seconds) that the CPU has spent working since the SQL Server was last
started. The value is in seconds even though the column name would imply milliseconds.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data that IBM Tivoli
Monitoring for Microsoft SQL Server collects about each SQL server. New data becomes available if a
new interval has occurred and data has been refreshed at the CMS hub.

Data Cache Size The number of kilobytes (KB) allocated for the data cache memory. The SQL server uses
the data cache to store data and index pages. The value format is an integer; for example, 1000. The cache
is sometimes referred to as the buffer cache.

Chapter 4. Attributes reference 199

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Lazy Writes per Sec The number of buffers written per second by the buffer manager lazy writer. The
lazy writer is a system process that flushes out batches of dirty, aged buffers and make them available to
user processes. The lazy writer eliminates the need to perform frequent checkpoints to create available
buffers.

Mixed Page Allocations Per Sec The number of pages that are allocated from mixed extents per second.
These pages can be used for storing the Index Allocation Map (IAM) pages. The first eight pages from
mixed extents are allocated to an allocation unit.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Page Life Expectancy The duration (in seconds) for which an SQL Server block or page is stored in the
memory.

Page Reads per Sec The number of physical database page reads that are issued per second. This statistic
displays the total number of physical page reads across all databases. Because physical IO is expensive,
you might be able to minimize the cost, either by using a larger data cache, intelligent indexes, and more
efficient queries, or by changing the database design.

Page Writes per Sec The number of physical database page writes issued.

Percent Max Locks The percentage of locks on resources of the maximum number of locks allowed by
the SQL server. The value format is a percentage with two decimal places allowed; for example, 10.00.
Setting a higher limit for the maximum number of locks does not impair performance. If your operations
exceed the number of available locks, you can increase this limit.

Procedure Cache Size The number of kilobytes (KB) allocated for the procedure cache. The SQL server
uses the procedure cache to compile queries and store procedures that are compiled. The value format is
an integer; for example, 1000.

Readahead Pages per Sec The number of pages read in anticipation of use.

Repl Distribution Delivered Cmds per Sec The number of distribution commands delivered per second
to the Subscriber.

Repl Distribution Delivered Trans per Sec The number of distribution transactions delivered per second
to the Subscriber.

Repl Distribution Delivery Latency The distribution latency (in MS), the time it takes for transactions to
be delivered to the Distributor and applied at the Subscriber.

Repl Logreader Delivered Cmds per Sec The number of Log Reader Agent commands delivered per
second to the Distributor.

Repl Logreader Delivered Trans per Sec The number of Log Reader Agent transactions delivered per
second to the Distributor.

200 Microsoft SQL Server agent: User’s Guide

Repl Logreader Delivery Latency The current amount of time (in MS) elapsed from when transactions
are applied at the Publisher to when they are delivered to the Distributor.

Repl Merge Conflicts per Sec The number of conflicts per second that occurred in the Publisher or
Subscriber upload and download. If the value is not zero, the value might require notifying the losing
side, overriding the conflict, and so on.

Repl Merge Downloaded Changes per Sec The number of rows merged (inserted, updated, and deleted)
per second from the Publisher to the Subscriber.

Repl Merge Uploaded Changes per Sec The number of rows merged (inserted, updated, and deleted)
per second from the Subscriber to the Publisher.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Server CPU Pct IO The percentage of time used for I/O operations during the current monitoring
interval. Use this attribute to gauge how much of the CPU resource the database server uses for I/O so
you can allocate resources more efficiently. You also can use this attribute to determine how I/O
resource-intensive certain operations are. The value format is an integer.

Server CPU Percent The percentage of CPU time the SQL server process is using on the host. The value
format is a percentage with two decimal places allowed; for example, 20.00.

Server Status Indicates the status of the SQL server. The server status is displayed as Unknown when the
collector process of the SQL Server agent is not running. The server status is displayed as Inactive when
the collector process of the SQL Server agent is running, but the SQL Server is not responding to the
request. The following values are also valid:

External value Internal value Description

Active Active or 1 SQL server is active.
Inactive Inactive SQL server status is inactive.
Unknown Unknown or 0 SQL server status is unknown.

Server Type The type of SQL server. The value format is an alphanumeric string; for example, SQL
Server.

Server Version The version of the SQL Server. The value format is the version in the format w.x.y.z; for
example, 10.0.2531.0.

Chapter 4. Attributes reference 201

Server Version (Superceded) The version of the SQL Server. The value format is the version in the format
x.y.z; for example, 10.0.253.

Note: For the complete version of the SQL Server, see the Server Version attribute.

SQLServerAgent Failed Jobs Reports any jobs run by the SQLServerAgent service that have failed in the
last monitoring interval. The first time you retrieve this attribute, it returns 0. The next time you retrieve
it, it returns the total number of SQLServerAgent failed jobs found in the system history tables since the
first run. These jobs include replication and user-defined jobs, such as maintenance or backup tasks. Use
this attribute to alert you when scheduled tasks have failed. The value format is an integer.

Stolen Pages The number of pages used for miscellaneous server purposes. The following values are
valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Stolen Pages Growth The growth of the number of stolen pages between the current sample and
previous sample. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Time Since Startup The number of minutes that have elapsed since the SQL server was started. The
value format is an integer; for example, 360.

Total Blocking Lock Requests The total number of current locks blocking other processes. A blocking
lock must be released before other processes requesting competing locks can progress. (For more
information on locks, see the Microsoft SQL Server Books online.) Use this attribute to show the number
of blocking locks active during server activity. This attribute can indicate that processes are being held up
through lock contention rather than hardware performance issues. The value format is an integer.

Total Locks Remaining The total number of locks that can still be taken out. The maximum number of
locks is configurable. In Microsoft SQL Server Version 8.0, you can have the number of locks configured
automatically. Use this attribute to show the number of locks active during server activity. The value
format is an integer.

Total OS CPU Percent The percentage of CPU time being used by all processes on the host. The value
format is a percentage with two decimal places allowed; for example, 40.00.

Total Pages The total number of stolen, free, and database pages in the buffer pool. The following values
are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.
Not Applicable -2 The value is not supported.

Total Server Memory The total amount of dynamic memory (in KB) that the server is using currently.

202 Microsoft SQL Server agent: User’s Guide

MS SQL Server Transactions Summary attributes
The MS SQL Server Transactions Summary attribute group contains attributes that you can use to
monitor the transaction summary information for SQL Servers.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, this
attribute is available for reports, queries, and workspaces.

Longest Transactions Running Time The transaction that is currently active for the longest duration of
time (in seconds). The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute. For
example, this attribute is available for reports, queries, and workspaces.

Server The name of the SQL Server. The value is an alphanumeric string with a maximum of 30
characters.

Tempdb Free Space The amount of free space (in KB) that is currently available in the tempdb database.
The value format is an integer. The following value is valid.

External value Internal value

Not Collected -1

Total Active Transactions The number of transaction enlistments (local, dtc, and bound) that are currently
active. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Non-Snapshot Version Transactions The number of currently active non-snapshot transactions that
generate version records. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Snapshot Transactions The number of snapshot transactions that are currently active. The value
format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Chapter 4. Attributes reference 203

Total Update Snapshot Transactions The number of currently active snapshot transactions that perform
update operations. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Update Conflict Ratio The percentage of snapshot transactions that currently have update conflicts. The
value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Cleanup Rate The current rate (in KB per second) at which versions are removed from the
version store. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Generation Rate The current rate (in KB per second) at which versions are generated in the
version store. The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Store Size The amount of space (in KB) that is currently available in the version store. The value
format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Store Unit Count The number of allocation units that are currently active in the version store.
The value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Store Unit Creation The number of units that are currently created in the version store. The
value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Version Store Unit Truncation The number of units that are currently truncated in the version store. The
value format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

204 Microsoft SQL Server agent: User’s Guide

MS SQL Statistics Detail attributes
The MS SQL Statistics Detail attribute group contains attributes that you can use to monitor detailed
information about SQL server statistics.

Average Value per Second The average value per second for the statistic since the SQL server was
started. The value format is a decimal with two decimal places allowed; for example, 5.00. This value
indicates the norm for the statistic during the current interval.

Current Value The value for the statistic during the current interval. The value format is an integer; for
example, 40. This is a cumulative value for the statistic.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Maximum Seen The greatest value per second for the statistic since the SQL server was started. The
value format is an integer; for example, 2000. This is a benchmark value.

Minimum Seen The smallest value per second for the statistic since the SQL server was stated. The value
format is an integer; for example, 10. This is a benchmark value.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Statistic Name The name of the statistic. The value format is an alphanumeric string with a maximum of
32 characters; for example, cpu_busy. The following values are also valid:

External value Internal value

CPU_busy cpu_busy
IO_busy io_busy
I/O_errors io errors

Chapter 4. Attributes reference 205

External value Internal value
connections connections
idle idle
packets_error packets_error
packets_received packets_received
packets_sent packets_sent
physical_reads physical reads
physical_writes physical writes

Total Since Startup The total of all the values for the statistic since the SQL server was started. The value
format is an integer; for example, 9000.

MS SQL Statistics Summary attributes

The MS SQL Statistics Summary attribute group contains attributes that you can use to monitor summary
information about SQL server statistics.

Client Count The number of client workstations currently connected to the database server. Use this
attribute as an alert when you are running out of client connections, which can result in server access
problems. This attribute is also useful for tracking client access patterns. The value format is an integer.

Client Count Percent Used The number of client workstations currently connected to the database server
and returns the ratio percentage of the number of possible connections. For example, if you have 10 client
connections and eight are currently in use, this attribute returns a value of 80%. Running out of client
connections can result in server access problems. The value format is an integer.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data the product collects
about each SQL server. New data becomes available if a new interval has occurred and data has been
refreshed at the CMS hub.

Current Logons The number of active connections (logons). The value format is an integer; for example,
50.

Disk IO Current Interval The number of times the SQL server accessed hard disk during the current
interval. The value includes access to hard disk for physical reads and physical writes. The value format
is an integer; for example, 50.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

IO ErrorsCurrent Interval The number of I/O errors that occurred when the SQL server accessed hard
disk during the current interval. The value format is an integer; for example, 5.

IO Errors Since Startup The number of I/O errors that have occurred when the SQL server accessed
hard disk since startup. The value format is an integer; for example, 2.

206 Microsoft SQL Server agent: User’s Guide

Max User Connection Allowed The maximum number of active connections (logons) allowed for the
SQL server. The value format is an integer in the range 5 through 2147483647; for example, 100. This is a
configuration value for the SQL server. To determine the number of connections that can be configured
for the SQL server, use the select @@max_connections command.

Network Read Rate The rate at which tabular data stream (TDS) packets are read from the network, in
packets per second. This statistic is an indicator of network throughput. When this statistic is high, it
indicates heavy network traffic. The value format is an integer.

Network Write Rate The rate at which tabular data stream (TDS) packets are written to the network, in
packets per second. This statistic is an indicator of network throughput. When this statistic is high, it
indicates heavy network traffic. The value format is an integer.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Percent IO Errors Current Interval The percentage of the accesses to hard disk that had errors occur
during the current interval. The value format is a percentage with two decimal places allowed; for
example, 1.00.

Percent Max Logons Active The percentage of active connections (logons) of the maximum number of
active connections allowed for the SQL server. The value format is a percentage with two decimal places
allowed; for example, 50.00.

Percent User Connections Remaining The current number of remaining user connections as a percentage
of the maximum number of available user connections for the database server. Use this attribute to gain
an overview of high and low access periods and to warn you of impending availability problems. The
value format is an integer.

Physical Reads per Second The average number of physical reads per second during the current interval.
The value format is a decimal with two decimal places allowed; for example, 5.00.

Physical Writes per Second The average number of physical writes per second during the current
interval. The value format is a decimal with two decimal places allowed; for example, 5.00.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Chapter 4. Attributes reference 207

Total Logins (Per Sec) The number of login operations that started per second in the current interval. The
value format is a decimal with two decimal places allowed; for example, 15.00. The following value is
possible:

External value Internal value Description

Not Collected -1 The value could not be collected.

Total Logons per Second The average number of active connections (logons) per second during the
current interval. The value format is a decimal with two decimal places allowed; for example, 15.00.

Total Logouts per Second Total number of logout operations started per second.

Total OS CPU Percent Busy The percentage of CPU seconds the SQL server has used during the current
interval of all the CPU seconds used since the SQL server was started. The value format is a percentage
with two decimal places allowed; for example, 20.00.

Total OS IO Percent Busy The percentage of I/O the SQL server used during the current interval of all
the I/O used since the SQL server was started. The value format is a percentage with two decimal places
allowed; for example, 25.00.

MS SQL Table Detail attributes

The MS SQL Table Detail attribute group contains attributes that you can use to monitor tables within
one or more databases.

Database ID ID number of this database. The format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Database Name The Database name. The value format is an alphanumeric string with a maximum of 30
characters. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

Fragmentation The degree of fragmentation for the table. Use this attribute to determine if fragmentation
is reaching a level that causes performance degradation. Performance degradation is due to
non-contiguous table reads that require additional extent switches. The format is an integer. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

208 Microsoft SQL Server agent: User’s Guide

Index ID The ID number of this table index. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Index Name The table index name. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

FileTable Indicates whether the current table is a FileTable. The format is an integer. The following values
are valid:

External value Internal value Description

Not Applicable -2 The value is not supported.
Not Collected -1 The value could not be collected.
No 1 The current table is not a FileTable.
Yes 2 The current table is a FileTable.

Number of Rows The number of rows that are present in a database table. The format is an integer. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Optimizer Statistics Age The time (in minutes) since statistics were updated for the table. Use this
attribute to ensure that queries base their query plans on up-to-date information. If query plans are based
on old information, they might be inefficient. The format is an integer. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Chapter 4. Attributes reference 209

Server The name of the SQL Server. The value format is an alphanumeric string with a maximum of 32
characters

Space Used (MB) The amount of space (in megabytes) used by the specified table. Use this attribute to
determine how much of the database space is used by a table. You can monitor the growth of individual
tables and compare the actual growth to the expected growth. The format is an integer. The following
value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Table ID ID number of this table. The format is an integer. The following value is also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Table Name The table name. The value format is an alphanumeric string with a maximum of 30
characters. The following value is valid:

External value Internal value Description

No Data nodata No data is collected.

MS SQL Table Summary attributes

The MS SQL Table Summary attribute group provides the summary of all the tables that are present in an
SQL Server instance. Note that empty tables are not monitored. If the table detail collection settings are
configured for the SQL Server agent, the attributes in this attribute group display the last collected value
of data.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute. For example, it is
available for reports, queries, and workspaces.

Last Collection Duration The time (in minutes) that is required to collect data of the MS SQL Table
Detail attribute group. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Last Collection Start Time The date and time when data collection of the MS SQL Table Detail attribute
group last started. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Maximum Fragmentation Percent Since Startup The highest value of fragmentation (in a percent) among
all tables since the agent was started. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

210 Microsoft SQL Server agent: User’s Guide

Maximum Optimizer Statistics Age (Min) The maximum age of the optimizer statistics in minutes
among all the tables in the current instance of the SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Maximum Table Size (MB) The maximum space in MB that is used among all the tables in the current
instance of the SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Maximum Fragmentation Percent The highest fragmentation value (in a percent) among all the tables in
the current interval. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Minimum Optimizer Statistics Age (Min) The minimum age of the optimizer statistic in minutes among
all the tables in the current instance of the SQL Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Minimum Table Size (MB) The minimum space in MB that is used among all the tables of the SQL
Server. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Minimum Fragmentation Percent The lowest value of fragmentation (in a percent) among all the tables
in the current interval. The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Server The name of the SQLServer. The value format is an alphanumeric string with a maximum of 32
characters

Total FileTables The total number of FileTables that are present in the current instance of the SQL Server.
The following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.
Not Applicable -2 The value is not supported.

Chapter 4. Attributes reference 211

Total Tables The total number of tables that are present in the current instance of the SQL Server. The
following value is valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

MS SQL Text attributes

The MS SQL Text attribute group contains attributes that you can use to monitor information about SQL
text strings associated with a selected process.

Note: For custom queries, this attribute group displays data only for the specified available process ID.

Client Host Name The host name of the client where the command was issued. The value format is an
alphanumeric string with a maximum of 16 characters.

Client Process ID The process ID assigned by the host client. The value format is an alphanumeric string
with a maximum of 16 characters.

Database Name The name of the database. The value format is an alphanumeric string with a maximum
of 30 characters; for example, KOQ3. Each database name is unique. The SQL server also assigns each
database its own identification number.

Database Name (Unicode) The Database name. Valid values include text strings with a maximum of 384
bytes.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces.

Process ID The ID of the process that is requesting or holding the lock on the resource. The value format
is an alphanumeric string with a maximum of 10 characters; for example, 42168.

Process Status Indicates the status of the process. The following values are also valid:

Value Description
Alarm sleep Process is waiting for an alarm.
Background Process is a Microsoft SQL Server process.
Bad status Process has errors.
Infected Process is infected.
Lock sleep Process is waiting for a lock to be released.
Log suspend Process is suspended by the log transaction.
Recv sleep Process is waiting for a network read.
Runnable Process is in the queue.

212 Microsoft SQL Server agent: User’s Guide

Value Description
Running Process is running.
Sleeping Process is sleeping.
Stopped Process is stopped.
Send sleep Process is waiting on a network send.
Dormant Process is resetting.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5.

Text The SQL text for the process. The value format is an alphanumeric string with a maximum of 255
characters.

Text (Unicode) The SQL text for the process.

Total CPU Time The amount of CPU time, in seconds, the process has used on the host since the process
started. The value format is an integer; for example, 60. This value is based on the statistics collected by
the SQL server. Use this value to check for processes that use abnormal amounts of CPU time.

MS SQL Workload Group Stats attributes

The MS SQL Workload Group Stats attribute group provides statistics associated with workload groups.

Note: This attribute group is not supported on the SQL Server 2005 and 2008 Express Edition.

Active Parallel Threads The number of threads used by parallel queries in the workload group. Serial
queries and the main thread of parallel queries are not included in this number. The format is an integer.
The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Active Requests The number of requests currently running in the workload group. The format is an
integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Chapter 4. Attributes reference 213

Blocked Tasks The number of blocked tasks in the workload group. The format is an integer. The
following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

CPU Usage Percent The system CPU usage by all requests in the specified instance of the performance
object. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when data is inserted at the hub.

Max Requests CPU Time The maximum requests for CPU time in milliseconds. The format is an integer.
The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Max Requests Memory Grant The maximum value of memory grant in megabytes used by a query in
the workload group. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Originnode The key to this table of the format serverid:hostname:MSS.

Query Optimization Per Sec The number of query optimizations per second occurring in the workload
group. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Queued Requests The number of requests waiting in the queue due to resource governor limits in the
workload group. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Reduced Memory Grants Per Sec The number of queries reduced per second from the memory in the
workload group. The format is an integer. The following values are also valid:

214 Microsoft SQL Server agent: User’s Guide

External value Internal value Description
Not Collected -1 The value could not be collected.

Requests Completed Per Sec The number of completed requests per second in the workload group. The
format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Sample Timestamp The time when data is collected. The format is an integer. The following values are
also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Server The name of the SQL Server.

Suboptimal Plans Per Sec The number of suboptimal query plans generated per second in the workload
group. The format is an integer. The following values are also valid:

External value Internal value Description

Not Collected -1 The value could not be collected.

Workload Group Name The name of the workload group. The following values are valid:

External value Internal value Description

No Data nodata The value could not be collected.

VMS SQL Remote Servers attributes

The VMS SQL Remote Servers attribute group contains attributes that you can use to monitor summary
information about remote SQL servers.

Connection Level The connection level for the remote SQL server. The value format is an integer; for
example, 3. If the SQL server is not a Microsoft SQL Server Secure SQL server, the value is 0. This
attribute is not available for use in situations. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Remote Servers attribute group.

Current Interval The number of seconds that have elapsed between the previous sample and the current
sample. The value format is an integer; for example, 90. A sample contains the data that IBM Tivoli
Monitoring for Microsoft SQL Server collects about each SQL server. New data becomes available if a
new interval has occurred and data has been refreshed at the CMS hub. This attribute is not available for
use in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Remote Servers
attribute group. The following values are valid:

External value Internal value Description

Not Collected -1 The value cannot be collected.

Chapter 4. Attributes reference 215

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Remote Servers
attribute group.

Network Name The name of the network for the remote SQL server. The value format is an
alphanumeric string with a maximum of 16 characters; for example, REM_NET. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces. To create a situation, use the MS SQL Remote
Servers attribute group.

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces. To create a situation, use the MS SQL Remote
Servers attribute group.

Remote Server ID The ID of the remote SQL server. The value format is an alphanumeric string with a
maximum of 12 characters; for example, SERV_ID. This attribute is not available for use in situations.
Otherwise, this attribute is available to use like any other attribute, for example it is available for reports,
queries, and workspaces. To create a situation, use the MS SQL Remote Servers attribute group. To create
a situation, use the MS SQL Remote Servers attribute group.

Remote Server Name The name of the remote SQL server. The value format is an alphanumeric string
with a maximum of 12 characters; for example, REM_SVR5. This attribute is not available for use in
situations. Otherwise, this attribute is available to use like any other attribute, for example it is available
for reports, queries, and workspaces. To create a situation, use the MS SQL Remote Servers attribute
group.

Remote Server Status The status of the remote SQL server. The server status is displayed as Unknown
when the collector process of the SQL Server agent is not running. The server status is displayed as
Inactive when the collector process of the SQL Server agent is running, but the SQL Server is not
responding to the request. The following values are valid:

External value Internal value Description

Active Active SQL server is active.
Inactive Inactive SQL server status is inactive.
Unknown Unknown SQL server status is unknown.

This attribute is not available for use in situations. Otherwise, this attribute is available to use like any
other attribute, for example it is available for reports, queries, and workspaces. To create a situation, use
the MS SQL Remote Servers attribute group.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour

216 Microsoft SQL Server agent: User’s Guide

mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m. This attribute is not available for use in situations. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Remote Servers attribute group.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5. This attribute is not available for use in situations. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Remote Servers attribute group.

VMS SQL Server Enterprise View attributes

The VMS SQL Server Enterprise View attribute group contains attributes that you can use to monitor the
SQL servers in your enterprise.

Age of Last Error The age in minutes of the last error encountered. The value format is an integer. This
attribute is not available for use in situations or for historical data collection. Otherwise, this attribute is
available to use like any other attribute, for example it is available for reports, queries, and workspaces.
To create a situation, use the MS SQL Server Enterprise View attribute group.

Collection Status Indicates the status of the data collector. The data collector is the part of the product
that collects information about the SQL server. The following values are also valid:

External value Internal value Description

Unknown Unknown Data collector is unknown.
Inactive Inactive Data collector is inactive.
Active Active Data collector is active.

This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Current Logons The number of logons and connections that are currently active. The value format is an
integer. This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Database Max Blocks The name of the database blocking the largest number of processes. This attribute
is not available for use in situations or for historical data collection. Otherwise, this attribute is available
to use like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Database Max Blocks (Unicode) The name of the database blocking the largest number of processes.

Database Max Locks The name of the database with largest number of locks. The value format is an
alphanumeric string with a maximum of 32 characters. This attribute is not available for use in situations
or for historical data collection. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces. To create a situation, use the MS SQL Server
Enterprise View attribute group.

Database Max Locks (Unicode) The name of the database with largest number of locks. Valid values
include text strings with a maximum of 32 bytes. This attribute is not available for use in situations or for

Chapter 4. Attributes reference 217

historical data collection. Otherwise, this attribute is available to use like any other attribute, for example
it is available for reports, queries, and workspaces. To create a situation, use the MS SQL Server
Enterprise View attribute group.

Error Log Size The size in bytes of the error log. The value format is an integer. This attribute is not
available for use in situations or for historical data collection. Otherwise, this attribute is available to use
like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Host Name The name of the computer on which the SQL Server is running. The value format is an
alphanumeric string with a maximum of 64 characters, for example, Voyager. This attribute is not
available for use in situations or for historical data collection.

Hub Timestamp The time when this data was inserted at the hub. This attribute is not available for use
in situations or for historical data collection. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Server Enterprise View attribute group.

IO Errors Current Interval The number of disk errors in the current interval. The value format is an
integer. This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Maximum Sev Level The highest severity level of an error message since startup. This attribute is not
available for use in situations or for historical data collection. Otherwise, this attribute is available to use
like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Maximum Sev Timestamp The timestamp of the of the error message with the highest severity level
since startup. The format is MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m. This attribute is not available for use in situations or for historical
data collection. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise
View attribute group.

Minimum Pct Data Freespace The lowest percentage of free space in data only and data and log
segments on a device allocated to a database. The value format is a percentage with two decimal places
allowed; for example, 5.00. The amount of space needed by the database depends on its anticipated
activity. Set alerts for abnormal conditions. Evaluate the possibility of adding more space to the database.
This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Minimum Pct Log Freespace The lowest percentage of free space in the log. The value format is a
decimal number 0.00 through 100.00. This attribute is not available for use in situations or for historical

218 Microsoft SQL Server agent: User’s Guide

data collection. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise
View attribute group.

Mirror Name The name of the database. The following values are valid:

External value Internal value

No Data nodata

Mirroring Role The current role of the local database in the database mirroring session. The format is an
integer. The following values are also valid:

External value Internal value

Not Collected -1
Mirror 0
Principal 1

Mirroring State The state of the mirror database. The format is an integer. The following values are also
valid:

External value Internal value

Not Collected -1
Suspended 0
Disconnected 1
Synchronizing 2
Pending Failover 3
Synchronized 4

Originnode The key for the table view in the format serverid:hostname:MSS. This attribute is not
available for use in situations or for historical data collection. Otherwise, this attribute is available to use
like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Pct Max Locks The percentage of locks on resources of the maximum number of locks allowed by the
SQL server. The value format is a percentage with two decimal places allowed; for example, 10.00. Setting
a higher limit for the maximum number of locks does not impair performance. If your operations exceed
the number of available locks, you can increase this limit. This attribute is not available for use in
situations or for historical data collection. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Server Enterprise View attribute group.

Percent Max Logons Active The percentage of the maximum user connections that are currently active.
The value format is a decimal number in the range 0.00 to 100.00. This attribute is not available for use in
situations or for historical data collection. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Server Enterprise View attribute group.

Percent Process Block The percentage of total processes in conflict. The value format is a decimal number
in the 0.00 through 100.00. This attribute is not available for use in situations or for historical data

Chapter 4. Attributes reference 219

collection. Otherwise, this attribute is available to use like any other attribute, for example it is available
for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise View
attribute group.

Physical Reads per Second The number of physical reads per second during the current interval. The
value format is a decimal number with 2 decimal places. This attribute is not available for use in
situations or for historical data collection. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Server Enterprise View attribute group.

Physical Writes per Second The Number of physical writes per second during the current interval. The
value is a decimal number with 2 decimal places. This attribute is not available for use in situations or
for historical data collection. Otherwise, this attribute is available to use like any other attribute, for
example it is available for reports, queries, and workspaces. To create a situation, use the MS SQL Server
Enterprise View attribute group.

Sample Timestamp The timestamp that indicates the date and time the product collected the sample for
the SQL server. A sample is the data the product collects about the SQL server. The format is
MM/DD/YY HH:mm:SS, where:

MM Month
DD Day
YY Year
HH Hour
mm Minute
SS Second

For example, 01/25/02 08:00:00 indicates that the product collected the data from the SQL server on
Friday, January 25, 2002 at 8:00 a.m. This attribute is not available for use in situations or for historical
data collection. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise
View attribute group.

Server The name of the SQL server. The value format is an alphanumeric string with a maximum of 30
characters; for example, CFS_SVR5. This attribute is not available for use in situations or for historical
data collection. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise
View attribute group.

Server CPU Percent The percentage of CPU time the SQL server process is using on the host. The value
format is a percentage with two decimal places allowed; for example, 20.00. This attribute is not available
for use in situations or for historical data collection. Otherwise, this attribute is available to use like any
other attribute, for example it is available for reports, queries, and workspaces. To create a situation, use
the MS SQL Server Enterprise View attribute group.

Server CPU Percent Application The percentage of CPU being used by application processes for the
server. The value format is a decimal number in the range 0.00 through 100.00. This attribute is not
available for use in situations or for historical data collection. Otherwise, this attribute is available to use
like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Server CPU Percent System The percentage of CPU being used by system processes for the server. The
value format is a decimal number in the range 0.00 through 100.00. This attribute is not available for use

220 Microsoft SQL Server agent: User’s Guide

in situations or for historical data collection. Otherwise, this attribute is available to use like any other
attribute, for example it is available for reports, queries, and workspaces. To create a situation, use the MS
SQL Server Enterprise View attribute group.

Server Status Indicates the status of the SQL server. The server status is displayed as Unknown when the
collector process of the SQL Server agent is not running. The server status is displayed as Inactive when
the collector process of the SQL Server agent is running, but the SQL Server is not responding to the
request.The following values are also valid:

External value Internal value Description

Active Active or 1 SQL server is active.
Inactive Inactive SQL server is not active.
Unknown Unknown or 0 SQL server status is unknown.

This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Server Version The version of the SQL Server. The value format is the version in the format w.x.y.z; for
example, 10.0.2531.0.

Server Version (Superceded) The version of the SQL Server. The value format is the version in the format
x.y.z; for example, 10.0.253. This attribute is not available for use in situations or for historical data
collection. Otherwise, this attribute is available to use like any other attribute, for example it is available
for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise View
attribute group.

Note: For the complete version of the SQL Server, see the Server Version attribute.

Synchronization State The synchronization state (is failover possible). The format is an integer. The
following values are also valid:

External value Internal value

Not Collected -1
Failover not possible 0
Failover possible 1

Table Max Locks The name of the table with largest number of locks. The value format is an
alphanumeric string with a maximum of 32 characters.

Table Max Locks (Unicode) The name of the table with largest number of locks. Valid values include text
strings with a maximum of 32 bytes. This attribute is not available for use in situations or for historical
data collection. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise
View attribute group.

Time Since Startup The number of minutes that have elapsed since the SQL server was started. The
value format is an integer; for example, 360. This attribute is not available for use in situations or for
historical data collection. Otherwise, this attribute is available to use like any other attribute, for example
it is available for reports, queries, and workspaces. To create a situation, use the MS SQL Server
Enterprise View attribute group.

Total Databases The number of databases for the SQL server. The value format is an integer; for example,
10. This attribute is not available for use in situations or for historical data collection. Otherwise, this

Chapter 4. Attributes reference 221

attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Total Errors High Sev The total number of messages with a severity of 17 or higher since the server was
started. The value format is an integer. This attribute is not available for use in situations or for historical
data collection. Otherwise, this attribute is available to use like any other attribute, for example it is
available for reports, queries, and workspaces. To create a situation, use the MS SQL Server Enterprise
View attribute group.

Total Lock Conflicts The total number of processes involved in lock conflicts. The value format is an
integer. This attribute is not available for use in situations or for historical data collection. Otherwise, this
attribute is available to use like any other attribute, for example it is available for reports, queries, and
workspaces. To create a situation, use the MS SQL Server Enterprise View attribute group.

Total Locks The total number of locks for the server. The value format is an integer. This attribute is not
available for use in situations or for historical data collection. Otherwise, this attribute is available to use
like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Total OS CPU Percent The percentage of CPU time being used by all processes on the host. The value
format is a percentage with two decimal places allowed; for example, 40.00. This attribute is not available
for use in situations or for historical data collection. Otherwise, this attribute is available to use like any
other attribute, for example it is available for reports, queries, and workspaces. To create a situation, use
the MS SQL Server Enterprise View attribute group.

Total Processes The total number of processes. The value format is an integer. This attribute is not
available for use in situations or for historical data collection. Otherwise, this attribute is available to use
like any other attribute, for example it is available for reports, queries, and workspaces. To create a
situation, use the MS SQL Server Enterprise View attribute group.

Total Processes Blocked The total number of processes blocked. The value format is an integer. This
attribute is not available for use in situations or for historical data collection. Otherwise, this attribute is
available to use like any other attribute, for example it is available for reports, queries, and workspaces.
To create a situation, use the MS SQL Server Enterprise View attribute group.

Transaction Delay The time (in milliseconds) awaited by the transaction termination to receive an
acknowledgment per second. The format is an integer. The following values are also valid:

External value Internal value

Not Collected -1

Disk capacity planning for historical data

Disk capacity planning for a monitoring agent is a prediction of the amount of disk space to be
consumed for each attribute group whose historical data is being collected. Required disk storage is an
important factor to consider when you are defining data collection rules and your strategy for historical
data collection.

Calculate expected disk space consumption by multiplying the number of bytes per instance by the
expected number of instances, and then multiplying that product by the number of samples. Table 8 on
page 223 provides the following information required to calculate disk space for the Microsoft SQL Server
agent:
v DB table name is the table name as it would appear in the warehouse database, if the attribute group is
configured to be written to the warehouse.

222 Microsoft SQL Server agent: User’s Guide

v Bytes per instance (agent) is an estimate of the record length for each row or instance written to the
agent disk for historical data collection. This estimate can be used for agent disk space planning
purposes.
v Bytes per instance (warehouse) is an estimate of the record length for detailed records written to the
warehouse database, if the attribute group is configured to be written to the warehouse. Detailed
records are those that have been uploaded from the agent for long-term historical data collection. This
estimate can be used for warehouse disk space planning purposes.
v Bytes per summarized instance (warehouse) is an estimate of the record length for aggregate records
written to the warehouse database, if the attribute group is configured to be written to the warehouse.
Aggregate records are created by the Summarization agent for attribute groups that have been
configured for summarization. This estimate can be used for warehouse disk space planning purposes.
v Expected number of instances is a guideline that can be different for each attribute group, because it is the
number of instances of data that the agent will return for a given attribute group, and depends upon
the application environment that is being monitored. For example, if your attribute group is monitoring
each processor on your machine and you have a dual processor machine, the number of instances is 2.
The IBM Tivoli Monitoring Installation and Setup Guide contains formulas that can be used to estimate the
amount of disk space used at the agent and in the warehouse database for historical data collection of an
attribute group.
Table 8. Capacity planning for historical data logged by the Microsoft SQL Server agent
Database Aggregate
Bytes per bytes per bytes per
row row row
Table Attribute group (agent) (warehouse) (warehouse)
KOQAADBD MS_SQL_Additional_Availability_ 832 834 1086
Database_Details
KOQADDBD MS_SQL_Additional_Database_Detail 1448 1451 1488
KOQSASDM MS_SQL_Analysis_Services_Data_ 220 250 658
Mining
KOQSASMX MS_SQL_Analysis_Services_MDX_ 364 380 1178
Processing
KOQSASSM MS_SQL_Analysis_Services_Memory_ 676 899 3926
Statistics
KOQSASPR MS_SQL_Analysis_Services_Rows_ 196 215 486
Processing
KOQSASSQ MS_SQL_Analysis_Services_Storage_ 516 815 2950
Engine_Query
KOQAVDBD MS_SQL_Availability_Database_ 1332 1342 1379
Details
KOQCAVDB MS_SQL_Availability_Database_ 1312 1317 1354
Details_In_Cluster
KOQADBST MS_SQL_Availability_Database_ 612 688 1227
Statistics
KOQADBSU MS_SQL_Availability_Database_ 208 212 522
Summary
KOQAVGLD MS_SQL_Availability_Group_ 1188 1191 1228
Listener_Details
KOQGRPDT MS_SQL_Availability_Groups_ 1272 1283 1398
Details
KOQCAVGD MS_SQL_Availability_Groups_ 928 928 965
Details_In_Cluster

Chapter 4. Attributes reference 223

Table 8. Capacity planning for historical data logged by the Microsoft SQL Server agent (continued)
Database Aggregate
Bytes per bytes per bytes per
row row row
Table Attribute group (agent) (warehouse) (warehouse)
KOQGRPSM MS_SQL_Availability_Groups_ 248 247 479
Summary
KOQAVARD MS_SQL_Availability_Replicas_ 1232 1240 1277
Details
KOQCAVRD MS_SQL_Availability_Replicas_ 1560 1567 1604
Details_In_Cluster
KOQAVRST MS_SQL_Availability_Replicas_ 284 355 851
Statistics
KOQAVARS MS_SQL_Availability_Replicas_ 820 824 900
Status
KOQAVRSU MS_SQL_Availability_Replicas_ 208 212 522
Status_Summary
KOQBTCHS MS_SQL_Batch_Stats 248 355 851
KOQBLKQD MS_SQL_Blocked_Queries_Details 7524 7548 7628
KOQSCFG MS_SQL_Configuration 313 310 347
KOQDBD MS_SQL_Database_Detail 2735 3028 4334
KOQDBMIR MS_SQL_Database_Mirroring 700 980 2088
KOQDBS MS_SQL_Database_Summary 266 288 559
KOQDEVD MS_SQL_Device_Detail 1444 1495 1724
KOQERROR MS_SQL_Error_Event_Detail 684 687 724
KOQFTBLD MS_SQL_FileTable_Detail 868 872 987
KOQFGRPD MS_SQL_Filegroup_Detail 1004 1053 1243
KOQINQRD MS_SQL_Individual_Queries_Details 2776 2857 3551
KOQSSISD MS_SQL_Integration_Service_ 192 226 658
Details
KOQJOBD MS_SQL_Job_Detail 1928 1954 2346
KOQJOBS MS_SQL_Job_Summary 268 281 522
KOQLOCK MS_SQL_Lock_Conflict_Detail 678 681 718
KOQLOCKS MS_SQL_Lock_Detail 1078 1087 1124
KOQLRTS MS_SQL_Lock_Resource_Type_Summary 244 285 529
KOQLOKSU MS_SQL_Lock_Summary 300 333 1096
KOQLSDBD MS_SQL_Log_Shipping_DB_Details 1796 1815 1852
KOQLSERR MS_SQL_Log_Shipping_Errors 1182 1191 1228
KOQLSJBD MS_SQL_Log_Shipping_Jobs_Detail 1442 1456 1493
KOQMEMGR MS_SQL_Memory_Manager 276 457 1208
KOQPROBD MS_SQL_Problem_Detail 804 808 845
KOQPROBS MS_SQL_Problem_Summary 278 277 437
KOQPRCD MS_SQL_Process_Detail 934 975 1207
KOQPRCS MS_SQL_Process_Summary 302 417 1225
KOQSRVR MS_SQL_Remote_Servers 284 281 318

224 Microsoft SQL Server agent: User’s Guide

Table 8. Capacity planning for historical data logged by the Microsoft SQL Server agent (continued)
Database Aggregate
Bytes per bytes per bytes per
row row row
Table Attribute group (agent) (warehouse) (warehouse)
KOQRPOOL MS_SQL_Resource_Pool_Stats 660 846 1597
KOQRUNQD MS_SQL_Running_Queries_Details 3144 3167 3513
KOQSRVD MS_SQL_Server_Detail 616 702 1294
KOQSRVRE MS_SQL_Server_Enterprise_View 1632 1801 2639
KOQSVRPR MS_SQL_Server_Properties 980 987 1024
KOQSRVS MS_SQL_Server_Summary 450 712 2387
KOQSTRNS MS_SQL_Server_Transactions_ 276 303 844
Summary
KOQSBACT MS_SQL_Service_Broker_Activation 572 604 875
KOQSBSTA MS_SQL_Service_Broker_Statistics 268 320 1050
KOQSBTRP MS_SQL_Service_Broker_Transport 260 311 982
KOQSRVCD MS_SQL_Services_Detail 620 628 665
KOQSTATD MS_SQL_Statistics_Detail 280 289 431
KOQSTATS MS_SQL_Statistics_Summary 310 451 1298
KOQTBLD MS_SQL_Table_Detail 1412 1450 1706
KOQTBLS MS_SQL_Table_Summary 204 276 442
KOQSQL MS_SQL_Text 2997 3017 3105
KOQWLGS MS_SQL_Workload_Group_Stats 648 795 1393

For more information about historical data collection, see the IBM Tivoli Monitoring Administrator's Guide.

Chapter 4. Attributes reference 225

226 Microsoft SQL Server agent: User’s Guide
Chapter 5. Situations reference
This chapter contains an overview of situations, references for detailed information about situations, and
descriptions of the predefined situations included in this monitoring agent.

About situations

A situation is a logical expression involving one or more system conditions. Situations are used to monitor
the condition of systems in your network. You can manage enterprise situations from the Tivoli
Enterprise Portal by using the Situation editor. You can manage enterprise situations from the Tivoli
Enterprise Portal by using the Situation Editor or from the command line interface using the tacmds for
situations.

The IBM Tivoli Monitoring agents that you use to monitor your system environment are shipped with a
set of predefined situations that you can use as-is or you can create new situations to meet your
requirements. Predefined situations contain attributes that check for system conditions common to many
enterprises.

Using predefined situations can improve the speed with which you can begin using the Microsoft SQL
Server agent. You can examine and, if necessary, change the conditions or values being monitored by a
predefined situation to those best suited to your enterprise.

Note: The predefined situations provided with this monitoring agent are not read-only. Do not edit these
situations and save over them. Software updates will write over any of the changes that you make to
these situations. Instead, clone the situations that you want to change to suit your enterprise.

You can display predefined situations and create your own situations using the Situation editor. The left
frame of the Situation editor initially lists the situations associated with the Navigator item that you
selected. When you click a situation name or create a new situation, the right frame opens with the
following tabs:
Formula
Condition being tested
Distribution
List of managed systems (operating systems, subsystems, or applications) to which the situation
can be distributed.
Expert Advice
Comments and instructions to be read in the event workspace
Action
Command to be sent to the system
Until Duration of the situation

IBM Tivoli Monitoring situations are distributed to managed systems and the Microsoft SQL Server agent
only has one type of managed system, the SQL server instance. When a situation is distributed to an SQL
server instance, the situation obtains all rows of data for the attribute group that is used by that situation.
If all database rows are returned, the situation occurs for all of the databases.

To restrict a situation to evaluate only a subset of data rows, add filters to modify the situation. You can
add one or more situation filters so that the situation evaluates only the desired database or database
table targets. For example, add the name of the database you want to monitor, such as Database Name =
"Northwind", to the situation so that the situation only monitors the Northwind database.

© Copyright IBM Corp. 2005, 2012 227

More information about situations

The IBM Tivoli Monitoring User's Guide contains more information about predefined and custom situations
and how to use them to respond to alerts.

For a list of the predefined situations for this monitoring agent and a description of each situation, see
Predefined situations and the information for each individual situation.

Predefined situations
This monitoring agent contains the following predefined situations:
v MS_SQL_Block_Critical
v MS_SQL_Block_Warning
v MS_SQL_Cache_Ave_FreePage_Crit
v MS_SQL_Cache_Ave_FreePage_Warn
v MS_SQL_Cache_Hit_Ratio_Crit
v MS_SQL_Cache_Hit_Ratio_Warn
v MS_SQL_Cache_Max_FreePage_Crit
v MS_SQL_Cache_Max_FreePage_Warn
v MS_SQL_Client_Cnt_Pct_Used_Crit
v MS_SQL_Client_Cnt_Pct_Used_Warn
v MS_SQL_Collection_Status_Warning
v MS_SQL_CPU_Critical
v MS_SQL_CPU_Warning
v MS_SQL_DB_Error_Status
v MS_SQL_DB_FreeSpace_Critical
v MS_SQL_DB_FreeSpace_Warning
v MS_SQL_DB_Num_Errors_Warning
v MS_SQL_DB_Space_Pct_Used_Crit
v MS_SQL_DB_Space_Pct_Used_Warn
v MS_SQL_DB_Status_Crit
v MS_SQL_DB_Suspect_Crit
v MS_SQL_Device_Free_PCT_Warning
v MS_SQL_Error_Warning
v MS_SQL_ErrorLog_Size_Warning
v MS_SQL_Failed_Jobs_Crit
v MS_SQL_Fragmentation_Warn
v MS_SQL_Fragmentation_Crit
v MS_SQL_IO_Disk_Errors_Crit
v MS_SQL_IOERR_Startup_Warning
v MS_SQL_IOError_Curintvl_Warning
v MS_SQL_Log_Freespace_Critical
v MS_SQL_Log_Freespace_Warning
v MS_SQL_Log_Shipping_Warning
v MS_SQL_Log_Shipping_Status_Err
v MS_SQL_Log_Space_Pct_Used_Crit
v MS_SQL_Log_Space_Pct_Used_Warn

228 Microsoft SQL Server agent: User’s Guide

v MS_SQL_Log_Suspend_Warning
v MS_SQL_LogonPct_Crit
v MS_SQL_LogonPct_Warning
v MS_SQL_Long_Running_Transaction_Warning
v MS_SQL_Mirroring_Failover_Critical
v MS_SQL_Mirrorring_Lagging_Warning
v MS_SQL_Mirrorring_Suspended_Error
v MS_SQL_Network_Read_Rate_Crit
v MS_SQL_Network_Read_Rate_Warn
v MS_SQL_Network_Write_Rate_Crit
v MS_SQL_Network_Write_Rate_Warn
v MS_SQL_Num_Process_Blocked_Crit
v MS_SQL_Num_Process_Blocked_Warn
v MS_SQL_Oldest_Transaction_Crit
v MS_SQL_Oldest_Transaction_Warn
v MS_SQL_Opt_Stats_Age_Crit
v MS_SQL_Opt_Stats_Age_Warn
v MS_SQL_Pct_Block_Warning
v MS_SQL_Pct_CPU_Yields_Warning
v MS_SQL_Pct_IO_Warning
v MS_SQL_PCT_MAX_Locks_Critical
v MS_SQL_PCT_MAX_Locks_Warning
v MS_SQL_ProbAge_GT_17_Warning
v MS_SQL_Proc_Buffs_Active_Crit
v MS_SQL_Proc_Buffs_Active_Warn
v MS_SQL_Proc_Buffs_Used_Crit
v MS_SQL_Proc_Buffs_Used_Warn
v MS_SQL_Proc_Cache_Active_Crit
v MS_SQL_Proc_Cache_Active_Warn
v MS_SQL_Proc_Cache_Used_Crit
v MS_SQL_Proc_Cache_Used_Warn
v MS_SQL_Process_Blocked_Warning
v MS_SQL_Process_Infected_Warning
v MS_SQL_ProcessLockSleep_Warning
v MS_SQL_ProcessOthSleep_Warning
v MS_SQL_Processes_Bad_Warning
v MS_SQL_Processes_Stop_Warning
v MS_SQL_Rem_Serv_Stat_Critical
v MS_SQL_Repl_Latency_Crit
v MS_SQL_Repl_Latency_Warn
v MS_SQL_Status_Critical
v MS_SQL_Status_Inactive
v MS_SQL_Total_Locks_Critical
v MS_SQL_Total_Locks_Warning

Chapter 5. Situations reference 229

Situation descriptions
Each situation description provides information about the situation that you can use to monitor the
condition of systems in your network.

MS_SQL_Block_Critical
Declares a critical condition if the number of processes in conflict is greater than or equal to 60.

MS_SQL_Block_Warning
Declares a warning condition if the number of processes in conflict is greater than or equal to 20 and less
than 60.

MS_SQL_Cache_Ave_FreePage_Crit
Declares a critical condition if the average number of cache buffers scanned to find a free buffer exceeds
the critical threshold. The default threshold is Cache Average Free Scan greater than 15.

MS_SQL_Cache_Ave_FreePage_Warn
Declares a warning condition if the average number of cache buffers scanned to find a free buffer exceeds
the warning threshold. The default threshold is Cache Average Free Scan greater than 10 and less than or
equal to 15.

MS_SQL_Cache_Hit_Ratio_Crit
Declares a critical condition if the ratio of data cache hits to total data requests exceeds the critical
threshold. The default threshold is Cache Hit Ratio less than 70.00.

MS_SQL_Cache_Hit_Ratio_Warn
Declares a warning condition if the ratio of data cache hits to total data requests exceeds the warning
threshold. The default threshold is Cache Hit Ratio less than 90.00 and greater than or equal to 70.00.

MS_SQL_Cache_Max_FreePage_Crit
Declares a critical condition if the maximum number of cache buffers scanned to find a free buffer
exceeds the critical threshold. The default threshold is Cache Maximum Free Page Scan greater than 15.

MS_SQL_Cache_Max_FreePage_Warn
Declares a warning condition if the maximum number of cache buffers scanned to find a free buffer
exceeds the warning threshold. The default threshold is Cache Maximum Free Page Scan greater than 5
and less than or equal to 15.

MS_SQL_Client_Cnt_Pct_Used_Crit
Declares a critical condition if the percentage of client licenses being used exceeds the critical threshold.
The default threshold is Client Count Pct Used greater than 90.00.

MS_SQL_Client_Cnt_Pct_Used_Warn
Declares a warning condition if the percentage of client licenses being used exceeds the warning
threshold. The default threshold is Client Count Pct Used greater than 70.00 and less than or equal to
90.00.

MS_SQL_Collection_Status_Warning
Declares a warning condition if the collection status is not Active.

230 Microsoft SQL Server agent: User’s Guide

MS_SQL_CPU_Critical
Declares a critical condition if the percentage of CPU usage is greater than or equal to 80 and elapsed
time since the SQL server was started is at least 10 minutes.

MS_SQL_CPU_Warning
Declares a warning condition if the percentage of CPU usage is greater than or equal to 60 and less than
80 and elapsed time since the SQL server was started is at least 10 minutes.

MS_SQL_DB_Error_Status
Provides an alert if the database has a serious error.

MS_SQL_DB_Freespace_Critical
Declares a critical condition if the percentage of freespace on the database is less than or equal to 10.

MS_SQL_DB_Join_State_Warn
Declares a warning condition if the availability database is in the Not Joined state.

MS_SQL_DB_Space_Pct_Used_Warn
Declares a warning condition if the percentage of space used in the database compared to the total space
allowed exceeds the warning threshold. The default threshold is Database Space Pct Used greater than
70.00 and less than or equal to 90.00.

MS_SQL_DB_Space_Pct_Used_Crit
Declares a critical condition if the percentage of space used in the database compared to the total space
allowed exceeds the critical threshold. The default threshold is Database Space Pct Used greater than
90.00.

MS_SQL_DB_Num_Errors_Warning
Declares a warning condition if the number of databases with an error status is greater than 0.

MS_SQL_DB_Freespace_Warning
Declares a warning condition if the percentage of freespace in the database is less than or equal to 20 and
greater than 10.

MS_SQL_DB_Status_Crit
Declares a critical condition if the database is unavailable because of an error or being taken offline.

MS_SQL_DB_Suspect_Crit
Declares a critical condition if the database is in an inconsistent state because it cannot be restored.

MS_SQL_DB_Sync_Health_Crit
Declares a critical situation when the synchronization health of an availability database is Not Healthy.

MS_SQL_DB_Sync_State_Warn
Declares a warning condition if an availability database is in the Not Synchronizing state.

MS_SQL_Device_Free_PCT_Warning
Declares a warning condition if the percentage of freespace on the device is less than or equal to 10.

Chapter 5. Situations reference 231

MS_SQL_Error_Event_Warning
Declares a warning condition if the SQL Server error is generated with severity greater than 16.

MS_SQL_Error_Warning
Declares a warning condition if the number of SQL Server errors during the current interval is greater
than 0.

MS_SQL_ErrorLog_Size_Warning
Declares a warning condition if the error log size is greater than or equal to 10000 bytes.

MS_SQL_Failed_Jobs_Crit
Declares a critical condition if the number of jobs run by the SQLServerAgent service that have failed
over the last monitoring interval has exceeded the critical threshold. The default threshold is
SQLServerAgent Failed Jobs greater than 0.

MS_SQL_Fragmentation_Crit
Declares a critical condition if the percentage of fragmentation exceeds the critical threshold. The default
threshold is Fragmentation greater than 80.00.

MS_SQL_Fragmentation_Warn
Declares a warning condition if the percentage of fragmentation exceeds the warning threshold. The
default threshold is Fragmentation greater than 30.00 and less than or equal to 80.00.

MS_SQL_Group_Role_Crit
Declares a critical condition if the role of an SQL Server instance in an availability group changes from
Primary to Secondary or Resolving, or if the role changes to Invalid.

MS_SQL_IOERR_Startup_Warning
Declares a warning condition if the number of IO errors since startup is greater than or equal to 10 and
the percentage of IO errors in the current interval is greater than or equal to 5.

MS_SQL_IO_Disk_Errors_Crit
Declares a critical condition if the number of SQL Server read/write disk errors exceeds the critical
threshold. The default threshold is Statistics Name equals IO errors and the Current Value is greater than
0.

MS_SQL_IOError_Curintvl_Warning
Declares a warning condition if the percentage of IO errors during the current interval is greater than or
equal to 80.

MS_SQL_Log_Freespace_Critical
Declares a critical condition if the percentage of freespace in the log is less than or equal to 10.

MS_SQL_Log_Freespace_Warning
Declares a warning condition if the percentage of freespace in the log is less than or equal to 20 and
greater than 10.

232 Microsoft SQL Server agent: User’s Guide

MS_SQL_Log_Shipping_Status_Err
Declares an error condition if the backup or restore job results in an error. The Job Status is displayed as
Error.

MS_SQL_Log_Shipping_Warning
Declares a warning condition if the configured threshold, minutes between backup or restore jobs are
exceeded. Test for Threshold Exceeded = Yes.

MS_SQL_Log_Space_Pct_Used_Crit
Declares a critical condition if the percentage of space used by the transaction log compared to the total
allocated transaction log size exceeds the critical threshold. The default threshold is Log Space Pct Used
greater than 90.00.

MS_SQL_Log_Space_Pct_Used_Warn
Declares a warning condition if the percentage of space used by the transaction log compared to the total
allocated transaction log size exceeds the warning threshold. The default threshold is Log Space Pct Used
greater than 70.00 and less than or equal to 90.00.

MS_SQL_Log_Suspend_Warning
Declares a warning condition if the number of processes in log suspend is greater than or equal to 1.

MS_SQL_LogonPct_Crit
Declares a critical condition if the number of current user connections as a percentage of the available
user connections has exceeded the critical threshold. The default threshold is Pct Max Logons Active
greater than 90.00.

MS_SQL_LogonPct_Warning
Declares a warning condition if the percentage of active logins is greater than or equal to 90.

MS_SQL_Long_Running_Transaction_Warning
Declares a warning condition if the same database transaction is identified to be the longest running
transaction over two consecutive 15 minutes interval cycles.

MS_SQL_Mirror_Failover_Critical
Declares a critical condition that is found only on the principal server after a failover, but the server is
not changed to the mirror role (Mirroring_State is equal to 'Pending Failover').

MS_SQL_Mirror_Lagging_Warning
Declares a warning condition if the contents of the mirror database lag the contents of the principal
database (Mirroring State is equal to 'Synchronizing'). The principal server instance sends log records to
the mirror server instance, which applies the changes to the mirror database to roll it forward.

MS_SQL_Mirror_Suspended_Warning
Declares a warning condition if the mirror copy of the database is not available (Mirroring_State is equal
to 'Suspended'). The principal database runs without sending any logs to the mirror server, a condition
known as running exposed.

Chapter 5. Situations reference 233

MS_SQL_Network_Read_Rate_Crit
Declares a critical condition if the rate (packets per second) of Tabular Data Stream (TDS) packets being
read from the network exceeds the critical threshold. The default threshold is Network Read Rate (per
Sec.) greater than 150.

MS_SQL_Network_Read_Rate_Warn
Declares a warning condition if the rate (packets per second) of Tabular Data Stream (TDS) packets being
read from the network exceeds the warning threshold. The default threshold is Network Read Rate (per
Sec.) greater than 50 and less than or equal to 150.

MS_SQL_Network_Write_Rate_Crit
Declares a critical condition if the rate (packets per second) of Tabular Data Stream (TDS) packets being
written from the network exceeds the critical threshold. The default threshold is Network Write Rate (per
Sec.) greater than 150.

MS_SQL_Network_Write_Rate_Warn
Declares a warning condition if the rate (packets per second) of Tabular Data Stream (TDS) packets being
written from the network exceeds the warning threshold. The default threshold is Network Write Rate
(per Sec.) greater than 50 and less than or equal to 150.

MS_SQL_Num_Process_Blocked_Crit
Declares a critical condition if the number of blocked processes exceeds the critical threshold. The default
threshold is Total Processes Blocked greater than 10.

MS_SQL_Num_Process_Blocked_Warn
Declares a warning condition if the number of blocked processes exceeds the warning threshold. The
default threshold is Total Processes Blocked greater than 2 and less than or equal to 10.

MS_SQL_Oldest_Transaction_Crit
Declares a critical condition if the age (in minutes) of the oldest transaction in the database's transaction
log exceeds the critical threshold. The default threshold is Oldest Open Transaction (min) greater than 15.

MS_SQL_Oldest_Transaction_Warn
Declares a warning condition if the age (in minutes) of the oldest transaction in the database's transaction
log exceeds the warning threshold. The default threshold is Oldest Open Transaction (min) greater than 5
and less than or equal to 15.

MS_SQL_Opt_Stats_Age_Crit
Declares a critical condition if the time (in minutes) since the table statistics were last updated exceeds
the critical threshold. The default threshold is Optimizer Statistics Age (in Min.) greater than 1440.

MS_SQL_Opt_Stats_Age_Warn
Declares a warning condition if the time (in minutes) since the table statistics were last updated exceeds
the warning threshold. The default threshold is Optimizer Statistics Age (in Min.) greater than 180 and
less than or equal to 1440.

MS_SQL_Pct_Block_Warning
Declares a warning condition if the percentage of processes in conflict is greater than or equal to 50.

MS_SQL_Pct_CPU_Yields_Warning
Declares a warning condition if the percentage of CPU yields is greater than 75.

234 Microsoft SQL Server agent: User’s Guide

MS_SQL_Pct_IO_Warning
Declares a warning condition if the percentage of time spent for IO operations is greater than or equal to
90.

MS_SQL_PCT_MAX_Locks_Critical
Declares a critical condition if the number of locks reaches or exceeds 80 percent of the maximum locks
allowed.

MS_SQL_PCT_MAX_Locks_Warning
Declares a warning condition if the number of locks ranges from 60 to 80 percent of the maximum locks
allowed.

MS_SQL_ProbAge_GT_17_Warning
Declares a warning condition if the age of the last error is 30 minutes or greater and the highest severity
level is greater than or equal to 17.

MS_SQL_Proc_Buffs_Active_Crit
Declares a critical condition if the percentage of active procedure buffers (buffers containing procedure(s)
actively being executed) to total available procedure buffers exceeds the critical threshold. The default
threshold is Procedure Buffers Pct Active less than 75.00.

MS_SQL_Proc_Buffs_Active_Warn
Declares a warning condition if the percentage of active procedure buffers (buffers containing one or
more procedures) actively being executed) to total available procedure buffers exceeds the warning
threshold. The default threshold is Procedure Buffers Pct Active less than 95.00 and greater than or equal
to 75.00.

MS_SQL_Proc_Buffs_Used_Crit
Declares a critical condition if the percentage of used procedure buffers to total available procedure
buffers exceeds the critical threshold. The default threshold is Procedure Buffers Pct Used less than 75.00.

MS_SQL_Proc_Buffs_Used_Warn
Declares a warning condition if the percentage of used procedure buffers to total available procedure
buffers exceeds the warning threshold. The default threshold is Procedure Buffers Pct Used less than
95.00 and greater than or equal to 75.00.

MS_SQL_Proc_Cache_Active_Crit
Declares a critical condition if the percentage of the procedure buffer cache with currently executing
procedures exceeds the critical threshold. The default threshold is Procedure Cache Pct Active less than
75.00.

MS_SQL_Proc_Cache_Active_Warn
Declares a warning condition if the percentage of the procedure buffer cache with procedures in it
exceeds the warning threshold. The default threshold is Procedure Cache Pct Active less than 95.00 and
greater than or equal to 75.00.

MS_SQL_Proc_Cache_Used_Crit
Declares a critical condition if the percentage of used procedure buffers to total available procedure
buffers exceeds the critical threshold. The default threshold is Procedure Cache Pct Used less than 75.00.

Chapter 5. Situations reference 235

MS_SQL_Proc_Cache_Used_Warn
Declares a warning condition if the percentage of the procedure buffer cache with currently executing
procedures exceeds the warning threshold. The default threshold is Procedure Cache Pct Used less than
95.00 and greater than or equal to 75.00.

MS_SQL_Process_Blocked_Warning
Declares a warning condition if the percentage of blocked processes is greater than or equal to 25 and the
number of blocked processes is greater than or equal to 5.

MS_SQL_Process_Infected_Warning
Declares a warning condition if the number of infected processes is greater than or equal to 1.

MS_SQL_Processes_Bad_Warning
Declares a warning condition if the number of bad processes is greater than or equal to 1.

MS_SQL_Processes_Stop_Warning
Declares a warning condition if the number of stopped processes is greater than or equal to 5 and the
percentage of stopped processes is greater than or equal to 10.

MS_SQL_ProcessLockSleep_Warning
Declares a waning condition if the percentage of processes in locksleep is greater than or equal to 10 and
the number of processes in locksleep is greater than or equal to 5.

MS_SQL_ProcessOthSleep_Warning
Declares a warning condition if the number of processes in other sleep is greater than or equal to 2 and
the percentage of processes in othersleep is greater than or equal to 50.

MS_SQL_Rem_Serv_Stat_Critical
Declares a critical condition if the remote server has a status of Inactive.

MS_SQL_Repl_Latency_Crit
Declares a critical condition if the time (in milliseconds) between the time a transaction marked for
replication is entered into the transaction log and the time the transaction is read out of the log and
delivered to the distribution database exceeds the critical threshold. The default threshold is Replication
Latency (ms) greater than 900,000.

MS_SQL_Repl_Latency_Warn
Declares a warning condition if the time (in milliseconds) between the time a transaction marked for
replication is entered into the transaction log and the time the transaction is read out of the log and
delivered to the distribution database exceeds the warning threshold. The default threshold is Replication
Latency (ms) greater than 120,000 and less than or equal to 900,000.

MS_SQL_Replica_Join_State_Warn
Declares a warning condition if the availability replica is in the Not Joined state.

MS_SQL_Replica_Role_Health_Crit
Declares a critical condition if the role of the availability replica is not Primary or Secondary. This
situation is supported for SQL Server 2012, or later.

236 Microsoft SQL Server agent: User’s Guide

MS_SQL_Replica_Sync_Health_Warn
Declares a warning condition if the synchronization health of an availability replica is not healthy.

MS_SQL_Replicas_Conn_State_Crit
Declares a critical condition if the state of an availability replica is Disconnected.

MS_SQL_Status_Critical
Declares a critical condition if the SQL Server status is not active.

MS_SQL_Status_Inactive
Initiates an action if the SQL server is inactive.

MS_SQL_Total_Locks_Critical
Declares a critical condition if the number of locks reaches or exceeds 4000.

MS_SQL_Total_Locks_Warning
Declares a warning condition if the number of locks reaches or exceeds 200.

Chapter 5. Situations reference 237

238 Microsoft SQL Server agent: User’s Guide
Chapter 6. Take Action commands reference
This chapter contains an overview of Take Action commands, references for detailed information about
Take Action commands, and descriptions of the Take Action commands included in this monitoring
agent.

About Take Action commands

Take Action commands can be run from the desktop or included in a situation or a policy.

When included in a situation, the command executes when the situation becomes true. A Take Action
command in a situation is also called reflex automation. When you enable a Take Action command in a
situation, you automate a response to system conditions. For example, you can use a Take Action
command to send a command to restart a process on the managed system or to send a text message to a
cell phone.

Advanced automation uses policies to perform actions, schedule work, and automate manual tasks. A
policy comprises a series of automated steps called activities that are connected to create a workflow.
After an activity is completed, Tivoli Enterprise Portal receives return code feedback, and advanced
automation logic responds with subsequent activities prescribed by the feedback.

More information about Take Action commands

For more information about working with Take Action commands, see the IBM Tivoli Monitoring User's
Guide.

For a list of the Take Action commands for this monitoring agent and a description of each command, see
“Predefined Take Action commands” section and the information for each individual command.

Predefined Take Action commands

The remaining sections of this chapter contain descriptions of each of these Take Action commands,
which are listed alphabetically. The following information is provided following the description of each
Take Action command:
Authorization role
The required authorization role, plus any required Microsoft SQL Server permissions
Arguments
List of arguments, if any, for the Take Action with a short description and default value for each
one. Each argument is positionally dependent and mandatory. The arguments for the MS SQL
Take Actions are organized according to their respective positions on the GUI. If any argument
requires an embedded space, the argument must be enclosed in double quotation marks.
When an argument is not required, a blank argument value must be used. A blank argument
value is double quotation marks: "".
Destination systems
Where the command is to be executed: on the Managed System (monitoring agent) where the
agent resides or on the Managing System (Tivoli Enterprise Monitoring Server) to which it is
connected
Usage notes
Additional relevant notes for using the Take Actions

© Copyright IBM Corp. 2005, 2012 239

Note: See the Windows Help or the Microsoft SQL Server Books On-line system for additional information,
formatting considerations, and so on, for the Take Actions.

User ID and password combinations

All Take Actions for this monitoring agent can optionally use an explicit user ID and password when
connecting to the MS SQL Server. If you specify a blank user ID and password, the "Log on as" Windows
user ID and password credentials of the Microsoft SQL Server agent are used and the connection to the
server is established using Windows authentication. Table 9 describes possible combinations for specifying
the user ID and password.
Table 9. User ID and password combinations
User ID Password Outcome
A given string A given string Both strings are used for user ID and password when connecting to
the server.
A given string Blank (use double The user ID string and blank password are used when connecting
quotation marks ) to the server.
Blank (use double A given string The windows authentication information associated with the agent
quotation marks ) process (service) is used when connecting to the server.
Blank (use double Blank (use double The windows authentication information associated with the agent
quotation marks ) quotation marks ) process (service) is used when connecting to the server.

This monitoring agent contains the following Take Action commands:

v Database Check-up and Tune-up
v Dump Database
v Dump Transaction Log
v Rebuild Fragmented Indexes
v Refresh Query Optimizer Statistics
v Start SQL server
v Stop SQL server
v Update Space Usage Information

Database Check-up and Tune-up action

Performs a series of regular maintenance tasks to correct inconsistencies in the database and tune the
performance of the system. The Database Check-up and Tune-up Take Action includes the following
tasks:
v Runs DBCC CHECKDB, DBCC CHECKALLOC, DBCC CHECKCATALOG, and DBCC CHECKIDENT.
– DBCC CHECKDB checks each table to ensure that the following statuses are true:
- Index and data pages are correctly linked.
- Indexes are in proper sorted order.
- All pointers are consistent.
- Data information on each page is reasonable.
- Page offsets are reasonable.
– DBCC CHECKCATALOG identifies inconsistencies between system tables and checks the validity of
the last checkpoint.
– DBCC CHECKIDENT corrects disrupted identity column values that can result from ungraceful
shutdowns or unlogged operations.
v Rebuilds fragmented indexes and runs UPDATE STATISTICS to ensure that the query optimizer is
using the most recent information.

240 Microsoft SQL Server agent: User’s Guide

v Drops and reloads stored procedures.
v Runs DBCC UPDATEUSAGE to ensure more accurate space usage statistics.
Authorization role
Microsoft SQL Server permissions are sysadmin or db_owner.
Arguments
SQL Server Name (sql_server_name)
SQL Server instance name
Database Name (database_name)
Name of the database
Fragmentation Limit (fragmentation_limit)
Value for the index fragmentation limit. When the actual index fragmentation percentage
is greater than the entered number, the index is rebuilt. The default value is 30.
SQL Server ID (sql_server_id)

Note: For information about specifying the SQL Server login ID, see the "User ID and
password combinations" table in the "Take Action commands reference" chapter of the
IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see see the "User
ID and password combinations" table in the "Take Action commands reference" chapter of
the IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
Destination system
Managed system
Usage notes
Not applicable

Dump Database action

Performs a full database backup. The Dump Database Take Action does the following tasks:
v Provides a way to check the database integrity before backing up to ensure that the backup is viable
v Provides a way to designate an existing backup device, a temporary backup device, or the previous
backup device when possible
v Provides a way to specify a list of backup options. For example, you can append to a previous backup
or overwrite it. You can specify the type of backup to perform.

Note: The available backup options vary by version of Microsoft SQL Server.
v Checks the readability of the backup after it is complete. Verification consists of reading header
information to ensure that the backup set is complete and all volumes are readable. Data structure in
the backup volume is not verified.
v Writes some statistics on the backup procedure along with the header information on the backup
device to a log file.
Authorization role
Microsoft SQL Server permissions are sysadmin, db_owner, or db_backupoperator.
Arguments
See the Microsoft SQL Server documentation for more detailed information about the arguments,
including which options are required and formatting.
SQL Server Name (sql_server_name)
SQL Server instance name

Chapter 6. Take Action commands reference 241

 Database Name (database_name)
Name of the database
Backup Device (backup_device)
Name of the logical backup device. This value is ignored when the Use Last Backup
Device argument is 1.

Note: The Dump Database take action does not work if you specify physical backup
device name for this parameter.
Backup Options (backup_options)
A comma-separated list of options. For all options that take an argument, use either a
Microsoft SQL Server variable or literal text. You can use the following options:
BLOCKSIZE=number
Sets the block size to use when writing the backup. When writing to disk or tape,
the size is set automatically unless overridden. When writing to PIPE, the default
size is 65,536 unless overridden.
DESCRIPTION='text'
Specifies a description for the backup set. The maximum length is 255 characters.
The default value is a blank.
DIFFERENTIAL
Specifies a differential backup rather than a full backup. The default value is a
full backup.
EXPIREDATE=date or RETAINDAYS=number
Specifies when the backup file can be overwritten. Only one of the following
options may be used:
v EXPIREDATE specifies the expiration date.
v RETAINDAYS specifies how many days to retain the backup.
FORMAT or NOFORMAT
Writes the media header on all volumes used for the backup and rewrites the
backup device. An existing media header is overwritten, and all media contents
are invalidated. Any existing password is ignored.
Use this option on complete backup sets only. Using it on a single tape that
belongs to an existing striped backup set makes the entire backup set useless.
Using FORMAT implicitly sets INIT and SKIP. They do not have to be specified
separately.
INIT or NOINIT
INIT means the backup overwrites any previous backup on the backup device.
The media header is preserved. NOINIT means the backup is appended to the
previous backup, if any. The default value is NOINIT.
The backup does not overwrite if it encounters any of the following conditions:
v The media contains unexpired backup sets. You can specify SKIP to override
this condition.
v An explicitly given backup set name does not match the name on the backup
media. You can specify SKIP to override this condition.
v The backup media is password-protected.
v The backup media is encrypted.
MEDIADESCRIPTION= 'text'
Specifies a description for the media set. The maximum length is 128 characters.
The default value is BLANK.

242 Microsoft SQL Server agent: User’s Guide

 MEDIANAME='text'
Specifies the media name for the backup. When specified, if the existing
MEDIANAME on the backup media does not match, the backup fails.
NAME='text'
Specifies the name of the backup set. The maximum length is 128 characters. The
default value is BLANK.
RESTART
Use this option when restarting a backup operation that was interrupted. SQL
Server attempts to restart the backup where it was interrupted, which can save
time.
SKIP or NOSKIP
SKIP disables the checking for name match and expiration date of all backup sets
on the media. SKIP can be used with INIT. NOSKIP can be used with FORMAT
to override its default behavior. The default value is NOSKIP except where
otherwise noted.
STATS=percent
Specifies how often to write a progress message, which is expressed as a percent
complete. The default value is 10.
UNLOAD or NOUNLOAD
Use this option for tape devices only. UNLOAD specifies rewinding and
unloading (ejecting) the media when the backup is complete. The default value is
NOUNLOAD.
Validate Database Integrity (validate_db)
Runs DBCC CHECKDB, NEWALLOC, CHECKCATALOG, and CHECKIDENT to
determine if the database is corrupted. If the database fails the integrity checks, the
backup is not performed. Specify 1 to execute the integrity check, otherwise specify 0.
Use Last Backup Device (use_last_backup_device)
You can use the same backup device that you used the last time you backed up the
database. Specify 1 for this argument if you want to use the previous backup device. If
you specify 0, you must provide the name of the backup device, and the integrity of the
database is not validated.
SQL Server ID (sql_server_id)

Note: For information about specifying the SQL Server login ID, see the "User ID and
password combinations" table in the "Take Action commands reference" chapter of the
IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see the "User ID
and password combinations" table in the "Take Action commands reference" chapter of
the IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
Destination system
Managed system
Usage notes
When using this Take Action, consider the following information:
v To do backups to remote machines, this monitoring agent must have rights on the remote
machine and cannot be running under the local system account.
v Because the Take Action could fail and return a warning, do not make master backups to
striped devices.

Chapter 6. Take Action commands reference 243

 v Before backing up a database, back up a transaction log using the “Dump Transaction Log
action,” which clears the log and decreases the total time that is required to back up the
database. However, if the database backup is not done immediately or if it fails, all the logged
transactions could be lost. This Take Action does not truncate the log before backing up the
database.

Dump Transaction Log action

Backs up, truncates, or backs up and truncates a database’s transaction log. The Dump Transaction Log
Take Action does the following tasks:
v Provides a way to designate an existing backup device, a temporary backup device, or the previous
backup device when possible.
v Provides a way to specify a list of backup options. For example, you can append a backup to a
previous backup or overwrite the previous backup. You can specify the type of backup to perform. The
backup options available vary according to the version of Microsoft SQL Server.
v Checks the backup’s readability after the backup is complete. Verification consists of reading header
information to ensure that the backup set is complete and all volumes are readable. Data structure in
the backup volume is not verified.
v Writes some statistics about the backup procedure and writes the header information on the backup
device to a log file.
Authorization role
Microsoft SQL Server permissions are sysadmin, db_owner, or db_backupoperator.
Arguments
See the Microsoft SQL Server documentation for more detailed information about the arguments,
including which options are required and formatting.
SQL Server Name (sql_server_name)
SQL Server instance name
Database Name (database_name)
Name of the database
Backup Device (backup_device)
Name of the logical backup device. This value is ignored when the Use Last Backup
Device argument is set to 1.

Note: The Dump Transaction Log take action does not work if you specify physical
backup device name for this parameter.
Backup Options (backup_options)
A comma-separated list of options. For all options that take an argument, use either a
Microsoft SQL Server variable or literal text. You can use the following options:
BLOCKSIZE=number
Sets the block size to use when writing the backup. When writing to disk or tape,
the size is set automatically unless overridden. When writing to PIPE, the default
size is 65,536 unless overridden.
DESCRIPTION='text'
Specifies a description for the backup set. The maximum length is 255 characters.
The default value is a blank.
DIFFERENTIAL
Specifies a differential backup rather than a full backup. The default value is a
full backup.

244 Microsoft SQL Server agent: User’s Guide

EXPIREDATE=date or RETAINDAYS=number
Specifies when the backup file may be overwritten. Only one of these options
may be used. EXPIREDATE specifies the expiration date. RETAINDAYS specifies
how many days to retain the backup.
FORMAT or NOFORMAT
Writes the media header on all volumes used for the backup and rewrites the
backup device. An existing media header is overwritten and all media contents
are invalidated. Any existing password is ignored.
Use this option on complete backup sets only. Using it on a single tape that
belongs to an existing striped backup set renders the entire backup set useless.
Using FORMAT implicitly sets INIT and SKIP. They do not have to be specified
separately.
INIT or NOINIT
INIT means the backup overwrites any previous backup on the backup device.
The media header is preserved. NOINIT means the backup is appended to the
previous backup, if any. The default value is NOINIT.
The backup does not overwrite if it encounters any of the following conditions:
v The media contains unexpired backup sets. You can specify SKIP to override
this condition.
v An explicitly given backup set name does not match the name on the backup
media. You can specify SKIP to override this condition.
v The backup media is password-protected.
v The backup media is encrypted.
MEDIADESCRIPTION= 'text'
Specifies a description for the media set. The maximum length is 128 characters.
The default value is BLANK.
MEDIANAME='text'
Specifies the media name for the backup. When specified, if the existing
MEDIANAME on the backup media does not match, the backup fails.
NAME='text'
Specifies the name of the backup set. The maximum length is 128 characters. The
default value is BLANK.
RESTART
Use this option when restarting a backup operation that was interrupted. SQL
Server attempts to restart the backup where it was interrupted, which can save
time.
SKIP or NOSKIP
SKIP disables the checking for name match and expiration date of all backup sets
on the media. SKIP can be used with INIT. NOSKIP can be used with FORMAT
to override its default behavior. The default value is NOSKIP except where
otherwise noted.
STATS=percent
Specifies how often to write a progress message, expressed as a percent complete.
The default value is 10.
UNLOAD or NOUNLOAD
Use this option for tape devices only. UNLOAD specifies rewinding and
unloading (ejecting) the media when the backup is complete. The default value is
NOUNLOAD.

Chapter 6. Take Action commands reference 245

 Dump Options (dump_option)
Specifies how to backup and/or truncate a transaction log.

Note: The dump option names should be passed literally as strings when issuing this
Take Action.
Use one of the following valid choices:
v backup backs up the transaction log, but does not truncate it.
v BackupAndTruncate backs up the transaction log and truncates it. Truncating the log
clears it of all non-active transactions. Use this option only when the transaction log
and the data are on separate device fragments.
v Truncate truncates the transaction log, but does not back it up. This operation is
logged.
v TruncateNoLog, which is used when log is full, truncates the transaction log, but does
not back it up. It is the only choice when the log is full. This operation is not logged.
Use Last Backup Device (use_last_backup_device)
You can use the same backup device that you used the last time you backed up the
database. Specify 1 for this argument if you want to use the previous backup device. If
you specify 0, you must provide the name of the backup device, and the integrity of the
database is not validated.
SQL Server ID (sql_server_id)

Note: For information about specifying the SQL Server login ID, see the "User ID and
password combinations" table in the "Take Action commands reference" chapter of the
IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see the "User ID
and password combinations" table in the "Take Action commands reference" chapter of
the IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
Destination system
Managed system
Usage notes
When using this Take Action, observe the following information:
v If the media fails, specify backup so that the transaction log can be dumped even if the
database is inaccessible. The backup option provides up-to-the-minute media recovery when
the master database and the log portion of the user database reside on undamaged database
devices and when only the data portion of the user database is damaged. Specify the backup
option to back up the master database log on its own.
v The “Dump Database action” on page 241 backs up both the data and the log. The Dump
Transaction Take Action backs up only the transaction log and not the data. When you dump a
database, you are doing a database backup. When you dump a transaction log, you could be
backing it up, truncating it, or both.

Rebuild Fragmented Indexes action

Rebuilds clustered and non-clustered indexes on tables. You can specify the level of fragmentation that
triggers reindexing.
Authorization role
Microsoft SQL Server permissions are sysadmin or db_owner.
Arguments

246 Microsoft SQL Server agent: User’s Guide

 SQL Server Name (sql_server_name)
SQL Server instance name
Database Name (database_name)
Name of the database
Table Name (table_name)
Updates the indexes for a specified table or for all tables. May have an empty string
value. If blank, this argument updates indexes for all tables.
Index Name (index_name)
Updates indexes of a particular name that you specify in this field, or all indexes. May
have an empty string value. If this argument is blank, it updates all indexes.
Rebuild if fragmentation % greater than (fragmentation_limit)
Rebuilds the index when the index reaches this percentage of fragmentation. If the actual
index fragmentation percentage is greater than the number you enter here, the Take
Action rebuilds the index. To rebuild the indexes under all circumstances, use zero. The
default value is 30 percent.
Fill Factor (fill_factor)
Specifies how full you want the new page to be. Enter a value that is the percentage of
the page to be filled. For example, entering 20 means that you want to fill one-fifth of the
page, leaving 80 percent free. To rebuild with the same FILLFACTOR used in the
previous rebuild, specify zero. If the actual fill factor is greater than the number you
enter, this Take Action rebuilds the index using the specified fill factor. Leaving some
space on a page can improve the performance on clustered indexes. If you specify a low
fill factor, remember that the database takes up more disk space.
SQL Server ID (sql_server_id)

Note: For information about specifying the SQL Server login ID, see the "User ID and
password combinations" table in the "Take Action commands reference" chapter of the
IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see the "User ID
and password combinations" table in the "Take Action commands reference" chapter of
the IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
Table 10 shows how entries in the Table Name and Index Name arguments determine which
indexes and tables are updated.
Table 10. Index and table updates
Table Name Table Exists Index Name Index Exists Outcome
Entered Y Entered Y Updates the specified index on the specified
table.
Entered Y Entered N Error. Specified index does not exist.
Entered Y Blank (use - Updates all indexes on the specified table.
double
quotation
marks “”)
Entered N Entered Y Error. Specified index does not exist.
Entered N Entered N Error. Specified index does not exist.

Chapter 6. Take Action commands reference 247

Table 10. Index and table updates (continued)
Table Name Table Exists Index Name Index Exists Outcome
Entered N Blank (use - Error. Specified index does not exist.
double
quotation
marks “”)
Blank (use - Entered Y Updates all indexes on the specified table
double
quotation
marks “”)
Blank (use - Entered N Error. Specified index does not exist.
double
quotation
marks “”)
Blank (use - Blank (use - Updates all indexes.
double double
quotation quotation
marks “”) marks “”)

Destination system
Managed system
Usage notes
You can improve table fragmentation only if the table has a clustered index that can be rebuilt.
Table data is directly related to the clustered index because it is the leaf level of the index. The
Take Action first checks the clustered index (INDID = 1).
Rebuilding the clustered index reorders the data pages and causes all other indexes to be rebuilt.
If a table has no clustered index or the clustered index is not fragmented (non-clustered index
fragmentation), you might still want to run this Take Action. It checks the non-clustered indexes
for fragmentation, which the Take Action automatically rebuilds on an individual basis if
necessary. Non-clustered indexes have an INDID > 1.

Refresh Query Optimizer Statistics action

Refreshes the optimizer statistics for all indexes on a table or for a specific index and forces every affected
stored procedure to recompile before it is run again.
Authorization role
Microsoft SQL Server permissions are sysadmin or the table owner.
Arguments
SQL Server Name (sql_server_name)
SQL Server instance name
Database Name (database_name)
Name of the database
Table Name (table_name)
Updates the indexes for a specified table. May have an empty string value. If blank, this
argument updates indexes for all tables.
Index Name (index_name)
Updates the specified indexes. May have an empty string value. If this argument is blank,
it updates all indexes.
SQL Server ID (sql_server_id)

248 Microsoft SQL Server agent: User’s Guide

 Note: For information about specifying the SQL Server login ID, see the "User ID and
password combinations" table in the "Take Action commands reference" chapter of the
IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see the "User ID
and password combinations" table in the "Take Action commands reference" chapter of
the IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
Table 11 shows how entries in the Table Name and Index Name arguments determine which
indexes and tables are updated.
Table 11. Index and table updates
Table Name Table Exists Index Name Index Exists Outcome
Entered Y Entered Y Updates the specified index on the specified
table.
Entered Y Entered N Error. Specified index does not exist.
Entered Y Blank (use - Updates all indexes on the specified table.
double
quotation
marks "")
Entered N Entered Y Error. Specified index does not exist.
Entered N Entered N Error. Specified index does not exist.
Entered N Blank (use - Error. Specified index does not exist.
double
quotation
marks “”)
Blank (use - Entered Y Updates all indexes on the specified table.
double
quotation
marks “”)
Blank (use - Entered N Error. Specified index does not exist.
double
quotation
marks “”)
Blank (use - Blank (use - Updates all indexes.
double double
quotation quotation
marks “”) marks “”)

Destination system
Managed system
Usage notes
This Take Action is limited by the sp_recompile stored procedure. For example, you cannot use
sp_recompile with system tables. If you must have stored procedures based solely on system
tables that were dropped and recreated, use the “Database Check-up and Tune-up action” on
page 240. If you update a single index on a table, all stored procedures based on that table are
recompiled.

Start SQL Server action

Starts any or all of the SQL Server services. The command starts an instance of SQL Server. By default,
the instance name is MSSQLServer. If you have a non-default instance name, replace net start
MSSQLSERVER with net start MSSQL$instancename in the command area.

Chapter 6. Take Action commands reference 249

Authorization role
None
Arguments
MS SQL Server Windows Service Name
The Windows service name of the MS SQL Server instance you want to start. The default
service name that the default SQL Server instance uses is MSSQLSERVER. This Take
Action uses that service name as the default. To start a named MS SQL Server instance,
set the value of this argument to the service name that is associated with the named SQL
Server instance.
Destination system
Managed system
Usage notes
Not applicable

Stop SQL Server action

Stops any or all of the SQL Server services. The command stops the instance of the SQL Server. By
default, the instance name is MSSQLSERVER. If you are using a non-default instance name, replace
MSSQLSERVER with MSSQL$instancename.
Authorization role
None
Arguments
MS SQL Server Windows Service Name
The Windows service name of the MS SQL Server instance you want to stop. The default
service name that the default SQL Server instance uses is MSSQLSERVER. This Take
Action uses that service name as the default. To stop a named MS SQL Server instance,
set the value of this argument to the service name that is associated with the named SQL
Server instance.
Destination system
Managed system
Usage notes
In the command, you can add /Y to stop dependent services too if they are running (for example,
net stop MSSQSERVER /Y). If the dependent service SQLServerAgent is running and /Y is not
added in the command, none of the SQL services is stopped.

Update Space Usage Information action

Corrects inaccuracies in the sysindexes table that can cause incorrect space usage reports by the
sp_spaceused system stored procedure.
Authorization role
Microsoft SQL Server permissions are sysadmin or db_owner.
Arguments
SQL Server Name (sql_server_name)
SQL Server instance name
Database Name (database_name)
Name of the database
Table Name (table_name)
Updates the space usage information for a specific table or for all tables. If blank, this
argument updates indexes for all tables.

250 Microsoft SQL Server agent: User’s Guide

 Index Name (index_name)
Updates the space usage information for indexes with a particular name, which you
specify in this field, or all indexes. If this argument is blank, it updates all indexes. The
Table 12 table shows how entries in the Table Name and Index Name arguments
determine which indexes and tables are updated.
Table 12. Index and table updates
Index name Table Name Outcome
Exists Exists Updates only the specified index on
the specified table.
Exists Does not exist Error. Specified index does not exist.
Exists Blank (use double quotation marks Updates all indexes on the specified
“”) table.
Does not exist Exists Error. Specified table does not exist.
Does not exist Does not exist Error. Specified table does not exist.
Does not exist Blank (use double quotation marks Error. Specified table does not exist.
“”)
Blank (use double quotation marks Exists Updates all indexes that share the
“”) specified name.
Blank (use double quotation marks Does not exist Error. Specified table does not exist.
“”)
Blank (use double quotation marks Blank (use double quotation marks Updates all indexes.
“”) “”)

SQL Server ID (sql_server_id)

For information about specifying the SQL Server login ID, see the "User ID and password
combinations" table in the "Take Action commands reference" chapter of the IBM Tivoli
Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
SQL Server Password (sql_server_password)
For information about specifying the SQL Server login password, see the "User ID and
password combinations" table in the "Take Action commands reference" chapter of the
IBM Tivoli Monitoring for Microsoft Applications: Microsoft SQL Server User's Guide.
Destination system
Managed system
Usage notes
In the command, you can add /Y to stop dependent services too if they are running (for example,
net stop MSSQSERVER /Y). If the dependent service SQLServerAgent is running and /Y is not
added in the command, none of the SQL services is stopped.

Chapter 6. Take Action commands reference 251

252 Microsoft SQL Server agent: User’s Guide
Chapter 7. Policies reference
Policies are an advanced automation technique for implementing more complex workflow strategies than
you can create through simple automation.

A policy is a set of automated system processes that can perform actions, schedule work for users, or
automate manual tasks. You use the Workflow Editor to design policies. You control the order in which
the policy executes a series of automated steps, which are also called activities. Policies are connected to
create a workflow. After an activity is completed, Tivoli Enterprise Portal receives return code feedback
and advanced automation logic responds with subsequent activities prescribed by the feedback.

Note: The predefined policies provided with this monitoring agent are not read-only. Do not edit these
policies and save over them. Software updates will write over any of the changes that you make to these
policies. Instead, clone the policies that you want to change to suit your enterprise.

More information about policies

For more information about working with policies, see the IBM Tivoli Monitoring User's Guide.

For information about using the Workflow Editor, see the IBM Tivoli Monitoring Administrator's Guide or
the Tivoli Enterprise Portal online help.

For a list of the policies for this monitoring agent and a description of each policy, see Predefined policies
section and the information for each individual policy.

Predefined policies
You can create policies for any agent. The Microsoft SQL Server agent provides one predefined policy.

Policy descriptions
The policy descriptions provide information about the actions that you can take when situations are
triggered in your network.

MS_SQL_DB_free_space_critical
This policy provides actions to take on low free space on the MS SQL server. This policy is triggered by
the MS_SQL_DB_Freespace_Critical situation. When triggered, the workflow requires that you select one
of the following actions:
v Run the koqignor command.
v Run the koqmail command as follows:
Where:
database user id
Connection user ID
password
Password as a sysadmin authority
email id
Email address of the database administrator

© Copyright IBM Corp. 2005, 2012 253

254 Microsoft SQL Server agent: User’s Guide
Chapter 8. Tivoli Common Reporting for the monitoring agent
You can use the Tivoli Common Reporting application to generate reports for the Microsoft SQL Server
agent. For more information about Tivoli Common Reporting, such as prerequisites, importing reports,
and running reports, see the IBM Tivoli Monitoring Administrator's Guide V6.2.3.

IBM Tivoli Monitoring for Microsoft Applications V6.3 reports are historical reports that include
summarized data that is collected in the Tivoli Data Warehouse. These reports are built to run only
against the IBM Tivoli Monitoring for Microsoft SQL Server agent V6.3.

The reports can be administered and run on Tivoli Common Reporting V1.3, V2.1, and V2.1.1, Fix Pack 6.

For more information about Tivoli Common Reporting, see the developerWorks® website
(http://www.ibm.com/developerworks/spaces/tcr).

This version of Tivoli Common Reporting includes Cognos Business Intelligence and Reporting V8.4.

Cognos-based report packages

The Cognos-based Tivoli Common Reporting tool is used to create, view, and manage reports for the
Tivoli group of products.

You can use the Cognos reports to analyze resource information such as availability, utilization,
performance, and so on. With Cognos reports, you can evaluate the key metrics of the computers that are
on the managed environment of your organization.

You can use the Tivoli Common Reporting tool to:

v Create custom reports by using the drag-and-drop feature integrated with the web-based editor.
v Schedule, share, secure, and administer reports in a single interface.
v Save the report in HTML, PDF, Excel, XML, or CSV file formats.
v Share reports by email or save the reports in a file system for later use.

The following databases are supported for all reports:

v DB2® V9.5 and V9.7, Fix Pack 2
v Oracle 10g and 11g
v SQL Server 2005 and 2008
You can use Tivoli Common Reporting V1.3, V2.1, and V2.1.1, Fix Pack 6 software that is shipped with
IBM Tivoli Monitoring V6.2.3, or later to administer, run, and edit Cognos reports. For more information
about Tivoli Common Reporting, see the Tivoli Common Reporting Information Center
(http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ic-home.html).

Prerequisites
Before you run the Cognos-based reports, ensure that the prerequisites that are required for installing and
running Tivoli Common Reporting packages are met.

Procedure
1. Install Tivoli Common Reporting. For more information, see the documentation in the IBM Tivoli
Common Reporting Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/
topic/com.ibm.tivoli.tcr.doc_211/ic-home.html).

© Copyright IBM Corp. 2005, 2012 255

 To ensure that Tivoli Common Reporting is running, go to:
https://machine_name:port_number/ibm/console/.
2. Obtain the reports package from the product media and extract the package.
The Cognos reports are available in the following package: Product Media root/REPORTS/KOQ/
ITCAMMA_SQLServer_V630_Cognos_Reports.
3. Copy this package in a directory on any drive of the same computer where the Tivoli Common
Reporting Server is installed, and extract the package in the same directory.
The directory contents include:
v Database scripts required to prepare the Tivoli Data Warehouse for Cognos reports.
v A report installer that imports the reports into Tivoli Common Reporting and sets up the database
connection.
4. Open the setup.batch file, and verify that the specified drive is the same drive where the Tivoli
Common Reporting Server is installed. If the specified drive is not correct, edit the setup.batch file to
specify the correct drive.
For example, change the TCR_DEFAULT_DIR=C:\IBM\tivoli\tip to TCR_DEFAULT_DIR=F:\IBM\tivoli\tip
if the Tivoli Common Reporting Server is installed on the F drive.
5. Configure historical collection for Microsoft SQL Server agent V6.3 and the IBM Tivoli Warehouse
Summarization and Pruning Agent. After IBM Tivoli Monitoring V6.2.3, Fix Pack 1, or later is
installed and the Microsoft SQL Server agent V6.3 is installed and configured, configure historical
collection. Also, configure the Warehouse Summarization and Pruning agent with or without shifts
enabled. For more information about how to enable historical collection and configure the Warehouse
Summarization and Pruning agent in IBM Tivoli Monitoring, see the following documentation:
v http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/
history_manage_intro.htm
v http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/
history_manage_collection.htm

Note: Historical collection and daily and hourly summarization must be enabled for all attribute
groups of Microsoft SQL Server agent V6.3.
To ensure that the required views are present, run the following query against the Tivoli Data
Warehouse:
v DB2: Select distinct "VIEWNAME" from SYSCAT.VIEWS where "VIEWNAME" like ’ %V’
v Oracle: Select distinct "OBJECT_NAME" from OBJ where "OBJECT_TYPE" like ’%V’
v MS SQL Server: Select distinct "NAME" from SYS.OBJECTS where "TYPE_DESC" like ’%V’
6. Prepare the Tivoli Data Warehouse to support Cognos dimensions.
Preparing the Tivoli Data Warehouse for Tivoli Common Reporting includes creating the IBM_TRAM
dimensions, which are required for running the Cognos reports and using the data models.
See "Creating shared dimension tables and populating the time dimensions table" in the IBM Tivoli
Monitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.3, Fix Pack 1 Information Center
(http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/
tcr_reports_dimensionsshared.htm).
7. Connect to the Tivoli Data Warehouse by using the database client over Open Database Connectivity
(ODBC).
Cognos uses ODBC to connect to the database. Install a database client on the Tivoli Common
Reporting Server and connect it to the Tivoli Data Warehouse.
See "Connecting to the Tivoli Data Warehouse using the database client over ODBC" in the IBM Tivoli
Monitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.3, Fix Pack 1 Information Center
(http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/adminuse/
tcr_tdwconnect.htm).

Important: All prerequisites described here must be met or the reports cannot run.

256 Microsoft SQL Server agent: User’s Guide

Importing Cognos report packages
You must import the Cognos report package that contains the Microsoft SQL Server agent data model
and reports into Tivoli Common Reporting. Before you import the Cognos report package, ensure that all
the prerequisites have been met. Otherwise, reports cannot run.

For Tivoli Common Reporting V1.3, use one of the following options to import the Cognos report
package:
v Importing by running the reports installer – For information about running the reports installer to
import the Cognos report package, see "Installing and running IBM Cognos reports" in the IBM Tivoli
Monitoring Administrator's Guide at the IBM Tivoli Monitoring V6.2.2, Fix Pack 2 Information Center
(http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/
tcr_install_itm.htm).
v Importing manually – For information about manually importing the reports package, see “Importing
report packages” at the IBM Tivoli Systems Management Information Center (http://pic.dhe.ibm.com/
infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr_cog.doc/ttcr_cog_import.html).

For Tivoli Common Reporting V2.1, or later, see "Importing report packages" at the Tivoli Common
Reporting Information Center (http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/topic/
com.ibm.tivoli.tcr.doc_211/ttcr_import.html).

If you are using a schema other than ITMUSER, you must complete the following steps for the data
model and reports to run:
1. Verify that you have completed the following steps:
a. Altered the schema name in the database scripts when you prepared the Tivoli Data Warehouse
for Cognos dimensions in Step 6 on page 256 of “Prerequisites” on page 255.
b. Installed the reports package by using the Reports installer as explained in "Importing reports by
using the report installer" topic in the IBM Tivoli Monitoring Administrator's Guide. To verify that
you have installed the reports package, go to Tivoli Common Reporting and make sure you can
see "ITCAMMA SQLServer V630 Cognos Reports" in the Public Folders of IBM Cognos
Connection.
2. Install and configure the Cognos Framework Manager, which is the data modeling tool. See the
instructions at the Tivoli Common Reporting Information Center (http://pic.dhe.ibm.com/
infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc_211/ttcr_import.html).
3. Open the Framework Manager. Select File > Open. Browse to the extracted ITCAMMA SQLServer
V630 Cognos Reports reports package. Browse to the model folder and select the ITCAMMA SQLServer
V630 Cognos Reports.cpf file.
4. If you are prompted to enter login credentials, enter your tipadmin user ID and password.
5. After the IBM Tivoli Monitoring for SQL Servers data model in the Framework Manager opens,
expand Data Sources under Tivoli Reporting and Analytics Model in the Project Viewer.
6. Select TDW under Data Sources.
7. When you select TDW, the Properties view is updated with information about the Tivoli Data
Warehouse data source. By default, the Properties view is located at the bottom center of the screen.
If the Properties view is not visible, select View > Properties.
8. In the Properties, edit the Schema field. Change it from ITMUSER to your schema name.
9. Save the project.
10. In the Project Viewer, expand Packages.
11. Right-click ITCAMMA SQLServer V630 Cognos Reports.
12. Select Publish Packages. The Publish Wizard opens.
13. Keep the default selection and click Next.
14. Click Next on the next screen.

Chapter 8. Tivoli Common Reporting for the monitoring agent 257

15. Clear the Verify the package before publishing check box.
16. Click Publish. A window is displayed that alerts you that A package with that name already
exists and asks Do you want to publish this package?
17. Click Yes.
18. Go back to Tivoli Common Reporting and check if the Modified field of "ITCAMMA SQLServer
V630 Cognos Reports" in the Public Folders of IBM Cognos Connection shows the time of
publishing.
After completing these steps, you can run any report from the IBM Tivoli Monitoring for ITCAMMA
SQLServer V630 Cognos Reports package.

Cognos data models and reports

When all the prerequisites are met, you can use the Tivoli Integrated Portal interface to create, modify,
and manage Cognos reports.

In Tivoli Common Reporting, the historical data that is collected by the agent is used to build ad hoc
reports and queries. The package that you import into Tivoli Common Reporting contains a Cognos data
model. All the reports that you create in Tivoli Common Reporting are based on the data model.

Cognos data models are virtual star schema models that contain facts and dimensions. Facts are
measurable quantities that can be aggregated, such as CPU utilization and number of processors.
Dimensions are the main identifiers by which facts can be grouped, aggregated, and organized. For
example, time and server are dimensions by which the fact CPU utilization can be grouped.

The facts in the data model are organized into the folders by their summarization type, such as Daily and
Hourly. The Daily and the Hourly folders contain attribute groups that correspond to tables or views in
the data warehouse. Each attribute group contains a group of facts and measures.

The data model is built on top of the data warehouse to organize data. The data model contains the
Tivoli Reporting and Analytics Model (TRAM) Shared Dimensions, which are shared across Tivoli by
products such as Time.

To create reports in Tivoli Common Reporting tool, you can use one of the following report authoring
tools:
v Query Studio: A web-based product that is used mostly for ad hoc reporting. Users can create simple
queries and reports, and apply basic formatting to the reports.
v Report Studio: A web-based tool that is used by technical users and professional report writers for
creating advanced reports. Users can retrieve data from multiple databases and create sophisticated
reports that have multiple pages and multiple queries.

Reports for the monitoring agent

You can verify whether the reporting functionality is installed and configured correctly by running the
reports for the Microsoft SQL Server agent. The Microsoft SQL Server agent reporting package that you
imported into Tivoli Common Reporting includes 10 reports. By using these reports, you can monitor the
reporting activity and see what a typical Cognos report includes. These reports are available in the
Common Reporting panel in Tivoli Common Reporting. The following tables describe these reports.
Table 13. Top Processes by CPU report
Name Top Processes by CPU report
Description This report displays the relative percentage of the CPU that is used by the selected server
processes compared to other server processes and the percentage of processes that are being
blocked.

258 Microsoft SQL Server agent: User’s Guide

Table 13. Top Processes by CPU report (continued)
Purpose You can use this report to provide information about the process details of the selected SQL
Server.
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Summarization Selection
Summarization Type
Select the summarization type, such as Hourly, Daily, Weekly, Monthly,
Quarterly, Yearly, or Default from the list. If you select the Default option, the
summarization type is calculated according to the number of days in the date
range.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Display Options
Server Name
Select the name of the server from the Server Name list.
Number of Processes to Display
Select the processes from the list

Tables/Views v MS_SQL_Process_Detail_%V
Used
v MS_SQL_Process_Summary_%V
Output The Top Processes by Current CPU % Used chart displays the current percentage of CPU that is
used for different processes on a selected server.
Note: You can change the number of processes to display to any positive integer. However, the
default value is 5.
The Processes Blocked % chart displays the percentage of processes that are blocked on a server
for a selected period.
Usage The administrators can use this report to observe the relative percentage of the CPU that is
used and the percentage of processes that are blocked.

Table 14. Server Transactions Details report

Name Server Transactions Details report
Description This report displays the replication latency between transactions, the number of transactions
that occurred in current interval, and the number of active transactions for the database.

Chapter 8. Tivoli Common Reporting for the monitoring agent 259

Table 14. Server Transactions Details report (continued)
Purpose You can use this report to observe the performance details of a database.
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Summarization Selection
Summarization Type
Select the summarization type, such as Hourly, Daily, Weekly, Monthly,
Quarterly, Yearly, or Default from the list. If you select the Default option, the
summarization type is calculated according to the number of days in the date
range.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Display Options
Server Name
Select the name of the server from the Server Name list.
Database Name
Select the name of the database from the list.

Tables or views MS_SQL_Database_Detail_%V

used
Output The AVG Replication Latency between Transactions chart displays average replication latency
for the selected databases on a server.

The AVG Transactions Per Sec chart displays the number of transactions per second for selected
databases on a server.

The Number of Active Transactions chart displays the maximum number of active transactions
for the selected databases on a server.

The Database Details table that follows the preceding charts, displays the same information
Usage The IT administrator can use this report to observe hindrance in the replication Reports 19
process, transactions started per second in the current interval, and the number of active
transactions for the database.

Table 15. Wait Time and Requests of Locks report

Name Wait Time and Requests of Locks report

260 Microsoft SQL Server agent: User’s Guide

Table 15. Wait Time and Requests of Locks report (continued)
Description This report displays the total wait time for locks in the last second and the total number of locks
that block the other processes.
Purpose You can use this report to provide information about the lock requests and wait time.
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Summarization Selection
Summarization Type
Select the summarization type, such as Hourly, Daily, Weekly, Monthly,
Quarterly, Yearly, or Default from the list. If you select the Default option, the
summarization type is calculated according to the number of days in the date
range.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Display Options
Server Name
Select the name of the server from the Server Name list.

Tables or views v MS_SQL_Lock_Resource_Type_Summary_%V

used
v MS_SQL_Server_Summary_%V
Output
The Average Lock Wait Time (in MS) Over a Period of Time line chart displays the average wait
time (in milliseconds) for locks in the last second over a period of time.

The Total Number of Blocking Lock Requests line chart displays the number of lock requests
that block the other processes over a period of time.
Usage The IT administrators can use this report to observe the total wait time for locks in the last
second and the number of locks that block the other processes over a period of time.

Table 16. Space Utilization by Database report

Name Space Utilization by Database report
Description This report displays the free space (in MB), the percentage of free space, the amount of space
used as percentage of the total space, the percentage of free space in the transaction log, and the
percentage of transaction log that contains the database.

Chapter 8. Tivoli Common Reporting for the monitoring agent 261

Table 16. Space Utilization by Database report (continued)
Purpose You can use this report to provide the space details of a database.
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select an end date from the calendar and an end time from the time widget.
You must select both date and time.
Display Options
Server Name
Select the name of the server from the Server Name list.
Database Name
Select the name of the database from the list.
Attribute Selection
Select the space used or the space available.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Thresholds
You can enter the threshold values that are represented by the status. The values
represent the default threshold values for the Space Used attribute.
Tables or views MS_SQL_Database_Detail_HV
used
Output
The Average Lock Wait Time (in MS) Over a Period of Time chart displays the average wait
time (in MS) for locks of the selected database over a period of time.

The Average Database Free Space % Per Hour Over a Period of Time chart displays the
percentage of the used space (in megabytes) of the selected database over a period of time.

The Average Log Free Space % Per Hour Over a Period of Time chart displays the percentage of
the used space of the selected database log over a period of time.
Usage The IT administrators can use this report to observer the used space for data and used space for
log, for a selected database.

Table 17. Free Space Availability report

Name Free Space Availability report
Description This report displays the lowest percentage of free space in the data segment on a device that is
allocated to a database and the lowest percentage of free space in the log segment on a device
that is allocated to a transaction log.

262 Microsoft SQL Server agent: User’s Guide

Table 17. Free Space Availability report (continued)
Purpose You can use this report to provide information about the free space in a data segment and a log
segment.
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select an end date from the calendar and an end time from the time widget.
You must select both date and time.
Display Options
Server Name
Select the name of the server from the Server Name list.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Thresholds
You can enter the threshold values that are represented by the status. The values
represent the default threshold values.
Tables or views MS_SQL_Database_Summary_HV
used
Output The Minimum Data Free Space % per hour over a period of time chart displays the minimum
percentage of data free space on the selected server.

The Minimum Log Free Space % per hour over a period of time chart displays the minimum
percentage of log free space that is allocated to a database transaction log for a selected server.
Usage The IT administrator can use this report to observe the free space in a database and in a log.

Table 18. Database Status Availability report

Name Database Status Availability report
Description This report displays the availability of the database for usage.
Purpose You can use this report to provide information about the status of a database.

Chapter 8. Tivoli Common Reporting for the monitoring agent 263

Table 18. Database Status Availability report (continued)
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Display Options
Server Name
Select the name of the server from the Server Name list.
Database Name
Select the name of the database from the list.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Thresholds
You can enter the threshold values that are represented by the status. The values
represent the default threshold values.
Tables or views MS_SQL_Database_Detail_HV
used
Output The Average Available % of Database per hour over a period of time chart displays the
percentage of the availability of the database.
Usage The IT administrators can use this report to observe the status of a database on a selected SQL
Server.

Table 19. CPU Utilization report

Name CPU Utilization report
Description This report displays the percentage of the CPU memory that is used by all the processes
including the SQL Server processes .
Purpose You can use this report to provide information about the CPU utilization of all the processes
including the SQL Server processes.

264 Microsoft SQL Server agent: User’s Guide

Table 19. CPU Utilization report (continued)
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Display Options
Server Name
Select the name of the server from the Server Name list.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Thresholds
You can enter the threshold values that are represented by the status. The following
values represent the default threshold values:
v Good: Less than or equal to 20
v Fair: Between 20 and 30
v Warning: Between 30 and 50
v Bad: Between 50 and 80
v Critical: Above 80

Tables or views MS_SQL_Server_Summary_HV

used
Output The Average Total CPU % Used Per Hour by SQL Processes over a period of time chart displays
the percentage of the CPU time that is utilized by the SQL processes.

The Average Total CPU % Used Per Hour by All Processes over a period of time chart displays
the total percentage of the CPU time that is utilized by the operating system.
Usage The IT administrator can use this report to compare the relative CPU percentage used by the
processes.

Table 20. Processes Details report

Name Processes Details report
Description This report displays the total number of processes that are started and are blocked since the
server was started.
Purpose You can use the report to provide information about the processes on a selected SQL Server.

Chapter 8. Tivoli Common Reporting for the monitoring agent 265

Table 20. Processes Details report (continued)
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Display Options
Server Name
Select the name of the server from the Server Name list.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Thresholds
You can enter the threshold values that are represented by the status. The following
values represent the default threshold values:
v Good: Less than or equal to 20
v Fair: Between 20 and 30
v Warning: Between 30 and 50
v Bad: Between 50 and 80
v Critical: Above 80

Tables or views MS_SQL_Process_Summary_HV

used
Output The Average Total Processes Blocked per hour over a period of time chart displays the total
processes that are blocked for a selected period.

The Average Processes Blocked (%) per hour over a period of time chart displays the percentage
of processes that are blocked for a selected period.
Usage The IT administrator can use this report to compare the number of blocked processes with the
number of total processes that are present.

Table 21. Server Lock Details report

Name Server Lock Details report
Description This report displays the number of lock conversions per second, the number of lock requests per
second that timed out, total wait time for locks in the last second, and the total number of
current locks that are blocking other processes.
Purpose You can use this report to provide information about locks on the different resource types.

266 Microsoft SQL Server agent: User’s Guide

Table 21. Server Lock Details report (continued)
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Summarization Selection
Summarization Type
Select the summarization type, such as Hourly, Daily, Weekly, Monthly,
Quarterly, Yearly, or Default from the list. If you select the Default option, the
summarization type is calculated according to the number of days in the date
range.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Display Options
Server Name
Select the name of the server from the Server Name list.

Tables or views v MS_SQL_Lock_Resource_Type_Summary_%V

used
v MS_SQL_Server_Summary_%V
Output The Number of Lock Requests/Timeouts in a Sec line chart displays the lock requests per
second and lock timeouts per second.

The Average Total Wait Time in Last Sec line chart displays total wait time (in milliseconds) for
locks in the last second for the selected server.

The table following the chart displays bar charts for average blocking requests and maximum
lock wait time. Click the server name in the table to drill down to the Wait Time and Requests
of Locks report.
Usage The IT administrator can use this report to observe the number of new locks and lock
conversions, and the number of timed out lock requests. The total wait time (in milliseconds) for
locks to release in the last second and the number of blocking locks indicate that the processes
are held up because of lock contention. Click the server name in the table to drill down to the
Wait Time and Requests of Locks report.

Table 22. Servers with Most Failed Jobs report

Name Servers with Most Failed Jobs report
Description This report provides the job summary of the top servers that display the highest number of
failed jobs since the agent was started.

Chapter 8. Tivoli Common Reporting for the monitoring agent 267

Table 22. Servers with Most Failed Jobs report (continued)
Purpose You can use this report to provide information about locks on the different resource types.
Parameters
Date Range
Report period
Select the report period from a predefined date range, such as Last Week,
Current Month, Last 30 Days, and so on. You can also enter a start date, an
end date, and the time for the reporting period.
Start Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
End Date
Select a start date from the calendar and the start time from the time widget.
You must select both date and time.
Summarization Selection
Summarization Type
Select the summarization type, such as Hourly, Daily, Weekly, Monthly,
Quarterly, Yearly, or Default from the list. If you select the Default option, the
summarization type is calculated according to the number of days in the date
range.
Shift Period
If shift period is enabled, the hourly tables display the Shift Period as 1
(off-peak hours) or 2 (peak hours), depending on the peak and off-peak hours
that are configured in the data warehouse. In the daily tables, the value 1
corresponds to peak hours, the value 2 corresponds to off-peak hours, and the
value -1 corresponds to the summarized value for that day. If shifts are not
enabled, the default value is -1.
Vacation Period
If Vacation Period is not enabled, the default value is -1 (All Days). You can
enter the value 0 (Work Days) or 1 (Vacation Days), if Vacation Period is
enabled.
Display Options
Server Name
Select the name of the server from the Server Name list.
Number of Servers to Display
Select the servers from the list.

Tables or views MS_SQL_Job_Summary _%V

used
Output The Number of Lock Requests/Timeouts in a Sec line chart displays the lock requests per
second and lock timeouts per second.

The table following chart displays the same data.

Usage The IT administrator can use this report to observe and compare the performance of different
SQL servers by using the number of failed jobs since the agent started.

268 Microsoft SQL Server agent: User’s Guide

Chapter 9. Troubleshooting
This chapter explains how to troubleshoot the IBM Tivoli Composite Application Manager for Microsoft
Applications: Microsoft SQL Server Agent. Troubleshooting is the process of determining why a certain
product is malfunctioning.

Note: You can resolve some problems by ensuring that your system matches the system requirements
listed in the Prerequisites topic for the agent in the information center.

This chapter provides agent-specific troubleshooting information. See the IBM Tivoli Monitoring
Troubleshooting Guide for general troubleshooting information. Also see “Support information” on page
307 for other problem-solving options.

Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencing with this product, gather
the following information that relates to the problem:
Table 23. Information to gather before contacting IBM Software Support
Information type Description
Log files
Collect trace log files from failing systems. Most logs are located in a logs subdirectory
on the host computer. See “Trace logging” on page 270 for lists of all trace log files and
their locations. See the IBM Tivoli Monitoring User's Guide for general information about
the IBM Tivoli Monitoring environment.
Microsoft SQL Server v Version number and patch level (For example: start Microsoft SQL Server Management
information Studio. Select the About... item in the Help menu to see this information.)
v Sample application data file (if monitoring a file)
Operating system Operating system version number and patch level (For example, you can right-click the
My Computer icon and select Properties to obtain this information.)
Messages Messages and other information displayed on the screen
Version numbers for Version number and patch level of the following members of the monitoring
IBM Tivoli Monitoring environment:
v IBM Tivoli Monitoring
v IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft SQL
Server Agent
Screen captures Screen captures of incorrect output, if any.

Built-in troubleshooting features

The primary troubleshooting feature in the IBM Tivoli Composite Application Manager for Microsoft
Applications: Microsoft SQL Server Agent is logging. Logging refers to the text messages and trace data
generated by the IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft SQL
Server Agent. Messages and trace data are sent to a log file.

Trace data captures transient information about the current operating environment when a component or
application fails to operate as designed. IBM Software Support personnel use the captured trace
information to determine the source of an error or unexpected condition. See “Trace logging” on page 270
for more information.

© Copyright IBM Corp. 2005, 2012 269

Problem classification
The following types of problems might occur with the IBM Tivoli Composite Application Manager for
Microsoft Applications: Microsoft SQL Server Agent:
v Installation and configuration
v General usage and operation
v Display of monitoring data
v Take Action commands

This chapter provides symptom descriptions and detailed workarounds for these problems, as well as
describing the logging capabilities of the monitoring agent. See the IBM Tivoli Monitoring Troubleshooting
Guide for general troubleshooting information.

Trace logging
Trace logs capture information about the operating environment when component software fails to
operate as intended. The principal log type is the RAS (Reliability, Availability, and Serviceability) trace
log. These logs are in the English language only. The RAS trace log mechanism is available for all
components of IBM Tivoli Monitoring. Most logs are located in a logs subdirectory on the host computer.
See the following sections to learn how to configure and use trace logging:
v “Principal trace log files” on page 271
v “Viewing trace logs” on page 274
v “Enabling detailed tracing in the collector trace log” on page 274
v “RAS trace parameters” on page 275

Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as "RAS1".

IBM Software Support uses the information captured by trace logging to trace a problem to its source or
to determine why an error occurred. The default configuration for trace logging, such as whether trace
logging is enabled or disabled and trace level, depends on the source of the trace logging. Trace logging
is always enabled.

Overview of log file management

Table 24 on page 272 provides the names, locations, and descriptions of RAS1 log files. The log file names
adhere to the following naming convention:
hostname_product_instance_program_timestamp-nn.log

where:
v hostname is the host name of the computer on which the monitoring component is running.
v product is the two-character product code. For Microsoft SQL Server agent, the product code is oq.
v instance is the name of a database instance that is being monitored.
v program is the name of the program being run.
v timestamp is an 8-character hexadecimal timestamp representing the time at which the program started.
v nn is a rolling log suffix. See “Examples of trace logging” for details of log rolling.

Examples of trace logging

For example, if a Microsoft SQL Server database dbinst02 is running on computer server01, the RAS log
file for the Microsoft SQL Server agent might be named as follows:
server01_oq_dbinst02_koqagent_437fc59-01.log

270 Microsoft SQL Server agent: User’s Guide

For long-running programs, the nn suffix is used to maintain a short history of log files for that startup of
the program. For example, the koqagent program might have a series of log files as follows:
server01_oq_dbinst02_koqagent_437fc59-01.log
server01_oq_dbinst02_koqagent_437fc59-02.log
server01_oq_dbinst02_koqagent_437fc59-03.log

As the program runs, the first log (nn=01) is preserved because it contains program startup information.
The remaining logs roll. In other words, when the set of numbered logs reach a maximum size, the
remaining logs are overwritten in sequence. Each time a program is started, a new timestamp is assigned
to maintain a short program history. For example, if the Microsoft SQL Server agent is started twice, it
might have log files as follows:
server01_oq_dbinst02_koqagent_437fc59-01.log
server01_oq_dbinst02_koqagent_437fc59-02.log
server01_oq_dbinst02_koqagent_437fc59-03.log

server01_oq_dbinst02_koqagent_537fc59-01.log
server01_oq_dbinst02_koqagent_537fc59-02.log
server01_oq_dbinst02_koqagent_537fc59-03.log

Each program that is started has its own log file. For example, the Microsoft SQL Server agent would
have agent logs in this format:
server01_oq_dbinst02_koqagent_437fc59-01.log

Other logs, such as logs for collector processes and Take Action commands, have a similar syntax, as in
the following example:
server01_oq_dbinst02_koqsql_447fc59-01.log

where koqsql is the name of a program.

Note: When you communicate with IBM Software Support, you must capture and send the RAS1 log
that matches any problem occurrence that you report.

Principal trace log files

Table 24 on page 272 contains locations, file names, and descriptions of trace logs that can help determine
the source of problems with agents.

Chapter 9. Troubleshooting 271

Table 24. Trace log files for troubleshooting agents
System where log
is located File name and path Description
On the computer Traces activity of the monitoring agent.
that hosts the The RAS1 log files are named Note: Other logs, such as logs for
monitoring agent hostname_oq_instance_program_timestamp-nn.log collector processes and Take Action
and are located in the install_dir\tmaitm6\logs commands (if available), have a similar
See Definitions of path: syntax and are located in this directory
variables for Note: File names for RAS1 logs include a path.
descriptions of the hexadecimal time stamp.
variables in the file
A collector trace log file is produced by
names in column The collector trace log file is named Microsoft SQL Server agent. New log
two. hostname_oq_instance_col.out. The file is located in files are created each time the agent is
the install_dir\tmaitm6\logs path. started. One backup copy, renamed from
*.out to *.ou1, is kept for historical
Note: A hostname_oq_instance_col.out log file also purposes. The log file is not pruned. See
exists and contains stderr and stdout messages. “Enabling detailed tracing in the
collector trace log” on page 274 to learn
how to change the default behavior of
this type of logging.

The agent trace log file is named An agent trace log file is produced by
hostname_oq_instance_agt.out. The file is located in Microsoft SQL Server agent. New log
the install_dir\tmaitm6\logs path. files are created each time the agent is
started. One backup copy, renamed from
*.out to *.ou1, is kept for historical
purposes.
The *.LG0 file is located in the install_dir\tmaitm6\
logs path. A new version of this file is generated
every time the agent is restarted. IBM
Tivoli Monitoring generates one backup
copy of the *.LG0 file with the tag .LG1.
View .LG0 to learn the following details
regarding the current monitoring
session:
v Status of connectivity with the
monitoring server.
v Situations that were running.
v The success or failure status of Take
Action commands.

272 Microsoft SQL Server agent: User’s Guide

Table 24. Trace log files for troubleshooting agents (continued)
System where log
is located File name and path Description
On the Tivoli Provides details about products that are
Enterprise Portal On UNIX: The candle_installation.log file in the installed.
Server install_dir/logs path. Note: Trace logging is enabled by
default. A configuration step is not
See Definitions of On Windows: The IBM Tivoli Monitoring required to enable this tracing.
variables for timestamp.log file in the install_dir\InstallITM
descriptions of the path. Unlike RAS1 log files, the name of the file
variables in the file displays a decimal time stamp. *
names in column The RAS1 log file is named hostname_ms_timestamp- Traces activity on the monitoring server.
two. nn.log and is located in the following path:
v On Windows: install_dir\logs
v On UNIX: install_dir/logs
Note: File names for RAS1 logs include a
hexadecimal time stamp

Also on UNIX, a log with a decimal time stamp is

provided: hostname_ms_timestamp.log and
hostname_ms_timestamp.pidnnnnn in the
install_dir/logs path, where nnnnn is the process
ID.
On the computer The Warehouse_Configuration.log file is located in Provides details about the configuration
that hosts the the following path on Windows: of data warehousing for historical
Warehouse Proxy install_dir\InstallITM\ reporting.
agent Warehouse_Configuration.log.The
Warehouse_Configuration.log file is located in the
following path on Unix: install_dir/logs/
KHDCFG.log .
On the Tivoli The RAS1 log file is named hostname_cq_timestamp- Traces activity on the portal server.
Enterprise Portal nn.log and is located in the following path:
Server v On Windows: install_dir\logs
See Definitions of v On UNIX: install_dir/logs
variables for Note: File names for RAS1 logs include a
descriptions of the hexadecimal time stamp
variables in the file
names in column Also on UNIX, a log with a decimal time stamp is
two. provided: hostname_cq_timestamp.log and
hostname_cq_timestamp.pidnnnnn in the
install_dir/logs path, where nnnnn is the process ID.
The TEPS_ODBC.log file is located in the following When you enable historical reporting,
path on Windows: install_dir\InstallITM. this log file traces the status of the
warehouse proxy agent.

Definitions of variables for RAS1 logs:

v hostname is the host name of the computer on which the agent is running.
v install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir can
represent a path on the computer that hosts the monitoring server, the monitoring agent, or the portal server.
v product is the two character product code. For Microsoft SQL Server agent, the product code is oq.
v instance refers to the name of the database instance that you are monitoring.
v program is the name of the program being run.
v timestamp is an eight-character hexadecimal time stamp representing the time at which the program started.
v nn is a rolling log suffix. See “Examples of trace logging” on page 270 for details of log rolling.

Chapter 9. Troubleshooting 273

See the IBM Tivoli Monitoring Installation and Setup Guide for more information on the complete set of
trace logs that are maintained on the monitoring server.

Viewing trace logs

About this task

Typically IBM Software Support applies specialized knowledge to analyze trace logs to determine the
source of problems. However, you can open trace logs in a text editor to learn some basic facts about
your IBM Tivoli Monitoring environment. Use a text editor that is enabled for UTF-8, such as Notepad.

On Windows, you can use the following alternate method to view trace logs:

Procedure
1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli
Monitoring Service. The Manage Tivoli Enterprise Monitoring Services window is displayed.
2. Right-click a component and select Advanced > View Trace Log in the pop-up menu. The program
displays the Select Log File window that lists the RAS1 logs for the monitoring agent.
3. Select a log file from the list and click OK. You can also use this viewer to access remote logs.

Note: The viewer converts time stamps in the logs to a readable format.

Enabling detailed tracing in the collector trace log

Collector trace logs are generated by a database monitoring agent. You can use the following options to
modify collector trace logging.

Option one: modify the settings file

This section provides the procedure to modify the settings file.

Procedure

Complete the following steps to enable detailed logging for the collector trace log:
1. Open the koqtrac.ctl file. The file is located in the following path: install_dir\tmaitm6, where
install_dir is the location of the IBM Tivoli Monitoring component.
2. Remove the two semicolons (;;) from the beginning of the line that contains trace_all;.
3. Save the file.
4. Restart the monitoring agent for the database instance that you want to trace. Logging goes to a
collector trace log file that is named in Table 24 on page 272. The log file is stored in the following
path: install_dir\tmaitm6\logs where install_dir is the path where you installed IBM Tivoli
Monitoring.
5. When you complete an analysis of detailed trace logs, turn off detailed logging as follows, because
trace logs can consume a large amount hard disk space.
a. Open the koqtrac.ctl file mentioned in Step 1.
b. Type two semicolons (;;) at the beginning of the line that contains trace_all;.
c. Save the file.
d. Restart the monitoring agent for the database instance that you have been tracing.

Option two: modify environment variables

This section proves the procedure to modify environment variables.

274 Microsoft SQL Server agent: User’s Guide

About this task

You can modify trace logging for the collector log by setting the following environment variables:
COLL_WRAPLINES
By default, new collector log files are created each time you start the agent or when the log file
reaches the limit specified by the COLL_WRAPLINES environment variable. COLL_WRAPLINES defines
the number of lines in the col.out file and is 90000 lines by default (about 2 MB).
COLL_NUMOUTBAK
By default, the product creates one backup copy of the collector log file. The file tag is changed
from *.out to *.ou1. You can configure the product to create up to nine backup files by defining
COLL_NUMOUTBAK to be an integer from one to nine. By default, the number of backup files is 5.

Set the environment variables as follows:

Procedure
1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring > Manage Tivoli
Monitoring Service. The Manage Tivoli Enterprise Monitoring Services window is displayed.
2. Right-click the row that contains the name of the monitoring agent whose environment variables you
want to set.
3. Select Advanced > Edit Variables in the pop-up menu.
4. If the agent is running, accept the prompt to stop the agent. A restart is necessary so that the
environment variable that you create takes effect.
5. The list dialog is displayed. When only the default settings are in effect, there are no variables
displayed. The variables are listed after you override them.
6. Override the variable settings as follows:
a. Click Add.
b. Select the variable you want to modify in the Variable pull-down menu. For example, select
COLL_NUMOUTBAK.
c. Type a value in the Value field. For example, type the number 9, the maximum number of backup
files that can be generated.
d. Select OK two times.
e. Restart the agent.

RAS trace parameters

Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and
modules

See“Overview of log file management” on page 270 to ensure that you understand log rolling and can
reference the correct log files when you manage log file generation.

Setting RAS trace parameters by using the GUI

On Windows systems, you can use the graphical user interface to set trace options.

About this task

The IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft SQL Server Agent
uses RAS1 tracing and generates the logs described in “Principal trace log files” on page 271. The default
RAS1 trace level is ERROR.

Chapter 9. Troubleshooting 275

Procedure
1. Open the Manage Tivoli Enterprise Monitoring Services window.
2. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters
window is displayed.
3. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid
string.
v General error tracing. KBB_RAS1=ERROR
v Intensive error tracing. KBB_RAS1=ERROR
v Maximum error tracing. KBB_RAS1=ERROR

Note: As this example shows, you can set multiple RAS tracing options in a single statement.
4. Modify the value for Maximum Log Size Per File (MB) to change the log file size (changes LIMIT
value).
5. Modify the value for Maximum Number of Log Files Per Session to change the number of log files
per startup of a program (changes COUNT value).
6. Modify the value for Maximum Number of Log Files Total to change the number of log files for all
startups of a program (changes MAXFILES value).
7. Optional: Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you
diagnose communications and connectivity problems between the monitoring agent and the
monitoring server. The KDC_DEBUG setting and the Maximum error tracing setting can generate a large
amount of trace logging. Use these settings only temporarily, while you are troubleshooting problems.
Otherwise, the logs can occupy excessive amounts of hard disk space.
8. Click OK. You see a message reporting a restart of the monitoring agent so that your changes take
effect.

What to do next

Monitor the size of the logs directory. Default behavior can generate a total of 45 - 60 MB for each agent
that is running on a computer. For example, each database instance that you monitor can generate 45 - 60
MB of log data. See the "Procedure" section to learn how to adjust file size and numbers of log files to
prevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log files
that are pruned automatically, other log types can grow indefinitely.

Use collector trace logs as an additional source of troubleshooting information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace
logging. Use these settings only temporarily while you are troubleshooting problems. Otherwise, the logs
can occupy excessive amounts of hard disk space.

Manually setting RAS trace parameters

You can manually edit the RAS1 trace logging parameters.

About this task

The Microsoft SQL Server agent uses RAS1 tracing and generates the logs described in “Principal trace
log files” on page 271. The default RAS1 trace level is ERROR.

Procedure
1. Open the trace options file:
v Windows systems:

276 Microsoft SQL Server agent: User’s Guide

 install_dir\tmaitm6\KOQENV_instance name
v UNIX systems:
install_dir /config/OQ_instance name.config
2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. For example, if you want
detailed trace logging, set the Maximum Tracing option: KBB_RAS1=ERROR (UNIT:kOQ ALL) (UNIT:kra
ALL)
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:
v MAXFILES: The total number of files that are to be kept for all startups of a specific program. When
this value is exceeded, the oldest log files are discarded. The default value is 9.
v LIMIT: The maximum size, in megabytes (MB) of a RAS1 log file. The default value is 5.
4. Restart the monitoring agent so that your changes take effect.

What to do next

Monitor the size of the logs directory. Default behavior can generate a total of 45 - 60 MB for each agent
that is running on a computer. For example, each database instance that you monitor can generate 45 - 60
MB of log data. See the "Procedure" section to learn how to adjust file size and numbers of log files to
prevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log files
that are pruned automatically, other log types can grow indefinitely.

Use collector trace logs as an additional source of troubleshooting information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace
logging. Use these settings only temporarily while you are troubleshooting problems. Otherwise, the logs
can occupy excessive amounts of hard disk space.

Problems and workarounds

The following sections provide symptoms and workarounds for problems that might occur with
Microsoft SQL Server agent:
v “Installation and configuration troubleshooting”
v “Agent troubleshooting” on page 287
v “Workspace troubleshooting” on page 297
v “Troubleshooting for remote deployment” on page 296
v “Situation troubleshooting” on page 301
v “Take Action command troubleshooting” on page 304
v “Troubleshooting for SQL Server” on page 286

Note: You can resolve some problems by ensuring that your system matches the system requirements
listed in the Prerequisites topic for the agent in the information center for IBM Tivoli Composite
Application Manager for Microsoft Applications.
This chapter provides agent-specific troubleshooting information. See the IBM Tivoli Monitoring
Troubleshooting Guide for general troubleshooting information.

Installation and configuration troubleshooting

This section provides tables that show solutions for the following types of installation, configuration, and
uninstallation problems:
v Operating system problems
v Problems with database applications

Chapter 9. Troubleshooting 277

Table 25. Problems and solutions for installation and configuration on UNIX and Windows systems
Problem Solution
When you upgrade to IBM Tivoli Fix packs for Candle, Version 350, are delivered as each monitoring
Monitoring, you might need to apply fix agent is upgraded to IBM Tivoli Monitoring.
packs to Candle, Version 350, agents. Note: The IBM Tivoli Monitoring download image or CD provides
application fix packs for the monitoring agents that are installed from
that CD (for example, the agents for operating systems such as
Windows, Linux, UNIX, and i5/OS™). The upgrade software for other
agents is located on the download image or CDs for that specific
monitoring agent, such as the agents for database applications.

If you do not upgrade the monitoring agent to IBM Tivoli Monitoring,

the agent continues to work. However, you must upgrade to have all the
functionality that IBM Tivoli Monitoring offers.
Presentation files and customized The upgrade from version 350 to IBM Tivoli Monitoring handles export
Omegamon DE screens for Candle of the presentation files and the customized Omegamon DE screens.
monitoring agents need to be upgraded
to a new Linux on z/Series system.
The following message is displayed in There is no workaround. The previous value of KBB_RAS1 from the
the installation log for some Windows OMEGAMON V350 agent is used, preserving prior customer settings for
agents when upgrading from Tivoli this variable. The problem has no adverse effect on the installation or
OMEGAMON® V350: <REPLACELINE> subsequent operation of the monitoring agent .
Pair missing 1=[KBB_RAS1=ERROR] no 2,
skipped.
Non-ASCII characters entered into the Enter only ASCII characters into these fields.
configuration window for the monitoring
agent do not show up or are not the
correct characters.
You must exit and restart the installation process. You cannot return to
(UNIX only) During a command-line the list where you selected components to install. When you run the
installation, you choose to install a installer again, do not attempt to install any component that is already
component that is already installed, and installed.
you see the following warning:
WARNING - you are about to install
the SAME version of "component"

where component is the name of the

component that you are attempting to
install.
Note: This problem affects UNIX
command-line installations. If you
monitor only Windows environments,
you would see this problem if you
choose to install a product component
(for example, a monitoring server) on
UNIX.

278 Microsoft SQL Server agent: User’s Guide

Table 25. Problems and solutions for installation and configuration on UNIX and Windows systems (continued)
Problem Solution
You must reconfigure the previously existing agents to restore their
A problem can arise when you install communication connection with TEMS1. For example, you can
and configure a new monitoring agent to right-click the row for a specific agent in the Manage Tivoli Enterprise
a computer where other agents are Monitoring Services, and select Reconfigure. See the IBM Tivoli
running as described in this example: Monitoring Installation and Setup Guide for more information on
v Agents are running on computer and reconfiguration.
communicating with a Tivoli
Enterprise Monitoring Server, called
TEMS1.
v You install a new agent on the same
computer and you want this agent to
communicate with a different
monitoring server, called TEMS2.
v When you configure the new agent to
communicate with TEMS2, all the
existing agents are re-configured to
communicate with TEMS2.
Diagnosing problems with product When you have problems with browse settings, perform the following
browse settings. steps:
1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli
Enterprise Monitoring Services. The Manage Tivoli Enterprise
Monitoring Services is displayed.
2. Right-click the Windows agent and select Browse Settings. A text
window is displayed.
3. Click Save As and save the information in the text file. If requested,
you can forward this file to IBM Software Support for analysis.
A message similar to Unable to find
running CMS on CT_CMSLIST in the log file If a message similar to Unable to find running CMS on CT_CMSLIST is
is displayed. displayed in the Log file, the agent is not able to connect to the
monitoring server. Confirm the following points:
v Do multiple network interface cards (NICs) exist on the system?
v If multiple NICs exist on the system, find out which one is configured
for the monitoring server. Ensure that you specify the correct host
name and port settings for communication in the IBM Tivoli
Monitoring environment.
You successfully upgraded from an Copy the attribute files (koq.atr) for the upgraded monitoring agent to
OMEGAMON monitoring agent to IBM install_dir\tmaitm6\attrlib on the computer where you have installed
Tivoli Monitoring, Version 6.x. However, the Warehouse Proxy. The Warehouse Proxy must be able to access the
when you configure historical data short attribute names for tables and columns. That way, if the longer
collection, you see an error message that versions of these names exceed the limits of the Warehouse database, the
includes, Attribute name may be shorter names can be substituted.
invalid, or attribute file not
installed for warehouse agent.
Text for configuration functions is None. You must complete configuration of the monitoring agent using
displayed in English instead of native English.
languages when installing and
configuring the monitoring agent. For
example, when using the Manage Tivoli
Enterprise Monitoring Services GUI on a
Windows system.

Chapter 9. Troubleshooting 279

Table 25. Problems and solutions for installation and configuration on UNIX and Windows systems (continued)
Problem Solution
Installation errors occur when installing Verify that the remote agent is not at a lower version than V6.1.2 before
the previous 6.1.0 version of the attempting to run the V6.1.0 remote installation with the -v option. If
monitoring agent after installing the 6.1.2 V6.1.2 is already present, do not force the V6.1.0 agent installation. After
version of the agent. an inadvertent back level to V6.1.0, run the V6.1.2 installation (or higher)
to upgrade the agent.
Ignore IBM Tivoli Monitoring for Microsoft Applications in the Add or
After you upgrade ITCAM for Microsoft Remove Programs window. If you want to modify or remove the
Applications from an earlier version to installed agents in IBM Tivoli Monitoring for Microsoft Applications, use
V6.2.3 or V6.3.0, the following entries are IBM Tivoli Monitoring from the Add or Remove Programs window.
created in the Add or Remove Programs
window:
v IBM Tivoli Monitoring for Microsoft
Applications
v IBM Tivoli Monitoring

Table 26. Problems and solutions for installation and configuration of the Microsoft SQL Server agent
Problem Solution

The procedure for launching the This problem happens when the KOQENV file is missing. If the KOQENV file
Microsoft SQL Server agent Trace is missing from the install_dir\tmaitm6 directory, the Microsoft SQL
Parameters window in “RAS trace Server agent must be reinstalled.
parameters” on page 275 fails because no
trace settings are available in the Enter
RAS1 Filters field.
Review the information in “Trace logging” on page 270 to ensure that
Collector trace logs are not receiving you are consulting the correct log file. The file is located in the following
error information. path: install_dir\tmaitm6, where install_dir is the location of IBM Tivoli
Monitoring.
After running the agent successfully, you
reinstall the agent software, and Consult the list of supported versions in the configuration chapter of the
collection of monitoring data stops. agent user's guide for SQL Server. Confirm that you are running a valid
version of the target application. If you are monitoring a supported
version of the database application, gather log files and other
information and contact IBM Software Support, as described in
“Gathering product information for IBM Software Support” on page 269.
Alert summary report of Tivoli
Enterprise Portal shows no information. Ensure that the configuration setting of agent's error log file defines a
valid path. Confirm that the error log file is correct. If the error log file is
correct, the problem can occur because the logon account that you are
using does not have sufficient permissions in the IBM Tivoli Monitoring
environment. For details see Chapter 2, “Agent installation and
configuration,” on page 15.
Error counts are displayed in the Alert
summary report in the Tivoli Enterprise Check the time stamp for the reports. If you have set up historical data
Portal, however, error messages are not collection for Alert summary report, it is recommended that you set up
displayed in the Alert detail report. historical data collection for the Alert detail report, too.

280 Microsoft SQL Server agent: User’s Guide

Table 26. Problems and solutions for installation and configuration of the Microsoft SQL Server agent (continued)
Problem Solution

When installing the SQL Server agent You can continue using the SQL Server agent despite this error. However,
support file for the Tivoli Enterprise the Enterprise Database Mirroring data collection is affected.
Monitoring Server, you see the following
error message:
RC=350

This problem might occur if the Tivoli

Enterprise Portal client fails to display
the Enterprise Database Mirroring
workspace.
Close the Manage Tivoli Enterprise Monitoring Services window before
During the silent uninstallation of the uninstalling the agent using the silent uninstallation method.
SQL Server agent, if the Manage Tivoli
Enterprise Monitoring Services window
is open, the agent fails to uninstall.
Keep the collection interval to a minimum of 5 minutes and use a
Historical Data Collection takes some smaller interval for an attribute group if it is critical.
seconds more than the configured data
collection interval time to finish data
collection. This delay gives an impression
that some data rows are missing when
the collection interval is 1 minute.
Remove the earlier instance of the SQL Server agent and create another
When you upgrade the SQL Server from instance.
V2005 to V2008 R2 or V2012 and
configure the SQL Server agent locally,
the database version in the Database
Server Properties window does not
display the upgraded version of the SQL
Server.

Chapter 9. Troubleshooting 281

Table 26. Problems and solutions for installation and configuration of the Microsoft SQL Server agent (continued)
Problem Solution
Unique names for monitoring
components: ORIGINNODE is truncated IBM Tivoli Monitoring might not be able to generate a unique name for
and doesn't show the product code. monitoring components due to the truncation of names that the product
automatically generates. IBM Tivoli Monitoring automatically creates a
name for each monitoring component by concatenating the subsystem
name, host name, and product code separated by colons
(subsystem_name:hostname:MSS).
Note: When you monitor a multinode systems, like databases, IBM
Tivoli Monitoring uses a database instance name as the subsystem name.

The length of the name that IBM Tivoli Monitoring generates is limited
to 32 characters. Truncation can result in multiple components having the
same 32-character name. If this problem happens, shorten the
subsystem_name portion of the name as described in the steps as below:
v On Windows:
Note: This procedure involves editing the Windows Registry. An error
in editing the Registry may cause other system errors. It is best
practice to make a backup copy of the Registry prior to modifying the
Registry. If you do not feel comfortable editing the Registry, contact
IBM Software Support.
1. Run the Registry editor, regedit. Select Start > Run. Type regedit
in the field and click OK.
2. Locate the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KOQ\610\instance_name

where instance_name is the Microsoft SQL Server instance name that

is associated with the target agent.
3. Open the Environment key.
4. Select the CTIRA_SUBSYSTEM_ID string attribute. If you do not find
CTIRA_SUBSYSTEM_ID, add it. step 6. Type a new name for an
instance name (subsystem name).
5. Right-click and select Modify.
6. Type a new instance name (subsystem name). Keep in mind that
the final concatenated name, including the subsystem name, host
name, and OQ, cannot be longer than 32 characters.
Note: You must ensure that the resulting name is unique with
respect to any existing monitoring component that was previously
registered with the Tivoli Enterprise Monitoring Server.
7. Exit from the Registry editor.
8. Restart the agent.
9. A second instance in the Tivoli Enterprise Portal Navigation tree
might be automatically added. If this happens, clear the old, offline
agent instance navigation item using the Managed System Status
workspace of the Enterprise Navigation tree item.

282 Microsoft SQL Server agent: User’s Guide

Table 26. Problems and solutions for installation and configuration of the Microsoft SQL Server agent (continued)
Problem Solution
To configure the SQL Server agent services on a Windows 2003 system,
In Windows 2003 system, a perform the following steps:
non-administrator user cannot configure
1. On the Windows Start menu, click Run.
the SQL Server agent services through
the Change Startup option in the 2. Type services.msc, and click OK.
Manage Tivoli Enterprise Monitoring 3. In the Services window, perform these steps for the agent service and
Services window. the agent collector service:
a. Right-click the service, and click Properties.
b. Click the Log On tab.
c. Click This account.
d. Type the user name.
e. In the Password and Confirm Password field, enter password,
and click OK.
4. In the Manage Tivoli Enterprise Monitoring Services window,
right-click the SQL Server agent service, and click Recycle.
There is no solution to this problem.
If you have installed a 64-bit agent for
ITCAM for Microsoft Applications,
information about the agent processes is
not displayed in the Kinviewer window.

Chapter 9. Troubleshooting 283

Table 26. Problems and solutions for installation and configuration of the Microsoft SQL Server agent (continued)
Problem Solution
When you install ITCAM for Microsoft Complete the following steps to resolve this problem for a 32-bit agent:
Applications from the product DVD, the 1. Edit the KXXWICMA.ver file in the Candle_home\InstallITM\Ver
kincinfo command does not display the directory, and then add the following properties and values at the
installation date when you install 32-bit end of the file:
or 64-bit agents of ITCAM for Microsoft
GSKit=LOCAL[INSTALL INFO] Install
Applications. For the 64-bit agent, the
Date=Date_TimeInstall Dir=Candle_homeInstall
kincinfo command displays two entries. GUID={23B43DE3-AE00-E230-ED11-BA05A422701D}
2. Replace Candle_home with the folder path where you have installed
the agent, for example, C:\IBM\ITM.
3. Replace Date_Time with the name of the latest folder that is created in
the Candle_home\InstallITM\VerPrevInstall directory, for example,
Install Date=20100721 0700.
Complete the following steps to resolve this problem for a 64-bit agent:
1. Edit the KXX64CMA.ver file in the Candle_home\InstallITM\Ver
directory, and then add the following properties and values at the
end of the file:
GSKit=LOCAL[INSTALL INFO] Install Date=Date_TimeInstall
Dir=Candle_home
Install GUID={A75F7F91-1FF2-49C6-ABFF-1FDAF54E7E67}
2. Replace Candle_home with the folder path where you have installed
the agent, for example, C:\IBM\ITM.
3. Replace Date_Time with the name of the latest folder that is created at
Candle_home\InstallITM\VerPrevInstall, for example, Install
Date=20100721 0700.
4. Edit the KXXWICMA.ver file in the Candle_home\InstallITM\Ver
directory, and then add the following properties and values at the
end of the file:
GSKit=LOCAL Dummy32BitVerfile=YES[INSTALL INFO] Install
Date=Date TimeInstall Dir=Candle_home
Install GUID={A75F7F91-1FF2-49C6-ABFF-1FDAF54E7E67}
5. Replace Candle_home and Date_Time values with the values that are
used in steps 2 and 3.
6. Edit the KXXWICMA.ver file in the Candle_home\InstallITM\Ver
directory, and then modify the value of the PlatformArch variable
from WIX64 to WINNT. For example, if the KXXWICMA.ver file contains
PlatformArch=WIX64, change it to PlatformArch=WINNT.

284 Microsoft SQL Server agent: User’s Guide

Table 27. General problems and solutions for uninstallation
Problem Solution
On Windows, uninstallation of IBM Confirm that the following problems do not exist:
Tivoli Monitoring fails to uninstall the v Ensure that you are the only user who is logging into the computer
entire environment. where you are performing an uninstallation operation. If another user
is performing operations during an uninstall process, the uninstall
process fails.
v Be sure that you follow the general uninstallation process described in
the IBM Tivoli Monitoring Installation and Setup Guide:
1. Uninstall monitoring agents first, as in the following examples:
– Uninstall a single monitoring agent for a specific database.
—OR—
– Uninstall all instances of a monitoring product, such as IBM
Tivoli Monitoring for Microsoft Applications.
2. Uninstall IBM Tivoli Monitoring.
The way to remove inactive managed Use the following steps to remove, but not uninstall, an offline managed
systems (systems whose status is system from the Navigator tree:
OFFLINE) from the Navigator tree in the 1. Click the Enterprise icon in the Navigator tree.
portal is not obvious.
2. Right-click, then click Workspace > Managed System Status.
3. Right-click the offline managed system, and select Clear offline
entry.

If you also want to uninstall the monitoring agent, use the procedure
described in the IBM Tivoli Monitoring Installation and Setup Guide.
Attempting a remote uninstallation of the The agent is uninstalled and no other known errors are associated with
Microsoft SQL Server agent through the this problem at this time.
Tivoli Enterprise Portal client triggers a
timeout error that does not correctly
identify the managed system where the
timeout is said to have occurred. The
error text does not display another
managed system; instead it displays
incorrect text in place of the managed
system name. However, the agent does
appear to be uninstalled. The error
message returned is KFWITM290E.
You have installed Tivoli Enterprise Remove the SQL Server agent instances from the Manage Tivoli
Monitoring Agent Framework V6.2.2, Fix Enterprise Monitoring Service window manually.
Pack 2 on a managed system. If you
uninstall the SQL Server agent by using
the Modify option in the Add or
Remove Programs window, the entry for
the SQL Server agent is not removed
from the Manage Tivoli Enterprise
Monitoring Service window.

Chapter 9. Troubleshooting 285

Table 27. General problems and solutions for uninstallation (continued)
Problem Solution
You have installed an ITCAM for To restore the entry for IBM Tivoli Monitoring in the Add or Remove
Microsoft Applications agent, V6.2.3 on a Programs window, run the setup.exe file of ITCAM Microsoft
computer. Later, you installed earlier Applications agent, V6.2.3.
version (V6.2.2) of other ITCAM for
Microsoft Applications agents on the
same computer. The entry for IBM Tivoli
Monitoring is removed from the Add or
Remove Programs window, and you
cannot uninstall any of the ITCAM for
Microsoft Applications agents from the
computer.
You have installed a 64-bit agent of Perform the following steps to start the 64-bit agent:
ITCAM for Microsoft Applications V6.2.3 1. Unconfigure the agent.
on a computer that has preinstalled
2. Reconfigure and start the agent.
ITCAM for Microsoft Applications agents
on the same computer. When you try to
uninstall and reinstall the 64-bit agent of
ITCAM for Microsoft Applications V6.2.3
on the computer, the 64-bit agent does
not start automatically.
You have the Windows OS agent and There is no solution to this problem.
one or more agents of ITCAM for
Microsoft Applications preinstalled on
the same computer. When you run the
ITCAM for Microsoft Applications
installation wizard to upgrade the agents
from V6.2.2 to a later version, the
installation wizard does not display the
version of the preinstalled ITCAM for
Microsoft Applications agents.
When you use the Installation Launch No action is required. You can ignore this message and continue with the
Pad to install a 32-bit agent on a 32-bit installation.
computer, the following message is
displayed:
The following components cannot
be installed because the
installation action failed.
IBM Tivoli Composite
Application Manager for
Microsoft Applications V6.2.3
for Windows on 64-bit AMD and
Intel systems (x64)

Troubleshooting for SQL Server

Table 28 lists problems that might occur on the system or application that you are monitoring. See the
IBM Tivoli Monitoring Troubleshooting Guide for general troubleshooting information.
Table 28. SQL Server problems and solutions
Problem Solution
The following Microsoft SQL Server Be aware of this problem as you monitor Microsoft SQL Server. There is
metrics might exceed 100 percent values: no known solution. Monitor the product support website for Microsoft
v Procedure Buffers Percent Active SQL Server for updated information on this problem.
v Procedure Cache Percent Active

286 Microsoft SQL Server agent: User’s Guide

Agent troubleshooting
This section lists problems that might occur with agents.

This chapter provides agent-specific troubleshooting information. See the IBM Tivoli Monitoring
Troubleshooting Guide for general troubleshooting information.
Table 29. General agent problems and solutions
Problem Solution
The system experiences high CPU usage View the memory usage of the KOQCMA process. If CPU usage seems to
after you install or configure Microsoft be excessive, recycle the monitoring agent.
SQL Server agent.
A monitoring agent seems to be offline. 1. Allow several minutes to pass whenever you restart the Tivoli
Enterprise Portal Server. A monitoring agent will seem to be down
while the portal server is restarting.
2. Select Physical View and highlight the Enterprise Level of the
navigator tree.
3. Select View > Workspace > Managed System Status to see a list of
managed systems and their status.
4. If a system is offline, check network connectivity and status of the
specific system or application.
Some TEC events from the Microsoft Solution This problem can be caused by a wrong data type, as shown in
SQL Server agent have PARSING_FAILED the following wtdumprl output:
status in wtdumprl output of TEC 1~14560~1~1158832838(??? 21 14:00:38 2006)
server. ### EVENT ###
ITM_MS_SQL_Process_Summary;source=’ITM’;sub_source=’TW06210:
TW06210:MSS’;cms_hostname=’tps06072.tw.twnet’;cms_port=’3661
’;integration_type=’U’;master_reset_flag=’’;appl_label=’’;si
tuation_name=’MS_SQL_ProcessOthSleep_Warning’;situation_orig
in=’TW06210:TW06210:MSS’;situation_time=’09/21/2006 \
14:00:37.000’;situation_status=’Y’;hostname=’TW06210’;origin
=’192.168.192.120’;adapter_host=’HUB_TPS06072’;severity=’WAR
NING’;date=’09/21/2006’;msg=’MS_SQL_ProcessOthSleep_Warning[
(Total_Other_Sleep>=2 AND Percent_Processes_Othersleep>=50.0
0 ) ON TW06210:TW06210:MSS (Total_Other_Sleep=46 Percent_ \
Processes_Othersleep=74.19)]’;situation_displayitem=
’’;current_interval=’193’;host_name=’TW06210’;hub_timestamp=
’1060921135139000’;originnode=’TW06210:TW06210:MSS’;percent_
processes_bad=’0.00’;percent_processes_blocked=’0.00’;percent
_processes_infected=’0.00’;percent_processes_locksleep=’0.00’
;percent_processes_othersleep=’74.19’;percent_processes_sleep
ing=’74.19’;percent_processes_stopped=’0.00’;sample_timestamp
=’1060921134858000’;server=’TW06210’;server_cpu_percent_appli
cation=’0.00’;server_cpu_percent_system=’0.00’;total_log_susp
end=’0’;total_other_sleep=’46’;total_processes=’62’;total_pro
cesses_bad=’0’;total_processes_blocked=’0’;total_processes_in
fected=’0’;total_processes_locksleep=’0’;total_processes_stop
ped=’0’;situation_eventdata=’~’;END

### END EVENT ###

PARSING_FAILED~’Line 1: Value does not match type REAL!’

Use the odadmin environ command as follows to set en_US in the oserv
environment:
1. odadmin environ get > /tmp/env.out
2. Edit /tmp/env.out and set LANG=en_US
3. odadmin reexec all

Chapter 9. Troubleshooting 287

Table 29. General agent problems and solutions (continued)
Problem Solution
No performance data is displayed in When the Windows operating system detects a problem in one of its
workspace views, no data is available extensible performance monitoring DLL files, it marks the DLL as
for situations, and no data is available disabled. Any DLL that is disabled cannot provide performance data
for historical logging. through the Windows Performance Monitor interfaces (Perfmon or
Performance Monitor APIs). This prevents IBM Tivoli Monitoring agents
from gathering data supplied by the disabled DLL. For more information,
see Microsoft Support Knowledge Base article 248993 at the following
Web address: http://support.microsoft.com/default.aspx?scid=kb;EN-
US;248993

Follow the Resolution instructions provided in this article (248993) to

re-enable any performance monitoring extension DLL files disabled by
Windows. Then, restart the monitoring agent.

288 Microsoft SQL Server agent: User’s Guide

Table 29. General agent problems and solutions (continued)
Problem Solution
A configured and running instance of Tivoli Monitoring products use Remote Procedure Call (RPC) to define
the monitoring agent is not displayed in and control product behavior. RPC is the mechanism that allows a client
the Tivoli Enterprise Portal, but other process to make a subroutine call (such as GetTimeOfDay or
instances of the monitoring agent on the ShutdownServer) to a server process somewhere in the network. Tivoli
same system do appear in the portal. processes can be configured to use TCP/UDP, TCP/IP, SNA, and SSL as
the desired protocol (or delivery mechanism) for RPCs.

"IP.PIPE" is the name given to Tivoli TCP/IP protocol for RPCs. The RPCs
are socket-based operations that use TCP/IP ports to form socket
addresses. IP.PIPE implements virtual sockets and multiplexes all virtual
socket traffic across a single physical TCP/IP port (visible from the
netstat command).

A Tivoli process derives the physical port for IP.PIPE communications

based on the configured, well-known port for the HUB Tivoli Enterprise
Monitoring Server. (This well-known port or BASE_PORT is configured
using the PORT: keyword on the KDC_FAMILIES / KDE_TRANSPORT
environment variable and defaults to 1918.)

The physical port allocation method is defined as (BASE_PORT + 4096*N)

where N=0 for a Tivoli Enterprise Monitoring Server process and N={1, 2,
..., 15} for a non-Tivoli Enterprise Monitoring Server. Two architectural
limits result as a consequence of the physical port allocation method:
v No more than one Tivoli Enterprise Monitoring Server reporting to a
specific Tivoli Enterprise Monitoring Server HUB can be active on a
system image.
v No more that 15 IP.PIPE processes can be active on a single system
image.

A single system image can support any number of Tivoli Enterprise

Monitoring Server processes (address spaces) provided that each Tivoli
Enterprise Monitoring Server on that image reports to a different HUB.
By definition, there is one Tivoli Enterprise Monitoring Server HUB per
monitoring Enterprise, so this architecture limit has been simplified to
one Tivoli Enterprise Monitoring Server per system image.

No more that 15 IP.PIPE processes or address spaces can be active on a

single system image. With the first limit expressed above, this second
limitation refers specifically to Tivoli Enterprise Monitoring Agent
processes: no more that 15 agents per system image.

This limitation can be circumvented (at current maintenance levels, IBM

Tivoli Monitoring V6.1 Fix Pack 4 and later) if the Tivoli Enterprise
Monitoring Agent process is configured to use EPHEMERAL IP.PIPE. (This
is IP.PIPE configured with the EPHEMERAL:Y keyword in the KDC_FAMILIES
/ KDE_TRANSPORT environment variable). There is no limitation to the
number of ephemeral IP.PIPE connections per system image. If ephemeral
endpoints are used, the Warehouse Proxy Agent is accessible from the
Tivoli Enterprise Monitoring Server associated with the agents using
ephemeral connections either by running the Warehouse Proxy Agent on
the same computer or by using the Firewall Gateway feature. (The
Firewall Gateway feature relays the Warehouse Proxy Agent connection
from the Tivoli Enterprise Monitoring Server computer to the Warehouse
Proxy Agent computer if the Warehouse Proxy Agent cannot coexist on
the same computer.)
Attributes do not allow non-ASCII input None. Any attribute that does not include (Unicode) might support only
in the Situation Editor. ASCII characters. For example Attribute (Unicode) will support Unicode
but Attribute without (Unicode) might only support ASCII characters.

Chapter 9. Troubleshooting 289

Table 29. General agent problems and solutions (continued)
Problem Solution
When remotely stopping an instance of After starting the instance, wait 10 minutes for the instance to complete
the Microsoft SQL Server agent shortly initialization before stopping the agent.
after the instance has started, a KDY1024E
error message is returned and the
monitoring agent instance is stopped.
Negative value is returned for No known workaround at this time.
Transactions per Second in the Database
Detail attribute group when the user
database has a similar name to that of a
system database.
The Total OS CPU percent attribute of Use the Operating System agents to monitor the Total OS CPU percent
the Tivoli Enterprise Portal Server shows attribute.
erroneous value in the Tivoli Enterprise
Portal.

ITM 6.X database agents do not monitor

attributes that are related to operating
systems. The database agent might not
reflect dynamic values collected at every
instance because the database agent
collects the value at a specific interval of
time.
Queries results that return No_Data These changes are implemented in the Microsoft SQL Server agent V6.2.1:
v If no data is available for an attribute group, then no rows are returned
If no data is available for an attribute
to the Tivoli Enterprise Monitoring Server or the Tivoli Enterprise
group, the Tivoli Enterprise Portal
Portal Server.
shows a row with zero values. This
triggers false situations. Also, if a row is v If a row is returned and the selected attributes have no data, then the
returned and selected attributes have no selected attributes are set to a value of -1 for integer type attributes
data, these attributes are returned as a and No_Data for string type attributes. -1 values are translated to
zero value. Not_Collected and displayed in the Tivoli Enterprise Portal Server.

The Server Status attribute of the Server Ensure that the SQL Server is running. It might take a few minutes for
Summary or Server Detail attribute the agent to successfully connect to the SQL Server and return a Server
groups returns a value of Inactive or Status value of Active. If the SQL Server is running and the Collection
Unknown. Status value is still Inactive, then restart the SQL Server agent.

A value of Inactive is returned to the

Tivoli Enterprise Portal Server when the
agent collector service fails to
communicate with the SQL Server. A
value of Unknown is returned to the
Tivoli Enterprise Portal Server when the
agent collector service is stopped, being
restarted, or not functioning properly.

290 Microsoft SQL Server agent: User’s Guide

Table 29. General agent problems and solutions (continued)
Problem Solution

The Collection Status attribute of the Ensure that the SQL Server is running. If the SQL Server is running and
Server Summary attribute group returns the Collection Status value is still Inactive, then restart the SQL Server
a value of Inactive. agent.

A value of Inactive indicates that the

SQL Server agent data collector service
has stopped. The collector service might
enter this state if:
v The collector service is manually
stopped.
v An internal error has occurred.
v The SQL Server is stopped.
Restart the SQL Server database service.
If you rename a database in the SQL
management studio, the SQL Server
agent does not collect data for the
following attributes in the MS SQL
Database Detail attribute group:
v Database Growth Percent
v Data Size
v Data Freespace Percent
v Log Freespace
v Log Size
v Last Database Size

When you create two SQL Server The space at the beginning of the database name is truncated by the
databases with the same name, but portal, making the two databases look identical.
precede one database name with a space
and the other database name without a Avoid spaces at the beginning of a database name.
space, the portal does not display data
properly.
Release the locks.
If the table level locking hint (Holdlock,
Tablock, and so on) is specified with the
SELECT, INSERT, UPDATE and DELETE
statements on multiple tables in an SQL
Server database, the portal does not
display data till the lock is released.
This is a limitation with the Windows 2008 environment.
The memory usage of data collector
service is high (approximately 150
megabytes) in the case of the SQL Server
agent that runs on the Windows Server
2008 operating system, whereas the
memory usage is about 50 megabytes in
a Windows 2003 environment.

Chapter 9. Troubleshooting 291

Table 29. General agent problems and solutions (continued)
Problem Solution
Configure the Windows server to run on other Windows locale that is
The remote agent functionality (for supported by the agent. Note that the change of locale affects the
example, Start SQL Server, Stop SQL functioning of other applications on the Windows server.
Server actions) and some other
functionality does not work in some
Windows locales, such as English
(India), English (Malaysia), English
(Singapore), and so on. Also, a few
attributes that are of the String data type
show garbage strings instead of
displaying correct values.
None.
If there is a shared or granted locks on
the tempdb database, then the Lock
Detail workspace displays lock
information for the tempdb database on
the portal. However, these locks might
not be counted under the Shared Locks
attribute of the Lock Summary attribute
group.
None.
If the SQL Server agent fails to collect
data, the Server Version attribute in the
Server Summary view of the Enterprise
Server Summary workspace displays
empty value.
Generally every instance of the agent creates an entry in the Task
Multiple instances of some agent Manager. If there are more entries than the total number of configured
processes, such as koqlog.exe, instances, which do not show any CPU usage for long hours but
koqos.exe, and koqserv.exe are continuously persist in the Task Manager, end these processes manually.
displayed in the Task Manager of the
workstation where the SQL Server agent
is installed. The memory usage for these
processes is constant and the CPU usage
is zero.

If you restart the workstation where the This problem occurs when the SQL Server service is not started.
SQL Server agent is installed, the agent
service koqcoll.exe stops and the event If the agent is in the stopped state even though the agent workstation is
viewer displays the following error restarted, recycle the agent from the Manage Tivoli Enterprise Monitoring
message: Services window.
Faulting application koqcoll.exe,
version 0.0.0.0, faulting
module ntdll.dll, version
5.2.3790.4455, fault address
0x00000000.
None.
If a linked server is configured on the
SQL Server, the portal displays incorrect
data for the Network Name attribute of
the Remote Server attribute group.

292 Microsoft SQL Server agent: User’s Guide

Table 29. General agent problems and solutions (continued)
Problem Solution
There is no solution to this problem.
The value of the Collection Level
attribute in the Remote Servers attribute
group is always displayed as 1 on the
Tivoli Enterprise Portal. However, the
possible values of the Collection level
attribute are 1 and 0.
There is no solution to this problem.
Although the incorrect version of the
SQL Server is configured with the SQL
Server agent, the agent data is displayed
on the Tivoli Enterprise Portal.
There is no solution to this problem.
The SQL Server agent takes time to
display data when a large number of
databases (typically, more than 6000) are
created on the SQL Server. The agent
data collector service stops running if
the memory used by the data collector
exceeds the threshold value because of a
large number of databases on the SQL
Server.
Install the SQL Server agent remotely.
You have installed and configured a
64-bit SQL Server agent locally on a
computer. When you start the SQL
Server agent, the collector service
(koqcoll.exe) stops abruptly.
In the "xxxagent.exe Properties" window, There is no solution to this problem.
the following agent information is not
updated:
v Copyright
v File Version
v Product Version
This problem occurs on both Windows
32-bit and 64-bit operating systems.
Note: On Windows 2003 systems, the
agent information is shown in the
Version tab; however, on Windows 2008
systems, the agent information is shown
in the Details tab.
On the z/OS® operating system, while In the History Collection Configuration window, select TEMA in the
configuring all attributes in the History Collection Location field.
Collection Configuration window, if
you select TEMS in the Collection
Location field, the attribute group tables
are not created in the Warehouse
database.

Chapter 9. Troubleshooting 293

Table 29. General agent problems and solutions (continued)
Problem Solution
When you install the 32-bit SQL Server Install the 64-bit SQL Server agent.
agent on a 64-bit operating system and a
64-bit MS SQL Server, you cannot view
data for the following workspaces:
v Analysis services Datamining
Statistics
v Analysis Services Memory Statistics
v Analysis services Storage Engine
Query processing
v Analysis Services Row Processing
The 64-bit SQL Server agent displays a Install the service pack 1 of the 64-bit Windows 2008 R2 operating
high use of memory when the agent is system.
installed and configured on the 64-bit
Windows 2008 R2 operating system.
On the Tivoli Enterprise Portal, no value Complete the following steps to resolve the problem:
is displayed for the primary replica in 1. In the Failover Cluster Manager, right-click the cluster node that hosts
the Availability Group Details attribute the SQL Server agent.
group. This problem occurs when you
2. If you have paused the cluster service on the node, click Resume. If
pause or stop the cluster service on the
you have stopped the cluster service on the node, click Start.
node that hosts the SQL Server agent.
On the Tivoli Enterprise Portal, incorrect Refresh the Tivoli Enterprise Portal after applying the custom query for
values are displayed when a custom the following attribute groups:
query is applied for the following v MS SQL Availability Groups Summary
attribute groups:
v MS SQL Availability Database Summary
v MS SQL Availability Groups Summary
v MS SQL Availability Database Details
v MS SQL Availability Database
v MS SQL Availability Replicas Status Summary
Summary
v MS SQL Availability Replicas Details In Cluster
v MS SQL Availability Database Details
v MS SQL Service Broker Activation
v MS SQL Availability Replicas Status
Summary
v MS SQL Availability Replicas Details
In Cluster
v MS SQL Service Broker Activation
On the Tivoli Enterprise Portal, the There is no solution to this problem.
Stolen Pages Growth attribute displays
negative values. The value for the Stolen
Pages Growth attribute is calculated on
the basis of the previous and the current
sample data.

294 Microsoft SQL Server agent: User’s Guide

Table 29. General agent problems and solutions (continued)
Problem Solution
You delete the Microsoft SQL Server After deleting the Microsoft SQL Server agent, close the Manage Tivoli
agent by completing the following steps: Enterprise Monitoring Services window and reopen it before you
v Click Start > Programs > IBM Tivoli configure the monitoring agent again.
Monitoring > Manage Tivoli
Enterprise Monitoring Services.
v In the Manage Tivoli Enterprise
Monitoring Services window,
right-click Microsoft SQL Server
agent, and click Advanced > Remove
Instance.
After the Microsoft SQL Server agent is
deleted, the status of the agent and
collector services changes to Disabled. If
you configure the SQL Server agent
again by using the agent configuration
panel without closing the Manage Tivoli
Enterprise Monitoring Services window,
the agent fails to start.
The Not collected enumeration value is There is no solution to this problem.
incorrectly displayed as -0.01 in the
warehouse database. Similarly, the Not
applicable enumeration value is
incorrectly displayed as -0.02 in the
warehouse database. While designing
Tivoli Common Reporting reports, the
value -0.01 must be displayed as Not
collected, and the value -0.02 must be
displayed as Not applicable in the
reports. The correct enumeration value
for Not collected is -1 and the correct
enumeration value for Not applicable
attribute is -2.
While upgrading the SQL Server agent There is no solution to this problem.
to version 6.3, the following message
appears:
Creating instance at Path
c:\IBM\ITM\TMAITM6\koqcma.ini
Product Code KOQ Instance instance
name failed

However, the SQL Server agent is

successfully upgraded to version 6.3.

Chapter 9. Troubleshooting 295

Table 29. General agent problems and solutions (continued)
Problem Solution
The configuration file of the MS SQL Update the koqErrConfig.ini file to resolve this issue. For example, for
Problem Detail attribute group cannot the French language, update the koqErrConfig.ini file to reflect the
handle non-English ERRORLOG files by following format:
default. [French_CI_AS]
Error=Erreur :
Severity=Gravité :
State=État:

For the English language, update koqErrConfig.ini the file to reflect the
following format:
[SQL_Latin1_General_CP1_CI_AS]
Error=Error:
Severity=Severity:
State=State:

Note: If you are using the 32-bit Microsoft SQL Server agent, the
koqErrConfig.ini file is saved in the candle_home\TMAITM6 directory. If
you are using the 64-bit SQL Server agent, the koqErrConfig.ini file is
saved in the candle_home\TMAITM6_x64 directory.
If the device type is FILESTREAM for There is no solution to this problem.
any database, the attributes in the MS
SQL Device Detail attribute group
display negative or incorrect values for
the database.

Troubleshooting for remote deployment

Table 30 lists problems that might occur with remote deployment. This section provides information
about troubleshooting remote deployment of the monitoring agent. See the IBM Tivoli Monitoring
Troubleshooting Guide for general troubleshooting information.

This section describes problems and solutions for remote deployment and removal of agent software
Agent Remote Deploy:
Table 30. Remote deployment problems and solutions
Problem Solution
Remote deployment fails because the process Increase the amount of time allowed for remote deployment,
exceeds the communication timeout. as described in the "Troubleshooting Tivoli Enterprise
Monitoring Agent problems" chapter of the IBM Tivoli
Monitoring Troubleshooting Guide.
You have one of following problems after you use Ensure that you have typed the correct values for the
the tacmd addSystem command to perform a remote parameters in the tacmd addSystem command. For example,
deployment: to run the command successfully, you must provide correct
v The Tivoli Enterprise Portal fails to display values for the following parameters:
workspaces for the monitoring agent. v the home directory of the database server
—OR— v the name of the Microsoft SQL Server that you want to
v You see the KDY1008E error message and a return monitor
code of 4. v the name of the Microsoft SQL Server instance that you
want to monitor
See Chapter 2, “Agent installation and configuration,” on
page 15 for more information on these parameters.

296 Microsoft SQL Server agent: User’s Guide

Table 30. Remote deployment problems and solutions (continued)
Problem Solution
While you are using the remote deployment feature Do not close or modify this window. It is part of the
to install Microsoft SQL Server agent, an empty installation process and will be dismissed automatically.
command window is displayed on the target
computer. This problem occurs when the target of
remote deployment is a Windows computer. (See the
IBM Tivoli Monitoring Installation and Setup Guide for
more information on the remote deployment
feature.)
The removal of a monitoring agent fails when you This problem might happen when you attempt the remote
use the remote removal process in the Tivoli removal process immediately after you have restarted the
Enterprise Portal desktop or browser. Tivoli Enterprise Monitoring Server. You must wait at least 10
minutes for the monitoring agent to refresh its connection
with the Tivoli Enterprise Monitoring Server before you begin
the remote removal process.
When you run the tacmd command with the The property DBSETTINGS.db_ver is not valid for V6.2.1 of
DBSETTINGS.db_ver property, the following error the SQL Server agent. Run the tacmd describeSystemType
message is displayed: command to view the properties that are permitted for the
The property DBSETTINGS.db_ver is invalid for agent type. If you run the tacmd command by using a script,
version 062100000 of the OQ agent. you must modify the script to remove the
DBSETTINGS.db_ver option.
If you have not specified the parameter values in the Enter the parameter values in the Table Detail Collection
Table Detail Collection Settings pane in the Database Settings pane in the Database Server Properties window for
Server Properties window and the size of the tables data collection of Table Detail attribute group.
in the databases is large, agent data is not displayed
on the Tivoli Enterprise Portal.
You have installed an agent of ITCAM for Microsoft Specify the account information in the domain\user format.
Applications remotely from the Tivoli Enterprise
Portal Client. On the Agent tab of the Managed
System Configuration window, you selected the Use
this account option, and typed the account
information in the "[email protected]"; format (for
example, [email protected]). The
Deployment Status Detail view shows the agent
deployment status as failed; however, the agent is
configured and installed with the LocalSystem
account instead of the specified user account.

Workspace troubleshooting
Table 31 shows problems that might occur with workspaces. This chapter provides agent-specific
troubleshooting information. See the IBM Tivoli Monitoring Troubleshooting Guide for general
troubleshooting information.
Table 31. Workspace problems and solutions
Problem Solution
No data is displayed for the monitoring 1. Confirm that the computer that hosts the monitoring agent is
agent in the workspaces of the Tivoli communicating with the Tivoli Enterprise Monitoring Server.
Enterprise Portal.
2. Verify the Microsoft SQL Server configuration credentials that you
used during configuration of the monitoring agent. The credentials
must match the options listed in Chapter 2, “Agent installation and
configuration,” on page 15.

Chapter 9. Troubleshooting 297

Table 31. Workspace problems and solutions (continued)
Problem Solution
You start collection of historical data but
the data cannot be seen. Managing options for historical data collection:
v Basic historical data collection populates the Warehouse with raw data.
This type of data collection is turned off by default. See Chapter 2,
“Agent installation and configuration,” on page 15 for information on
managing this feature including how to set the interval at which data is
collected. By setting a more frequent interval for data collection you
reduce the load on the system incurred every time data is uploaded.
v You use the Summarization and Pruning monitoring agent to collect
specific amounts and types of historical data. Be aware that historical
data is not displayed until the Summarization and Pruning monitoring
agent begins collecting the data. By default, this agent begins collection
at 2 AM daily. At that point, data is visible in the workspace view. See
the IBM Tivoli Monitoring Administrator's Guide to learn how to
modify the default collection settings.
The following workspace views display
column headers, but no data: Process The workspaces containing these views only display valid data when the
Holding Lock SQL Text, Blocking workspace is accessed from a workspace link. Workspace Administrators
Process SQL Text, Waiting Process SQL may access these workspaces directly (without following the correct
Text, and SQL Text workspace link) and this will result in no data being displayed for these
views. When you want to view monitored data in these views, use the
workspace links. See the workspaces chapter of this user's guide for
additional information on these workspace views.

The SQL Server ID configured for use by the MS SQL agent requires
System Administrators SQL Server Role authorization to access the SQL
text data. If you want to display SQL test information, give System
Administrators authorization to the MS SQL agent's SQL Server user ID.
Refer to the Chapter 2, “Agent installation and configuration,” on page 15
section in this book.
The Microsoft SQL Server agent The absence of the target MS SQL Server performance counters causes
workspace views have empty data, and this problem. If these prerequisite counters are not installed and enabled,
there is no hostname_OQ_sql server the monitoring agent is not able to properly collect monitoring data for
instance name__regtitls.txt file in the the target MS SQL Server. When this happens, the RAS1 trace log contains
TMAITM6\logs subdirectory. the following error trace message: SQL Server Instance performance data
is not enabled!

This might be caused by installing the MS SQL Server instance using a

Minimum installation setup type, or by not selecting Performance
Counters from a Custom installation setup type. Install and configure the
performance counters for the target MS SQL Server instance. This might
require reinstallation of the MS SQL Server instance. Use either the
Typical or Custom installation setup type.

298 Microsoft SQL Server agent: User’s Guide

Table 31. Workspace problems and solutions (continued)
Problem Solution
When configuring the time span for the When configuring the time span, click the Apply to all views associated
historical data in the Errorlog Alerts with this view's query checkbox in the Select the Time Span property
workspace, the time span icon will gray box and click OK.
out (become inactive) and no historical
data will be displayed. –OR–

Regenerate the query for each view by:

1. Right-click the view with the inactive time span icon.
2. Select Properties.
3. Click Click here to assign a query.
4. Reselect the query assigned for that view.
5. Click Apply on the Query Editor page.
When creating a job in the SQL Server, Do not specify the job name in double quotation marks.
if you specify the job name in double
quotation marks, then the Job Detail and
Job Status views of the Job Detail
workspace do not display data rows on
the portal.
When creating a database in the SQL Do not specify the database name in single or double quotation marks.
Server, if you specify the database name
in single quotation marks, then the last
character of the database name is
truncated on the portal. If you specify a
database name in double quotation
marks, then the value of the Database
Name attribute is displayed as blank on
the portal.
In the Table Detail workspace, the agent There is no workaround for this problem.
does not show table details for empty
tables (tables that do not contain rows)
in the SQL Server database.
The portal displays incorrect value for There is no workaround for this problem.
the Database State attribute of the MS
SQL Database Detail attribute group if
the database name contains single or
double quotation marks.
The following views in the Tivoli The database is not accessible when the database is in one of the
Enterprise Portal do not display data following states:
rows for the databases that are not v Offline
accessible.
v Restoring
v Device Detail view of the Device
v Transition
Detail workspace
v File group Detail view of the File Make sure that the state of the database is online.
group Detail workspace

Because the database is not accessible,

no data is retuned by the database that
can be displayed in the portal.

Chapter 9. Troubleshooting 299

Table 31. Workspace problems and solutions (continued)
Problem Solution
The Tivoli Enterprise Portal client There is no workaround for this problem.
displays negative values for the
Transactions per second and the
Database Growth Percent attributes in
the Database Detail view of the
Database Information workspace.

If you have multiple databases having

four or more characters in the database
name common, the Tivoli Enterprise
Portal client displays negative values for
the Transactions per second and the
Database Growth Percent attributes in
the Database Detail view. The SQL
Server agent calculates the values of the
Transactions per second and the
Database Growth Percent attributes
based on the previous and current
sample data.
The portal does not display rows for the None.
Statistic Name attribute values, such as
connections, physical reads, physical
write, I/O Errors in the MS SQL
Statistics Detail attribute group.
On the Tivoli Enterprise Portal, the Alert There is no solution to this problem.
Detail view in the Errorlog Alerts
workspace does not display data for
more than 200 error messages with a
severity level 17 or more.
On the Tivoli Enterprise Portal, the There is no solution to this problem.
Fragmentation (greater than 30%) by
Index Name view does not display the
index name in the bar chart when the
index value is zero. The Fragmentation
(greater than 30%) by Index Name view
is available in the Table Detail
workspace.
On the Tivoli Enterprise Portal, the There is no solution to this problem.
Fragmentation (greater than 30%) by
Index Name view displays the
fragmentation data in the bar chart
although the fragmentation is below
30%.
There is an inconsistency in the There is no solution to this problem.
representation of the value
Not_Collected in a bar chart for
different workspaces.

300 Microsoft SQL Server agent: User’s Guide

Table 31. Workspace problems and solutions (continued)
Problem Solution
You have installed the Tivoli Enterprise Reconfigure history collection, and set the collection location as TEMA for
Monitoring Server on z/OS. In the these attribute groups.
Configuration panel of the History
Collection Configuration window, if you
have selected TEMS from the
Collection Location list, then the Tivoli
Enterprise Portal does not display
historical data for all the attribute
groups.

Situation troubleshooting
This section provides information about both general situation problems and problems with the
configuration of situations. See the IBM Tivoli Monitoring Troubleshooting Guide for more information about
troubleshooting for situations.

General situation problems

Table 32 lists problems that might occur with specific situations.
Table 32. Specific situation problems and solutions
Problem Solution
You want to change the appearance of 1. Right-click an item in the Navigation tree.
situations when they are displayed in a
2. Select Situations in the pop-up menu. The Situation Editor window is
Workspace view.
displayed.
3. Select the situation that you want to modify.
4. Use the Status pull-down menu in the lower right of the window to
set the status and appearance of the Situation when it triggers.
Note: This status setting is not related to severity settings in IBM
Tivoli Enterprise Console.
Monitoring activity requires too much Check the RAS trace logging settings that are described in “RAS trace
disk space. parameters” on page 275. For example, trace logs grow rapidly when you
apply the ALL logging option.
Monitoring activity requires too many If possible, reduce the number of attributes that you monitor to a smaller
system resources. set.

Be aware that the Table Detail attribute group can consume significant
system resources because it gathers data from each table and index in
each database that you monitor.
A formula that uses mathematical This formula is incorrect because situation predicates support only logical
operators appears to be incorrect. For operators. Your formulas cannot have mathematical operators.
example, if you were monitoring Linux, Note: The Situation Editor provides alternatives to math operators.
a formula that calculates when Free Regarding the example, you can select % Memory Free attribute and
Memory falls under 10 percent of Total avoid the need for math operators.
Memory does not work: LT
#’Linux_VM_Stats.Total_Memory’ / 10
Situations that you create display the For a situation to have the correct severity in TEC for those situations
severity UNKNOWN in IBM Tivoli which are not mapped, you need to ensure that an entry exists in the
Enterprise Console. tecserver.txt file for the situation and that SEVERITY is specified.

See the “Configuring Tivoli Enterprise Console integration” chapter in the

IBM Tivoli Monitoring Administrator's Guide for more information.

Chapter 9. Troubleshooting 301

Table 32. Specific situation problems and solutions (continued)
Problem Solution
You see the Unable to get attribute
name error in the Tivoli Enterprise Ensure that the agent attribute files are installed on the Tivoli Enterprise
Monitoring Server log after creating a Monitoring Server.
situation.
The following example shows a typical log entry when you have this
problem:
(4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer") \
Unable to get attribute name for tablename/column \
<UAG524400.UA4>. Ignored.
Situations are triggered in the Tivoli None. This is a limitation of the Tivoli Enterprise Monitoring Server event
Enterprise Monitoring Server, but events forwarding function. Situations that only monitor other situations do not
for the situation are not sent to the send events to the event server.
Tivoli Enterprise Console server. The
Tivoli Enterprise Monitoring Server is This condition can occur when a situation is only monitoring the status of
properly configured for event other situations. The event forwarding function requires an attribute
forwarding, and events for many other group reference in the situation in order to determine the correct event
situations are sent to the event server. class to use in the event. When the situation only monitors other
situations, no attribute groups are defined and the event class cannot be
determined. Because the event class cannot be determined, no event is
sent.
The situation None.
MS_SQL_Rem_Serv_Stat_Critical
triggers when the SQL Server is down
or the Microsoft SQL Server agent
collector service is stopped (that means
when the collector service fails to collect
data.)
The MS_SQL_Status_Critical situation is Enter the parameters values in the Table Detail Collection Settings pane in
triggered when the SQL Server, the SQL the Database Server Properties window for the data collection of the Table
Server agent, and the collector service of Detail attribute group.
the SQL Server agent is running.

Problems with configuration of situations

Table 33 lists problems that might occur with situations.

This section provides information for troubleshooting for agents. Be sure to consult the IBM Tivoli
Monitoring Troubleshooting Guide for more general troubleshooting information.
Table 33. Problems with configuring situations that you solve in the Situation Editor
Problem Solution
Note: To get started with the solutions in this section, perform these steps:
1. Launch the Tivoli Enterprise Portal.
2. Click Edit > Situation Editor.
3. In the tree view, choose the agent whose situation you want to modify.
4. Choose the situation in the list. The Situation Editor view is displayed.
The situation for a specific agent is v Open the Situation Editor. Access the All managed servers view. If the
not visible in the Tivoli Enterprise situation is absent, confirm that application support for Microsoft SQL Server
Portal. agent has been added to the monitoring server. . If not, add application
support to the server, as described in the IBM Tivoli Monitoring Installation
and Setup Guide.
v Click the Action tab and check whether the situation has an automated
corrective action. This action can occur directly or through a policy. The
situation might be resolving so quickly that you do not see the event or the
update in the graphical user interface.

302 Microsoft SQL Server agent: User’s Guide

Table 33. Problems with configuring situations that you solve in the Situation Editor (continued)
Problem Solution
The monitoring interval is too Access the Situation Editor view for the situation that you want to modify.
long. Check the Sampling interval area in the Formula tab. Adjust the time interval
as needed.
The situation did not activate at Manually recycle the situation as follows:
startup. 1. Right-click the situation and choose Stop Situation.
2. Right-click the situation and choose Start Situation.
Note: You can permanently avoid this problem by placing a check mark in the
Run at Startup option of the Situation Editor view for a specific situation.
An Alert event has not occurred Check the logs, reports, and workspaces.
even though the predicate has been
properly specified.
A situation fires on an unexpected Confirm that you have distributed and started the situation on the correct
managed object. managed system.
The product did not distribute the Click the Distribution tab and check the distribution settings for the situation.
situation to a managed system.
The situation does not fire. Click the Distribution tab and check the distribution settings for the situation.

Incorrect predicates are present in In the Formula tab, analyze predicates as follows:
the formula that defines the 1. Click the fx icon in the upper-right corner of the Formula area. The Show
situation. For example, the formula window is displayed.
managed object shows a state that
a. Confirm the following details in the Formula area at the top of the
normally triggers a monitoring
window:
event, but the situation is not true
v The attributes that you intend to monitor are specified in the formula.
because the wrong attribute is
v The situations that you intend to monitor are specified in the formula.
specified in the formula.
v The logical operators in the formula match your monitoring goal.
v The numerical values in the formula match your monitoring goal.
b. (Optional) Click the Show detailed formula check box in the lower left
of the window to see the original names of attributes in the application
or operating system that you are monitoring.
c. Click OK to dismiss the Show formula window.
2. (Optional) In the Formula area of the Formula tab, temporarily assign
numerical values that will immediately trigger a monitoring event. The
triggering of the event confirms that other predicates in the formula are
valid.
Note: After you complete this test, you must restore the numerical values
to valid levels so that you do not generate excessive monitoring data based
on your temporary settings.

Table 34. Problems with configuration of situations that you solve in the Workspace area
Problem Solution
Situation events are not displayed Associate the situation with a navigator item.
in the Events Console view of the Note: The situation does not need to be displayed in the workspace. It is
workspace. sufficient that the situation be associated with any navigator item.
You do not have access to a Note: You must have administrator privileges to perform these steps.
situation. 1. Select Edit > Administer Users to access the Administer Users window.
2. In the Users area, select the user whose privileges you want to modify.
3. In the Permissions tab, Applications tab, and Navigator Views tab, select
the permissions or privileges that correspond to the user's role.
4. Click OK.

Chapter 9. Troubleshooting 303

Table 34. Problems with configuration of situations that you solve in the Workspace area (continued)
Problem Solution
A managed system seems to be 1. Allow several minutes to pass whenever you restart the Tivoli Enterprise
offline. Portal Server. A managed system will seem to be down while the portal
server is restarting.
2. Select Physical View and highlight the Enterprise Level of the navigator
tree.
3. Select View > Workspace > Managed System Status to see a list of
managed systems and their status.
4. If a system is offline, check network connectivity and status of the specific
system or application.

Table 35. Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Services
window
Problem Solution
After an attempt to restart the Check the system status and check the appropriate IBM Tivoli Monitoring logs.
agents in the Tivoli Enterprise
Portal, the agents are still not
running.
The Tivoli Enterprise Monitoring Check the system status and check the appropriate IBM Tivoli Monitoring logs.
Server is not running.

Take Action command troubleshooting

Table 36 lists general problems that might occur with Take Action commands. When each Take Action
command runs it generates the log file listed in Table 24 on page 272. This chapter provides agent-specific
troubleshooting information. See the IBM Tivoli Monitoring Troubleshooting Guide for general
troubleshooting information.
Table 36. Take Action commands problems and solutions
Problem Solution
Take Action commands might require several Allow several minutes. If you do not see a pop-up message
minutes to complete. advising you of completion, try to run the command manually.
If you are unable to perform the Take Action command
manually, see the IBM Tivoli Monitoring Troubleshooting Guide for
general information on troubleshooting the Take Action
command.
A Take Action command fails with a pop-up Check the trace log of the Take Action command. If you see a
message containing a non-zero return value. log entry containing the "insufficient authorization" string, verify
that you are using one of the authorizations for Microsoft SQL
Server that are listed in Chapter 6, “Take Action commands
reference,” on page 239.
Dump Transaction Log Take Action command The documentation might list a "backup and truncate" option.
fails. The task fails if you use this option as documented. You must
use the following syntax for this option: BackupAndTruncate

304 Microsoft SQL Server agent: User’s Guide

Table 36. Take Action commands problems and solutions (continued)
Problem Solution
When running koqDumpDatabase take action The backup actually occurred. The error can be ignored.
command against a SQL Server 2005, the
following (or similar) trace information might be
returned in the take action's trace log:
(48244D4D.0000-
1AF8:koqdumpdatabase.cpp,137,"main") Calling
DumpDatabase DLL API(48244D51.0000-
1AF8:koqdumpdatabase.cpp,145,"main")
koqdumpdatabase has found an
error:(48244D51.0001-
1AF8:koqdumpdatabase.cpp,146,"main") Error
code: 1(48244D51.0002-
1AF8:koqdumpdatabase.cpp,147,"main") Error
source: dmoDumpDatabase(48244D51.0003-
1AF8:koqdumpdatabase.cpp,148,"main") Error
description:
+48244D51.0003{ERROR:8011:101102tivoliTIV162\
TIV162OTHmsdb6112005-10-14
01:54:05.00049259526700000

Tivoli Common Reporting troubleshooting

Table 37 contains a list of problems that might occur with the Tivoli Common Reporting predefined
reports for Microsoft SQL Server agent.

For information about troubleshooting for the Tivoli Common Reporting tool, see http://
publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_welcome.html.
Table 37. Tivoli Common Reporting for Microsoft SQL Server agent problems and solutions
Problem Solution
When you simultaneously query two tables in the Query This problem occurs when a relationship between the
Studio interface, no data is displayed. However, when tables is not defined. To resolve this problem, ensure that
you query the two tables separately, data is displayed. all the ad hoc queries have at least one identifier.
When you create an ad hoc query by dragging some This is an SQL error related to arithmetic flow. This error
columns in the Query Studio interface, the following is generated because the average or the sum for certain
error message is displayed: columns is more than the threshold size that is defined
RQP-DEF-0177 An error occurred in the database. To resolve this error, use the limited
while performing columns and add a standard timestamp while creating
operation ’sqlPrepareWithOptions’ an ad hoc query.
status=’-232’.
If a view or a table for the selected summarization type To resolve this problem, complete the following tasks:
does not exist in the database for a report, the report v Verify that the summarization and pruning agent is
does not open and the following error message is working correctly.
displayed:
v Generate data for all the summarization types.
RQP-DEF-0177 An error occurred
while performing v Verify that the warehouse is collecting historical data.
operation ’sqlPrepareWithOptions’
status=’-232’.

Chapter 9. Troubleshooting 305

Table 37. Tivoli Common Reporting for Microsoft SQL Server agent problems and solutions (continued)
Problem Solution
When you run a report, the report is not displayed in the This problem occurs due to incorrect data source. To
correct format and the following error message is resolve this problem, complete the following tasks:
displayed: v Verify that the datasource configuration parameters are
RQP-DEF-0177 An error occurred configured correctly.
while performing v Verify that the specified values for the parameters of
operation ’sqlPrepareWithOptions’
the summarization and pruning agent such as
status=’-232’.
database URL, driver user, and password match with
the values of these parameters on the database.
If data is not available in the database for the selected To resolve this error, complete the following tasks:
parameters, the following error message is displayed v Configure the summarization and pruning agent and
after querying these parameters: verify that it is working correctly.
Empty data set No data returned by query. v Generate data for all the summarization types in the
Try another set of parameters. database.
Reports are not generated correctly in the Microsoft Excel There are some limitations to generate reports in the
format. Microsoft Excel format. To view these limitations, see the
IBM Cognos Business Intelligence Information Center
(http://publib.boulder.ibm.com/infocenter/
cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.
cognos.ug_cr_rptstd.10.1.0.doc%2Fug_cr_rptstd_
id32474excel_limitations.html).
When you view a report spanning multiple pages in the No solution is available for this problem at this time.
PDF format, the report parameters section is displayed at
the top of each page.
Charts are not displayed correctly in Microsoft Excel No solution is available for this problem at this time.
2007.
Labels for some charts are displayed in the HTML The font size is rendered differently in the HTML and
output, but are not displayed in the PDF output. the PDF output. In the PDF output, some fonts are not
displayed because of the large font size. To resolve this
issue, reduce the font size by completing the following
steps:
1. Open the report in Report Studio.
2. Click the chart.
3. In the chart properties, select Font.
4. Modify the font properties, such as family, size,
weight, and style.
5. Save the settings, and run the report in the PDF
format.
The value of the Not collected attribute is incorrectly There is no solution to this problem.
displayed as -0.01 in the warehouse database. Similarly,
the value of the Not applicable attribute is incorrectly
displayed as -0.02 in the warehouse database. While
designing the Tivoli Common Reporting reports, the
value -0.01 must be displayed as Not collected, and the
value -0.02 must be displayed as Not applicable in the
reports.

The correct value for the Not collected attribute is -1 and

the correct value for the Not applicable attribute is -2.

306 Microsoft SQL Server agent: User’s Guide

Support information
If you have a problem with your IBM software, you want to resolve it quickly.

IBM provides the following ways for you to obtain the support you need:
Online
The following websites contain troubleshooting information:
v Go to the IBM Software Support website (http://www.ibm.com/support/entry/portal/
software) and follow the instructions.
v Go to the Application Performance Management Wiki (http://www.ibm.com/developerworks/
servicemanagement/apm/index.html). Feel free to contribute to this wiki.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability workbench that helps you
resolve questions and problems with IBM software products. The ISA provides quick access to
support-related information and serviceability tools for problem determination. To install the ISA
software, go to the IBM Support Assistant website (http://www.ibm.com/software/support/isa).

Chapter 9. Troubleshooting 307

308 Microsoft SQL Server agent: User’s Guide
Appendix A. Upgrading for warehouse summarization
Refer to appendix A only when you are upgrading the agent from V6.1 to V6.2.1. This appendix does not
apply when you are upgrading the agent from V6.2 to V6.2.1.

The Microsoft SQL Server agent made changes to the warehouse collection and summarization
characteristics for some agent attribute groups. These changes correct and improve the way warehouse
data is summarized, producing more meaningful historical reports. This appendix explains those changes
and the implications to your warehouse collection and reporting.

Warehouse summarization is controlled on a per-table basis. How the rows in each table are summarized
is determined by a set of attributes in each table that are designated as primary keys. There is always one
primary key representing the monitored resource, and data is minimally summarized based on this value.
For all agents, this primary key is represented internally by the column name, ORIGINNODE; however,
the external attribute name varies with each monitoring agent.

One or more additional primary keys are provided for each attribute group to further refine the level of
summarization for that attribute group. For example, in an OS agent disk attribute group, a primary key
might be specified for the logical disk name that allows historical information to be reported for each
logical disk in a computer.

Tables in the warehouse

For a monitoring agent, there are two main types of warehouse tables:
v Raw tables:
These tables contain the raw information reported by a monitoring agent and written to the warehouse
by the Warehouse Proxy agent. Raw tables are named for the attribute group that they represent, for
example, MS_SQL_DATABASE_DETAIL.
v Summary tables:
These tables contain summarized information based on the raw tables and written to the warehouse by
the Summarization and Pruning agent. Summarization provides aggregation results over various
reporting intervals, for example, hours, days, and so on. Summary table names are based on the raw
table name with an appended suffix, for example, MS_SQL_DATABASE_DETAIL_H,
MS_SQL_DATABASE_DETAIL_D, and so on.

Effects on summarized attributes

When tables are summarized in the warehouse, the summary tables and summary views are created to
include additional columns to report summarization information. Table 38 contains a list of the time
periods and the suffixes for the summary tables and views.
Table 38. Time periods and suffixes for summary tables and views
Data collection time period Summary table suffixes Summary view suffixes
Hourly _H _HV
Daily _D _DV
Weekly _W _WV
Monthly _M _MV
Quarterly _Q _QV
Yearly _Y _YV

© Copyright IBM Corp. 2005, 2012 309

Table 39 shows the expansion to summary columns of some of the most commonly used attribute types.
Table 39. Additional columns to report summarization information
Attribute name Aggregation type Additional summarization columns
MyGauge GAUGE
MIN_MyGauge
MAX_MyGauge
SUM_MyGauge
AVG_MyGauge
MyCounter COUNTER
TOT_MyCounter
HI_MyCounter
LO_MyCounter
LAT_MyCounter
MyProperty PROPERTY LAT_Property

These additional columns are provided only for attributes that are not primary keys. In the cases when
an existing attribute is changed to be a primary key, the Summarization and Pruning agent no longer
creates summarization values for the attributes, but the previously created column names remain in the
table with any values already provided for those columns. These columns cannot be deleted from the
warehouse database, but as new data is collected, these columns will not contain values. Similarly, when
the primary key for an existing attribute has its designation removed, that attribute has new
summarization columns automatically added. As new data is collected, it is used to populate these new
column values, but any existing summarization records do not have values for these new columns.

The overall effect of these primary key changes is that summarization information is changing. If these
changes result in the old summarization records no longer making sense, you can delete them. As a part
of warehouse upgrade, summary views are dropped. The views will be recreated by the Summarization
and Pruning agent the next time it runs. Dropping and recreating the views ensure that they reflect the
current table structure.

Upgrading your warehouse with limited user permissions

The IBM Tivoli Monitoring warehouse agents (Warehouse Proxy and Summarization and Pruning agents)
can dynamically adjust warehouse table definitions based on attribute group and attribute information
being loaded into the warehouse. These types of table changes must be done for this monitoring agent
for one or both of the following conditions:
v The monitoring agent has added new attributes to an existing attribute group and that attribute group
is included in the warehouse.
v The monitoring agent has added a new attribute group and that attribute group is included in the
warehouse.

For the warehouse agents to automatically modify the warehouse table definitions, they must have
permission to alter warehouse tables. You might not have granted these agents these permissions,
choosing instead to manually define the raw tables and summary tables needed for the monitoring
agents. Or, you might have granted these permissions initially, and then revoked them after the tables
were created.

You have two options to effect the required warehouse table changes during the upgrade process:
v Grant the warehouse agents temporary permission to alter tables
If using this option, grant the permissions, start historical collection for all the desired tables, allow the
Warehouse Proxy agent to add the new data to the raw tables, and allow the Summarization and
Pruning agent to summarize data for all affected tables. Then, remove the permission to alter tables

310 Microsoft SQL Server agent: User’s Guide

v Make the warehouse table updates manually
If using this option, you must determine the table structures for the raw and summary tables. If you
manually created the tables in the earlier warehouse definition, you already have a methodology and
tools to assist you in this effort. You can use a similar technique to update and add new tables for this
warehouse migration.
For a method of obtaining raw table schema, refer to the IBM Redbook,Tivoli Management Services
Warehouse and Reporting, January 2007, SG24-7290. The chapter that explains warehouse tuning includes
a section on creating data tables manually.

Appendix A. Upgrading for warehouse summarization 311

312 Microsoft SQL Server agent: User’s Guide
Appendix B. Event mapping
The Tivoli Event Integration Facility (EIF) interface is used to forward situation events to Tivoli
Netcool/OMNIbus or Tivoli Enterprise Console.

EIF events specify an event class and the event data is specified as name value pairs that identify the
name of an event slot and the value for the slot. An event class can have subclasses. IBM Tivoli
Monitoring provides the base event class definitions and a set of base slots that are included in all
monitoring events. Agents extend the base event classes to define subclasses that include agent-specific
slots. For Microsoft SQL Server agent events, the event classes correspond to the agent attribute groups,
and the agent-specific slots correspond to the attributes in the attribute group.

A description of the event slots for each event class is provided in this topic. The situation editor in the
Tivoli Enterprise Portal can be used to perform custom mapping of data to EIF slots instead of using the
default mapping described in this topic. For more information about EIF slot customization, see theTivoli
Enterprise Portal User's Guide .

Tivoli Enterprise Console requires that event classes and their slots are defined in BAROC (Basic Recorder
of Objects in C) files. Each agent provides a BAROC file that contains event class definitions for the agent
and is installed on the Tivoli Enterprise Monitoring Server in the TECLIB directory (install_dir/cms/
TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems) when
application support for the agent is installed. The BAROC file for the agent and the base BAROC files
provided with Tivoli Monitoring must also be installed onto the Tivoli Enterprise Console. For details, see
"Setting up event forwarding to Tivoli Enterprise Console" in the IBM Tivoli Monitoring Installation and
Setup Guide.

Each of the event classes is a child of KOQ_Base and is defined in the oq.baroc (version 6.3) file. The
KOQ_Base event class can be used for generic rules processing for any event from the IBM Tivoli
Composite Application Manager for Microsoft Applications: Microsoft SQL Server Agent..

© Copyright IBM Corp. 2005, 2012 313

Table 40. Overview of attribute groups to event classes and slots
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Summary MS_SQL_Server_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v server_type: STRING
v server_status: STRING
v server_status_enum: STRING
v collection_status: STRING
v collection_status_enum: STRING
v data_cache_size: INTEGER
v data_cache_size_enum: SRING
v procedure_cache_size: INTEGER
v procedure_cache_size_enum: STRING
v percent_max_locks: REAL
v percent_max_locks_enum: STRING
v server_cpu_percent: REAL
v server_cpu_percent_enum: STRING
v total_os_cpu_percent: REAL
v total_os_cpu_percent_enum: STRING
v time_since_startup: INTEGER
v time_since_startup_enum: STRING
v server_version: STRING
v server_version_enum: STRING
v current_interval: INTEGER
v current_interval_enum: STRING
v sample_timestamp: STRING
v description: STRING
v koq_value: STRING
v cache_average_free_scan: INTEGER
v cache_average_free_scan_enum: STRING
v cache_hit_ratio: REAL
v cache_hit_ratio_enum: STRING
v cache_maximum_free_page_scan: INTEGER
v cache_maximum_free_page_scan_enum: STRING
v cache_free_buffers: INTEGER
v cache_free_buffers_enum: STRING
v sqlserveragent_failed_jobs: INTEGER
v sqlserveragent_failed_jobs_enum: STRING
v server_cpu_percent_io: REAL
v server_cpu_percent_io_enum: STRING
v cpu_percent_idle: REAL
v cpu_percent_idle_enum: STRING
(Continued on the next page.)

314 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Summary v total_blocking_lock_requests: INTEGER
(Continued)
v total_blocking_lock_requests_enum: STRING
v total_locks_remaining: INTEGER
v total_locks_remaining_enum: STRING
v lazy_writes_per_sec: REAL
v lazy_writes_per_sec_enum: STRING
v stolen_pages: INTEGER
v stolen_pages_enum: STRING
v stolen_pages_growth: INTEGER
v stolen_pages_growth_enum: STRING
v page_reads_per_sec: REAL
v page_reads_per_sec_enum: STRING
v readahead_pages_per_sec: REAL
v readahead_pages_per_sec_enum: STRING
v page_writes_per_sec: REAL
v page_writes_per_sec_enum: STRING
v checkpoint_pages_per_sec: REAL
v checkpoint_pages_per_sec_enum: STRING
v repl_distribution_delivery_latency: INTEGER
v repl_distribution_delivery_latency_enum: STRING
v repl_distribution_delivered_cmds_
per_sec: REAL
v repl_distribution_delivered_cmds_per_
sec_enum: STRING
v repl_distribution_delivered_trans_per_sec: REAL
v repl_distribution_delivered_trans_per_
sec_enum: STRING
v repl_logreader_delivery_latency: INTEGER
v repl_logreader_delivery_latency_enum: STRING
v repl_logreader_delivered_cmds_per_sec: REAL
v repl_logreader_delivered_cmds_per_
sec_enum: STRING
v repl_logreader_delivered_trans_per_sec: REAL
v repl_logreader_delivered_trans_per_
sec_enum: STRING
v repl_merge_conflicts_per_sec: REAL

Appendix B. Event mapping 315

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Summary v repl_merge_conflicts_per_sec_enum: STRING
(Continued)
v repl_merge_uploaded_changes_per_sec: REAL
v repl_merge_uploaded_changes_per_
sec_enum: STRING
v repl_merge_downloaded_changes_
per_sec: REAL
v repl_merge_downloaded_changes_
per_sec_enum: STRING
v cpu_idle_ms: INTEGER
v cpu_idle_sec_enum: STRING
v cpu_idle_delta: INTEGER
v cpu_idle_delta_enum: STRING
v cpu_usage_sec: INTEGER
v cpu_usage_sec_enum: STRING
v cpu_usage_delta: INTEGER
v cpu_usage_delta_enum: STRING
v total_server_memory: INTEGER
v total_server_memory_enum: STRING
v sql_server_ver: STRING
v sql_server_ver_enum: STRING
v total_pages: INTEGER
v total_pages_enum: STRING
v mixed_page_allocations_per_sec: REAL
v mixed_page_allocations_per_
sec_enum: STRING

316 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Detail MS_SQL_Server_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v server_type: STRING
v server_type_enum: STRING
v server_version: STRING
v server_version_enum: STRING
v server_status: STRING
v server_status_enum: STRING
v current_locks: INTEGER
v current_locks_enum: STRING
v max_locks_allowed: INTEGER
v max_locks_allowed_enum: STRING
v percent_max_locks: REAL
v percent_max_locks_enum: STRING
v data_cache_size: INTEGER
v data_cache_size_enum: STRING
v procedure_cache_size: INTEGER
v procedure_cache_size_enum: STRING
v procedure_cache_percent: REAL
v procedure_cache_percent_enum: STRING
v startup_timestamp: STRING
v startup_timestamp_enum: STRING
v time_since_startup: INTEGER
v time_since_startup_enum: STRING
v error_log_name: STRING
v error_log_name_enum: STRING
v error_log_size: INTEGER
v error_log_size_enum: STRING
v os_type: STRING
v os_type_enum: STRING
v os_version: STRING
v os_version_enum: STRING
v sample_timestamp: STRING
v procedure_buffers_percent_
active: REAL
v procedure_buffers_percent_
active_enum: STRING
v procedure_buffers_total: INTEGER
v procedure_buffers_total_enum: STRING
v procedure_buffers_percent_used: REAL
v procedure_buffers_percent_
used_enum: STRING

Appendix B. Event mapping 317

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Detail v procedure_cache_percent_active: REAL
(Continued)
v procedure_cache_percent_active_enum: STRING
v procedure_cache_pages: INTEGER
v procedure_cache_pages_enum: STRING
v procedure_cache_percent_used: REAL
v procedure_cache_percent_used_enum: STRING
v error_log_name_u: STRING
v error_log_name_u_enum: STRING
v sql_server_ver: STRING
v sql_server_ver_enum: STRING
ITM_MS_SQL_Database_Summary MS_SQL_Database_Summary attribute group
v originnode: STRING
v hub_timestamp: INTEGER
v server: STRING
v host_name: STRING
v total_databases: INTEGER
v minimum_pct_data_freespace: REAL
v minimum_pct_data_freespace_enum: STRING
v minimum_pct_log_freespace: REAL
v minimum_pct_log_freespace_enum: STRING
v total_dbs_in_error: INTEGER
v total_dbs_read_only: INTEGER
v total_dbs_dbo_only: INTEGER
v total_dbs_single_user: INTEGER
v total_dbs_no_free_space_accounting: INTEGER
v current_interval: INTEGER
v sample_timestamp: INTEGER
v description: STRING
v koq_value: STRING

318 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Database_Detail MS_SQL_Database_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v database_name_enum: STRING
v db_id: STRING
v db_id_enum: STRING
v db_owner: STRING
v error_status: STRING
v error_status_enum: STRING
v dbo_only_access: STRING
v dbo_only_access_enum: STRING
v single_user_access: STRING
v single_user_access_enum: STRING
v read_only_access: STRING
v read_only_access_enum: STRING
v select_into_bulkcopy_enabled: STRING
v select_into_bulkcopy_enabled_enum: STRING
v dump_tran_date: STRING
v dump_tran_date_enum: STRING
v free_space_accounting_
suppresed: STRING
v free_space_accounting_
suppresed_enum: STRING
v no_ckpt_after_recovery: STRING
v no_ckpt_after_recovery_enum: STRING
v data_size: REAL
v data_size_enum: STRING
v log_size: REAL
v log_size_enum: STRING
v data_freespace: REAL
v data_freespace_enum: STRING
v log_freespace: REAL
v log_freespace_enum: STRING
v data_freespace_percent: REAL
v data_freespace_percent_enum: STRING
v log_freespace_percent: REAL
v log_freespace_percent_enum: STRING
v total_devices: INTEGER
v total_devices_enum: STRING
(Continued)

Appendix B. Event mapping 319

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Database_Detail MS_SQL_Database_Detail attribute group
(Continued) v sample_timestamp: STRING
v sample_timestamp_enum: STRING
v database_space_percent_used: REAL
v database_space_percent_used_
enum: STRING
v database_status: INTEGER
v database_status_enum: STRING
v log_space_percent_used: REAL
v log_space_percent_used_enum: STRING
v oldest_open_transaction: INTEGER
v oldest_open_transaction_enum: STRING
v suspect_database: INTEGER
v suspect_database_enum: STRING
v replicated_transaction_rate: REAL
v replicated_transaction_rate_enum: STRING
v replicated_transactions: INTEGER
v replicated_transactions_enum: STRING
v replication_latency: INTEGER
v replication_latency_enum: STRING
v db_owner_u: STRING
v database_name_u: STRING
v log_maximum_growth_size: REAL
v log_maximum_growth_size_enum: STRING
v database_maximum_growth_size: REAL
v database_maximum_growth_size_enum: STRING
v last_database_size: REAL
v last_database_size_enum: STRING
v database_growth_percent: REAL
v database_growth_percent_enum: STRING
v active_transactions: INTEGER
v active_transactions_enum: STRING
v transactions_per_second: REAL
v transactions_per_second_enum: STRING
v log_file_names: STRING
v data_file_names: STRING
v write_transactions_per_sec: REAL
v write_transactions_per_sec_
enum: STRING
v long_running_transaction_
process_id: INTEGER

320 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Database_Detail (Continued)
(Continued) v long_running_transaction_process_
id_enum: STRING
v long_running_transaction_
time_per_sec: REAL
v long_running_transaction_
time_per_sec_enum: STRING
v long_running_transaction_name: STRING
v long_running_transaction_name_enum: STRING
v database_state: STRING
v database_state_enum: STRING
v table_count: INTEGER
v table_count_enum: STRING
v access_validation: INTEGER
v access_validation_enum: STRING
v log_growths: INTEGER
v log_growths_enum: STRING
v log_bytes_flushed_per_sec: REAL
v log_bytes_flushed_per_sec_enum: STRING
v data_files_freespace: REAL
v data_files_freespace_enum: STRING
v aggregate_database_freespace: REAL
v aggregate_database_freespace_enum: STRING
v aggregate_database_freespace_pct: REAL
v aggregate_database_freespace_
pct_enum: STRING;

Appendix B. Event mapping 321

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Device_Detail MS_SQL_Device_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_version: STRING
v host_name: STRING
v database_name: STRING
v database_name_enum: STRING
v device_name: STRING
v device_size: REAL
v device_size_enum: STRING
v device_free_space: REAL
v device_free_space_enum: STRING
v device_free_space_percent: REAL
v device_free_space_
percent_enum: STRING
v device_type: STRING
v device_type_enum: STRING
v physical_device_name: STRING
v mirror_device_name: STRING
v mirror_device_name_enum: STRING
v sample_timestamp: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v device_name_u: STRING
v physical_device_name_u: STRING
v sql_server_ver: STRING
ITM_MS_SQL_Error_Event_Detail MS_SQL_Error_Event_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v message_timestamp: STRING
v message_age: INTEGER
v error_id: STRING
v severity_level: INTEGER
v sql_state_code: INTEGER
v message_issuer: STRING
v sample_timestamp: STRING
v message_text_u: STRING
v error_spid: STRING

322 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Lock_Detail MS_SQL_Lock_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v type: STRING
v type_enum: STRING
v process_holding_lock: INTEGER
v process_holding_lock_enum: STRING
v database_name: STRING
v database_id: INTEGER
v database_id_enum: STRING
v table_name: STRING
v table_name_enum: STRING
v page_number: INTEGER
v page_number_enum: STRING
v sample_timestamp: STRING
v lock_resource_type_e: INTEGER
v lock_resource_type_e_enum: STRING
v lock_request_status_e: INTEGER
v lock_request_status_e_enum: STRING
v database_name_u: STRING
v table_name_u: STRING
ITM_MS_SQL_Lock_Conflict_Detail MS_SQL_Lock_Conflict_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v database_id: INTEGER
v server_user_id: STRING
v client_user_id: STRING
v client_group_id: STRING
v requestor_process_id: INTEGER
v blocking_process_id: INTEGER
v sample_timestamp: STRING
v database_name_u: STRING

Appendix B. Event mapping 323

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Text MS_SQL_Text attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v client_host_name: STRING
v client_process_id: STRING
v process_id: INTEGER
v total_cpu_time: REAL
v process_status: STRING
v text: STRING
v sample_timestamp: STRING
v database_name_u: STRING
v text_u: STRING
ITM_MS_SQL_Process_Summary MS_SQL_Process_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v server_cpu_percent_system: REAL
v server_cpu_percent_application: REAL
v total_processes: INTEGER
v total_processes_blocked: INTEGER
v percent_processes_blocked: REAL
v total_processes_infected: INTEGER
v percent_processes_infected: REAL
v total_processes_bad: INTEGER
v percent_processes_bad: REAL
v total_processes_stopped: INTEGER
v percent_processes_stopped: REAL
v total_processes_locksleep: INTEGER
v percent_processes_locksleep: REAL
v total_other_sleep: INTEGER
v percent_processes_othersleep: REAL
v percent_processes_sleeping: REAL
v total_log_suspend: INTEGER
v current_interval: INTEGER
v sample_timestamp: STRING
v description: STRING
v koq_value: STRING

324 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Process_Detail MS_SQL_Process_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v process_id: INTEGER
v database_name: STRING
v process_status: STRING
v total_cpu_time: REAL
v current_cpu_percent_used: REAL
v total_disk_io: INTEGER
v total_memory_alloc: INTEGER
v blocking_process_id: STRING
v os_process_id: STRING
v server_user_id: STRING
v command: STRING
v client_host_name: STRING
v client_process_id: STRING
v program_name: STRING
v client_user_id: STRING
v client_group_id: STRING
v login_name: STRING
v sample_timestamp: STRING
v database_name_u: STRING
v command_u: STRING
v program_name_u: STRING
v koq_duration: INTEGER
v nt_user: STRING

Appendix B. Event mapping 325

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Problem_Summary MS_SQL_Problem_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v age_of_last_error: INTEGER
v maximum_sev_level: STRING
v maximum_sev_timestamp: STRING
v maximum_sev_current_interval: STRING
v total_error_messages: INTEGER
v total_errors_current_interval: INTEGER
v total_errors_high_sev: INTEGER
v total_errors_other: INTEGER
v error_log_size: INTEGER
v current_interval: INTEGER
v sample_timestamp: STRING
v description: STRING
v koq_value: STRING
ITM_MS_SQL_Problem_Detail MS_SQL_Problem_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v message_timestamp: STRING
v message_age: INTEGER
v error_id: STRING
v severity_level: STRING
v sql_state_code: INTEGER
v message_issuer: STRING
v message_text: STRING
v sample_timestamp: STRING
v message_text_u: STRING
v error_spid: STRING

326 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Statistics_Summary MS_SQL_Statistics_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v total_os_cpu_percent_busy: REAL
v total_os_io_percent_busy: REAL
v current_logons: INTEGER
v percent_max_logons_active: REAL
v total_logons_per_second: REAL
v max_user_connections_allowed: INTEGER
v physical_reads_per_second: REAL
v physical_writes_per_second: REAL
v disk_io_current_interval: INTEGER
v io_errors_since_startup: INTEGER
v io_errors_current_interval: INTEGER
v percent_io_errors_current_interval: REAL
v current_interval: INTEGER
v sample_timestamp: STRING
v description: STRING
v koq_value: STRING
v client_count: INTEGER
v client_count_percent_used: REAL
v network_read_rate: INTEGER
v network_write_rate: INTEGER
v percent_user_connections_remaining: REAL
v total_logouts_per_second: REAL
ITM_MS_SQL_Statistics_Detail MS_SQL_Statistics_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v statistic_name: STRING
v statistic_name_enum: STRING
v current_value: INTEGER
v total_since_startup: INTEGER
v average_value_per_second: REAL
v maximum_seen: INTEGER
v minimum_seen: INTEGER
v sample_timestamp: STRING

Appendix B. Event mapping 327

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Remote_Servers MS_SQL_Remote_Servers attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v remote_server_id: STRING
v remote_server_id_enum: STRING
v remote_server_status: STRING
v remote_server_status_enum: STRING
v remote_server_name: STRING
v remote_server_name_enum: STRING
v network_name: STRING
v network_name_enum: STRING
v connection_level: INTEGER
v connection_level_enum: STRING
v current_interval: INTEGER
v current_interval_enum: STRING
v sample_timestamp: STRING
ITM_MS_SQL_Configuration MS_SQL_Configuration attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v config_parameter: STRING
v parm_type: STRING
v parm_type_enum: STRING
v config_value: STRING
v run_value: STRING
v minimum_value: STRING
v maximum_value: STRING
v sample_timestamp: STRING

328 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Enterprise_View MS_SQL_Server_Enterprise_View attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v collection_status: STRING
v collection_status_enum: STRING
v percent_max_locks: REAL
v percent_max_locks_enum: STRING
v server_cpu_percent: REAL
v server_cpu_percent_enum: STRING
v total_os_cpu_percent: REAL
v total_os_cpu_percent_enum: STRING
v time_since_startup: INTEGER
v time_since_startup_enum: STRING
v server_version: STRING
v server_version_enum: STRING
v total_databases: INTEGER
v total_databases_enum: STRING
v minimum_pct_data_freespace: REAL
v minimum_pct_data_
freespace_enum: STRING
v minimum_pct_log_freespace: REAL
v minimum_pct_log_
freespace_enum: STRING
v total_locks: INTEGER
v total_locks_enum: STRING
v total_lock_conflicts: INTEGER
v total_lock_conflicts_enum: STRING
v database_max_locks: STRING
v database_max_locks_enum: STRING
v database_max_blocks: STRING
v database_max_blocks_enum: STRING
v table_max_locks: STRING
v table_max_locks_enum: STRING
v percent_process_block: REAL
v percent_process_block_enum: STRING
v server_cpu_percent_system: REAL
v server_cpu_percent_system_enum: STRING
v server_cpu_percent_application: REAL
v server_cpu_percent_
application_enum: STRING
v total_processes: INTEGER
v total_processes_enum: STRING
(Continued on the next page)

Appendix B. Event mapping 329

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Enterprise_ MS_SQL_Server_Enterprise_View attribute group
View(Continued) v total_processes_blocked: INTEGER
v total_processes_blocked_enum: STRING
v age_of_last_error: INTEGER
v age_of_last_error_enum: STRING
v maximum_sev_level: STRING
v maximum_sev_level_enum: STRING
v maximum_sev_timestamp: STRING
v maximum_sev_timestamp_enum: STRING
v total_errors_high_sev: INTEGER
v total_errors_high_sev_enum: STRING
v error_log_size: INTEGER
v error_log_size_enum: STRING
v current_logons: INTEGER
v current_logons_enum: STRING
v percent_max_logons_active: REAL
v percent_max_logons_
active_enum: STRING
v physical_reads_per_second: REAL
v physical_reads_per_
second_enum: STRING
v physical_writes_per_
second: REAL
v physical_writes_per_second_enum: STRING
v io_errors_current_interval: INTEGER
v io_errors_current_interval_enum: STRING
v sample_timestamp: STRING
v server_status: STRING
v server_status_enum: STRING
v database_max_locks_u: STRING
v database_max_locks_u_enum: STRING
v database_max_blocks_u: STRING
v database_max_blocks_u_enum: STRING
v table_max_locks_u: STRING
v table_max_locks_u_enum: STRING
v sql_server_ver: STRING
v sql_server_ver_enum: STRING

330 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Table_Detail MS_SQL_Table_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v database_name_enum: STRING
v database_id: INTEGER
v database_id_enum: STRING
v table_name: STRING
v table_name_enum: STRING
v table_id: INTEGER
v table_id_enum: STRING
v index_name: STRING
v index_name_enum: STRING
v index_id: INTEGER
v index_id_enum: STRING
v optimizer_statistics_age: INTEGER
v optimizer_statistics_age_enum: STRING
v fragmentation: REAL
v fragmentation_enum: STRING
v space_used: REAL
v space_used_enum: STRING
v sample_timestamp: STRING

Appendix B. Event mapping 331

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Lock_Summary MS_SQL_Lock_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v exclusive_extent_locks: INTEGER
v extent_locks: INTEGER
v update_extent_locks: INTEGER
v exclusive_intent_locks: INTEGER
v shared_intent_locks: INTEGER
v intent_locks: INTEGER
v exclusive_page_locks: INTEGER
v shared_page_locks: INTEGER
v page_locks: INTEGER
v update_page_locks: INTEGER
v exclusive_table_locks: INTEGER
v shared_table_locks: INTEGER
v table_locks: INTEGER
v exclusive_locks: INTEGER
v shared_locks: INTEGER
v sample_timestamp: STRING
v table_lock_escalations_per_sec: REAL

332 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Job_Summary MS_SQL_Job_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v running_jobs_current_interval: INTEGER
v running_jobs_current_
interval_enum: STRING
v max_running_jobs_interval: INTEGER
v max_running_jobs_
interval_enum: STRING
v jobs_failed_current_interval: INTEGER
v jobs_failed_current_interval_enum: STRING
v max_jobs_failed_interval: INTEGER
v max_jobs_failed_
interval_enum: STRING
v jobs_failed_since_startup: INTEGER
v jobs_failed_since_
startup_enum: STRING
v sample_timestamp: STRING
v active_jobs: INTEGER
v active_jobs_enum: STRING
v failed_jobs: INTEGER
v failed_jobs_enum: STRING
v job_success_rate: REAL
v job_success_rate_enum: STRING
v queued_jobs: INTEGER
v queued_jobs_enum: STRING
v successful_jobs: INTEGER
v successful_jobs_enum: STRING

Appendix B. Event mapping 333

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Job_Detail MS_SQL_Job_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v job_name: STRING
v job_id: STRING
v enabled: INTEGER
v enabled_enum: STRING
v current_status: INTEGER
v current_status_enum: STRING
v last_run_timestamp: STRING
v last_run_outcome: INTEGER
v last_run_outcome_enum: STRING
v next_run_timestamp: STRING
v sample_timestamp: STRING
v job_category_id: INTEGER
v job_category_id_enum: STRING
v job_category_name: STRING
v job_status: INTEGER
v job_status_enum: STRING
v job_duration: INTEGER
v job_duration_enum: STRING
v job_error_code: STRING
v job_error_code_enum: STRING
ITM_MS_SQL_Services_Detail MS_SQL_Services_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v service_name: STRING
v service_state: INTEGER
v service_state_enum: STRING
v service_status: INTEGER
v service_status_enum: STRING
v service_start_mode: INTEGER
v service_start_mode_enum: STRING
v service_type: INTEGER
v service_type_enum: STRING
v sample_timestamp: STRING

334 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Filegroup_Detail MS_SQL_Filegroup_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_name: STRING
v filegroup_id: INTEGER
v filegroup_name: STRING
v filegroup_size: REAL
v filegroup_space_
percent_used: REAL
v filegroup_max_growth_size: REAL
v sample_timestamp: STRING
ITM_MS_SQL_Lock_ Resource_Type_Summary MS_SQL_Lock_Resource_Type_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v lock_resource_type: INTEGER
v lock_resource_type_enum: STRING
v lock_requests_per_second: REAL
v lock_timeouts_per_second: REAL
v lock_wait_time: INTEGER
v number_deadlocks_per_second: REAL
v sample_timestamp: STRING
v average_wait_time_locks: INTEGER

Appendix B. Event mapping 335

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Workload_Group_Stats MS_SQL_Workload_Group_Stats attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v workload_group_name: STRING
v workload_group_name_enum: STRING
v cpu_usage_percent: REAL
v cpu_usage_percent_enum: STRING
v queued_requests: REAL
v queued_requests_enum: STRING
v requests_completed_per_sec: REAL
v requests_completed_per_sec_enum: STRING
v active_requests: REAL
v active_requests_enum: STRING
v max_requests_cpu_time: REAL
v max_requests_cpu_time_enum: STRING
v blocked_tasks: REAL
v blocked_tasks_enum: STRING
v reduced_memory_grants_per_sec: REAL
v reduced_memory_grants_
per_sec_enum: STRING
v max_requests_memory_grant: REAL
v max_requests_memory_
grant_enum: STRING
v query_optimization_per_sec: REAL
v query_optimization_per_sec_enum: STRING
v suboptimal_plans_per_sec: REAL
v suboptimal_plans_per_sec_enum: STRING
v active_parallel_threads: REAL
v active_parallel_threads_enum: STRING
v sample_timestamp: STRING

336 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Resource_Pool_Stats MS_SQL_Resource_Pool_Stats attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v resource_pool_name: STRING
v resource_pool_name_enum: STRING
v cpu_usage_percent: REAL
v cpu_usage_percent_enum: STRING
v cpu_usage_target_percent: REAL
v cpu_usage_target_percent_enum: STRING
v cpu_control_effect_percent: REAL
v cpu_control_effect_percent_enum: STRING
v cache_memory_target: REAL
v cache_memory_
target_enum: STRING
v compile_memory_target: REAL
v compile_memory_target_enum: STRING
v query_exec_memory_target: REAL
v query_exec_memory_
target_enum: STRING
v memory_grants_per_sec: REAL
v memory_grants_per_sec_enum: STRING
v memory_grant_timeouts_per_sec: REAL
v memory_grant_timeouts_
per_sec_enum: STRING
v active_memory_grants_count: REAL
v active_memory_grants_count_enum: STRING
v active_memory_grant_amount: REAL
v active_memory_grant_amount_enum: STRING
v pending_memory_grants_count: REAL
v pending_memory_grants_
count_enum: STRING
v max_memory: REAL
v max_memory_enum: STRING
v used_memory: REAL
v used_memory_enum: STRING
v target_memory: REAL
v target_memory_enum: STRING
v sample_timestamp: STRING

Appendix B. Event mapping 337

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Database_Mirroring MS_SQL_Database_Mirroring attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v mirror_name: STRING
v mirror_name_enum: STRING
v synchronization_state: INTEGER
v synchronization_state_enum: STRING
v mirroring_state: INTEGER
v mirroring_state_enum: STRING
v mirroring_role: INTEGER
v mirroring_role_enum: STRING
v bytes_sent_per_sec: REAL
v bytes_sent_per_sec_enum: STRING
v pages_sent_per_sec: REAL
v pages_sent_per_sec_enum: STRING
v sends_per_sec: REAL
v sends_per_sec_enum: STRING
v transaction_delay: REAL
v transaction_delay_enum: STRING
v redo_queue: REAL
v redo_queue_enum: STRING
v redo_bytes_per_sec: REAL
v redo_bytes_per_sec_enum: STRING
v log_send_queue: REAL
v log_send_queue_enum: STRING
v bytes_received_per_sec: REAL
v bytes_received_per_sec_enum: STRING
v receives_per_sec: REAL
v receives_per_sec_enum: STRING
v log_bytes_received_per_sec: REAL
v log_bytes_received_per_sec_enum: STRING
v log_bytes_sent_per_sec: REAL
v log_bytes_sent_per_sec_
enum: STRING
v send_receive_ack_time: REAL
v send_receive_ack_time_enum: STRING
v log_compressed_bytes_rcvd_
per_sec: REAL
v log_compressed_bytes_rcvd_
per_sec_enum: STRING
(Continued on the next page)

338 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Database_Mirroring (Continued) v log_compressed_bytes_sent_
per_sec: REAL
v log_compressed_bytes_sent_
per_sec_enum: STRING
v mirrored_write_transactions_
per_sec: REAL
v mirrored_write_transactions_
per_sec_enum: STRING
v log_scanned_for_undo: REAL
v log_scanned_for_undo_enum: STRING
v log_remaining_for_undo: REAL
v log_remaining_for_undo_enum: STRING
v log_bytes_sent_from_cache_
per_sec: REAL
v log_bytes_sent_from_cache_
per_sec_enum: STRING
v log_bytes_redone_from_cache_
per_sec: REAL
v log_bytes_redone_from_cache_
per_sec_enum: STRING
v log_send_flow_control_time: REAL
v log_send_flow_control_time_enum: STRING
v log_harden_time: REAL
v log_harden_time_enum: STRING
v sample_timestamp: STRING

Appendix B. Event mapping 339

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Memory_Manager MS_SQL_Memory_Manager attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v connection_memory: REAL
v connection_memory_enum: STRING
v granted_workspace_memory: REAL
v granted_workspace_memory_enum: STRING
v lock_memory: REAL
v lock_memory_enum: STRING
v lock_blocks_allocated: REAL
v lock_blocks_allocated_enum: STRING
v lock_owner_blocks_allocated: REAL
v lock_owner_blocks_
allocated_enum: STRING
v lock_blocks: REAL
v lock_blocks_enum: STRING
v lock_owner_blocks: REAL
v lock_owner_blocks_enum: STRING
v maximum_workspace_memory: REAL
v maximum_workspace_
memory_enum: STRING
v memory_grants_outstanding: REAL
v memory_grants_outstanding_enum: STRING
v memory_grants_pending: REAL
v memory_grants_pending_enum: STRING
v optimizer_memory: REAL
v optimizer_memory_enum: STRING
v sql_cache_memory: REAL
v sql_cache_memory_enum: STRING
v target_server_memory: REAL
v target_server_memory_enum: STRING
v total_server_memory: REAL
v total_server_memory_enum: STRING
v sample_timestamp: STRING

340 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Log_Shipping_DB_Details MS_SQL_Log_Shipping_DB_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server_type: INTEGER
v server_type_enum: STRING
v server: STRING
v database_name: STRING
v database_id: INTEGER
v threshold: INTEGER
v threshold_exceeded: INTEGER
v threshold_exceeded_enum: STRING
v last_file_processed: STRING
v last_file_processed_time: STRING
v message: STRING
v koq_source: STRING
v sample_timestamp: STRING
ITM_MS_SQL_Log_Shipping_Errors MS_SQL_Log_Shipping_Errors attribute group
v originnode: STRING
v hub_timestamp: STRING
v agent_type: INTEGER
v agent_type_enum: STRING
v server: STRING
v database_name: STRING
v database_id: INTEGER
v sequence_number: INTEGER
v log_time: STRING
v message: STRING
v error_source: STRING
v sample_timestamp: STRING
ITM_MS_SQL_Log_Shipping_Jobs_Detail MS_SQL_Log_Shipping_Jobs_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v agent_type: INTEGER
v agent_type_enum: STRING
v server: STRING
v database_id: INTEGER
v database_name: STRING
v session_id: INTEGER
v job_status: INTEGER
v job_status_enum: STRING
v message: STRING
v log_time: STRING
v job_name: STRING
v sample_timestamp: STRING

Appendix B. Event mapping 341

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Enterprise_ MS_SQL_Enterprise_Database_Mirroring attribute group
Database_Mirroring v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v mirror_name: STRING
v mirror_name_enum: STRING
v synchronization_state: INTEGER
v synchronization_state_enum: STRING
v mirroring_state: INTEGER
v mirroring_state_enum: STRING
v mirroring_role: INTEGER
v mirroring_role_enum: STRING
v bytes_sent_per_sec: REAL
v bytes_sent_per_sec_enum: STRING
v pages_sent_per_sec: REAL
v pages_sent_per_sec_enum: STRING
v sends_per_sec: REAL
v sends_per_sec_enum: STRING
v transaction_delay: REAL
v transaction_delay_enum: STRING
v redo_queue: REAL
v redo_queue_enum: STRING
v redo_bytes_per_sec: REAL
v redo_bytes_per_sec_enum: STRING
v log_send_queue: REAL
v log_send_queue_enum: STRING
v bytes_received_per_sec: REAL
v bytes_received_per_sec_enum: STRING
v receives_per_sec: REAL
v receives_per_sec_enum: STRING
v log_bytes_received_per_sec: REAL
v log_bytes_received_per_sec_enum: STRING
v log_bytes_sent_per_sec: REAL
v log_bytes_sent_per_sec_enum: STRING
v send_receive_ack_time: REAL

342 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Enterprise_ v send_receive_ack_time_enum: STRING
Database_Mirroring (Continued)
v log_compressed_bytes_rcvd_
per_sec: REAL
v log_compressed_bytes_rcvd_
per_sec_enum: STRING
v log_compressed_bytes_sent_per_sec: REAL
v log_compressed_bytes_sent_per_sec_enum: STRING
v mirrored_write_transactions_per_sec: REAL
v mirrored_write_transactions_per_sec_enum: STRING
v log_scanned_for_undo: REAL
v log_scanned_for_undo_enum: STRING
v log_remaining_for_undo: REAL
v log_remaining_for_undo_enum: STRING
v log_bytes_sent_from_
cache_per_sec: REAL
v log_bytes_sent_from_
cache_per_sec_enum: STRING
v log_bytes_redone_from_
cache_per_sec: REAL
v log_bytes_redone_from_
cache_per_sec_enum: STRING
v log_send_flow_control_time: REAL
v log_send_flow_control_time_enum: STRING
v log_harden_time: REAL
v log_harden_time_enum: STRING
v sample_timestamp: STRING
ITM_MS_SQL_Enterprise_ MS_SQL_Enterprise_Log_Shipping_
Log_Shipping_DB_Details DB_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server_type: INTEGER
v server_type_enum: STRING
v server: STRING
v database_name: STRING
v database_id: INTEGER
v threshold: INTEGER
v threshold_exceeded: INTEGER
v threshold_exceeded_enum: STRING
v last_file_processed: STRING
v last_file_processed_time: STRING
v message: STRING
v koq_source: STRING
v sample_timestamp: STRING

Appendix B. Event mapping 343

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Batch_Stats MS_SQL_Batch_Stats attribute group
v originnode: STRING
v hub_timestamp: STRING
v auto_param_attempts: REAL
v auto_param_attempts_enum: STRING
v batch_reuests: REAL
v batch_reuests_enum: STRING
v failed_auto_params: REAL
v failed_auto_params_enum: STRING
v safe_auto-params: REAL
v safe_auto-params_enum: STRING
v server_attention_rate: REAL
v server_attention_rate_enum: STRING
v server_compilations: REAL
v server_compilations_enum: STRING
v unsafe_auto_params: REAL
v unsafe_auto_params_enum: STRING
v server_re_compilations: REAL
v server_re_compilations_enum: STRING
v forced_params: REAL
v forced_params_enum: STRING
v server: STRING
v host_name: STRING

344 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_Properties MS_SQL_Server_Properties attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_version:STRING
v server_version_enum: STRING
v collation: STRING
v collation_enum: STRING
v collation_id: INTEGER
v collation_id_enum: STRING
v edition: STRING
v edition_enum: STRING
v edition_id: REAL
v edition_id_enum: STRING
v engine_edition: INTEGER
v engine_edition_enum: STRING
v is_clustered: INTEGER
v is_clustered_enum: STRING
v isintegrated_security_only: INTEGER
v isintegrated_security_only_enum: STRING
v is_single_user: INTEGER
v is_single_user_enum: STRING
v license_type: STRING
v license_type_enum: STRING
v num_licenses: INTEGER
v num_licenses_enum: STRING
v product_level: INTEGER
v product_level_enum: STRING
v physical_netbios_name: STRING
v physical_netbios_name_enum: STRING
v qualified_server_name: STRING
v qualified_server_name_enum: STRING
v filestream_share_name: STRING
v filestream_share_name_enum: STRING
v filestream_level: INTEGER
v filestream_level_enum: STRING
v is_hadr_enabled: INTEGER
v is_hadr_enabled_enum: STRING
v hadr_manager_status:INTEGER
v hadr_manager_status_enum: STRING;

Appendix B. Event mapping 345

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Server_ MS_SQL_Server_Transactions_Summary attribute group
Transactions_Summary v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v tempdb_free_space: INTEGER
v tempdb_free_space_enum: STRING
v longest_transaction_running_time: INTEGER
v longest_transaction_running_
time_enum: STRING
v total_non-snapshot_version_
transactions: INTEGER
v total_non-snapshot_version_
transactions_enum: STRING
v total_snapshot_transactions: INTEGER
v total_snapshot_transactions_enum: STRING
v total_active_transactions: INTEGER
v total_active_transactions_enum: STRING
v update_conflict_ratio: REAL
v update_conflict_ratio_enum: STRING
v total_update_snapshot_transactions: INTEGER
v total_update_snapshot_transactions_enum: STRING
v version_cleanup_rate: REAL
v version_cleanup_rate_enum: STRING
v version_generation_rate: REAL
v version_generation_rate_enum: STRING
v version_store_size: INTEGER
v version_store_size_enum: STRING
v version_store_unit_count: INTEGER
v version_store_unit_count_enum: STRING
v version_store_unit_creation: INTEGER
v version_store_unit_creation_enum: STRING
v version_store_unit_truncation: INTEGER
v version_store_unit_truncation_enum: STRING;

346 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Service_Broker_Activation MS_SQL_Service_Broker_Activation attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v stored_procedure_invoked_per_sec: REAL
v stored_procedure_invoked_per_sec_enum: STRING
v task_limit_reached_per_sec: REAL
v task_limit_reached_per_sec_enum: STRING
v total_task_limit_reached: INTEGER
v total_task_limit_reached_enum: STRING
v tasks_aborted_per_sec: REAL
v tasks_aborted_per_sec_enum: STRING
v tasks_started_per_sec: REAL
v tasks_started_per_sec_enum: STRING
v total_tasks_started: INTEGER
v total_tasks_started_enum: STRING;
ITM_MS_SQL_Service_Broker_Statistics MS_SQL_Service_Broker_Statistics attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v broker_transaction_rollbacks: REAL
v broker_transaction_rollbacks_enum: STRING
v enqueued_local_messages_per_sec: REAL
v enqueued_local_messages_per_sec_enum: STRING
v total_enqueued_local_messages: REAL
v total_enqueued_local_messages_enum: STRING
v total_enqueued_messages: REAL
v total_enqueued_messages_enum: STRING
v total_enqueued_transport_messages: REAL
v total_enqueued_transport_messages_enum: STRING
v total_forwarded_messages: REAL
v total_forwarded_messages_enum: STRING
v forwarded_pending_messages: REAL
v forwarded_pending_messages_enum: STRING

Appendix B. Event mapping 347

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Service_Broker_Statistics (Continued)
(Continued) v total_forwarded_messages_discarded: REAL
v total_forwarded_messages_
discarded_enum: STRING
v forwarded_messages_discarded_per_sec: REAL
v forwarded_messages_discarded_per_
sec_enum: STRING
v enqueued_messages_per_sec: REAL
v enqueued_messages_per_sec_enum: STRING
v enqueued_transport_messages_per_sec: REAL
v enqueued_transport_messages_per_
sec_enum: STRING
v sql_receives_per_sec: REAL
v sql_receives_per_sec_enum: STRING
v sql_sends_per_sec: REAL
v sql_sends_per_sec_enum: STRING
v total_sql_receives: REAL
v total_sql_receives_enum: STRING
v total_sql_sends: REAL
v total_sql_sends_enum: STRING;

348 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Service_Broker_Transport MS_SQL_Service_Broker_Transport attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v current_bytes_received_io: REAL
v current_bytes_received_io_enum: STRING
v current_bytes_send_io: REAL
v current_bytes_send_io_enum: STRING
v current_message_fragments_send_io: REAL
v current_message_fragments_
send_io_enum: STRING
v message_fragment_received_per_sec: REAL
v message_fragment_received_
per_sec_enum: STRING
v message_fragments_send_per_sec: REAL
v message_fragments_send_per_sec_enum: STRING
v avg_size_message_fragments_received: REAL
v avg_size_message_fragments_
received_enum: STRING
v avg_size_message_fragments_send: REAL
v avg_size_message_fragments_send_enum: STRING
v total_open_connection_count: REAL
v total_open_connection_count_enum: STRING
v pending_bytes_received_io: REAL
v pending_bytes_received_io_enum: STRING
v pending_bytes_send_io: REAL
v pending_bytes_send_io_enum: STRING
v pending_message_fragments_received_io: REAL
v pending_message_fragments_received_
io_enum: STRING
v pending_message_fragments_send_io: REAL
v pending_message_fragments_send_io_enum: STRING
v receive_ios_per_sec: REAL
v receive_ios_per_sec_enum: STRING
v send_ios_per_sec: REAL
v send_ios_per_sec_enum: STRING;

Appendix B. Event mapping 349

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Table_Summary MS_SQL_Table_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v total_tables: INTEGER
v total_tables_enum: STRING
v maximum_optimizer_statistics_age: INTEGER
v maximum_optimizer_statistics_
age_enum: STRING
v minimum_optimizer_statistics_age: INTEGER
v minimum_optimizer_statistics_
age_enum: STRING
v maximum_fragmentation_percent: REAL
v maximum_fragmentation_percent_enum: STRING
v minimum_fragmentation_percent: REAL
v minimum_fragmentation_percent_enum: STRING
v maximum_fragmentation_percent_
since_startup: REAL
v maximum_fragmentation_percent_since_
startup_enum: STRING
v maximum_table_size_mb: REAL
v maximum_table_size_mb_enum: STRING
v minimum_table_size_mb: REAL
v minimum_table_size_mb_enum: STRING
v last_collection_duration: REAL
v last_collection_duration_enum: STRING
v last_collection_start_time: STRING
v last_collection_start_time_enum: STRING
v total_filetables: INTEGER
v total_filetables_enum: STRING

350 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Integration_Service_Details MS_SQL_Integration_Service_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_enum: STRING
v buffer_memory: REAL
v buffer_memory_enum: STRING
v buffer_in_use: INTEGER
v buffer_in_use_enum: STRING
v buffer_spooled: INTEGER
v buffer_spooled_enum: STRING
v flat_buffer_memory: REAL
v flat_buffer_memory_enum: STRING
v flat_buffers_in_use: INTEGER
v flat_buffers_in_use_enum: STRING
v private_buffer_memory: REAL
v private_buffer_memory_enum: STRING
v private_buffers_in_use: INTEGER
v private_buffers_in_use_enum: STRING
v total_rows_read: REAL
v total_rows_read_enum: STRING
v total_rows_written: REAL
v total_rows_written_enum: STRING

Appendix B. Event mapping 351

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ MS_SQL_Analysis_Services_Data_Mining attribute group
Data_Mining v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_enum: STRING
v cases_per_sec: REAL
v cases_per_sec_enum: STRING
v current_models_processing: REAL
v current_models_processing_enum: STRING
v concurrent_data_mining_queries: REAL
v concurrent_data_mining_
queries_enum: STRING
v predictions_per_sec: REAL
v predictions_per_sec_enum: STRING
v queries_per_sec: REAL
v queries_per_sec_enum: STRING
v rows_per_sec: REAL
v rows_per_sec_enum: STRING
v total_predictions: REAL
v total_predictions_enum: STRING
v total_queries: REAL
v total_queries_enum: STRING
v total_rows: REAL
v total_rows_enum: STRING

352 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ MS_SQL_Analysis_Services_Memory_
Memory_Statistics Statistics attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_enum: STRING
v average_cache: REAL
v average_cache_enum: STRING
v aggregation_map_files: REAL
v aggregation_map_files_enum: STRING
v cleaner_balance_per_sec: REAL
v cleaner_balance_per_sec_enum: STRING
v cleaner_current_price: REAL
v cleaner_current_price_enum: STRING
v cleaner_memory: REAL
v cleaner_memory_enum: STRING
v cleaner_memory_nonshrinkable: REAL
v cleaner_memory_nonshrinkable_
enum: STRING
v cleaner_memory_shrinkable: REAL
v cleaner_memory_shrinkable_enum: STRING
v cleaner_memory_shrunk_kb_sec: REAL
v cleaner_memory_shrunk_kb_
sec_enum: STRING
v dimension_index_files: REAL

Appendix B. Event mapping 353

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
(Continued)
v dimension_index_files_enum: STRING
v dimension_property_files: REAL
v dimension_property_files_enum: STRING
v dimension_string_files: REAL
v dimension_string_files_enum: STRING
v fact_aggregation_files: REAL
v fact_aggregation_files_enum: STRING
v fact_data_files: REAL
v fact_data_files_enum: STRING
v fact_string_files: REAL
v fact_string_files_enum: STRING
v filestore_clock_pages_examined_
per_sec: REAL
v filestore_clock_pages_examined_
per_sec_enum: STRING
v filestore_clock_pages_haveref_
per_sec: REAL
v filestore_clock_pages_haveref_
per_sec_enum: STRING
v filestore_clock_pages_valid_per_sec: REAL
v filestore_clock_pages_valid_per_sec_enum: STRING
v total_filestore_io_errors: REAL
v total_filestore_io_errors_enum: STRING
v total_filestore_io_errors_per_sec: REAL

354 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
Memory_Statistics (Continued) v total_filestore_io_errors_per_sec_enum: STRING
v filestore: REAL
v filestore_enum: STRING
v filestore_kb_reads_per_sec: REAL
v filestore_kb_reads_per_sec_enum: STRING
v filestore_kb_writes_per_sec: REAL
v filestore_kb_writes_per_sec_enum: STRING
v filestore_memory_pinned: REAL
v filestore_memory_pinned_enum: STRING
v filestore_page_faults_per_sec: REAL
v filestore_page_faults_per_sec_enum: STRING
v filestore_reads_per_sec: REAL
v filestore_reads_per_sec_enum: STRING
v filestore_writes_per_sec: REAL
v filestore_writes_per_sec_enum: STRING
v in_memory_aggregation_map_file: REAL
v in_memory_aggregation_map_
file_enum: STRING
v in_memory_aggregation_map_
file_kb_per_sec: REAL
v in_memory_aggregation_map_
file_kb_per_sec_enum: STRING
v in_memory_dimension_index_file: REAL

Appendix B. Event mapping 355

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
(Continued)
v in_memory_dimension_index_file_enum: STRING
v in_memory_dimension_index_file_
kb_per_sec: REAL
v in_memory_dimension_index_file_
kb_per_sec_enum: STRING
v in_memory_property_file: REAL
v in_memory_property_file_enum: STRING
v in_memory_property_file_kb_
per_sec: REAL
v in_memory_property_file_kb_
per_sec_enum: STRING
v in_memory_string_file: REAL
v in_memory_string_file_enum: STRING
v in_memory_string_file_kb_per_sec: REAL
v in_memory_string_file_kb_per_sec_enum: STRING
v in_memory_fact_aggregation_file: REAL
v in_memory_fact_aggregation_file_enum: STRING
v in_memory_fact_aggregation_file_kb_
per_sec: REAL
v in_memory_fact_aggregation_file_kb_
per_sec_enum: STRING
v in_memory_fact_data_file: REAL
v in_memory_fact_data_file_enum: STRING
v in_memory_fact_data_file_kb_per_sec: REAL
v in_memory_fact_data_file_kb_
per_sec_enum: STRING
v in_memory_fact_string_file: REAL

356 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
(Continued)
v in_memory_fact_string_file_enum: STRING
v in_memory_fact_string_file_
per_sec: REAL
v in_memory_fact_string_file_
per_sec_enum: STRING
v in_memory_map_file: REAL
v in_memory_map_file_enum: STRING
v in_memory_map_file_per_sec: REAL
v in_memory_map_file_per_
sec_enum: STRING
v in_memory_other_file: REAL
v in_memory_other_file_enum: STRING
v in_memory_other_file_per_sec: REAL
v in_memory_other_file_
per_sec_enum: STRING
v map_files: REAL
v map_files_enum: STRING
v memory_limit_low: REAL
v memory_limit_low_enum: STRING
v memory_limit_high: REAL
v memory_limit_high_enum: STRING
v memory_usage: REAL
v memory_usage_enum: STRING
v other_files: REAL

Appendix B. Event mapping 357

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
Memory_Statistics (Continued) v other_files_enum: STRING
v page_pool_1_alloc: REAL
v page_pool_1_alloc_enum: STRING
v page_pool_1_lookaside: REAL
v page_pool_1_lookaside_enum: STRING
v page_pool_64_alloc: REAL
v page_pool_64_alloc_enum: STRING
v page_pool_64_lookaside: REAL
v page_pool_64_lookaside_enum: STRING
v page_pool_8_alloc: REAL
v page_pool_8_alloc_enum: STRING
v page_pool_8_lookaside: REAL
v page_pool_8_lookaside_enum: STRING
v potential_in-memory_aggregation_
map_file: REAL
v potential_in-memory_aggregation_
map_file_enum: STRING
v potential_in-memory_dimension_
index_file: REAL
v potential_in-memory_dimension_
index_file_enum: STRING
v potential_in-memory_dimension_
property_file: REAL
v potential_in-memory_dimension_
property_file_enum: STRING
v potential_in-memory_dimension_
string_file: REAL

358 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
(Continued)
v potential_in-memory_dimension_
string_file_enum: STRING
v potential_in-memory_fact_
aggregation_file: REAL
v potential_in-memory_fact_
aggregation_file_enum: STRING
v potential_in-memory_fact_data_file: REAL
v potential_in-memory_fact_
data_file_enum: STRING
v potential_in-memory_fact_string_file: REAL
v potential_in-memory_fact_
string_file_enum: STRING
v potential_in-memory_map_file: REAL
v potential_in-memory_map_
file_enum: STRING
v potential_in-memory_other_file: REAL
v potential_in-memory_other_
file_enum: STRING
v quota_blocked: REAL
v quota_blocked_enum: STRING
v quota: REAL
v quota_enum: STRING

Appendix B. Event mapping 359

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ MS_SQL_Analysis_Services_Storage_
Storage_Engine_Query Engine_Query attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_enum: STRING
v aggregation_hits_per_sec: REAL
v aggregation_hits_per_
sec_enum: STRING
v aggregation_lookups_per_sec: REAL
v aggregation_lookups_per_sec_enum: STRING
v average_time_per_query: REAL
v average_time_per_query_enum: STRING
v bytes_sent_per_sec: REAL
v bytes_sent_per_sec_enum: STRING
v calculation_cache_hits_per_sec: REAL
v calculation_cache_hits_per_sec_enum: STRING
v calculation_cache_lookups_per_sec: REAL
v calculation_cache_lookups_per_
sec_enum: STRING
v current_dimension_queries: REAL
v current_dimension_queries_enum: STRING
v current_measure_group_queries: REAL
v current_measure_group_
queries_enum: STRING
v current_pyramid_operations: REAL
v current_pyramid_operations_enum: STRING
v data_bytes_per_sec: REAL
v data_bytes_per_sec_enum: STRING

360 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
Storage_Engine_Query (Continued) v data_reads_per_sec: REAL
v data_reads_per_sec_enum: STRING
v dimension_cache_hits_per_sec: REAL
v dimension_cache_hits_per_
sec_enum: STRING
v dimension_cache_lookups_per_sec: REAL
v dimension_cache_lookups_
per_sec_enum: STRING
v dimension_queries_per_sec: REAL
v dimension_queries_per_
sec_enum: STRING
v filter_rows_excluded_per_sec: REAL
v filter_rows_excluded_per_
sec_enum: STRING
v filter_rows_included_per_sec: REAL
v filter_rows_included_per_
sec_enum: STRING
v filtered_rows_per_sec: REAL
v filtered_rows_per_
sec_enum: STRING
v flat_cache_hits_per_sec: REAL
v flat_cache_hits_per_sec_enum: STRING
v flat_cache_lookups_per_sec: REAL
v flat_cache_lookups_per_sec_enum: STRING
v index_bytes_per_sec: REAL
v index_bytes_per_sec_enum: STRING
v index_reads_per_sec: REAL
v index_reads_per_sec_enum: STRING
v map_bytes_per_sec: REAL
v map_bytes_per_sec_enum: STRING

Appendix B. Event mapping 361

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
Storage_Engine_Query (Continued) v map_reads_per_sec: REAL
v map_reads_per_sec_enum: STRING
v measure_group_cache_hits_per_sec: REAL
v measure_group_cache_hits_
per_sec_enum: STRING
v measure_group_lookups_per_sec: REAL
v measure_group_lookups_
per_sec_enum: STRING
v measure_group_queries_per_sec: REAL
v measure_group_queries_
per_sec_enum: STRING
v network_round_trips_per_sec: REAL
v network_round_trips_
per_sec_enum: STRING
v persisted_cache_hits_per_sec: REAL
v persisted_cache_hits_
per_sec_enum: STRING
v persisted_cache_lookups_per_sec: REAL
v persisted_cache_lookups_
per_sec_enum: STRING
v pyramid_operations_per_sec: REAL
v pyramid_operations_per_sec_enum: STRING
v queries_answered_per_sec: REAL
v queries_answered_per_sec_enum: STRING
v queries_from_cache_direct_per_sec: REAL
v queries_from_cache_direct_
per_sec_enum: STRING
v queries_from_cache_filtered_per_sec: REAL
v queries_from_cache_filtered_
per_sec_enum: STRING
v queries_from_files_per_sec: REAL
v queries_from_files_per_sec_enum: STRING
v rows_read_per_sec: REAL
v rows_read_per_sec_enum: STRING
v rows_sent_per_sec: REAL
v rows_sent_per_sec_enum: STRING
v total_bytes_sent: REAL

362 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
Storage_Engine_Query (Continued) v total_bytes_sent_enum: STRING
v total_dimension_queries: REAL
v total_dimension_queries_enum: STRING
v total_measure_group_queries: REAL
v total_measure_group_queries_enum: STRING
v total_network_round_trips: REAL
v total_network_round_trips_
enum: STRING
v total_pyramid_operations: REAL
v total_pyramid_operations_
enum: STRING
v total_queries_answered: REAL
v total_queries_answered_enum: STRING
v total_queries_from_cache_direct: REAL
v total_queries_from_cache_
direct_enum: STRING
v total_queries_from_cache_filtered: REAL
v total_queries_from_cache_
filtered_enum: STRING
v total_queries_from_file: REAL
v total_queries_from_file_enum: STRING
v total_rows_sent: REAL
v total_rows_sent_enum: STRING
ITM_MS_SQL_Analysis_Services_ MS_SQL_Analysis_Services_Rows_Processing attribute
Rows_Processing group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v server_enum: STRING
v rows_read_per_sec: REAL
v rows_read_per_sec_enum: STRING
v rows_written_per_sec: REAL
v rows_written_per_sec_enum: STRING
v total_rows_converted: REAL
v total_rows_converted_enum: STRING
v total_rows_read: REAL
v total_rows_read_enum: STRING
v total_rows_written: REAL
v total_rows_written_enum: STRING
v rows_converted_per_sec: REAL
v rows_converted_per_sec_enum: STRING

Appendix B. Event mapping 363

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ MS_SQL_Analysis_Services_
MDX_Processing MDX_Processing attribute group
v hub_timestamp: STRING
v server: STRING
v server_enum: STRING
v current_cached_evaluation_nodes: REAL
v current_cached_evaluation_nodes_enum: STRING
v current_evaluation_nodes: REAL
v current_evaluation_nodes_enum: STRING
v total_bulk_mode_evaluation_nodes: REAL
v total_bulk_mode_evaluation_nodes_enum: STRING
v total_cached_bulk_mode_evaluation_nodes: REAL
v total_cached_bulk_mode_evaluation_
nodes_enum: STRING
v total_cached_other_evaluation_nodes: REAL
v total_cached_other_evaluation_
nodes_enum: STRING
v total_cached_storage_engine_
evaluation_nodes: REAL
v total_cached_storage_engine_evaluation_
nodes_enum: STRING
v total_calculations_covered: REAL
v total_calculations_covered_enum: STRING
v total_cell_by_cell_evaluation_nodes: REAL
v total_cell_by_cell_evaluation_
nodes_enum: STRING
v total_cell_by_cell_hits_in_cache_of_
evaluation_nodes: REAL
v total_cell_by_cell_hits_in_cache_of_
evaluation_nodes_enum: STRING
v total_cell_by_cell_misses_in_cache_of_
evaluation_nodes: REAL

364 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
MDX_Processing (Continued) v total_cell_by_cell_misses_in_cache_
of_evaluation_nodes_enum: STRING
v total_evaluation_nodes_covered_
single_cell: REAL
v total_evaluation_nodes_covered_
single_cell_enum: STRING
v total_evaluation_nodes_calculations_
at_same_granularity: REAL
v total_evaluation_nodes_calculations_
at_same_granularity_enum: STRING
v total_evictions_of_evaluation_nodes: REAL
v total_evictions_of_evaluation_nodes_enum: STRING
v total_hash_index_hits_in_
cache_of_evaluation_nodes: REAL
v total_hash_index_hits_in_
cache_of_evaluation_nodes_enum: STRING
v total_storage_engine_evaluation_nodes: REAL
v total_storage_engine_evaluation_
nodes_enum: STRING
v total_subcube_hits_in_cache_of_
evaluation_nodes: REAL
v total_subcube_hits_in_cache_of_evaluation_
nodes_enum: STRING
v total_subcube_misses_in_cache_of_
evaluation_nodes: REAL
v total_subcube_misses_in_cache_of_
evaluation_nodes_enum: STRING
v total_autoexist: REAL
v total_autoexist_enum: STRING
v total_calculation_cache_registered: REAL
v total_calculation_cache_
registered_enum: STRING

Appendix B. Event mapping 365

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Analysis_Services_ (Continued)
MDX_Processing (Continued) v total_cells_calculated: REAL
v total_cells_calculated_enum: STRING
v total_existing_operators: REAL
v total_existing_operators_
enum: STRING
v total_flat_cache_inserts: REAL
v total_flat_cache_inserts_enum: STRING
v total_nonempty_algorithms: REAL
v total_nonempty_algorithms_enum: STRING
v total_nonempty_algorithms_for_
calculated_members: REAL
v total_nonempty_algorithms_for_
calculated_members_enum: STRING
v total_nonempty_unoptimized_
algorithms: REAL
v total_nonempty_unoptimized_
algorithms_enum: STRING
v total_recomputes: REAL
v total_recomputes_enum: STRING
v total_sonar_subcubes: REAL
v total_sonar_subcubes_enum: STRING

366 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Running_Queries_Details MS_SQL_Running_Queries_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v cpu_time_sec: REAL
v cpu_time_sec_enum: STRING
v total_elaplsed_time_sec: REAL
v total_elaplsed_time_sec_enum: STRING
v query_reads: REAL
v query_reads_enum: STRING
v query_writes: REAL
v query_writes_enum: STRING
v query_start_time: STRING
v query_start_time_enum: STRING
v sql_handle: STRING
v sql_handle_enum: STRING
v command_type: STRING
v command_type_enum: STRING
v row_count: REAL
v row_count_enum: STRING
v query_status: INTEGER
v query_status_enum: STRING
v running_query_text: STRING
v running_query_text_enum: STRING
v session_id: INTEGER
v session_id_enum: STRING
v blocking_session_id: INTEGER
v blocking_session_id_enum: STRING
v client_host_name: STRING
v client_host_name_enum: STRING
v login_name: STRING
v login_name_enum: STRING
v program_name: STRING
v program_name_enum: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v percent_work_complete: REAL
v percent_work_complete_enum: STRING
v granted_query_memory: REAL
v granted_query_memory_enum: STRING

Appendix B. Event mapping 367

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Blocked_Queries_Details MS_SQL_Blocked_Queries_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v blocked_session_id: INTEGER
v blocked_session_id_enum: STRING
v total_wait_time_sec: REAL
v total_wait_time_sec_enum: STRING
v blocked_query_text: STRING
v blocked_query_text_enum: STRING
v blocking_query_text: STRING
v blocking_query_text_enum: STRING
v blocked_parent_query_text: STRING
v blocked_parent_query_text_enum: STRING
v blocking_reason: STRING
v blocking_reason_enum: STRING
v blocking_resource: STRING
v blocking_resource_enum: STRING
v blocking_session_id: INTEGER
v blocking_session_id_enum: STRING
v blocked_database_name_u: STRING
v blocked_database_name_u_enum: STRING
v blocking_user_name: STRING
v blocking_user_name_enum: STRING
v blocked_user_name_u: STRING
v blocked_user_name_u_enum: STRING

368 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Individual_Queries_Details MS_SQL_Individual_Queries_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v session_id: INTEGER
v session_id_enum: STRING
v query_hash: REAL
v query_hash_enum: STRING
v query_execution_count: REAL
v query_execution_count_enum: STRING
v query_text: STRING
v query_text_enum: STRING
v total_percent_cpu_used: REAL
v total_percent_cpu_used_enum: STRING
v total_percent_waiting: REAL
v total_percent_waiting_enum: STRING
v last_execution_time: STRING
v last_execution_time_enum: STRING
v total_cpu_time_sec: REAL
v total_cpu_time_sec_enum: STRING
v avg_cpu_time_sec: REAL
v avg_cpu_time_sec_enum: STRING
v avg_logical_reads: REAL
v avg_logical_reads_enum: STRING
v avg_logical_writes: REAL
v avg_logical_writes_enum: STRING
v avg_physical_reads: REAL
v avg_physical_reads_enum: STRING
v max_physical_reads: REAL
v max_physical_reads_enum: STRING
v max_logical_reads: REAL
v max_logical_reads_enum: STRING
v max_logical_writes: REAL
v max_logical_writes_enum: STRING
v max_cpu_time_sec: REAL
v max_cpu_time_sec_enum: STRING
v max_waiting_time_sec: REAL
v max_waiting_time_sec_enum: STRING
v max_clr_time_sec: REAL
v max_clr_time_sec_enum: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v sql_handle: STRING
v sql_handle_enum: STRING

Appendix B. Event mapping 369

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_FileTable_Detail MS_SQL_FileTable_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_id: INTEGER
v database_id_enum: STRING
v table_name: STRING
v table_name_enum: STRING
v table_id: INTEGER
v table_id_enum: STRING
v filetable_directory: STRING
v filetable_directory_enum: STRING
v filetable_enabled: INTEGER
v filetable_enabled_enum: STRING
v total_non_transactional_handles_
opened: INTEGER
v total_non_transactional_handles_
opened_enum: STRING
ITM_MS_SQL_Additional_Database_Detail MS_SQL_Additional_Database_Detail attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v database_id: INTEGER
v database_id_enum: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v filetable_directory_name: STRING
v filetable_directory_
name_enum: STRING
v non_transactional_
access_level: INTEGER
v non_transactional_
access_level_enum: STRING
v containment: INTEGER
v containment_enum: STRING

370 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_Replicas_Details MS_SQL_Availability_Replicas_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v replica_id: STRING
v replica_id_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name: STRING
v group_name_enum: STRING
v replica_server_name: STRING
v replica_server_name_enum: STRING
v owner_sid: STRING
v owner_sid_enum: STRING
v endpoint_url: STRING
v endpoint_url_enum: STRING
v create_date: STRING
v create_date_enum: STRING
v modify_date: STRING
v modify_date_enum: STRING
v availability_mode: INTEGER
v availability_mode_enum: STRING
v failover_mode: INTEGER
v failover_mode_enum: STRING
v session_timeout: INTEGER
v session_timeout_enum: STRING
v primary_connection_type: INTEGER
v primary_connection_
type_enum: STRING
v secondary_connection_type: INTEGER
v secondary_connection_
type_enum: STRING
v backup_priority: INTEGER
v backup_priority_enum: STRING
v role: INTEGER
v role_enum: STRING

Appendix B. Event mapping 371

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_Replicas_Status MS_SQL_Availability_Replicas_Status attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v replica_id: STRING
v replica_id_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name: STRING
v group_name_enum: STRING
v local: INTEGER
v local_enum: STRING
v role: INTEGER
v role_enum: STRING
v operational_state: INTEGER
v operational_state_enum: STRING
v connection_state: INTEGER
v connection_state_enum: STRING
v recovery_health: INTEGER
v recovery_health_
enum: STRING
v synchronization_health: INTEGER
v synchronization_
health_enum: STRING
v last_connect_error_number: INTEGER
v last_connect_error_
number_enum: STRING
v total_databases: INTEGER
v total_databases_enum: STRING

372 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_ MS_SQL_Availability_Replicas_
Replicas_Status_Summary Status_Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v total_primary_replicas: INTEGER
v total_primary_replicas_
enum: STRING
v total_secondary_replicas: INTEGER
v total_secondary_replicas_
enum: STRING
v min_secondary_replicas: INTEGER
v min_secondary_replicas_
enum: STRING
v max_secondary_replicas: INTEGER
v max_secondary_replicas_
enum: STRING
v total_local_replicas: INTEGER
v total_local_replicas_
enum: STRING
v total_connected_replicas: INTEGER
v total_connected_replicas_
enum: STRING
v total_disconnected_replicas: INTEGER
v total_disconnected_replicas_
enum: STRING
v min_disconnected_replicas: INTEGER
v min_disconnected_replicas_
enum: STRING
v max_disconnected_replicas: INTEGER
v max_disconnected_replicas_enum: STRING
v total_local_failed_replicas: INTEGER
v total_local_failed_replicas_enum: STRING
v min_local_failed_replicas: INTEGER
v min_local_failed_replicas_
enum: STRING
v max_local_failed_replicas: INTEGER
v max_local_failed_replicas_enum: STRING
v total_non_healthy_replicas: INTEGER
v total_non_healthy_replicas_enum: STRING
v min_non_healthy_replicas: INTEGER
v min_non_healthy_replicas_enum: STRING
v max_non_healthy_replicas: INTEGER
v max_non_healthy_replicas_enum: STRING

Appendix B. Event mapping 373

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_Groups_Details MS_SQL_Availability_Groups_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name_u: STRING
v group_name_u_enum: STRING
v primary_replica_id: STRING
v primary_replica_id_enum: STRING
v primary_replica_u: STRING
v primary_replica_u_enum: STRING
v groups_role: INTEGER
v groups_role_enum: STRING
v database_count: INTEGER
v database_count_enum: STRING
v failure_condition: INTEGER
v failure_condition_enum: STRING
v wait_timeout: INTEGER
v wait_timeout_enum: STRING
v backup_preference: INTEGER
v backup_preference_
enum: STRING
v local_replica_recovery_health: INTEGER
v local_replica_recovery_
health_enum: STRING
v synchronization_health: INTEGER
v synchronization_health_enum: STRING
v secondary_replica_count: INTEGER
v secondary_replica_count_
enum: STRING
v last_groups_role: INTEGER
v last_groups_role_enum: STRING

374 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_ MS_SQL_Availability_Database_
Availability_Database_Details Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v database_id: INTEGER
v database_id_enum: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name_u: STRING
v group_name_u_enum: STRING
v replica_id: STRING
v replica_id_enum: STRING
v group_database_id: STRING
v group_database_id_enum: STRING
v role: INTEGER
v role_enum: STRING
v local: INTEGER
v local_enum: STRING
v synchronization_state: INTEGER
v synchronization_state_enum: STRING
v synchronized_commit: INTEGER
v synchronized_commit_enum: STRING
v synchronization_health: INTEGER
v synchronization_health_enum: STRING
v database_state: INTEGER
v database_state_enum: STRING
v suspend_reason: INTEGER
v suspend_reason_enum: STRING

Appendix B. Event mapping 375

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Additional_Availability_ MS_SQL_Additional_Availability_
Database_Details Database_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_database_id: STRING
v group_database_id_enum: STRING
v log_send_queue_size: REAL
v log_send_queue_size_enum: STRING
v log_bytes_sent_rate: REAL
v log_bytes_sent_rate_enum: STRING
v redo_queue_size: REAL
v redo_queue_size_enum: STRING
v redo_rate: REAL
v redo_rate_enum: STRING
v filestream_send_rate: REAL
v filestream_send_rate_enum: STRING
v role: INTEGER
v role_enum: STRING

376 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_ MS_SQL_Availability_Database_
Database_Summary Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v total_databases: INTEGER
v total_databases_enum: STRING
v total_primary_databases: INTEGER
v total_primary_databases_enum: STRING
v total_secondary_databases: INTEGER
v total_secondary_databases_enum: STRING
v total_unsynchronized_databases: INTEGER
v total_unsynchronized_
databases_enum: STRING
v min_unsynchronized_databases: INTEGER
v min_unsynchronized_
databases_enum: STRING
v max_unsynchronized_
databases: INTEGER
v max_unsynchronized_databases_enum: STRING
v total_unsynchronized_commit_
db_replicas: INTEGER
v total_unsynchronized_commit_
db_replicas_enum: STRING
v min_unsynchronized_commit_
db_replicas: INTEGER
v min_unsynchronized_commit_
db_replicas_enum: STRING
v max_unsynchronized_commit_
db_replicas: INTEGER
v max_unsynchronized_commit_
db_replicas_enum: STRING
v total_non-online_databases: INTEGER
v total_non-online_
databases_enum: STRING
v min_non-online_databases: INTEGER
v min_non-online_databases_enum: STRING
v max_non-online_databases: INTEGER
v max_non-online_databases_enum: STRING
v total_non_healthy_databases: INTEGER
v total_non_healthy_databases_enum: STRING
v min_non_healthy_databases: INTEGER
v min_non_healthy_databases_enum: STRING
v max_non_healthy_databases: INTEGER
v max_non_healthy_databases_enum: STRING

Appendix B. Event mapping 377

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_ MS_SQL_Availability_Groups_
Groups_Summary Summary attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v host_name: STRING
v total_groups: INTEGER
v total_groups_enum: STRING
v total_primary_role_group: INTEGER
v total_primary_role_group_enum: STRING
v total_secondary_role_group: INTEGER
v total_secondary_role_group_enum: STRING
v total_non_healthy_groups: INTEGER
v total_non_healthy_groups_enum: STRING
v min_non_healthy_groups: INTEGER
v min_non_healthy_groups_enum: STRING
v max_non_healthy_groups: INTEGER
v max_non_healthy_groups_enum: STRING
v total_non_online_local_
replica_groups: INTEGER
v total_non_online_local_
replica_groups_enum: STRING
v min_non_online_local_
replica_groups: INTEGER
v min_non_online_local_
replica_groups_enum: STRING
v max_non_online_local_
replica_groups: INTEGER
v max_non_online_local_
replica_groups_enum: STRING

378 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_ MS_SQL_Availability_Replicas_
Replicas_Statistics Statistics attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v instance_name: STRING
v instance_name_enum: STRING
v bytes_received_per_sec: REAL
v bytes_received_per_sec_enum: STRING
v bytes_sent_per_sec: REAL
v bytes_sent_per_sec_enum: STRING
v bytes_sent_to_transport_per_sec: REAL
v bytes_sent_to_transport_per_sec_enum: STRING
v flow_control_time: REAL
v flow_control_time_enum: STRING
v flow_control_per_sec: REAL
v flow_control_per_sec_enum: STRING
v received_messages_per_sec: REAL
v received_messages_per_sec_enum: STRING
v resent_messages_per_sec: REAL
v resent_messages_per_sec_enum: STRING
v sent_messages_per_sec: REAL
v sent_messages_per_sec_enum: STRING
v messages_sent_to_transport_
per_sec: REAL
v messages_sent_to_transport_
per_sec_enum: STRING

Appendix B. Event mapping 379

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_ MS_SQL_Availability_Database_
Database_Statistics Statistics attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v file_bytes_received_per_sec: REAL
v file_bytes_received_per_
sec_enum: STRING
v log_bytes_received_per_sec: REAL
v log_bytes_received_per_
sec_enum: STRING
v undo_log_remaining: REAL
v undo_log_remaining_enum: STRING
v log_send_queue: REAL
v log_send_queue_enum: STRING
v mirrored_write_transaction_per_sec: REAL
v mirrored_write_transaction_per_
sec_enum: STRING
v recovery_queue: REAL
v recovery_queue_enum: STRING
v redo_blocked_per_sec: REAL
v redo_blocked_per_sec_enum: STRING
v redo_bytes_remaining: REAL
v redo_bytes_remaining_enum: STRING
v redone_bytes_per_sec: REAL
v redone_bytes_per_sec_enum: STRING
v total_log_requiring_undo: REAL
v total_log_requiring_undo_enum: STRING

380 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_Groups_ MS_SQL_Availability_Groups_Details_
Details_In_Cluster In_Cluster attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name_u: STRING
v group_name_u_enum: STRING
v cluster_resource_id: STRING
v cluster_resource_id_enum: STRING
v resource_group_id: STRING
v resource_group_id_enum: STRING
v failure_condition: INTEGER
v failure_condition_enum: STRING
v wait_timeout: INTEGER
v wait_timeout_enum: STRING
v backup_preference: INTEGER
v backup_preference_enum: STRING
ITM_MS_SQL_Availability_Replicas_ MS_SQL_Availability_Replicas_Details_
Details_In_Cluster In_Cluster attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v replica_id: STRING
v replica_id_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name_u: STRING
v group_name_u_enum: STRING
v cluster_node: STRING
v cluster_node_enum: STRING
v replica_server_name: STRING
v replica_server_name_enum: STRING
v join_state: INTEGER
v join_state_enum: STRING

Appendix B. Event mapping 381

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_Database_ MS_SQL_Availability_Database_Details_
Details_In_Cluster In_Cluster attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v database_name_u: STRING
v database_name_u_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name_u: STRING
v group_name_u_enum: STRING
v replica_id: STRING
v replica_id_enum: STRING
v group_database_id: STRING
v group_database_id_enum: STRING
v failover_ready: INTEGER
v failover_ready_enum: STRING
v secondary_suspension_
pending: INTEGER
v secondary_suspension_
pending_enum: STRING
v join_state: INTEGER
v join_state_enum: STRING

382 Microsoft SQL Server agent: User’s Guide

Table 40. Overview of attribute groups to event classes and slots (continued)
IBM Tivoli Enterprise Console event class Event slots
ITM_MS_SQL_Availability_ MS_SQL_Availability_Group_
Group_Listener_Details Listener_Details attribute group
v originnode: STRING
v hub_timestamp: STRING
v server: STRING
v listener_id: STRING
v listener_id_enum: STRING
v listener_name_u: STRING
v listener_name_u_enum: STRING
v group_id: STRING
v group_id_enum: STRING
v group_name_u: STRING
v group_name_u_enum: STRING
v listener_ip_address: STRING
v listener_ip_address_enum: STRING
v listener_subnet_ip: STRING
v listener_subnet_ip_enum: STRING
v port: INTEGER
v port_enum: STRING
v is_dhcp: INTEGER
v is_dhcp_enum: STRING
v state: INTEGER
v state_enum: STRING
v is_conformant: INTEGER
v is_conformant_enum: STRING

Appendix B. Event mapping 383

384 Microsoft SQL Server agent: User’s Guide
Appendix C. Discovery Library Adapter for the Microsoft SQL
Server agent
The Tivoli Management Services Discovery Library Adapter (DLA) discovers resources and relationships,
and creates a Discovery Library Book file for the agent.

About the DLA

The Book file follows the Discovery Library IdML schema and is used to populate the Configuration
Management Database (CMDB) and Tivoli Business Service Manager products. The Tivoli Management
Services DLA discovers Microsoft SQL Server resources. For all VMware systems that are active and
online at the Tivoli Enterprise Portal Server, information is included in the discovery book for those
resources. The Tivoli Management Services DLA discovers active resources. It is run on demand and can
be run periodically to discover resources that were not active during previous discoveries.

The DLA discovers Microsoft SQL Server components.

More information about DLAs

The following sources contain additional information about using the DLA program with all monitoring
agents:
v The IBM Tivoli Monitoring Administrator's Guide contains information about using the Tivoli
Management Services Discovery Library Adapter.
v For information about using a DLA with Tivoli Application Dependency Discovery Manager (TADDM),
see the TADDM Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/topic/
com.ibm.taddm.doc_7.2/welcome_page/welcome.html).

DLA data model class types represented in CDM

The source application data objects map to classes in the Common Data Model (CDM) for the Microsoft
SQL Server agent.

The following information is provided for each class:

CDM class name
Class name for which the agent is providing information
Relationships
CDM relationships (hierarchical) between currently identified model objects
CDM attributes, agent attributes, descriptions, and examples
CDM and agent attributes that are required to create an instance of a resource, descriptions of the
attributes, and examples of the attributes

DLA data model classes for Microsoft SQL Server agent

Each agent that uses the Discovery Library Adapter has DLA data model classes defined for the agent.

The Microsoft SQL Server agent has the following Discovery Library Adapter data model classes:
v SqlServer
v SqlServerDatabase
v SqlServerTable

© Copyright IBM Corp. 2005, 2012 385

v SqlServerProcess
v TMSAgent

SqlServer class
The ActiveDirectory class represents an instance of the domain controller.
CDM class name
app.db.mssql.SqlServer
Relationships
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.ComputerSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-ComputerSystem
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-OperatingSystem
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerDatabase
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
SqlServerDatabase
contains
v Source: app.db.mssql.SqlServerDatabase
v Target: app.db.mssql.SqlServerTable
v Example: SQLServer:SQLInstance:MSS-1-SqlServerDatabase contains
SQLServer:SQLInstance:MSS-1-0-spt_monitor-SqlServerTable
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerProcess
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
7412-SqlServerProcess
installedOn
v Source: app.TMSAgent
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-TMSAgent is installedOn 9.65.44.55-OperatingSystem
v Source: app.TMSAgent
v Target: app.db.mssql.SqlServer
v Example: SQLServer:SQLInstance:MSS-TMSAgent monitors SQLServer:SQLInstance:MSS-
SqlServer
CDM attributes, agent attributes, descriptions, and examples
v CDM attribute: Id (IdML)
Agent attribute: INODESTS.HOSTADDR
Description: The host address of the workstation where the Microsoft SQL Server instance is
running.
Example: INSTANCE1_2005:PS3213W2K3:MSS-SqlServer

386 Microsoft SQL Server agent: User’s Guide

 v CDM attribute: ManagedSystemName
Agent attribute: INODESTS.NODE
Description: The name of the IBM Tivoli Monitoring component that provides data for the
management of the Microsoft SQL Server instance.
Example: INSTANCE1_2005:PS3213W2K3:MSS
v CDM attribute: KeyName
Agent attribute: AppServer
Description: A user defined string that is used to identify the Microsoft SQL Server instance.
Example: AppServer
v CDM attribute: ProductVersion
Agent attribute: KOQSRVRE.SRVVERSN
Description: The version of the Microsoft SQL Server.
Example: 9.00.13
v CDM attribute: Name
Agent attribute: KOQSRVRE.SERVERID
Description: The name of the Microsoft SQL Server.
Example: INSTANCE1_2005
v CDM attribute: Status
Agent attribute: KOQSRVRE.SRVSTATUS
Description: The status of the Microsoft SQL Server (Running/Stopped).
Example: Running
v CDM attribute: Label
Agent attribute: KOQSRVRE.SERVERID
Description: The label of the Microsoft SQL Server.
Example: INSTANCE1_2005

SqlServerDatabase class
The ServiceAccessPoint class represents the instance of the services that are used by the Microsoft Active
Directory.
CDM class name
app.db.mssql.SqlServerDatabase
Superior CDM class
SqlServer
Relationships
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.ComputerSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-ComputerSystem
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-OperatingSystem
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerDatabase
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
SqlServerDatabase
contains

Appendix C. Discovery Library Adapter for the Microsoft SQL Server agent 387
 v Source: app.db.mssql.SqlServerDatabase
v Target: app.db.mssql.SqlServerTable
v Example: SQLServer:SQLInstance:MSS-1-SqlServerDatabase contains
SQLServer:SQLInstance:MSS-1-0-spt_monitor-SqlServerTable
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerProcess
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
7412-SqlServerProcess
installedOn
v Source: app.TMSAgent
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-TMSAgent is installedOn 9.65.44.55-OperatingSystem
v Source: app.TMSAgent
v Target: app.db.mssql.SqlServer
v Example: SQLServer:SQLInstance:MSS-TMSAgent monitors SQLServer:SQLInstance:MSS-
SqlServer
CDM attributes, agent attributes, descriptions, and examples
v CDM attribute: Id (IdML)
Agent attribute: INODESTS.HOSTADDR
Description: The host address of the workstation where the Microsoft SQL Server instance is
running.
Example: INSTANCE1_2005:PS3213W2K3:MSS-2-SqlServerDatabase
v CDM attribute: ManagedSystemName
Agent attribute: INODESTS.NODE
Description: The name of the IBM Tivoli Monitoring component that provides data for the
management of the Microsoft SQL Server instance.
Example: INSTANCE1_2005:PS3213W2K3:MSS
v CDM attribute: Name
Agent attribute: KOQDBD.DBNAME
Description: The name of the Microsoft SQL Server database.
Example: tempdb
v CDM attribute: DbId
Agent attribute: KOQDB.DBID
Description: The ID of the Microsoft SQL Server database.
Example: 2
v CDM attribute: Label
Agent attribute: KOQDBD.DBNAME
Description: The label of the Microsoft SQL Server database.
Example: INSTANCE1_2005:PS3213W2K3:MSS

SqlServerTable class
The BindAddress class represents an IP protocol endpoint on which a service is provided.
CDM class name
app.db.mssql.SqlServerTable
Superior CDM class
SqlServerDatabase
Relationships

388 Microsoft SQL Server agent: User’s Guide

 runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.ComputerSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-ComputerSystem
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-OperatingSystem
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerDatabase
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
SqlServerDatabase
contains
v Source: app.db.mssql.SqlServerDatabase
v Target: app.db.mssql.SqlServerTable
v Example: SQLServer:SQLInstance:MSS-1-SqlServerDatabase contains
SQLServer:SQLInstance:MSS-1-0-spt_monitor-SqlServerTable
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerProcess
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
7412-SqlServerProcess
installedOn
v Source: app.TMSAgent
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-TMSAgent is installedOn 9.65.44.55-OperatingSystem
v Source: app.TMSAgent
v Target: app.db.mssql.SqlServer
v Example: SQLServer:SQLInstance:MSS-TMSAgent monitors SQLServer:SQLInstance:MSS-
SqlServer
CDM attributes, agent attributes, descriptions, and examples
v CDM attribute: Id (IdML)
Agent attribute: INODESTS.HOSTADDR
Description: The host address of the workstation where the Microsoft SQL Server instance is
running.
Example: INSTANCE1_2005:PS3213W2K3:MSS-0-spt_monitor-SqlServerTable
v CDM attribute: ManagedSystemName
Agent attribute: INODESTS.NODE
Description: The name of the IBM Tivoli Monitoring component that provides data for the
management of the Microsoft SQL Server instance.
Example: INSTANCE1_2005:PS3213W2K3:MSS
v CDM attribute: Name
Agent attribute: KOQTBLD.UTBLNAME
Description: The name of the table in the Microsoft SQL Server database.
Example: spt_monitor
v CDM attribute: Label

Appendix C. Discovery Library Adapter for the Microsoft SQL Server agent 389
 Agent attribute: KOQTBLD.UTBLNAME
Description: The label of the Microsoft SQL Server table.
Example: spt_monitor

SqlServerProcess class
The IpAddress class represents the instance of an IP address.
CDM class name
app.db.mssql.SqlServerProcess
Superior CDM class
SqlServer
Relationships
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.ComputerSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-ComputerSystem
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-OperatingSystem
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerDatabase
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
SqlServerDatabase
contains
v Source: app.db.mssql.SqlServerDatabase
v Target: app.db.mssql.SqlServerTable
v Example: SQLServer:SQLInstance:MSS-1-SqlServerDatabase contains
SQLServer:SQLInstance:MSS-1-0-spt_monitor-SqlServerTable
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerProcess
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
7412-SqlServerProcess
installedOn
v Source: app.TMSAgent
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-TMSAgent is installedOn 9.65.44.55-OperatingSystem
v Source: app.TMSAgent
v Target: app.db.mssql.SqlServer
v Example: SQLServer:SQLInstance:MSS-TMSAgent monitors SQLServer:SQLInstance:MSS-
SqlServer
CDM attributes, agent attributes, descriptions, and examples
v CDM attribute: Id (IdML)
Agent attribute: INODESTS.HOSTADDR

390 Microsoft SQL Server agent: User’s Guide

 Description: The host address of the workstation where the Microsoft SQL Server instance is
running.
Example: INSTANCE1_2005:PS3213W2K3:MSS-1-SqlServerProcess
v CDM attribute: ManagedSystemName
Agent attribute: INODESTS.NODE
Description: The name of the IBM Tivoli Monitoring component that provides data for the
management of the Microsoft SQL Server instance.
Example: INSTANCE1_2005:PS3213W2K3:MSS
v CDM attribute: Spid
Agent attribute: KOQPRCD.PROCESSID
Description: The ID of the process.
Example: 51
v CDM attribute: Status
Agent attribute: KOQPRCD.STATUS
Description: The status of the process.
Example: runnable
v CDM attribute: PhysicalIo
Agent attribute: KOQPRCD.IO
Description: The number of accesses to the hard disk since the process started.
Example: 0
v CDM attribute: MemUsage
Agent attribute: KOQPRCD.MEMORY
Description: The number of KB allocated for this process.
Example: 2
v CDM attribute: Cpu
Agent attribute: KOQPRCD.CPU
Description: The amount of CPU time (in seconds) that the process has used since it started.
Example: 0.1317
v CDM attribute: Cmd
Agent attribute: KOQPRCD.CMDNAME
Description: The name of the executing command.
Example: SELECT
v CDM attribute: Label
Agent attribute: KOQPRCD.PROCESSID
Description: The label of the Microsoft SQL Server process.
Example: 51

TMSAgent class
The IpAddress class represents the instance of an IP address.
CDM class name
app.TMSAgent
Relationships
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.ComputerSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-ComputerSystem
runsOn
v Source: app.db.mssql.SqlServer
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-SqlServer runsOn 9.65.44.55-OperatingSystem

Appendix C. Discovery Library Adapter for the Microsoft SQL Server agent 391
 contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerDatabase
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
SqlServerDatabase
contains
v Source: app.db.mssql.SqlServerDatabase
v Target: app.db.mssql.SqlServerTable
v Example: SQLServer:SQLInstance:MSS-1-SqlServerDatabase contains
SQLServer:SQLInstance:MSS-1-0-spt_monitor-SqlServerTable
contains
v Source: app.db.mssql.SqlServer
v Target: app.db.mssql.SqlServerProcess
v Example: SQLServer:SQLInstance:MSS-SqlServer contains SQLServer:SQLInstance:MSS-1-
7412-SqlServerProcess
installedOn
v Source: app.TMSAgent
v Target: sys.OperatingSystem
v Example: SQLServer:SQLInstance:MSS-TMSAgent is installedOn 9.65.44.55-OperatingSystem
v Source: app.TMSAgent
v Target: app.db.mssql.SqlServer
v Example: SQLServer:SQLInstance:MSS-TMSAgent monitors SQLServer:SQLInstance:MSS-
SqlServer
CDM attributes, agent attributes, descriptions, and examples
v CDM attribute: Id (IdML)
Agent attribute: INODESTS.HOSTADDR
Description: The host address of the workstation where the Microsoft SQL Server instance is
running.
Example: INSTANCE1_2005:PS3213W2K3:MSS-TMSAgent
v CDM attribute: ManagedSystemName
Agent attribute: INODESTS.NODE
Description: The name of the IBM Tivoli Monitoring component that provides data for the
management of the Microsoft SQL Server instance.
Example: INSTANCE1_2005:PS3213W2K3:MSS
v CDM attribute: ManagedObjectName
Agent attribute: INODESTS.NODE
Description: The name of the IBM Tivoli Monitoring component that provides data for the
management of the Microsoft SQL Server instance.
Example: p@INSTANCE1_2005:PS3213W2K3:MSS
v CDM attribute: SoftwareVersion
Agent attribute: INODESTS.VERSION
Description: The version of the Microsoft SQL Server agent.
Example: 06.12.00
v CDM attribute: ProductCode
Agent attribute: INODESTS.PRODUCT
Description: The product code of Microsoft SQL Server agent.
Example: OQ
v CDM attribute: Affinity
Agent attribute: INODESTS.AFFINITIES

392 Microsoft SQL Server agent: User’s Guide

 Description: The affinity of Microsoft SQL Server agent.
Example: 00000000000W000000000000000000000G00004w0a7
v CDM attribute: Label
Agent attribute: INODESTS.NODE
Description: The label of the Microsoft SQL Server agent.
Example: INSTANCE1_2005:PS3213W2K3:MSS-TMSAgent

Appendix C. Discovery Library Adapter for the Microsoft SQL Server agent 393
394 Microsoft SQL Server agent: User’s Guide
Appendix D. Integration with Tivoli Business Service Manager
Microsoft SQL Server agent provides data to create, update the status of, and view IBM Tivoli Business
Service Manager services.

The Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library Toolkit
provides data for the Tivoli Business Service Manager service models. The Tivoli Event Integration
Facility (EIF) probe updates the status of these services, and you use the Tivoli Enterprise Portal to view
the data for the services. To implement the integration of the agent with Tivoli Business Service Manager,
perform the integration tasks.

Components for integrating with Tivoli Business Service Manager

The data for integrating with Tivoli Business Service Manager is supplied through the following
components: Tivoli Management Services Discovery Library Adapter (DLA) and Discovery Library
Toolkit, Tivoli Event Integration Facility (EIF) probe, and Tivoli Enterprise Portal Server.

Tivoli Management Services Discovery Library Adapter (DLA) and Discovery

Library Toolkit

By using data from the Tivoli Management Services Discovery Library Adapter, you can build Tivoli
Business Service Manager service models that include resources monitored by the Microsoft SQL Server.

The DLA files can be imported directly into Tivoli Business Service Manager using the Discovery Library
Toolkit or they can be loaded into IBM Tivoli Application Dependency Discovery Manager (Tivoli
Business Service Manager) and then fed into Tivoli Business Service Manager using the Discovery Library
Toolkit.

See the following sources for more information about the DLA and Discovery Library Toolkit:
v Resources and relationships that are discovered by the Microsoft SQL Server and included in Tivoli
Management Services DLA files: Appendix C, “Discovery Library Adapter for the Microsoft SQL Server
agent,” on page 385
v Using the Tivoli Management Services DLA: IBM Tivoli Monitoring Administrator's Guide
v Using the Discovery Library Toolkit: Tivoli Business Service Manager Customization Guide

Tivoli Event Integration Facility (EIF) probe

Situation events detected by the Microsoft SQL Server can update the status of services in Tivoli Business
Service Manager.

The situation events are forwarded from IBM Tivoli Monitoring to the Netcool/OMNIbus Probe for the
Tivoli Event Integration Facility. The Microsoft SQL Server provides a probe rules file that updates its
events with information to identify the affected service in Tivoli Business Service Manager. The EIF probe
then forwards the events to the Netcool/OMNIbus ObjectServer. Tivoli Business Service Manager
monitors the Netcool/OMNIbus ObjectServer for new events and updates the status of affected services.

See the following sources for more information about event integration:
v Installation (using an existing EIF probe and Netcool/OMNIbus ObjectServer installation or using
Tivoli Business Service Manager to install these components): Netcool/OMNIbus Information Center or
the Tivoli Business Service Manager Installation Guide.

© Copyright IBM Corp. 2005, 2012 395

v Setting up event integration between IBM Tivoli Monitoring, the EIF probe, and the Netcool/OMNIbus
ObjectServer: IBM Tivoli Monitoring Installation and Setup Guide.
v Configuring the EIF probe to use the Microsoft SQL Server rules file after the EIF probe has been
installed and configured for event integration with IBM Tivoli Monitoring: “Configuring the Tivoli
Event Integration Facility (EIF) probe to enrich events”

Tivoli Enterprise Portal

You can use the integration of the Tivoli Enterprise Portal Server with Tivoli Business Service Manager to
view the services in the Tivoli Business Service Manager console.

For more detailed examination and analysis, you can easily link from the Tivoli Business Service Manager
console to the Tivoli Enterprise Portal Server to view the data within the Microsoft SQL Server.

Tasks to integrate the agent with Tivoli Business Service Manager

To integrate the Microsoft SQL Server agent with Tivoli Business Service Manager, you must install and
configure the required components. Then, you can view the data in the Tivoli Enterprise Portal.

To integrate the Microsoft SQL Server agent with Tivoli Business Service Manager and view the data,
complete the following tasks:
v Install the Discovery Library Toolkit on theTivoli Business Service Manager server.
v Configure the Tivoli Event Integration Facility (EIF) probe to enrich Microsoft SQL Server agent events.
v Create a service in the Tivoli Business Service Manager console that you want to monitor.
v Create a data source mapping for each data source that you want to access within the Tivoli Business
Service Manager.
v Configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal Server.
v View data in the Tivoli Enterprise Portal for the services that you have created to monitor through
Tivoli Business Service Manager.

Installing the Discovery Library Toolkit on the Tivoli Business Service

Manager
You must install the Discovery Library Toolkit on the Tivoli Business Service Manager server.

The Discovery Library Toolkit imports data from the DLA files and TADDM, which includes information
about the hardware and the applications that are discovered by the source.

See "Installing the Discovery Library Toolkit" in the Tivoli Business Service Manager Installation Guide.

Configuring the Tivoli Event Integration Facility (EIF) probe to enrich

events
The Netcool/OMNIbus Probe for Tivoli Event Integration Facility (EIF) forwards the Microsoft SQL
Server agent events that are received from Tivoli Business Service Manager to the Netcool/OMNIbus
ObjectServer. Tivoli Business Service Manager monitors the Netcool/OMNIbus ObjectServer for new
events, and updates the status of affected services. The Microsoft SQL Server agent provides a probe rules
include file that updates its events with information to identify the affected service in Tivoli Business
Service Manager.

Before you begin

Install and configure the Netcool/OMNIbus ObjectServer and EIF probe and set up event integration
between IBM Tivoli Monitoring and Netcool/OMNIbus.

396 Microsoft SQL Server agent: User’s Guide

About this task

To enable event enrichment, configure the EIF probe to use the rules file for the agent.

Procedure
1. Locate the Microsoft SQL Server agent rules file (koq_tbsm.rules) on a computer system where the
Microsoft SQL Server agent, Tivoli Enterprise Monitoring Server, or Tivoli Enterprise Portal Server is
installed. The file is in the following locations:
v On Windows systems
The file is in the installdir\cms\TECLIB directory of the monitoring server, in the
installdir\cnps\TECLIB directory of the portal server, or in the installdir\TMAITM6\EIFLIB
directory of the agent, where installdir is the IBM Tivoli Monitoring or ITCAM for Microsoft
Applications installation directory.
v On Linux and UNIX systems
The file is in the installdir/tables/cicatrsq/TECLIB directory of the monitoring server or in the
installdir/platform/xx/TECLIB directory of the agent, where installdir is the IBM Tivoli Monitoring
or ITCAM for Microsoft Applications directory, platform is the architecture directory for the agent,
and xx is the product code for the agent.
2. Copy the koq_tbsm.rules file to the following directory on the computer system where the EIF probe
is installed:
v On Windows systems
%OMNIHOME%\probes\arch
v On UNIX systems
$OMNIHOME/probes/arch
Where:
OMNIHOME
System-defined variable defining the installation location of Netcool/OMNIbus
arch Operating system directory where the probe is installed; for example, solaris2 when running
on a Solaris system, and win32 for a Windows system.
3. Edit the tivoli_eif.rules file and uncomment the include statement for koq_tbsm.rules. (The
tivoli_eif.rules file is located in the same directory as the koq_tbsm.rules file.) If you are using a
version of the tivoli_eif.rules file without an include statement for koq_tbsm.rules, add the
following line after the include statement for itm_event.rules:
include "koq_tbsm.rules"
4. Restart the EIF probe.

Creating a service in Tivoli Business Service Manager

You must create a service in the Tivoli Business Service Manager console for each service that you want
to monitor.

To create the services that you want to monitor in the Tivoli Business Service Manager console, see
"Configuring services" in the IBM Tivoli Business Service Manager Service Configuration Guide.

Creating a data source mapping for each data source

You can create a data source mapping for each data source that you want to access within Tivoli Business
Service Manager.

Also, you can create the data fetchers and use the data to create incoming status rules that are populated
in your service templates.

Appendix D. Integration with Tivoli Business Service Manager 397

For more information, see "Data sources" and "Data fetchers" in the IBM Tivoli Business Service Manager
Service Configuration Guide.

Configuring additional IBM Tivoli Monitoring web services

You can configure additional IBM Tivoli Monitoring web services for each Tivoli Enterprise Portal Server.

To configure an additional IBM Tivoli Monitoring web service for each Tivoli Enterprise Portal server, see
"Configure TBSM charts" in the IBM Tivoli Business Service Manager Scenarios Guide.

Viewing data in the Tivoli Enterprise Portal

From Tivoli Business Service Manager, you can open the Tivoli Enterprise Portal and view the Microsoft
SQL Server agent.

You can also launch Tivoli Business Service Manager from the Tivoli Enterprise Portal.

For more information about launching applications, see "Launching to and from applications" in the Tivoli
Business Service Manager Customization Guide.

398 Microsoft SQL Server agent: User’s Guide

Appendix E. Documentation library
A variety of publications are relevant to the use of theIBM Tivoli Composite Application Manager for
Microsoft Applications: Microsoft SQL Server Agent.

The IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Manager products: Documentation
Guide contains information about accessing and using publications. You can find the Documentation
Guide in the following information centers:
v IBM Tivoli Monitoring and OMEGAMON XE (http://publib.boulder.ibm.com/infocenter/tivihelp/
v15r1/index.jsp)
v IBM Tivoli Composite Application Manager (http://publib.boulder.ibm.com/infocenter/tivihelp/
v24r1/index.jsp)
To open the Documentation Guide in the information center, select Using the publications in the
Contents pane.

To find a list of new and changed publications, click What's new in the information center on the
Welcome page of the IBM Tivoli Monitoring and OMEGAMON XE Information Center.

To find publications from the previous version of a product, click Previous versions under the name of
the product in the Contents pane.

IBM Tivoli Composite Application Manager for Microsoft Applications: Microsoft

SQL Server Agent library

The documentation for this agent and other product components is located in the IBM Tivoli Composite
Application Manager for Microsoft Applications Information Center (http://publib.boulder.ibm.com/
infocenter/tivihelp/v24r1/topic/com.ibm.itcamms.doc_6.3/welcome_msapps63.html).

One document is specific to the Microsoft SQL Server agent. The IBM Tivoli Composite Application
Manager for Microsoft Applications: Microsoft SQL Server Agent User’s Guide provides agent-specific
information for configuring, using, and troubleshooting the Microsoft SQL Server agent.

The Offering Guide also provides information about installing and configuring the component products in
the offering.

The Prerequisites topic in the information center contains information about the prerequisites for each
component.

Use the information in the user's guide for the agent with the Tivoli Enterprise Portal User's Guide to
monitor Microsoft SQL Server resources.

Prerequisite publications
See the following publications to gain the required prerequisite knowledge:
v IBM Tivoli Monitoring Troubleshooting Guide
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring
v IBM Tivoli Monitoring: Upgrading from V5.1.2
v IBM Tivoli Monitoring Universal Agent User's Guide
v IBM Tivoli Monitoring Universal Agent API and Command Programming Reference Guide
v Tivoli Enterprise Portal User's Guide

© Copyright IBM Corp. 2005, 2012 399

v IBM Tivoli Monitoring Administrator's Guide
v IBM Tivoli Monitoring Agent Builder User's Guide
v IBM Tivoli Monitoring Command Reference
v Configuring IBM Tivoli Enterprise Monitoring Server on z/OS
v IBM Tivoli Monitoring Installation and Setup Guide
v IBM(r) Tivoli(r) Monitoring High Availability Guide for Distributed Systems
v IBM Tivoli Monitoring: Messages
v IBM Tivoli Monitoring Troubleshooting Guide
v IBM Tivoli Monitoring Universal Agent User's Guide
v IBM Tivoli Universal Agent API and Command Programming Reference Guide
v IBM Tivoli Monitoring: i5/OS Agent User's Guide
v IBM Tivoli Monitoring: Linux OS Agent User's Guide
v IBM Tivoli Monitoring: UNIX OS Agent User's Guide
v IBM Tivoli Monitoring: UNIX Logs OS Agent User's
v IBM Tivoli Monitoring: Windows OS Agent User's Guide
v Tivoli Enterprise Portal User's Guide
v IBM(r) Tivoli(r) Performance Analyzer User's Guide
v IBM(r)Tivoli(r) Warehouse Proxy Agent User's Guide
v IBM(r)Tivoli(r) Warehouse Summarization and Pruning Agent User's Guide

Related publications
The publications in related information centers provide useful information.

See the following information centers, which you can find by accessing Tivoli Documentation Central
(http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Home):
v IBM Tivoli Monitoring
v IBM Tivoli Netcool/OMNIbus
v IBM Tivoli Application Dependency Discovery Manager
v IBM Tivoli Enterprise Console

Other sources of documentation

See the following sources of technical documentation about monitoring products:
v Service Management Connect (SMC)
See the introductory information about SMC (http://www.ibm.com/developerworks/
servicemanagement/).
For information about Tivoli products, see the Application Performance Management community on
SMC (http://www.ibm.com/developerworks/servicemanagement/apm/index.html).
Connect, learn, and share with Service Management professionals. Get access to developers and
product support technical experts who provide their perspectives and expertise. You can use SMC for
these purposes:
– Become involved with transparent development, an ongoing, open engagement between external
users and developers of Tivoli products where you can access early designs, sprint demos, product
roadmaps, and pre-release code.
– Connect one-on-one with the experts to collaborate and network about Tivoli and Integrated Service
Management.
– Benefit from the expertise and experience of others using blogs.

400 Microsoft SQL Server agent: User’s Guide

 – Collaborate with the broader user community using wikis and forums.
v IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/
ismlibrary/) is an online catalog that contains integration documentation as well as other
downloadable product extensions.
v IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks® publications,
Redpapers, and Redbooks technotes that provide information about products from platform and
solution perspectives.
v Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBM
Software Support website, provide the latest information about known product limitations and
workarounds.
v Tivoli wikis
Tivoli Wiki Central (http://www.ibm.com/developerworks/wikis/display/tivoli/Home) is the home
for interactive wikis that offer best practices and scenarios for using Tivoli products. The wikis contain
white papers contributed by IBM employees, and content created by customers and business partners.
Two of these wikis are of particular relevance to IBM Tivoli Monitoring:
– Tivoli Distributed Monitoring and Application Management Wiki (http://www-10.lotus.com/ldd/
tivmonitorwiki.nsf) provides information about IBM Tivoli Monitoring and related distributed
products, including IBM Tivoli Composite Application Manager products.
– Tivoli System z® Monitoring and Application Management Wiki (http://www.ibm.com/
developerworks/wikis/display/tivoliomegamon/Home) provides information about the
OMEGAMON XE products, Tivoli NetView® for z/OS, Tivoli Monitoring Agent for z/TPF, and
other System z monitoring and application management products.

Appendix E. Documentation library 401

402 Microsoft SQL Server agent: User’s Guide
Accessibility
Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, to
use software products successfully.

The major accessibility features in this product enable users in the following ways:
v Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear what
is displayed on the screen. Consult the product documentation of the assistive technology for details
on using those technologies with this product.
v Operate specific or equivalent features using only the keyboard.
v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the following features to aid
accessibility:
v All documentation is available in both HTML and convertible PDF formats to give the maximum
opportunity for users to apply screen-reader software.
v All images in the documentation are provided with alternative text so that users with vision
impairments can understand the contents of the images.

Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and are documented by the operating
system. See the documentation provided by your operating system for more information.

Magnifying what is displayed on the screen

You can enlarge information in the product windows using facilities provided by the operating systems
on which the product is run. For example, in a Microsoft Windows environment, you can reduce the
resolution of the screen to enlarge the font sizes of the text on the screen. See the documentation
provided by your operating system for more information.

© Copyright IBM Corp. 2005, 2012 403

404 Microsoft SQL Server agent: User’s Guide
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the
products, services, or features discussed in this document in other countries. Consult your local IBM
representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can send
license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

© Copyright IBM Corp. 2005, 2012 405

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases
payment of a fee.

The licensed program described in this document and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without
notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without
notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the
products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform for
which the sample programs are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs. You may copy, modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application programs conforming
to IBM‘s application programming interfaces.

406 Microsoft SQL Server agent: User’s Guide

Each copy or any portion of these sample programs or any derivative work, must include a copyright
notice as follows:

© IBM 2009. Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.
2009. All rights reserved.

If you are viewing this information in softcopy form, the photographs and color illustrations might not be
displayed.

Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at
“Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States
and other countries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the
United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Notices 407
408 Microsoft SQL Server agent: User’s Guide
Index
A data from operating system or MS SQL Server files
data from SELECT statements 8
13

accessibility 403 data provider 271

agent database agent installation problems 277
functions 1 detailed 275
trace logs 271 Discovery Library Adapter 395
troubleshooting 287 See DLA
attribute groups Discovery Library Toolkit 395
cache duration for 6 installing 396
list of all 59 disk capacity planning for historical data 222
that gather data from operating system or MS SQL Server DLA 385, 395
files 13 data model 385
that gather data from SELECT statements 8 classes 385
when data is collected 6 documentation
authorization See publications
additional 19
required 19

E
B Error Log File 27
event
built-in troubleshooting features 269 mapping 313

C F
cache duration for attribute groups 6 files
calculate historical data disk space 222 agent trace 271
capacity planning for historical data 222 installation trace 271
changes other trace log 271
baroc file updated 2 trace logs 270
cluster environment
creating a resource 38
installing and configuring the monitoring agent 37
making configuration changes 39 G
requirements 37 gathering support information 269
setting up the monitoring agent 36 granting permission 19
commands
tacmd 25
tacmd addSystem 35 H
tacmd configureSystem 35 historical data
tacmd startAgent 36 calculate disk space 222
components 4 disk capacity planning 222
IBM Tivoli Monitoring 4 Home Directory 27
configuration
local 23
Manage Tivoli Enterprise Monitoring Services window 23
parameters 25 I
procedures 18 IBM Software Support 269
remote 34 IBM Tivoli Composite Application Manager for Microsoft
settings 25 Applications: Microsoft SQL Server Agent
tacmd command line 35 performance considerations 301
Tivoli Enterprise Portal 34 IBM Tivoli Enterprise Console
creating user ID 19 event mapping 313
IBM Tivoli Monitoring 4
overview 1
D include file 396
information, additional
data policies 253
trace logs 270 situations 227
data collection Take Action commands 239
processes 6 installation
data collection for attribute groups 6 log file 271

© Copyright IBM Corp. 2005, 2012 409

installation (continued)
problems 277
R
silent 32 reconfiguration 35
instance name 26 remote configuration 34
instance property 35 remote deployment
interface, user 5 troubleshooting 296
requirements
configuration 15
installation 15
L
limited user permissions, upgrading your warehouse
with 310
logging
S
agent trace logs 271 SELECT statements 8
built-in features 269 Server Name 26
installation log files 271 situations
location and configuration of logs 270 general troubleshooting 302
trace log files 270 more information 227
Login 26 predefined 228
specific troubleshooting 301
SQL Server problems 286
starting the monitoring agent 35
M when 19
Manage Tivoli Enterprise Monitoring Services support
reconfiguring the agent 35 gathering information for 269
starting the agent 36
Manage Tivoli Enterprise Monitoring Services window
local configuration 23
messages
T
built-in features 269 tacmd addSystem command 35
MS_SQL_DB_free_space_critical policy 253 tacmd command line
reconfiguring 35
remote configuration 35
tacmd configureSystem command 35
O tacmd startAgent 36
overview Take Action commands
IBM Tivoli Monitoring 1 more information 239
troubleshooting 304
target application
P problems 286
Password 26 Tivoli Business Service Manager
path names, for trace logs 270 components for integrating with 395
performance considerations 301 configuring additional IBM Tivoli Monitoring web
permission, granting 19 services 398
permissions, upgrading your warehouse with limited creating a service 397
user 310 creating data source mapping 397
policies installing Discovery Library Toolkit 396
list of all 253 integration 395
MS_SQL_DB_free_space_critical_NAME 253 launching from Tivoli Enterprise Portal 398
overview 253 Tivoli Enterprise Portal Server
policies Tivoli Event Integration Facility (EIF) probe 395
more information 253 viewing data in Tivoli Enterprise Portal 398
predefined 253 Tivoli Business Service Managerintegration tasks 396
prerequisite checker 16 Tivoli Common Reporting
prerequisites 16 troubleshooting 305
probe rules file Tivoli Enterprise Portal
include 396 configuring the agent remotely 34
problems and workarounds 277 reconfiguring agent instance 35
problems with monitoring SQL Server 286 Tivoli Event Integration Facility (EIF) probe
properties configuring 396
instance 35 trace logs 270
publications 399 directories 270
prerequisite 399 tracing 275
related 400 transport command 286
purposes troubleshooting 269, 277
troubleshooting 269 agents 287
built-in features 269
installation 277
installation logs 271

410 Microsoft SQL Server agent: User’s Guide

troubleshooting (continued)
remote deployment 296
situations 301, 302
Take Action commands 304
Tivoli Common Reporting 305
uninstallation 277
uninstallation logs 271
workspaces 297

U
uninstallation
log file 271
problems 277
upgrading for warehouse summarization 309
upgrading your warehouse with limited user
permissions 310
User ID 26
user ID, creating 19
user interfaces options 5
user permissions, upgrading your warehouse with
limited 310

W
warehouse summarization
upgrading for
overview 309
warehouse summarization upgrading
effects on summarized attributes 309
tables in the warehouse 309
Windows agent installation problems 277
workarounds 277
agents 287
remote deployment 296
situations 301
Take Action commands 304
Tivoli Common Reporting 305
workspaces 297
workspaces
troubleshooting 297

Index 411
412 Microsoft SQL Server agent: User’s Guide



Product Number: 1234-SS1

Printed in USA

SC23-8880-06