Tivoli Monitoring for Databases: Microsoft SQL Server Agent


Version 6.1.0

User’s Guide

SC32-9452-00
 Tivoli Monitoring for Databases: Microsoft SQL Server Agent
®


Version 6.1.0

User’s Guide

SC32-9452-00
 Note
Before using this information and the product it supports, read the information in Appendix E, “Notices,” on page 141.

First Edition (November 2005)

This edition applies to version 6.1 of IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent (product
number 5724-B96) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . vii View real-time data about Microsoft SQL Server . . 15
Investigate an event . . . . . . . . . . . 16
About this guide . . . . . . . . . . . ix Recover the operation of a resource . . . . . . 16
Customize your monitoring environment . . . . 17
Who should read this guide . . . . . . . . . ix
Monitor with custom situations that meet your
What this guide contains . . . . . . . . . . ix
requirements . . . . . . . . . . . . . . 18
Publications . . . . . . . . . . . . . . x
Collect and view historical data . . . . . . . 19
Prerequisite publications . . . . . . . . . x
Related publications . . . . . . . . . . . x
Accessing terminology online . . . . . . . xi Chapter 4. Workspaces reference . . . 21
Accessing publications online . . . . . . . xi About workspaces . . . . . . . . . . . . 21
Ordering publications . . . . . . . . . . xi More information about workspaces . . . . . . 21
Accessibility . . . . . . . . . . . . . . xi Predefined workspaces . . . . . . . . . . 21
Tivoli technical training . . . . . . . . . . xii Databases Navigator item . . . . . . . . 22
Support information . . . . . . . . . . . xii Errorlog Alerts Navigator item . . . . . . . 23
Conventions used in this guide . . . . . . . . xii Server Locking Navigator item . . . . . . . 23
Typeface conventions . . . . . . . . . . xii Processes Navigator item . . . . . . . . . 24
Operating system-dependent variables and paths xii Servers Navigator item . . . . . . . . . 25

Chapter 1. Overview of the Monitoring Chapter 5. Attributes reference . . . . 27

Agent for Microsoft SQL Server . . . . 1 About attributes . . . . . . . . . . . . . 27
IBM Tivoli Monitoring overview . . . . . . . . 1 More information about attributes . . . . . . . 27
Features of the Monitoring Agent for Microsoft SQL Attribute groups and attributes for the Monitoring
Server . . . . . . . . . . . . . . . . 1 Agent for Microsoft SQL Server . . . . . . . 28
Components of Monitoring Agent for Microsoft SQL Configuration attributes . . . . . . . . . 28
Server . . . . . . . . . . . . . . . . 2 Database Detail attributes . . . . . . . . 29
User interface options . . . . . . . . . . . 2 Database Summary attributes . . . . . . . 32
Device Detail attributes . . . . . . . . . 33
Lock Conflict Detail attributes . . . . . . . 35
Chapter 2. Requirements and Lock Detail attributes . . . . . . . . . . 36
configuration for the monitoring agent . 5 Lock Summary attributes . . . . . . . . . 37
Requirements for the monitoring agent . . . . . 5 Problem Detail attributes . . . . . . . . . 38
Configuration settings for installing the monitoring Problem Summary attributes . . . . . . . 39
agent . . . . . . . . . . . . . . . . . 6 Process Detail attributes . . . . . . . . . 40
Configuring on your local system from the Process Summary attributes . . . . . . . . 42
Manage Tivoli Enterprise Monitoring Services Remote Servers attributes . . . . . . . . . 44
window . . . . . . . . . . . . . . . 6 Server Detail attributes . . . . . . . . . 45
Configuring on your local system using the tacmd Server Enterprise attributes . . . . . . . . 47
command line . . . . . . . . . . . . . 7 Server Summary attributes . . . . . . . . 49
Configuration settings for reconfiguring the Statistics Detail attributes . . . . . . . . . 51
monitoring agent . . . . . . . . . . . . . 8 Statistics Summary attributes . . . . . . . 52
Reconfiguring on your local system from the Table Detail attributes . . . . . . . . . . 54
Manage Tivoli Enterprise Monitoring Services Text attributes . . . . . . . . . . . . 55
window . . . . . . . . . . . . . . . 8 Disk capacity planning for historical data . . . . 56
Reconfiguring on your local system using the
tacmd command line . . . . . . . . . . 9 Chapter 6. Situations reference . . . . 59
Configuration settings and parameters for deploying
About situations . . . . . . . . . . . . . 59
monitoring across your environments . . . . . 10
More information about situations . . . . . . . 60
Deploying the monitoring agent remotely from
Predefined situations . . . . . . . . . . . 60
the Tivoli Enterprise Portal . . . . . . . . 10
MS_SQL_Block_Critical situation . . . . . . 62
Deploying the monitoring agent using the tacmd
MS_SQL_Block_Warning situation . . . . . . 62
command line . . . . . . . . . . . . 11
MS_SQL_Cache_Ave_FreePage_Crit situation . . 62
Granting permissions . . . . . . . . . . . 12
MS_SQL_Cache_Ave_FreePage_Warn situation . 62
MS_SQL_Cache_Hit_Ratio_Crit situation . . . 62
Chapter 3. How to use the Monitoring MS_SQL_Cache_Hit_Ratio_Warn situation . . . 62
Agent for Microsoft SQL Server . . . . 15 MS_SQL_Cache_Max_FreePage_Crit situation . . 62

© Copyright IBM Corp. 2005 iii

 MS_SQL_Cache_Max_FreePage_Warn situation 63 MS_SQL_Repl_Latency_Crit situation . . . . . 71
MS_SQL_Client_Cnt_Pct_Used_Crit situation . . 63 MS_SQL_Repl_Latency_Warn situation . . . . 71
MS_SQL_Client_Cnt_Pct_Used_Warn situation . 63 MS_SQL_Status_Critical situation . . . . . . 72
MS_SQL_Collection_Status_Warning situation . . 63 MS_SQL_Status_Inactive situation . . . . . . 72
MS_SQL_CPU_Critical situation . . . . . . 63 MS_SQL_Total_Locks_Critical situation . . . . 72
MS_SQL_CPU_Warning situation . . . . . . 63 MS_SQL_Total_Locks_Warning situation . . . . 72
MS_SQL_DB_Error_Status situation . . . . . 63
MS_SQL_DB_FreeSpace_Critical situation . . . 64 Chapter 7. Take Action commands
MS_SQL_DB_FreeSpace_Warning situation . . . 64 reference . . . . . . . . . . . . . . 73
MS_SQL_DB_Num_Errors_Warning situation . . 64
About Take Action commands . . . . . . . . 73
MS_SQL_DB_Space_Pct_Used_Crit situation . . 64
More information about Take Action commands . . 73
MS_SQL_DB_Space_Pct_Used_Warn situation . . 64
Predefined Take Action commands . . . . . . 73
MS_SQL_DB_Status_Critical situation . . . . 64
User ID and password combinations . . . . . 74
MS_SQL_DB_Suspect_Crit situation . . . . . 64
Database Check-up and Tune-up action . . . . 74
MS_SQL_Device_Free_PCT_Warning situation . . 65
Dump Database action . . . . . . . . . 75
MS_SQL_Error_Warning situation . . . . . . 65
Dump Transaction Log action . . . . . . . 78
MS_SQL_ErrorLog_Size_Warning situation . . . 65
Rebuild Fragmented Indexes action . . . . . 81
MS_SQL_Failed_Jobs_Crit situation . . . . . 65
Refresh Query Optimizer Statistics action . . . 83
MS_SQL_Fragmentation_Crit situation . . . . 65
Start SQL Server action . . . . . . . . . 84
MS_SQL_Fragmentation_Warn situation . . . . 65
Stop SQL Server action . . . . . . . . . 85
MS_SQL_IO_Disk_Errors_Crit situation . . . . 65
Update Space Usage Information action . . . . 85
MS_SQL_IOERR_Startup_Warning situation . . 65
MS_SQL_IOError_Curintvl_Warning situation . . 66
MS_SQL_Log_Freespace_Critical situation . . . 66 Chapter 8. Policies reference . . . . . 87
MS_SQL_Log_Freespace_Warning situation . . . 66 About policies . . . . . . . . . . . . . 87
MS_SQL_Log_Space_Pct_Used_Crit situation . . 66 More information about policies . . . . . . . 87
MS_SQL_Log_Space_Pct_Used_Warn situation . 66 Predefined policies . . . . . . . . . . . . 87
MS_SQL_Log_Suspend_Warning situation . . . 66 MS_SQL_DB_free_space_critical . . . . . . 87
MS_SQL_LogonPct_Crit situation . . . . . . 66
MS_SQL_LogonPct_Warning situation . . . . 67 Appendix A. Workspaces . . . . . . . 89
MS_SQL_Network_Read_Rate_Crit situation . . 67 Determining which category of workspaces to use 89
MS_SQL_Network_Read_Rate_Warn situation . . 67 Determining where to find the information you
MS_SQL_Network_Write_Rate_Crit situation . . 67 need . . . . . . . . . . . . . . . . . 89
MS_SQL_Network_Write_Rate_Warn situation . . 67 Displaying information for databases . . . . . . 90
MS_SQL_Num_Process_Blocked_Crit situation . 67 Determining the predefined workspace to use . . 90
MS_SQL_Num_Process_Blocked_Warn situation 67 Relationship to the attribute groups . . . . . 90
MS_SQL_Oldest_Transaction_Crit situation . . . 68 Example tasks and the predefined workspaces
MS_SQL_Oldest_Transaction_Warn situation . . 68 available . . . . . . . . . . . . . . 91
MS_SQL_Opt_Stats_Age_Crit situation . . . . 68 Typical scenarios . . . . . . . . . . . 91
MS_SQL_Opt_Stats_Age_Warn situation . . . . 68 Displaying information for error log alerts . . . . 92
MS_SQL_Pct_Block_Warning situation . . . . 68 Determining the predefined workspace to use . . 92
MS_SQL_Pct_CPU_Yields_Warning situation . . 68 Relationship to the attribute groups . . . . . 92
MS_SQL_Pct_IO_Warning situation . . . . . 68 Example tasks and the predefined workspaces
MS_SQL_PCT_MAX_Locks_Critical situation . . 69 available . . . . . . . . . . . . . . 92
MS_SQL_PCT_MAX_Locks_Warning situation . . 69 Typical scenarios . . . . . . . . . . . 93
MS_SQL_ProbAge_GT_17_Warning situation . . 69 Displaying information for locks . . . . . . . 94
MS_SQL_Proc_Buffs_Active_Crit situation . . . 69 Determining the predefined workspace to use . . 94
MS_SQL_Proc_Buffs_Active_Warn situation . . 69 Relationship to the attribute groups . . . . . 94
MS_SQL_Proc_Buffs_Used_Crit situation . . . 69 Example tasks and the predefined workspaces
MS_SQL_Proc_Buffs_Used_Warn situation . . . 69 available . . . . . . . . . . . . . . 94
MS_SQL_Proc_Cache_Active_Crit situation . . . 70 Typical scenarios . . . . . . . . . . . 95
MS_SQL_Proc_Cache_Active_Warn situation . . 70 Displaying information for processes . . . . . . 96
MS_SQL_Proc_Cache_Used_Crit situation . . . 70 Determining the predefined workspace to use . . 96
MS_SQL_Proc_Cache_Used_Warn situation . . . 70 Relationship to the attribute groups . . . . . 97
MS_SQL_Process_Blocked_Warning situation . . 70 Example tasks and the predefined workspaces
MS_SQL_Process_Infected_Warning situation . . 70 available . . . . . . . . . . . . . . 97
MS_SQL_ProcessLockSleep_Warning situation . . 70 Typical scenarios . . . . . . . . . . . 97
MS_SQL_ProcessOthSleep_Warning situation . . 71 Displaying information for Microsoft SQL servers 98
MS_SQL_Processes_Bad_Warning situation . . . 71 Determining the predefined workspace to use . . 98
MS_SQL_Processes_Stop_Warning situation . . 71 Relationship to the attribute groups . . . . . 99
MS_SQL_Rem_Serv_Stat_Critical situation . . . 71

iv IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Example tasks and predefined workspaces Procedure . . . . . . . . . . . . . 122
available . . . . . . . . . . . . . . 99 Problems and workarounds . . . . . . . . 123
Typical scenarios . . . . . . . . . . . 100 Installation and configuration problem
determination . . . . . . . . . . . . 124
Appendix B. IBM Tivoli Enterprise Agent problem determination . . . . . . . 128
Console event mapping . . . . . . . 103 Problem determination for remote deployment 128
Workspace problem determination . . . . . 129
Situation problem determination . . . . . . 130
Appendix C. Problem determination 115 Take Action command problem determination 134
Gathering product information for IBM Software Problem determination for SQL Server . . . . 135
Support . . . . . . . . . . . . . . . 115 Support information . . . . . . . . . . . 135
Built-in problem determination features . . . . 115 Searching knowledge bases . . . . . . . . 135
Problem classification . . . . . . . . . . . 116 Obtaining fixes . . . . . . . . . . . . 136
Trace logging . . . . . . . . . . . . . 116 Receiving weekly support updates . . . . . 136
Overview of log file management . . . . . 116 Contacting IBM Software Support . . . . . 137
Examples of trace logging . . . . . . . . 117
Principal trace log files . . . . . . . . . 117
Appendix D. Accessibility . . . . . . 139
Enabling detailed tracing in the collector trace log 120
Navigating the interface using the keyboard . . . 139
Option one: modify the settings file . . . . . 120
Magnifying what is displayed on the screen . . . 139
Option two: modify the environment variables 120
Setting RAS trace parameters . . . . . . . . 121
Objective . . . . . . . . . . . . . . 121 Appendix E. Notices . . . . . . . . 141
Background Information . . . . . . . . . 121 Trademarks . . . . . . . . . . . . . . 142
Before you begin . . . . . . . . . . . 121
After you finish . . . . . . . . . . . 121 Index . . . . . . . . . . . . . . . 145

Contents v
vi IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Tables
1. Requirements for Monitoring Agent for 26. Workspaces for processes and the relationship
Microsoft SQL Server. . . . . . . . . . 5 to attribute groups . . . . . . . . . . 97
2. Additional authorization . . . . . . . . 13 27. Example tasks and the predefined workspaces
3. Viewing real-time data about Microsoft SQL available for processes . . . . . . . . . 97
Server . . . . . . . . . . . . . . 15 28. Determining the workspace to use for servers 98
4. Investigating an event . . . . . . . . . 16 29. Workspaces for servers and the relationship to
5. Recovering the operation of a resource . . . 17 attribute groups . . . . . . . . . . . 99
6. Customizing your monitoring environment 17 30. Example tasks and predefined workspaces
7. Monitoring with custom situations . . . . . 19 available for servers . . . . . . . . . . 99
8. Collecting and viewing historical data . . . 20 31. Overview of event slots to event classes 104
9. Capacity planning for historical data . . . . 57 32. Information to gather before contacting IBM
10. User ID and password combinations . . . . 74 Software Support . . . . . . . . . . 115
11. Index and table updates . . . . . . . . 82 33. Trace log files for troubleshooting agents 118
12. Index and table updates . . . . . . . . 83 34. Problems and solutions for installation and
13. Index and table updates . . . . . . . . 86 configuration . . . . . . . . . . . 124
14. Determining which category of workspaces to 35. Problems and solutions for installation and
use . . . . . . . . . . . . . . . 89 configuration of the database agent . . . . 126
15. Determining where to find the information 36. General problems and solutions for
you need . . . . . . . . . . . . . 89 uninstallation . . . . . . . . . . . 127
16. Determining the workspace to use for 37. General agent problems and solutions 128
databases . . . . . . . . . . . . . 90 38. Remote deployment problems and solutions 129
17. Workspaces for databases and the relationship 39. Workspace problems and solutions . . . . 129
to attribute groups . . . . . . . . . . 90 40. Specific situation problems and solutions 130
18. Example tasks and the predefined workspaces 41. Sample frequency and collection limitation for
available for databases . . . . . . . . . 91 attribute groups . . . . . . . . . . . 131
19. Determining the workspace to use for error log 42. Problems with configuring situations that you
alerts . . . . . . . . . . . . . . . 92 solve in the Situation Editor . . . . . . 132
20. Workspaces for error log alerts and the 43. Problems with configuration of situations that
relationship to attribute groups . . . . . . 92 you solve in the Workspace area . . . . . 134
21. Example tasks and the predefined workspaces 44. Problems with configuration of situations that
available for error log alerts . . . . . . . 93 you solve in the Manage Tivoli Enterprise
22. Determining the workspace to use for locks 94 Monitoring Services window . . . . . . 134
23. Workspaces for locks and the relationship to 45. Take Action commands problems and
attribute groups . . . . . . . . . . . 94 solutions . . . . . . . . . . . . . 134
24. Example tasks and the predefined workspaces 46. SQL Server problems and solutions . . . . 135
available for locks . . . . . . . . . . 95
25. Determining the workspace to use for
processes . . . . . . . . . . . . . 96

© Copyright IBM Corp. 2005 vii

viii IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
About this guide
The IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent User’s Guide
provides information about installing and using IBM® Tivoli® Monitoring for
Databases: Microsoft® SQL Server.

Use the configuration chapter in this guide along with the IBM Tivoli Monitoring
Installation and Setup Guide to set up the software.

Use the information in this guide along with the IBM Tivoli Monitoring User’s Guide
to monitor Microsoft SQL Server.

Who should read this guide

This guide is for system administrators who install and use the Monitoring Agent
for Microsoft SQL Server to monitor and manage Microsoft SQL Server resources.

Readers should be familiar with the following topics:

v Tivoli Enterprise™ Portal interface
v IBM Tivoli Monitoring application software
v IBM Tivoli Enterprise Console® (optional)
v Microsoft SQL Server
v Microsoft Windows® operating systems

What this guide contains

This guide contains the following chapters:
v Chapter 1, “Overview of the Monitoring Agent for Microsoft SQL Server,” on
page 1
Provides an introduction to the Monitoring Agent for Microsoft SQL Server.
v Chapter 2, “Requirements and configuration for the monitoring agent,” on page
5
Provides requirements and configuration information specific to the Monitoring
Agent for Microsoft SQL Server.
v Chapter 3, “How to use the Monitoring Agent for Microsoft SQL Server,” on
page 15
Provides a list of tasks to achieve when using a monitoring agent, a list of
procedures for performing each task, and references for where to find
information about the procedures. After completing installation and
configuration and becoming familiar with the information in Chapter 1 of this
guide, use this chapter to see how you can use a monitoring agent.
v Chapter 4, “Workspaces reference,” on page 21
Provides an overview of workspaces, references to additional information about
workspaces, and descriptions of predefined workspaces in this monitoring agent.
v Chapter 5, “Attributes reference,” on page 27
Provides an overview of attributes, references to additional information about
attributes, descriptions of the attribute groups and attributes in this monitoring
agent, and disk space requirements for historical data.
v Chapter 6, “Situations reference,” on page 59

© Copyright IBM Corp. 2005 ix

 Provides an overview of situations, references to additional information about
situations, and descriptions of the predefined situations in this monitoring agent.
v Chapter 7, “Take Action commands reference,” on page 73
Provides detailed information about the Take Action commands, references to
additional information about Take Action commands, and descriptions of the
Take Action commands provided in this monitoring agent.
v Chapter 8, “Policies reference,” on page 87
Provides an overview of policies, references for detailed information about
policies, and descriptions of the predefined policies included in this monitoring
agent.
v Appendix A, “Workspaces,” on page 89
Provides additional information about the predefined workspaces provided with
this monitoring agent.
v Appendix B, “IBM Tivoli Enterprise Console event mapping,” on page 103
Provides an overview of the IBM Tivoli Enterprise Console event mapping
information for this monitoring agent.
v Appendix C, “Problem determination,” on page 115
Provides information about troubleshooting the various components of the
Monitoring Agent for Microsoft SQL Server, information about log files and
messages, and information about your options for obtaining software support.
v Appendix D, “Accessibility,” on page 139
Provides information about the accessibility features in the Monitoring Agent for
Microsoft SQL Server.
v Appendix E, “Notices,” on page 141
Provides IBM and Tivoli notices and trademark information as it applies to the
Monitoring Agent for Microsoft SQL Server.

Publications
This section lists publications relevant to the use of the Monitoring Agent for
Microsoft SQL Server. It also describes how to access these publications online and
how to order these publications.

Prerequisite publications
To use the information in this guide effectively, you must have some knowledge of
IBM Tivoli Monitoring products, which you can obtain from the following
documentation:
v IBM Tivoli Monitoring Administrator’s Guide
v IBM Tivoli Monitoring Installation and Setup Guide
v IBM Tivoli Monitoring Problem Determination Guide
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring
v IBM Tivoli Monitoring User’s Guide
v Introducing IBM Tivoli Monitoring Version 6.1.0

Related publications
The following documents also provide useful information:
v IBM Tivoli Enterprise Console Adapters Guide
v IBM Tivoli Enterprise Console Event Integration Facility User’s Guide
v IBM Tivoli Enterprise Console Reference Manual

x IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 v IBM Tivoli Enterprise Console Rule Developer’s Guide

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available at the following
Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

http://www.ibm.com/ibm/terminology

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

Ordering publications
You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755
v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli

publications.

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate most features of the graphical
user interface.

For additional information, see Appendix D, “Accessibility,” on page 139.

About this guide xi

Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education/

Support information
“Support information” on page 135 describes the following options for obtaining
support for IBM products:
v “Searching knowledge bases” on page 135
v “Obtaining fixes” on page 136
v “Contacting IBM Software Support” on page 137

Conventions used in this guide

This guide uses several conventions for special terms and actions, and operating
system-dependent commands and paths.

Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

Operating system-dependent variables and paths

The direction of the slash for directory paths might vary in this documentation. No
matter which type of slash you see in the documentation, use the following
guidelines for a slash:
v If using UNIX®, use a forward slash (/).
v If using Windows, use a backslash (\).

xii IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
The names of environment variables are not always the same in Windows and
UNIX. For example, %TEMP% in Windows is equivalent to $TMPDIR in UNIX.

For environment variables, use the following guidelines:

v If using UNIX, use $variable.
v If using Windows, use %variable%.

Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.

About this guide xiii

xiv IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 1. Overview of the Monitoring Agent for Microsoft
SQL Server
The Monitoring Agent for Microsoft SQL Server provides you with the capability
to monitor Microsoft SQL Server, and to perform basic actions with Microsoft SQL
Server. This chapter provides a description of the features, components, and
interface options for the Monitoring Agent for Microsoft SQL Server.

IBM Tivoli Monitoring overview

IBM Tivoli Monitoring is the base software for the Monitoring Agent for Microsoft
SQL Server. 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 do the following:

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 perform actions, schedule work, and automate manual tasks.

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. By
providing a consolidated view of your environment, the Tivoli Enterprise Portal
permits you to monitor and resolve performance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” on

page x for complete information about IBM Tivoli Monitoring and the Tivoli
Enterprise Portal.

Features of the Monitoring Agent for Microsoft SQL Server

The Monitoring Agent for Microsoft SQL Server 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 Monitoring Agent for Microsoft SQL Server 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 Monitoring Agent for Microsoft SQL Server, 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:

© Copyright IBM Corp. 2005 1

 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 Monitoring Agent for Microsoft
SQL Server helps you to monitor and to gather the consistent, accurate, and
timely information you need to effectively perform your job.

Components of Monitoring Agent for Microsoft SQL Server

After you install and set up the Monitoring Agent for Microsoft SQL Server, you
have an environment that contains the client, server, and monitoring agent
implementation for IBM Tivoli Monitoring that contains the following components:
v Tivoli Enterprise Portal client with a Java-based user interface for viewing and
monitoring your enterprise.
v Tivoli Enterprise Portal Server that is placed between the client and the Tivoli
Enterprise Monitoring Server and enables retrieval, manipulation, and analysis
of data from the monitoring agents.
v Tivoli Enterprise Monitoring Server, which acts as a collection and control point
for alerts received from the monitoring agents, and collects their performance
and availability data.
v Monitoring agent, Monitoring Agent for Microsoft SQL Server, installed on the
systems or subsystems that you want to monitor. This monitoring agent collects
and distributes data to a Tivoli Enterprise Portal Server.

IBM Tivoli Enterprise Console is an optional product, which acts as a central

collection point for events from a variety of sources, including those from other
Tivoli software applications, Tivoli partner applications, custom applications,
network management systems, and relational database systems. You can view
these events through the Tivoli Enterprise Portal (using the event viewer), and you
can forward events from IBM Tivoli Monitoring situations to the IBM Tivoli
Enterprise Console component.

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 browser client interface
The browser interface is automatically installed with Tivoli Enterprise

2 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Portal. To start Tivoli Enterprise Portal in your Internet browser, enter the
URL for a specific Tivoli Enterprise Portal browser client installed on your
Web server.
Tivoli Enterprise Portal desktop client interface
The desktop interface is a Java-based graphical user interface (GUI) on a
Windows or Linux® workstation.
IBM Tivoli Enterprise Console
Event management application
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.

Chapter 1. Overview of the Monitoring Agent for Microsoft SQL Server 3

4 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 2. Requirements and configuration for the monitoring
agent
This chapter contains information about the following topics and procedures
relevant to the installation and configuration of the Monitoring Agent for Microsoft
SQL Server:
v “Requirements for the monitoring agent”
v “Configuration settings for installing the monitoring agent” on page 6
v “Configuration settings for reconfiguring the monitoring agent” on page 8
v “Configuration settings and parameters for deploying monitoring across your
environments” on page 10
v “Granting permissions” on page 12

Requirements for the monitoring agent

In addition to the requirements described in the IBM Tivoli Monitoring Installation
and Setup Guide, the Monitoring Agent for Microsoft SQL Server has the
requirements listed in Table 1.
Table 1. Requirements for Monitoring Agent for Microsoft SQL Server
Operating system Windows
Operating system versions v Windows 2000 Server (32-bit)
v Windows 2000 Advanced Server (32-bit)
v Windows 2003 Server SE (32-bit)
v Windows 2003 Server EE (32-bit)
Application versions v MS SQL 7.0 Enterprise/Standard Edition Service Packs
2, 3, and 4 (32-bit)
v MS SQL Server 2000 Service Pack 3a and 4 (32-bit)
Memory v 32 MB RAM
v 150 MB virtual memory, plus 5 MB for each agent
instance
Disk space v Installation: 75 MB disk space (monitoring agent), 1 MB
(agent support files on the management server), 1 MB
(agent support files on the portal server)
v Agent depot 95 MB (agent deploy image on the
management server)
v Trace logging: 50 MB per agent instance
v Historical data disk space: see “Disk capacity planning
for historical data” on page 56.

© Copyright IBM Corp. 2005 5

 Table 1. Requirements for Monitoring Agent for Microsoft SQL Server (continued)
Operating system Windows
Other requirements v For remote administration, IBM Tivoli Monitoring:
Windows OS Agent must be installed and running.
v Grant permissions for Microsoft SQL Server
v SQL Server and Windows authentication mode
v This monitoring agent requires that the following
performance objects be enabled:
– System
– Process
– Thread
– Memory
– Physical Disk
– SQLServer:Buffer Manager
– SQLServer:General Statistics
– SQLServer:Locks
– SQLServer:Databases
– SQLServer:Cache Manager
– SQLServer:Memory Manager

If you have a named SQL Server instance, then the

″SQLServer″ will be replaced with
″MSSQL$instance_name″.

Configuration settings for installing the monitoring agent

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

After completing the steps to install the Monitoring Agent for Microsoft SQL
Server as described in the IBM Tivoli Monitoring Installation and Setup Guide,
″Installing monitoring agents,″ you configure the Monitoring Agent for Microsoft
SQL Server.

Configuring on your local system from the Manage Tivoli

Enterprise Monitoring Services window
See the IBM Tivoli Monitoring Installation and Setup Guide for the steps for using this
window.

Note: Enter only ASCII characters in these fields.

Server Name
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.

6 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Login SQL Server user ID to be used to connect to the SQL Server. See “Granting
permissions” on page 12 for more information.
Password
Password for the SQL Server user ID
Database Version
SQL Server version. Valid values are 7 (for SQL Server 7.0) and 8 (8 is for
SQL Server 2000).
Home Directory
Install directory for the SQL Server instance to be monitored. For example,
the default home directory path for the default SQL Server 2000 instance is
C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server
2000 instance has a default home directory path int the format C:\Program
Files\Microsoft SQL Server\MSSQL$instance_name, where instance_name is
the SQL Server instance name.
Error Log File
Location and name of the SQL Server Error Log For example, the default
error log path for the default SQL Server 2000 instance is C:\Program
Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL
Server 2000 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.

Configuring on your local system using the tacmd command

line
See the IBM Tivoli Monitoring Installation and Setup Guide for the complete tacmd
addSystem command.

Note: For the addSystem command, all properties are mandatory.

Use the following parameters for the -p | --properties parameter to configure the
Monitoring Agent for Microsoft SQL Server:
DBSETTINGS.db_sid=InstanceName
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
INSTANCE=InstanceName
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
DBSETTINGS.db_login=UserId
SQL Server user ID to be used to connect to the SQL Server. See “Granting
permissions” on page 12 for more information.

Chapter 2. Requirements and configuration for the monitoring agent 7

 DBSETTINGS.db_password=Password
Password for the SQL Server user ID
DBSETTINGS.db_ver=Version
SQL Server version. Valid values are 7 (for SQL Server 7.0) and 8 (8 is for
SQL Server 2000).
DBSETTINGS.db_home=HomeDirPath
Install directory for the SQL Server instance to be monitored. For example,
the default home directory path for the default SQL Server 2000 instance is
C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server
2000 instance has a default home directory path int the format C:\Program
Files\Microsoft SQL Server\MSSQL$instance_name, where instance_name is
the SQL Server instance name.
DBSETTINGS.db_errorlog=ErrorlogPath
Location and name of the SQL Server Error Log For example, the default
error log path for the default SQL Server 2000 instance is C:\Program
Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL
Server 2000 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.

Configuration settings for reconfiguring the monitoring agent

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

Ensure that the steps were completed to install the Monitoring Agent for Microsoft
SQL Server as described in the IBM Tivoli Monitoring Installation and Setup Guide,
″Installing monitoring agents,″ before configuring or reconfiguring the Monitoring
Agent for Microsoft SQL Server.

Reconfiguring on your local system from the Manage Tivoli

Enterprise Monitoring Services window
See the IBM Tivoli Monitoring Installation and Setup Guide for the steps for using this
window.
Server Name
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
Login SQL Server user ID to be used to connect to the SQL Server. See “Granting
permissions” on page 12 for more information.
Password
Password for the SQL Server user ID
Database Version
SQL Server version. Valid values are 7 (for SQL Server 7.0) and 8 (8 is for
SQL Server 2000).

8 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Home Directory
Install directory for the SQL Server instance to be monitored. For example,
the default home directory path for the default SQL Server 2000 instance is
C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server
2000 instance has a default home directory path int the format C:\Program
Files\Microsoft SQL Server\MSSQL$instance_name, where instance_name is
the SQL Server instance name.
Error Log File
Location and name of the SQL Server Error Log For example, the default
error log path for the default SQL Server 2000 instance is C:\Program
Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL
Server 2000 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.

Reconfiguring on your local system using the tacmd

command line
See the IBM Tivoli Monitoring Installation and Setup Guide for the complete tacmd
configureSystem command.

Note: For the configureSystem command, only the INSTANCE property is

mandatory. Also, for reconfiguration, one other property besides INSTANCE
must be specified.

Use the following parameters for the -p | --properties parameter to configure the
Monitoring Agent for Microsoft SQL Server:
DBSETTINGS.db_sid=InstanceName
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
INSTANCE=InstanceName
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
DBSETTINGS.db_login=UserId
SQL Server user ID to be used to connect to the SQL Server. See “Granting
permissions” on page 12 for more information.
DBSETTINGS.db_password=Password
Password for the SQL Server user ID
DBSETTINGS.db_ver=Version
SQL Server version. Valid values are 7 (for SQL Server 7.0) and 8 (8 is for
SQL Server 2000).

Chapter 2. Requirements and configuration for the monitoring agent 9

 DBSETTINGS.db_home=HomeDirPath
Install directory for the SQL Server instance to be monitored. For example,
the default home directory path for the default SQL Server 2000 instance is
C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server
2000 instance has a default home directory path int the format C:\Program
Files\Microsoft SQL Server\MSSQL$instance_name, where instance_name is
the SQL Server instance name.
DBSETTINGS.db_errorlog=ErrorlogPath
Location and name of the SQL Server Error Log For example, the default
error log path for the default SQL Server 2000 instance is C:\Program
Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL
Server 2000 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.

Configuration settings and parameters for deploying monitoring

across your environments
Use these settings to configure the Monitoring Agent for Microsoft SQL Server
when deploying this monitoring agent remotely as described in the IBM Tivoli
Monitoring Installation and Setup Guide.

Deploying the monitoring agent remotely from the Tivoli

Enterprise Portal
Use following settings for the Database Server Properties tab:
Database Server Instance Name
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
Database Server User Id
SQL Server user ID to be used to connect to the SQL Server in the
Database Server Instance Name field. See “Granting permissions” on page
12 for more information.
Password
Password for the SQL Server user ID
Database Server Version
SQL Server version. Valid values are 7 (for SQL Server 7.0) and 8 (8 is for
SQL Server 2000).
Database Server Home Directory Path
Install directory for the SQL Server instance to be monitored. For example,
the default home directory path for the default SQL Server 2000 instance is
C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server
2000 instance has a default home directory path int the format C:\Program
Files\Microsoft SQL Server\MSSQL$instance_name, where instance_name is
the SQL Server instance name.

10 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Database Server Error Log File
Location and name of the SQL Server Error Log For example, the default
error log path for the default SQL Server 2000 instance is C:\Program
Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL
Server 2000 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.

Use following settings for the Agent tab ″Run as″ information:
Use local system account
Select this setting.
Allow service to interact with desktop
Leave this check box clear.

Deploying the monitoring agent using the tacmd command

line
See the IBM Tivoli Monitoring Installation and Setup Guide for the complete tacmd
addSystem command.

Note: For the addSystem command, all properties are mandatory.

Use the -t |--type TYPE parameter to specify the Monitoring Agent for Microsoft
SQL Server that you are configuring: OQ

Use the following parameters for the -p | --properties parameter to configure the
Monitoring Agent for Microsoft SQL Server:
DBSETTINGS.db_sid=InstanceName
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
INSTANCE=InstanceName
Name of the SQL Server instance that is to be monitored. Use the
hostname if the SQL Server being monitored is the default instance;
otherwise use the instance name. For example, if the SQL Server instance
being monitored is the default SQL Server instance and the hostname is
popcorn, then enter popcorn in this field. If the SQL Server instance being
monitored is a named instance with the instance name of mysqlserver and
the hostname is popcorn, enter mysqlserver in this field. SQL Server 7.0
only supports a default SQL Server instance.
DBSETTINGS.db_login=UserId
SQL Server user ID to be used to connect to the SQL Server. See “Granting
permissions” on page 12 for more information.
DBSETTINGS.db_password=Password
Password for the SQL Server user ID
DBSETTINGS.db_ver=Version
SQL Server version. Valid values are 7 (for SQL Server 7.0) and 8 (8 is for
SQL Server 2000).

Chapter 2. Requirements and configuration for the monitoring agent 11

 DBSETTINGS.db_home=HomeDirPath
Install directory for the SQL Server instance to be monitored. For example,
the default home directory path for the default SQL Server 2000 instance is
C:\Program Files\Microsoft SQL Server\MSSQL. A named SQL Server
2000 instance has a default home directory path int the format C:\Program
Files\Microsoft SQL Server\MSSQL$instance_name, where instance_name is
the SQL Server instance name.
DBSETTINGS.db_errorlog=ErrorlogPath
Location and name of the SQL Server Error Log For example, the default
error log path for the default SQL Server 2000 instance is C:\Program
Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. A named SQL
Server 2000 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.

Example:

tacmd addSystem -t OQ -n Primary:MWD:NT -p DBSETTINGS.db_sid=MyServer

DBSETTINGS.db_login=sa DBSETTINGS.db_password=sapwd
DBSETTINGS.db_ver=8.0.194 "DBSETTINGS.db_home=c:\Program Files\Microsoft
SQL Server\MSSQL" "DBSETTINGS.db_errorlog=C:\Program Files\Microsoft SQL
Server\MSSQL\LOG\ERRORLOG" INSTANCE=MyServer

Granting permissions
Objective
To grant Microsoft SQL Server access to the Monitoring Agent for Microsoft SQL
Server.

Background information
This procedure includes creating a Microsoft SQL Server user ID for and granting
permission to the new user ID. This 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 being monitored.
– Server Roles: No special Server Role is required.
v Optional Authorization Roles: Each Take Action has a separate set of
authorization roles required for the SQL Server credentials pass to the Take
Action.
These authorities are listed for each Take Action in Chapter 7, “Take Action
commands reference,” on page 73. The following monitored attributes require
additional authorization for the SQL Server Id use to configure the MS SQL agent.
If you want to monitor any of these attributes, configure the SQL Server Id used
by the MS SQL agent with the corresponding authorization.

The following monitored attributes require additional authorization for the SQL
Server Id use to configure the MS SQL agent. If you want to monitor any of these
attributes, configure the SQL Server Id used by the MS SQL agent with the
corresponding authorization.

12 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 2. Additional authorization
Navigation item/
Attribute workspace/ view Situation Authorization
Table Detail attribute None predefined MS_SQL_Fragmentation Database Role: db_owner
group: All attributes in _Warn (for each database)
group MS_SQL_Fragmentation OR
_Crit Server Role: System
MS_SQL_Opt_Stats_Age Administrator
_Warn
MS_SQL_Opt_Stats_Age
_Crit
Server Detail attribute None predefined MS_SQL_Proc_Buffs_Active Database Role: db_owner
group: _Warn (on default database
Procedure Buffers Pct MS_SQL_Proc_Buffs_Active associated with the SQL
Active _Crit Server ID)
Procedure Buffer Pct Used MS_SQL_Proc_Buffs_Used OR
Procedure Buffers Total _Warn Server Role: System
Procedure Cache Pages MS_SQL_Proc_Buffs_Used Administrator
Procedure Cache Pct Used _Crit MS_SQL_Proc_Cache_
Procedure Cache Pct Active Active_Warn
MS_SQL_Proc_Cache_
Active_Crit
MS_SQL_Proc_Cache_Used
_Warn
MS_SQL_Proc_Cache_Used
_Crit
SQL Text v Server Locking/ Process None predefined Server Role: System
Holding Lock SQL Text/ Administrator
Process Holding Lock
v SQL Text Server
Locking/ SQL Text for
Process ID/ Blocking
Process
v SQL Text Server
Locking/ SQL Text for
Process ID/ Waiting
Process
v SQL Text Processes/ SQL
Text for Process ID/ SQL
Text

Required authorization role

Database administrator

Before you begin

Before beginning this procedure, perform the appropriate installation procedures in
the IBM Tivoli Monitoring Installation and Setup Guide.

When you finish

Start the Monitoring Agent for Microsoft SQL Server so you can begin using the
monitoring agent to monitor your Microsoft SQL Server application.

Procedure
1. Click Start → Programs → Microsoft SQL Server → Enterprise Manager to
display the SQL Server Enterprise Manager window.

Chapter 2. Requirements and configuration for the monitoring agent 13

 2. In the Tree tab, select Logins in the Security folder (Console Root → Microsoft
SQL Servers → SQL Server Group → WindowsName → Security → Logins).
3. Right-click Logins and select New Login.
4. In the General tab Name field, type the SQL Server user ID to be used to
connect to the SQL Server.
5. In the Authentication area, click SQL Server authentication.
6. Type a password in the Password field.
7. Click the Database Access tab.
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 database.
9. In Database Roles for database_name, check public to establish minimum
permission.

Note: If you are running a take action command, you might need additional
authority. See the Take Action command descriptions in Chapter 7,
“Take Action commands reference,” on page 73. Also see Table 2 on
page 13.
10. Click OK to display the Confirm Password window.
11. Retype the password you typed for the user ID.
12. Click OK to display the new user ID in the Logins list.

14 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 3. How to use the Monitoring Agent for Microsoft
SQL Server
After you have installed and configured the Monitoring Agent for Microsoft SQL
Server, you can begin using this monitoring agent to monitor your resources.

This chapter provides information about how to use the Monitoring Agent for
Microsoft SQL Server to perform the following tasks:
v “View real-time data about Microsoft SQL Server”
v “Investigate an event” on page 16
v “Recover the operation of a resource” on page 16
v “Customize your monitoring environment” on page 17
v “Monitor with custom situations that meet your requirements” on page 18
v “Collect and view historical data” on page 19

For each of these tasks, there is a list of procedures that you perform to complete
the task. For the procedures, there is a cross-reference to where you can find
information about performing that procedure. Information about the procedures is
located in subsequent chapters and appendixes of this user’s guide and in the IBM
Tivoli Monitoring documentation.

View real-time data about Microsoft SQL Server

After the Monitoring Agent for Microsoft SQL Server has been installed,
configured, and started, the monitoring agent begins monitoring.

Table 3 contains a list of the procedures for viewing the real-time data about
Microsoft SQL Server that the monitoring agent collects. The table also contains a
cross-reference to where you can find information about each procedure.
Table 3. Viewing real-time data about Microsoft SQL Server
Procedure Where to find information
View the hierarchy of your monitored IBM Tivoli Monitoring User’s Guide:
resources from a system point of view ″Navigating through workspaces″ (in
(Navigator view organized by operating ″Monitoring: real-time and event-based″
platform, system type, monitoring agents, chapter)
and attribute groups).
View the indicators of real or potential
problems with the monitored resources
(Navigator view).
View changes in the status of the resources IBM Tivoli Monitoring User’s Guide: ″Using
that are being monitored (Enterprise workspaces″ (in ″Monitoring: real-time and
Message Log view). event-based″ chapter)
View the status of the agents in the Chapter 4, “Workspaces reference,” on page
managed enterprise that you are monitoring 21 in this guide
(Monitoring Agent Status view).

© Copyright IBM Corp. 2005 15

 Table 3. Viewing real-time data about Microsoft SQL Server (continued)
Procedure Where to find information
View the number of times an event has been IBM Tivoli Monitoring User’s Guide: ″Using
opened for a situation during the past 24 workspaces″ (in ″Monitoring: real-time and
hours (Open Situations Count view). event-based″ chapter)

Chapter 4, “Workspaces reference,” on page

21 in this guide

Chapter 6, “Situations reference,” on page 59

in this guide
Manipulate the views in a workspace. IBM Tivoli Monitoring User’s Guide: ″Using
views″ (in ″Monitoring: real-time and
event-based″ chapter)

Investigate an event
When the conditions of a situation have been met, an event indicator is displayed
in the Navigator. When an event occurs, you want to obtain information about that
event so you can correct the conditions and keep your enterprise running
smoothly. The situation must be associated with a Navigator Item in order to
appear.

Table 4 contains a list of the procedures for investigating an event and a

cross-reference to where you can find information about each procedure.
Table 4. Investigating an event
Procedure Where to find information
Determine which situation raised the event IBM Tivoli Monitoring User’s Guide: ″Opening
and identify the attributes that have values the situation event workspace″ (in
that are contributing to the alert. ″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)

Chapter 4, “Workspaces reference,” on page

Review available advice. 21 in this guide

Appendix A, “Workspaces,” on page 89 in

this guide
Notify other users that you have taken IBM Tivoli Monitoring User’s Guide:
ownership of the problem related to an ″Acknowledging an situation event″ (in
event and are working on it. ″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)
Remove the event from the Navigator. IBM Tivoli Monitoring User’s Guide: ″Closing
the situation event workspace″ (in
″Monitoring: real-time and event-based″
chapter, ″Responding to alerts″ section)

Recover the operation of a resource

When you find out that a resource is not operating as desired, you can control it
manually or automatically using Take Action commands.

Table 5 on page 17 contains a list of the procedures for recovering the operation of
a resource and a cross-reference to where you can find information about each
procedure.

16 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table 5. Recovering the operation of a resource
Procedure Where to find information
Take an action on a resource manually. IBM Tivoli Monitoring User’s Guide:
v ″Other views″ (in ″Custom workspaces″
chapter, ″Workspace views″ section)
v ″Take action – Reflex automation″ (in
Situations for event-based monitoring″
chapter, ″Event-based monitoring
overview″ section)

Chapter 7, “Take Action commands

reference,” on page 73 in this guide
Take an action on a system condition IBM Tivoli Monitoring User’s Guide:
automatically by setting up a situation to ″Situations for event-based monitoring″
run a Take Action command. chapter
v ″Customizing a situation″
v ″Creating a situation″
v ″Specify an action to take″
v ″Distribute the situation″

Chapter 7, “Take Action commands

reference,” on page 73 in this guide
Take multiple actions on system conditions IBM Tivoli Monitoring User’s Guide: ″Policies
automatically using a policy. for automation″ chapter
v ″Creating a policy″
v ″Maintaining policies″
Take actions across systems, monitoring v ″Workflows window″
agents, or computers using a policy.
Chapter 8, “Policies reference,” on page 87 in
this guide

Customize your monitoring environment

You can change how your monitoring environment looks by creating new
workspaces with one or more views in it.

Table 6 contains a list of the procedures for customizing your monitoring

environment and a cross-reference to where you can find information about each
procedure.
Table 6. Customizing your monitoring environment
Procedure Where to find information
Display data in tables or charts (views) in IBM Tivoli Monitoring User’s Guide:
Tivoli Enterprise Portal. v ″Custom workspaces″
v ″Table and chart views″
Display an overview of changes in the status IBM Tivoli Monitoring User’s Guide: ″Message
of the situations for your monitored log view″ (in ″Situation event views:
resources (Message Log View). message log, situation event console,
graphic, and Tivoli Enterprise Console″
chapter)

Chapter 3. How to use the Monitoring Agent for Microsoft SQL Server 17
 Table 6. Customizing your monitoring environment (continued)
Procedure Where to find information
Specify which attributes to retrieve for a IBM Tivoli Monitoring User’s Guide: ″Creating
table or chart so you can retrieve only the custom queries″ (in ″Table and chart views″
data you want by creating custom queries. chapter)

Chapter 5, “Attributes reference,” on page 27

in this guide
Build links from one workspace to another. IBM Tivoli Monitoring User’s Guide:
v ″Link from a workspace″ (in ″Custom
workspaces″ chapter)
v ″Link from a table or chart″ (in ″Table and
chart views″ chapter)
Identify which predefined situations started IBM Tivoli Monitoring User’s Guide: ″What
running automatically when you started the the enterprise workspace shows″ (in
Tivoli Enterprise Monitoring Server. ″Monitoring: real-time and event-based″
chapter, ″Using workspaces″ section)

Chapter 6, “Situations reference,” on page 59

in this guide
Determine whether to run situations as Chapter 6, “Situations reference,” on page 59
defined, modify the values in situations, or in this guide
create new situations to detect possible
problems.

Monitor with custom situations that meet your requirements

When your environment requires situations with values that are different from
those in existing situations, or when you need to monitor conditions not defined
by the existing situations, you can create custom situations to detect problems with
resources in two ways:
v Create an entirely new situation
v Create a situation by copying and editing a predefined situation

Note: When you create and run a situation, an IBM Tivoli Enterprise Console
event is created. For information on how to define event severities from
forwarded IBM Tivoli Monitoring situations and other event information,
see the IBM Tivoli Monitoring Administrator’s Guide.

You can specify the following information for a situation:

v Name
v Attribute group and attributes
v Qualification to evaluate multiple rows when a situation has a multiple-row
attribute group (display item)
v Formula
v Take Action commands
v Run at startup
v Sampling interval
v Persistence
v Severity
v Clearing conditions

18 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 v Expert Advice
v When a true situation closes
v Available Managed Systems

Table 7 contains a list of the procedures for monitoring your resources with custom
situations that meet your requirements and a cross-reference to where you can find
information about each procedure.
Table 7. Monitoring with custom situations
Procedure Where to find information
Create an entirely new situation. IBM Tivoli Monitoring User’s Guide: ″Creating
a new situation″ (in ″Situations for
event-based monitoring″ chapter, ″Creating a
situation″ section)

Chapter 5, “Attributes reference,” on page 27

in this guide
Create a situation by copying and editing a IBM Tivoli Monitoring User’s Guide:
predefined situation. ″Customizing a situation″ (in ″Situations for
event-based monitoring″ chapter)

Chapter 6, “Situations reference,” on page 59

in this guide

Chapter 5, “Attributes reference,” on page 27

in this guide
Run a situation on a managed system. IBM Tivoli Monitoring User’s Guide:
″Situations for event-based monitoring″
chapter
v ″Associate situations with navigator
items″
v ″Distribute the situation″ (in ″Customizing
a situation″ section)
v ″Start, stop, or delete a situation″

Collect and view historical data

When you collect historical data, you specify the following configuration
requirements:
v Attribute groups for which to collect data
v Collection interval
v Summarization and pruning of attribute groups
v Roll-off interval to a data warehouse, if any
v Where to store the collected data (at the agent or the Tivoli Enterprise
Monitoring Server)

Table 8 on page 20 contains a list of the procedures for collecting and viewing
historical data and a cross-reference to where you can find information about each
procedure.

Chapter 3. How to use the Monitoring Agent for Microsoft SQL Server 19
 Table 8. Collecting and viewing historical data
Procedure Where to find information
Configure and start collecting short-term IBM Tivoli Monitoring User’s Guide:
data (24 hours). ″Historical reporting″ (in ″Table and chart
views″ chapter)
Configure and start collecting longer-term
data (more than 24 hours). IBM Tivoli Monitoring Administrator’s Guide
View historical data in the Tivoli Enterprise
Portal. “Disk capacity planning for historical data”
on page 56
Create reports from historical data using
third-party reporting tools.
Filter out unwanted data to see specific
areas of interest.

20 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 4. Workspaces reference
This chapter contains an overview of workspaces, references for detailed
information about workspaces, and descriptions of the predefined workspaces
included in this monitoring agent.

About workspaces
A workspace is the working area of the Tivoli Enterprise Portal application
window. At the left of the workspace is a Navigator that you use to select the
workspace you want to see.

As you select items in the Navigator, the workspace presents views pertinent to
your selection. Each workspace has at least one view. Some views have links to
workspaces. Every workspace has a set of properties associated with it.

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.

More information about workspaces

For more information about creating, customizing, and working with workspaces,
see the IBM Tivoli Monitoring User’s Guide.

For a list of the predefined workspaces for this monitoring agent and a description
of each workspace, refer to the Predefined workspaces section below and the
information in that section for each individual workspace.

For additional information about workspaces for this monitoring agent, see
Appendix A, “Workspaces,” on page 89.

Predefined workspaces
The Monitoring Agent for Microsoft SQL Server provides the following predefined
workspaces, which are organized by Navigator item:
v Databases Navigator item
– Databases Information
– Enterprise Database Summary
– Log and Space Information
v Errorlog Alerts Navigator item
– Enterprise Errorlog Alerts
– Errorlog Alerts
v Server Locking Navigator item
– Enterprise Server Locking
– Process Holding Lock SQL Text
– Server Locking
– SQL Text for Process ID
v Processes Navigator item

© Copyright IBM Corp. 2005 21

 – Enterprise Processes Summary
– Processes Information
– SQL Text for Process ID
v Servers Navigator item
– Enterprise Server Statistics
– Enterprise Server Summary
– Server Configuration
– Server Statistics
– Servers

The remaining sections of this chapter contain descriptions of each of these

predefined workspaces. The workspaces are organized by Navigator item.

Databases Navigator item

Databases Information workspace
Databases 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 free space
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 free space in the database
and log)

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 Summery 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 free space bar chart showing the percentage of freespace in the
database from the column in the Database Summary table view

Log and Space Information workspace

Log and Space Information is a predefined workspace that you access from the
Database Detail table view in the Databases Information workspace. The Log and
Space information workspace 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 free space for the database
and log)

22 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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)

Errorlog Alerts Navigator item

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

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)

Server Locking Navigator item

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)
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)

Process Holding Lock SQL Text workspace

Process Holding Lock SQL Text is a predefined workspace that you access from the
Lock Detail view of the Server Locking workspace. This workspace has the
following two views:
v Event Console table
v Process Holding Lock SQL Text table

This workspace 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.

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:

Chapter 4. Workspaces reference 23

 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)

SQL Text for Process ID workspace

SQL Text for Process ID is a predefined workspace that you access from the Lock
Conflict view of the Server Locking workspace. The SQL Text for Process ID
workspace displays information about the SQL text string for the selected process.
The predefined workspace contains the following views:
v Event Console table
v Blocking Process SQL Text table
v Waiting Process SQL Text table

Processes Navigator item

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 charts that displays the number of processes blocked by
locks

Processes Information 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)
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)

SQL Text for Process ID workspace

SQL Text for Process ID is a predefined workspace that you access from the
Process Detail table view of the Processes Information workspace. The SQL Text for
Process ID displays process information, including the SQL command, for the
blocking as well as the waiting processes. The predefined workspace contains the
following views:
v SQL Text table that displays detailed information about the SQL text strings
(such as the total CPU time)
v Event Console

24 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Servers Navigator item
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

Server Configuration workspace

Server Configuration is a predefined workspace that you access from the Server
Summary table view of the Server Summary workspace. The Server Configuration
workspace 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 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)

Servers workspace
Servers is a predefined workspace that displays an overview of the SQL server
activity for your environment. The predefined workspace contains the following
views:

Chapter 4. Workspaces reference 25

 v Server Summary table view that displays summary information about the SQL
servers (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)

26 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 5. Attributes reference
This chapter contains information about the following topics:
v Overview of attributes
v References for detailed information about attributes
v Descriptions of the attributes for each attribute group included in this
monitoring agent
v Disk space requirements for historical data

About attributes
Attributes are the application properties being measured and reported by the
Monitoring Agent for Microsoft SQL Server, such as the amount of memory usage
or the message ID.

Attributes are organized into groups according to their purpose. The attributes in a
group can be used in the following two ways:
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 Query editor to create a new query, modify an existing query, or
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 Tivoli Enterprise Portal compares the values
you have assigned to the situation attributes with the values collected by the
Monitoring Agent for Microsoft SQL Server and registers an event if the
condition is met. You are alerted to events by indicator icons that appear in the
Navigator.

Some of the attributes in this chapter are listed twice, with the second attribute
having a ″(Unicode)″ designation after the attribute name. These Unicode attributes
were created to provide access to globalized data. Use the globalized attribute
names because this is where the monitoring agent is putting the data. If you were
using a previous Candle® OMEGAMON® release of this monitoring agent, you
must run the Application Migration Tool to create globalized attributes for your
customized queries, situations, and policies. See the IBM Tivoli Monitoring
Installation and Setup Guide for more information.

More information about attributes

For more information about using attributes and attribute groups, see the IBM
Tivoli Monitoring 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 Attribute
groups and attributes section in this chapter.

© Copyright IBM Corp. 2005 27

Attribute groups and attributes for the Monitoring Agent for Microsoft
SQL Server
This monitoring agent contains the following attribute groups:
v Configuration
v Database Detail
v Database Summary
v Device Detail
v Lock Conflict Detail
v Lock Detail
v Lock Summary
v Problem Detail
v Problem Summary
v Process Detail
v Process Summary
v Remote Servers
v Server Detail
v Server Enterprise
v Server Summary
v Statistics Detail
v Statistics Summary
v Table Detail
v Text

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

Configuration attributes
The Microsoft SQL Configuration attribute group contains attributes that you can
use to monitor the configuration of an 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 specific
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 running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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.

28 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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.

Parm Type The type of configuration parameter. If the configuration parameter is

dynamic, a server restart is not required. The following values are valid:
Dynamic
Configuration parameter is dynamic.
Static Configuration parameter is static.

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 time stamp 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.

Server The name of the SQL server. The value format is an alphanumeric string
with a maximum of 30 characters; for example, CFS_SVR5.

Database Detail attributes

The Microsoft SQL Database Detail attribute group contains attributes that you can
use to monitor the performance and usage of databases.

Abort Tran On Log Full Specifies whether tran dump on log full is enabled: Yes
or No.

Data Freespace The number of megabytes (MB) of maximum available free space
for the database. The value includes the megabytes of free ″data only″ space. The
value format is a decimal number with two decimal places allowed; for example,
10.00.

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.

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.

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. The value format is an
alphanumeric string 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.

Chapter 5. Attributes reference 29

 Database Space Percent Used Reports 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.

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.

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.

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. The value format is an alphanumeric string with a maximum of 72 bytes;
for example, DBO. Use the create database command to establish this identifier.

DBO Only Access Indicates whether the database has a status of DBO only. The
following values are valid:
No Database can be access by authorized users.
Yes Database has a status of DBO only.

Dump Tran Date The time stamp that indicates the date and time the dump
transaction command was last executed for the database. This value does not
apply to MS SQL Server version 7. 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. The format is YY.MM.DD,
with the following valid values:
YY Year
MM Month
DD Day of week

For example, 02.05.01 indicates May 1, 2002.

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:
No Database does not have an error status.
Yes Database has an error status.

Free Space Accounting Suppresed Indicates whether the free space accounting
option is enabled 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:

30 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
No Free space accounting is enabled.
Yes Free space accounting is disabled.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

Log Freespace The number of megabytes (MB) of free space in the allocated
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, 7.00. Various types of transactions, such
as mass updates and bulk copying in can involve extensive logging.

Log Freespace Percent The percentage of free space in the allocated 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.

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, affect sizing. Evaluate the
need to truncate the transaction log to prevent it from filling up.

Log Space Percent Used Reports 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, and then spawn a task to dump or truncate the transaction log or to do
both.

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:
No No CKPT After Recovery option is disabled.
Yes No CKPT After Recovery option is enabled.

Oldest Open Transaction Reports 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.

Read Only Access Indicates whether the database has a status of read only. The
following values are valid:
No Database is read and write database.
Yes Database has a status of read-only.

Replicated Transaction Rate Reports 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.

Chapter 5. Attributes reference 31

 Replicated Transactions Reports 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.

Replication Latency Reports 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.

Sample Timestamp The time stamp 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.

Select Into Bulkcopy Enabled Indicates whether the select into/bulkcopy option is
enabled for the database. The following values are valid:
No Select Into/Bulkcopy option is disabled.
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:
No Database can be accessed by multiple users.
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.

Total Devices The number of devices allocated for the database. The value format
is an integer in the range 1-128; for example, 4.

Truncate Log on CKPT Specifies whether the database truncates the log on
checkpoint: Yes or No.

Suspect Database Reports whether a database is marked as suspect. Use this

attribute to warn you that a database cannot be loaded.

Database Summary attributes

The Microsoft 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 Monitoring Agent 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.

32 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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.

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.

Device Detail attributes

The Microsoft SQL Device Detail attribute group contains attributes that you can
use to monitor the usage and performance of devices.

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.

Database Name (Unicode) The Database name. The value format is an

alphanumeric string with a maximum of 384 bytes.

Device Free Space The number of megabytes (MB) of free space on a device that is
available for database file or transaction log file expansion. This number is
bounded by the maximum size configured for the database or log. The value

Chapter 5. Attributes reference 33

 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.

Device Free Space Percent The percentage of free space on the device. Refer to the
Device Free Space attribute description for additional information on the
calculation of a database or log file’s 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.

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. The value format is an alphanumeric
string 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. The size relates to the number of pages and is a multiple
of 512 megabytes. Use this value when analyzing the amount of free space.

Device Type Indicates the type of device allocated for the database. The following
values are valid:
Data only
Device stores data for the database.
Log only
Device stores the transaction log for the database.
Data and log
Device stores data and the transaction log for the database.

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 running the SQL server. The value format is
alphanumeric with a maximum of 64 characters; for example, Voyager.

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.

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. The value
format is an alphanumeric string with a maximum of 192 bytes.

34 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Sample Timestamp The time stamp 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.

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 Version The version of the SQL server. The value format is the version in
the format version.release; for example, 10.0.

Lock Conflict Detail attributes

The Microsoft 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. The value format is an
alphanumeric string with a maximum of 384 bytes.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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 time stamp 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.

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 ID of the server user. The value format is an alphanumeric string
with a maximum of 8 characters.

Chapter 5. Attributes reference 35

 Lock Detail attributes
The Microsoft 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.

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 database that is locked. The value
format is an alphanumeric string with a maximum of 384 bytes; for example, DB12.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

Lock Request Status Enumeration that identifies the Lock Request Status. The
following values are valid:
Converted
Converted value
Granted
Granted value
Waiting
Waiting value

Lock Resource Type Enumeration that identifies the Lock Resource Type. The
following values are valid:
Database
Database value
Extent Extent value
File File value
Index Index value
Key Key value
NULL NULL value
Resource
Resource value
Page Page value
RID RID value
Table Table value

Page Number The page number of the table being locked. The value format is an
integer.

Process Holding Lock The ID of the process holding the lock. The value format is
an integer.

Sample Timestamp The time stamp 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.

36 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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. The value format is an
alphanumeric string with a maximum of 384 bytes.

Type If the process is being blocked, indicates the type of lock on the resource that
is being requested. The following values are valid:
Excl intent lock
Exclusive intent lock
Excl page lock
Exclusive page lock
Excl tbl lock
Exclusive table lock
Shr intent lock
Shared intent lock
Shr page lock
Shared page lock
Shr tbl lock
Shared table lock
Unknown
Unknown type
Update page lock
Update page lock

Lock Summary attributes

The Microsoft SQL Lock Summary attribute group provides a summary of current
locks for each server.

Exclusive Extent Locks Number of granted Exclusive Extent locks. The format is
an integer.

Exclusive Intent Locks Number of granted Exclusive Intent locks. The format is an
integer.

Exclusive Locks Number of granted Exclusive locks. The format is an integer.

Exclusive Page Locks Number of granted Exclusive Page locks. The format is an
integer.

Exclusive Table Locks Number of granted Exclusive Table locks. The format is an
integer.

Extent Locks Number of granted Extent locks. The format is an integer.

Host Name Host on which SQL server resides. The value format is an
alphanumeric string with a maximum of 64 characters.

Chapter 5. Attributes reference 37

 Intent Locks Number of granted Intent locks. The format is an integer.

Page Locks Number of granted Page locks. The format is an integer.

Sample Timestamp The time when these data were collected.

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

Shared Intent Locks Number of granted Shared Intent locks. The format is an
integer.

Shared Locks Number of granted Shared locks. The format is an integer.

Shared Page Locks Number of granted Shared Page locks. The format is an
integer.

Shared Table Locks Number of granted Shared Table locks. The format is an
integer.

Table Locks Number of granted Table locks. The format is an integer.

Update Extent Locks Number of granted Update Extent locks. The format is an
integer.

Update Page Locks Number of granted Update Page locks. The format is an
integer.

Problem Detail attributes

The Microsoft 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.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

Hub Timestamp The time when this data was inserted at the hub.

Maximum Severity The maximum severity code encountered. The value format is
an alphanumeric string with a maximum of 2 characters.

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. The value format is an alphanumeric string with a
maximum of 120 characters.

38 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Message Text (Unicode) The message text. The value format is an alphanumeric
string with a maximum of 360 bytes.

Message Timestamp The time stamp that indicates the date and time the error
occurred.

Sample Timestamp The time stamp 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.

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. The following values are
valid:
10-16 User error
17-18 Software error or hardware error
19-24 System error

Example: 12.

SQL State Code The SQL state value for the error message. The value format is an
integer; for example, 37.

Problem Summary attributes

The Microsoft 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 the Monitoring Agent 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 running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

Maximum Sev CurrentInterval 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 time stamp that indicates the date and time the
error message with the highest severity level occurred.

Chapter 5. Attributes reference 39

 Sample Timestamp The time stamp 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.

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.

Process Detail attributes

The Microsoft 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.

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 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.

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.

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.

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.

Command (Unicode) The name of the executing command. The value format is an
alphanumeric string with a maximum of 48 bytes.

Current CPU Percent Used The percentage of CPU time the process is using on
the operating system. The value format is a percentage with two decimal places

40 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
allowed; for example, 80.00. This dynamic information is from the sysprocesses
table. Set alerts for processes using an abnormal amount of CPU.

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. The value format is an

alphanumeric string with a maximum of 384 bytes.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

Login Name The name of the process. The value format is an alphanumeric string
with a maximum of 30 characters.

OS Process ID The ID the operating system assigned to the process. The value
format is an alphanumeric string with a maximum of 10 characters; for example,
35427. This value is from the sysengines table.

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 valid:
Alarm sleep
Process is waiting for an alarm.
Background
Process is an MS 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.

Chapter 5. Attributes reference 41

 Example: send sleep.

Program Name The name of the program (front-end module) for the process. The
value format is an alphanumeric string with a maximum of 8 characters; for
example, ISQL.

Program Name (Unicode) The Program Name. The value format is an

alphanumeric string with a maximum of 48 bytes.

Sample Timestamp The time stamp 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.

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 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.

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.

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.

Total Memory Alloc KB The number of kilobytes (KB) of memory allocated for the
process. The value format is an integer; for example, 500.

Process Summary attributes

The Microsoft 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 Monitoring Agent 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 running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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.

42 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
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, or send sleep. 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 includes processes with a status of alarm sleep, lock sleep, recv sleep, or
send 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 time stamp 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.

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.

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.

Chapter 5. Attributes reference 43

 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.

Remote Servers attributes

The Microsoft 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 Monitoring Agent 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 running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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.

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 following values
are valid:
0 The remote SQL server connection times out if inactive for 1 minute.
1 The remote SQL server connection does not time out.
2 The remote SQL server uses network password encryption.

Sample Timestamp The time stamp 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.

Server The name of the SQL server. The value format is an alphanumeric string
with a maximum of 30 characters; for example, CFS_SVR5.

44 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Server Detail attributes
The Microsoft 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. This value is a configuration parameter.

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.

Error Log Name (Unicode) 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 192
bytes; 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.

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 running the SQL server. The value format is
alphanumeric with a maximum of 64 characters; for example, Voyager.

Max Locks Allowed The greatest value per second for the statistic since the SQL
server was started. The value format is an integer; for example, 2000. This value is
a configuration parameter.

OS Type The operating system for the SQL server. The value format is an
alphanumeric string; for example, AIX®.

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 Reports 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 Reports 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.

Chapter 5. Attributes reference 45

 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 Reports 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 Reports 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 The percentage of cache memory the SQL server uses for
the procedure cache. This value does not apply to MS SQL Server version 7. The
value format is a percentage with two decimal places allowed; for example, 20.00.

Procedure Cache Percent Active Reports the percentage of the procedure cache
that has currently executing procedures in it. 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 Cache Percent Used Reports 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.

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.

Sample Timestamp The time stamp 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.

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 following values are
valid:
Active SQL server is active.
Inactive
SQL server is not active.
Unknown
SQL server status is unknown.

Example: Active

Server Type The type of SQL server. The value format is an alphanumeric string;
for example, SQL Server.

46 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Server Version The version of the SQL server. The value format is the version in
the format version.release; for example, 10.0.

Startup Timestamp The time stamp that indicates the date and time the SQL
server was started.

Server Enterprise attributes

The Microsoft SQL Enterprise 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.

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 valid:
Active Data collector is active.
Inactive
Data collector is inactive.

Current Logons The number of logons and connections that are currently active.
The value format is an integer.

Database Max blocks The name of the database blocking the largest number of
processes. The value format is an alphanumeric string with a maximum of 32
characters.

Database Max blocks (Unicode) The name of the database blocking the largest
number of processes. The value format is an alphanumeric string with a maximum
of 384 bytes.

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.

Database Max Locks (Unicode) The name of the database with largest number of
locks. The value format is an alphanumeric string with a maximum of 384 bytes.

Error Log Size The size in bytes of the error log. The value format is an integer.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

IO Errors Current Interval The number of disk errors in the current interval. The
value format is an integer.

Maximum Sev Level The highest severity level of an error message since startup.
The following values are valid:
10-16 User error
17-18 Software error or hardware error
19-24 System error

Maximum Sev Timestamp The time stamp of the of the error message with the
highest severity level since startup.

Chapter 5. Attributes reference 47

 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 the log. The
value format is a decimal number 0.00 through 100.00.

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.

Percent Max Logons Active The percentage of the maximum user connections that
are currently active. The value is format is a decimal number in the range 0.00 to
100.00.

Percent Process Block The percentage of total processes in conflict. The value
format is a decimal number in the 0.00 through 100.00.

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.

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.

Sample Timestamp The time stamp 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.

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 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 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.

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.

Server Status Indicates the status of the SQL server. The following values are
valid:
Active SQL server is active.
Inactive
SQL server is not active.

48 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Unknown
SQL server status is unknown.

Server Version The version of the SQL server. The value format is the version in
the format version.release; for example, 10.0.

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 the largest number of
locks. The value format is an alphanumeric string with a maximum of 384 bytes.

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 Databases The number of databases for the SQL server. The value format is
an integer; for example, 10.

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.

Total Lock Conflicts The total number of processes involved in lock conflicts. The
value format is an integer.

Total Locks The total number of locks for the server. 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 Processes The total number of processes. The value format is an integer.

Total Processes Blocked The total number of processes blocked. The value format
is an integer.

Server Summary attributes

The Microsoft SQL Server Summary attribute group contains attributes that you
can use to monitor summary information for SQL servers.

Cache Average Free Scan Reports 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 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 Reports 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.

Cache Hit Ratio Reports 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 should be approximately 95% or greater. The value format is an
integer.

Chapter 5. Attributes reference 49

 Cache Maximum Free Page Scan Reports 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.

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 valid:
Active Data collector is active.
Inactive
Data collector is inactive.

CPU Percent Idle Reports 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.

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 Monitoring Agent 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.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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.

Sample Timestamp The time stamp 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.

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 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 CPU Pct IO Reports the percentage of time used for I/O operations during
the current monitoring interval. Use this attribute to gauge how much of the CPU

50 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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 Status Indicates the status of the SQL server. The following values are
valid:
Active SQL server is active.
Inactive
SQL server is not active.
Unknown
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 version.release; for example, 10.0.

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.

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 Reports 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 Reports the total number of locks that can still be taken
out. The maximum number of locks is configurable. In Microsoft SQL Server
Version 7.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.

Statistics Detail attributes

The Microsoft SQL Statistics Detail attribute group contains attributes that you can
use to monitor detailed information about SQL server statistics.

Chapter 5. Attributes reference 51

 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 running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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.

Sample Timestamp The time stamp 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.

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.

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.

Statistics Summary attributes

The Microsoft SQL Statistics Summary attribute group contains attributes that you
can use to monitor summary information about SQL server statistics.

Client Count Reports 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 Reports 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.

52 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
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 running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

IO Errors Current 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.

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 Reports 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 Reports 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.

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 Reports the current number of user

connections as a percentage of the available number of 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 time stamp 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.

Chapter 5. Attributes reference 53

 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 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 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.

Table Detail attributes

The Microsoft 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.

Database Name The Database name. The value format is an alphanumeric string
with a maximum of 384 bytes.

Fragmentation Reports 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 a percentage with two decimal
places allowed.

Host Name Host on which SQL server resides. The value format is an
alphanumeric string with a maximum of 64 characters.

Optimizer Statistics Age Reports 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.

Index Name The table index name. The value format is an alphanumeric string
with a maximum of 384 characters.

Index ID ID number of this table index.

Sample Timestamp The time when these data were collected.

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

Space Used Reports 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.

Table Id ID number of this table. The format is an integer.

54 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table Name The Table name. The value format is an alphanumeric string with a
maximum of 384 bytes.

Text attributes
The Microsoft SQL Text attribute group contains attributes that you can use to
monitor information about SQL text strings associated with a selected process.

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. The value format is an

alphanumeric string with a maximum of 384 bytes.

Host Name The name of the computer running the SQL server. The value format is
an alphanumeric string with a maximum of 64 characters; for example, Voyager.

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 valid:
Alarm sleep
Process is waiting for an alarm.
Background
Process is a MS 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.

Chapter 5. Attributes reference 55

 Send sleep
Process is waiting on a network send.

Sample Timestamp The time stamp 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.

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. The value format is an alphanumeric
string with a maximum of 2048 bytes.

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.

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 9 on page 57 provides the following
information required to calculate disk space for the Monitoring Agent for Microsoft
SQL Server:
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.
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.

56 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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 9. Capacity planning for historical data
Bytes per
Bytes per Bytes per summarized
Attribute DB table instance instance instance Expected number of
Group name (agent) (warehouse) (warehouse) instances
Configuration KOQSCFG 313 310 347 43 rows for each
monitored SQL Server
instance
Database KOQDBD 823 954 1567 1 row for each database
Detail in each monitored SQL
Server instance
Database KOQDBS 266 292 563 1 row per monitored
Summary SQL Server instance
Device KOQDEVD 1416 1463 1653 1 row for each device
Detail for each database data file
plus one row for each
device for each database
transaction log file
for each monitored SQL
Server instance
Lock KOQLOCK 678 681 718 1 row for each lock
Conflict conflict in each monitored
Detail SQL Server instance
Lock KOQLOCKS 1078 1087 1124 1 row for each lock
Detail in each monitored SQL
Server instance
Lock KOQLOKSU 288 294 916 1 row per monitored
Summary SQL Server instance
Problem KOQPROBD 756 759 796 1 row for each SQL
Detail Server message in each
monitored SQL Server
instance
Problem KOQPROBS 278 281 441 1 row per monitored
Summary SQL Server instance
Process KOQPRCD 906 945 1138 1 row for each database
Detail process in each monitored
SQL Server instance
Process KOQPRCS 302 421 1229 1 row per monitored
Summary SQL Server instance
Remote KOQSRVR 284 281 318 1 row for each remotely
Servers connected server connected
to each monitored SQL
Server instance
Server KOQSRVD 600 685 1277 1 row per monitored
Detail SQL Server instance
Server KOQSRVS 338 423 1054 1 row per monitored
Summary SQL Server instance

Chapter 5. Attributes reference 57

Table 9. Capacity planning for historical data (continued)
Bytes per
Bytes per Bytes per summarized
Attribute DB table instance instance instance Expected number of
Group name (agent) (warehouse) (warehouse) instances
Statistics KOQSTATD 280 289 431 10 rows for each
Detail monitored SQL Server
instance
Statistics KOQSTATS 302 421 1166 1 row per monitored
Summary SQL Server instance
Table KOQTBLD 1404 1440 1618 1 row per table index
Detail for every database in each
monitored SQL Server
instance

For more information about historical data collection, see the IBM Tivoli Monitoring
Administrator’s Guide.

58 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 6. 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 situations from the Tivoli Enterprise Portal by using the Situation editor.

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 Monitoring Agent for Microsoft SQL Server. 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
Monitoring Agent for Microsoft SQL Server 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.

© Copyright IBM Corp. 2005 59

 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.

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, refer to the Predefined situations section below and the
information in that section 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

60 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
v MS_SQL_IOError_Curintvl_Warning
v MS_SQL_Log_Freespace_Critical
v MS_SQL_Log_Freespace_Warning
v MS_SQL_Log_Space_Pct_Used_Crit
v MS_SQL_Log_Space_Pct_Used_Warn
v MS_SQL_Log_Suspend_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_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 6. Situations reference 61

 The remaining sections of this chapter contain descriptions of each of these
predefined situations. The situations are organized alphabetically.

MS_SQL_Block_Critical situation
Declares a critical condition if the number of processes in conflict is greater than
60.

This situation has the following formula:

Total Lock Conflicts GE 60

MS_SQL_Block_Warning situation
Declares a warning condition if the number of processes in conflict is greater than
or equal to 20 and less than 60.

This situation has the following formula:

(Total Lock Conflicts GE 20) AND
(Total Lock Conflicts LT 60)

MS_SQL_Cache_Ave_FreePage_Crit situation
Average number of cache buffers scanned to find that a free buffer exceeds the
critical threshold

This situation has the following formula:

Cache Average Free Scan GT 15

MS_SQL_Cache_Ave_FreePage_Warn situation
Average number of cache buffers scanned to find that a free buffer exceeds the
warning threshold

This situation has the following formula:

(Cache Average Free Scan GT 10) AND
(Cache Average Free Scan LE 15)

MS_SQL_Cache_Hit_Ratio_Crit situation
Ratio of data cache hits to total data requests exceeds the critical threshold

This situation has the following formula:

Cache Hit Ratio LT 70

MS_SQL_Cache_Hit_Ratio_Warn situation
Ratio of data cache hits to total data requests exceeds the warning threshold

This situation has the following formula:

(Cache Hit Ratio LT 90) AND
(Cache Hit Ratio GE 70)

MS_SQL_Cache_Max_FreePage_Crit situation
Maximum number of cache buffers scanned to find that a free buffer exceeds the
critical threshold

This situation has the following formula:

Cache Maximum Free Page Scan GT 15

62 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
MS_SQL_Cache_Max_FreePage_Warn situation
Maximum number of cache buffers scanned to find that a free buffer exceeds the
warning threshold

This situation has the following formula:

(Cache Maximum Free Page Scan GT 5) AND
(Cache Maximum Free Page Scan LE 15)

MS_SQL_Client_Cnt_Pct_Used_Crit situation
Percentage of client licenses being used exceeds the critical threshold

This situation has the following formula:

Client Count Percent Used GT 90

MS_SQL_Client_Cnt_Pct_Used_Warn situation
Percentage of client licenses being used exceeds the warning threshold

This situation has the following formula:

(Client Count Percent Used GT 70) AND
(Client Count Percent Used LE 90)

MS_SQL_Collection_Status_Warning situation
Declares a warning condition if the status of the collector is not Active.

This situation has the following formula:

Collection Status NE ’Active’

MS_SQL_CPU_Critical situation
Declares a critical condition if the percentage of CPU usage is greater than or equal
to 80.

This situation has the following formula:

Total OS CPU Percent GE 80.00 AND
Time Since Startup (Min.) GE 10

MS_SQL_CPU_Warning situation
Declares a warning condition if the percentage of CPU usage is greater than or
equal to 60 and less than 80.

This situation has the following formula:

Total OS CPU Percent GE 60.00 AND
Total OS CPU Percent LT 80.00 AND
Time Since Startup (Min.) GE 10

MS_SQL_DB_Error_Status situation
Provides an alert if the database has a serious error.

This situation has the following formula:

Error Status EQ ’Yes’

Chapter 6. Situations reference 63

 MS_SQL_DB_FreeSpace_Critical situation
Declares a critical condition if the percentage of free space on the database is less
than or equal to 10.

This situation has the following formula:

Minimum Pct Data free space LE 10.00

MS_SQL_DB_FreeSpace_Warning situation
Declares a warning condition if the percentage of free space in the database is less
than or equal to 20 and greater than 10.

This situation has the following formula:

Minimum Pct Data free space GT 10.00 AND
Minimum Pct Data free space LE 20.00

MS_SQL_DB_Num_Errors_Warning situation
Declares a warning condition if the number of databases with an error status is
greater than 0.

This situation has the following formula:

Total DBs in Error GT 0

MS_SQL_DB_Space_Pct_Used_Crit situation
Percentage of space used in the database compared to the total space allowed
exceeds the critical threshold

This situation has the following formula:

Database Space Percent Used GT 90

MS_SQL_DB_Space_Pct_Used_Warn situation
Percentage of space used in the database compared to the total space allowed
exceeds the warning threshold

This situation has the following formula:

(Database Space Percent Used GT 70) AND
(Database Space Percent Used LE 90)

MS_SQL_DB_Status_Critical situation
Database is unavailable because of an error or being taken offline

This situation has the following formula:

Database Status NE "AVAILABLE"

MS_SQL_DB_Suspect_Crit situation
A database is in an inconsistent state because it cannot be restored.

This situation has the following formula:

Suspect Database EQ "TRUE"

64 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
MS_SQL_Device_Free_PCT_Warning situation
Declares a warning condition if the percentage of free space on the device is less
than or equal to 10.

This situation has the following formula:

Device Free Space Percent LE 10.00

MS_SQL_Error_Warning situation
Declares a warning condition if the number of SQL Server errors during the
current interval is greater than 0.

This situation has the following formula:

Total Errors High Sev GT 0

MS_SQL_ErrorLog_Size_Warning situation
Declares a warning condition if the error log size is greater than or equal to 10000
bytes

This situation has the following formula:

Error Log Size (Bytes) GE 10,000

MS_SQL_Failed_Jobs_Crit situation
Number of jobs run by the SQLServerAgent service that have failed over the last
monitoring interval has exceeded the critical threshold

This situation has the following formula:

SQLServerAgent Failed Jobs GT 0

MS_SQL_Fragmentation_Crit situation
Percentage of fragmentation exceeds the critical threshold

This situation has the following formula:

Fragmentation GT 80

MS_SQL_Fragmentation_Warn situation
Percentage of fragmentation exceeds the warning threshold

This situation has the following formula:

(Fragmentation GT 30) AND
(Fragmentation LE 80)

MS_SQL_IO_Disk_Errors_Crit situation
Number of SQL Server read/write disk errors exceeds the critical threshold

This situation has the following formula:

(Statistic Name EQ ’io errors’) AND
(Current Value GT 0)

MS_SQL_IOERR_Startup_Warning situation
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 is greater than or equal to 5.

Chapter 6. Situations reference 65

 This situation has the following formula:
IO Errors Since Startup GE 10 AND
Pct IO Errors Cur Intvl GE 5.00

MS_SQL_IOError_Curintvl_Warning situation
Declares a warning condition if the percentage of IO errors during the current
interval is greater than or equal to 80.

This situation has the following formula:

IO Errors Current Interval GE 80

MS_SQL_Log_Freespace_Critical situation
Declares a critical condition if the percentage of free space in the log is less than or
equal to 10.

This situation has the following formula:

Minimum Pct Log free space LE 10.00

MS_SQL_Log_Freespace_Warning situation
Declares a warning condition if the percentage of free space in the log is less than
or equal to 10.

This situation has the following formula:

Minimum Pct Log free space GT 10.00 AND
Minimum Pct Log free space LE 20.00

MS_SQL_Log_Space_Pct_Used_Crit situation
Percentage of space used by the transaction log compared to the total allocated
transaction log size exceeds the critical threshold

This situation has the following formula:

Log Space Percent Used GT 90

MS_SQL_Log_Space_Pct_Used_Warn situation
Percentage of space used by the transaction log compared to the total allocated
transaction log size exceeds the warning threshold

This situation has the following formula:

(Log Space Percent Used GT 70) AND
(Log Space Percent Used LE 90)

MS_SQL_Log_Suspend_Warning situation
Declares a warning condition if the number of processes in log suspend is greater
than or equal to 1.

This situation has the following formula:

Total Log Suspend GE 1

MS_SQL_LogonPct_Crit situation
Number of current user connections as a percentage of the available user
connections has exceeded the critical threshold

66 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 This situation has the following formula:
Pct Max Logons Active GT 90

MS_SQL_LogonPct_Warning situation
Declares a warning condition if the percentage of active logins is greater than or
equal to 90.

This situation has the following formula:

Pct Max Logons Active GE 90.00

MS_SQL_Network_Read_Rate_Crit situation
Rate (packets per second) of Tabular Data Stream (TDS) packets being read from
the network exceeds the critical threshold

This situation has the following formula:

Network Read Rate GT 150

MS_SQL_Network_Read_Rate_Warn situation
Rate (packets per second) of Tabular Data Stream (TDS) packets being read from
the network exceeds the warning threshold

This situation has the following formula:

(Network Read Rate GT 50) AND
(Network Read Rate LE 150)

MS_SQL_Network_Write_Rate_Crit situation
Rate (packets per second) of Tabular Data Stream (TDS) packets being written from
the network exceeds the warning threshold

This situation has the following formula:

Network Write Rate GT 150

MS_SQL_Network_Write_Rate_Warn situation
Rate (packets per second) of Tabular Data Stream (TDS) packets being written from
the network exceeds the warning threshold

This situation has the following formula:

(Network Write Rate GT 50) AND
(Network Write Rate LE 150)

MS_SQL_Num_Process_Blocked_Crit situation
Number of blocked processes exceeds the critical threshold

This situation has the following formula:

Total Processes Blocked GT 10

MS_SQL_Num_Process_Blocked_Warn situation
Number of blocked processes exceeds the warning threshold

This situation has the following formula:

(Total Processes Blocked GT 2) AND
(Total Processes Blocked LE 10)

Chapter 6. Situations reference 67

 MS_SQL_Oldest_Transaction_Crit situation
Age (in minutes) of the oldest transaction in the database transaction log exceeds
the critical threshold

This situation has the following formula:

Oldest Open Transaction GT 15

MS_SQL_Oldest_Transaction_Warn situation
Age (in minutes) of the oldest transaction in the database transaction log exceeds
the warning threshold

This situation has the following formula:

(Oldest Open Transaction GT 5) AND
(Oldest Open Transaction LE 15)

MS_SQL_Opt_Stats_Age_Crit situation
Time (in minutes) since the table statistics were last updated exceeds the critical
threshold

This situation has the following formula:

Optimizer Statistics Age GT 1440

MS_SQL_Opt_Stats_Age_Warn situation
Time (in minutes) since the table statistics were last updated exceeds the warning
threshold

This situation has the following formula:

(Optimizer Statistics Age GT 180) AND
(Optimizer Statistics Age LE 1440)

MS_SQL_Pct_Block_Warning situation
Declares a warning condition if the percentage of processes in conflict is greater
than 50.

This situation has the following formula:

Percent Process Block GE 50.00

MS_SQL_Pct_CPU_Yields_Warning situation
Declares a warning condition if the percentage of CPU yields is greater than 75.

This situation has the following formula:

Current CPU Pct Used GT 75.00

MS_SQL_Pct_IO_Warning situation
Declares a warning condition if the percentage of time spent for IO operations is
greater than or equal to 90.

This situation has the following formula:

Total OS IO Pct Busy GE 90.00

68 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
MS_SQL_PCT_MAX_Locks_Critical situation
Declares a critical condition if the number of locks reaches or exceeds 80 percent of
the maximum locks allowed.

This situation has the following formula:

Pct Max Locks GE 80.00

MS_SQL_PCT_MAX_Locks_Warning situation
Declares a warning condition if the number of locks ranges from 60 to 80 percent
of the maximum locks allowed.

This situation has the following formula:

Pct Max Locks GE 60.00 AND
Pct Max Locks LT 80.00

MS_SQL_ProbAge_GT_17_Warning situation
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.

This situation has the following formula:

Age of Last Error (Min.) GE 30 AND
Maximum Sev Current Interval GE ’17’

MS_SQL_Proc_Buffs_Active_Crit situation
Percentage of active procedure buffers (buffers containing procedures actively
being executed) to total available procedure buffers exceeds the critical threshold

This situation has the following formula:

Procedure Buffers Active LT 75

MS_SQL_Proc_Buffs_Active_Warn situation
Percentage of active procedure buffers (buffers containing procedures actively
being executed) to total available procedure buffers exceeds the warning threshold

This situation has the following formula:

(Procedure Buffers Active LT 95) AND
(Procedure Buffers Active GE 75)

MS_SQL_Proc_Buffs_Used_Crit situation
Percentage of used procedure buffers to total available procedure buffers exceeds
the critical threshold

This situation has the following formula:

Procedure Buffers Used LT 75

MS_SQL_Proc_Buffs_Used_Warn situation
Percentage of used procedure buffers to total available procedure buffers exceeds
the warning threshold

This situation has the following formula:

(Procedure Buffers Used LT 95) AND
(Procedure Buffers Used GE 75)

Chapter 6. Situations reference 69

 MS_SQL_Proc_Cache_Active_Crit situation
Percentage of the procedure buffer cache with currently executing procedures
exceeds the critical threshold

This situation has the following formula:

Procedure Cache Active LT 75

MS_SQL_Proc_Cache_Active_Warn situation
Percentage of the procedure buffer cache with currently executing procedures
exceeds the warning threshold

This situation has the following formula:

(Procedure Cache Active LT 95) AND
(Procedure Cache Active GE 75)

MS_SQL_Proc_Cache_Used_Crit situation
Percentage of the procedure buffer cache with procedures in it exceeds the critical
threshold

This situation has the following formula:

Procedure Cache Used LT 75

MS_SQL_Proc_Cache_Used_Warn situation
Percentage of the procedure buffer cache with procedures in it exceeds the warning
threshold

This situation has the following formula:

(Procedure Cache Used LT 95) AND
(Procedure Cache Used GE 75)

MS_SQL_Process_Blocked_Warning situation
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.

This situation has the following formula:

Percent Processes Blocked GE 25.00
Total Processes Blocked GE 5

MS_SQL_Process_Infected_Warning situation
Declares a warning condition if the number of infected processes is greater than or
equal to 1.

This situation has the following formula:

Total Processes Infected GE 1

MS_SQL_ProcessLockSleep_Warning situation
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 10.

This situation has the following formula:

70 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Percent Processes Locksleep GE 10.00 AND
Total Processes Locksleep GE 5

MS_SQL_ProcessOthSleep_Warning situation
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.

This situation has the following formula:

Total Other Sleep GE 2 AND
Percent Processes Othersleep GE 50.00

MS_SQL_Processes_Bad_Warning situation
Declares a warning condition if the number of bad processes is greater than or
equal to 1.

This situation has the following formula:

Total Processes Bad GE 1

MS_SQL_Processes_Stop_Warning situation
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 5.

This situation has the following formula:

Total Processes Stopped GE 5 AND
Percent Processes Stopped GE 10.00

MS_SQL_Rem_Serv_Stat_Critical situation
Declares a critical condition if the remote server has a status of Inactive.

This situation has the following formula:

Remote Server Status NE ’Active’

MS_SQL_Repl_Latency_Crit situation
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

This situation has the following formula:

Replication Latency GT 900000

MS_SQL_Repl_Latency_Warn situation
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

This situation has the following formula:

(Replication Latency GT 120000) AND
(Replication Latency LE 900000)

Chapter 6. Situations reference 71

 MS_SQL_Status_Critical situation
Declares a critical condition if the SQL Server status is Inactive.

This situation has the following formula:

Server Status NE ’Active’

MS_SQL_Status_Inactive situation
Initiates an action if the SQL server is inactive. The following reflex automation is
associated with this situation: kddmail

The kddmail utility sends a message through e-mail to a specified e-mail address.
The e-mail address provided with this action is only an example; you must modify
this situation and provide a valid e-mail address. See IBM Tivoli Monitoring User’s
Guide for information about how to modify a predefined situation.

This situation has the following formula:

Server Status EQ ’Inactive’

MS_SQL_Total_Locks_Critical situation
Declares a critical condition if the number of locks totals more than 4000.

This situation has the following formula:

Total Locks GE 4000

MS_SQL_Total_Locks_Warning situation
Declares a warning condition if the number of locks is greater than or equal to 200.

This situation has the following formula:

Total Locks GE 200

72 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 7. 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, refer to the Predefined Take Action commands section below
and the information in that section for each individual command.

Predefined Take Action commands

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

The remaining sections of this chapter contain descriptions of each of these Take
Action commands, which are listed alphabetically. The following information is
provided about each Take Action command:
Description
Actions that the command performs on the system to which it is sent

© Copyright IBM Corp. 2005 73

 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.
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

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 may optionally use an explicit user ID
and password when connecting to the MS SQL Server. If you do not specify an
explicit user ID and password, a Take Action uses the Windows user ID and
password to establish the connection. Table 10 describes possible combinations for
specifying the user ID and password. If a blank string is used for specifying the
user ID, the connection to the server is established using Windows authentication.
Table 10. 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 The user ID string and blank password are used
double quotation when connecting to the server.
marks )
Blank (use A given string The windows authentication information associated
double quotation with the agent process (service) is used when
marks ) connecting to the server.
Blank (use Blank (use The windows authentication information associated
double quotation double quotation with the agent process (service) is used when
marks ) marks ) connecting to the server.

Database Check-up and Tune-up action

Description
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 NEWALLOC, DBCC CHECKCATALOG, and
DBCC CHECKIDENT.

74 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 – 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.
v Drops and reloads stored procedures.
v Runs DBCC UPDATEUSAGE to ensure more accurate space usage statistics.

Authorization roles
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
Table 10 on page 74.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see
Table 10 on page 74.

Restrictions
Managed system

Usage notes
Not applicable

Dump Database action

Description
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

Chapter 7. Take Action commands reference 75

 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 (7.0
or 2000).
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 roles
Microsoft SQL Server Permissions are sysadmin, db_owner, or
db_backupoperator.

Arguments
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 backup device. This value is ignored when the Use Last
Backup Device argument is 1.
Backup Options (backup_options)
A comma-separated list of options. For all options that take a 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.

76 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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.
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.

Chapter 7. Take Action commands reference 77

 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
Table 10 on page 74.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see
Table 10 on page 74.

Restrictions
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.
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

Description
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 (7.0 or 2000).
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 roles
Microsoft SQL Server Permissions are sysadmin, db_owner, or
db_backupoperator.

78 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Arguments
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 backup device. This value is ignored when the Use Last
Backup Device argument is set to 1.
Backup Options (backup_options)
A comma-separated list of options. For all options that take a 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 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.

Chapter 7. Take Action commands reference 79

 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.
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)

80 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Note: For information about specifying the SQL Server login ID, see
Table 10 on page 74.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see
Table 10 on page 74.

Restrictions
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 75 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

Description
Rebuilds clustered and non-clustered indexes on tables. You can specify the level of
fragmentation that triggers reindexing.

Authorization roles
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 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

Chapter 7. Take Action commands reference 81

 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
Table 10 on page 74.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see
Table 10 on page 74.

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 Index Index
Name Table Exists Name 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
double table.
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
double table
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 “”)

Restrictions
Managed system

82 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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

Description
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 roles
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)

Note: For information about specifying the SQL Server login ID, see
Table 10 on page 74.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see
Table 10 on page 74.

Table 12 shows how entries in the Table Name and Index Name arguments
determine which indexes and tables are updated.
Table 12. Index and table updates
Table Index Index
Name Table Exists Name Exists Outcome
Entered Y Entered Y Updates the specified index on the
specified table.
Entered Y Entered N Error. Specified index does not exist.

Chapter 7. Take Action commands reference 83

 Table 12. Index and table updates (continued)
Table Index Index
Name Table Exists Name Exists Outcome
Entered Y Blank (use - Updates all indexes on the specified
double table.
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
double table.
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 “”)

Restrictions
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 74. If you update a single index
on a table, all stored procedures based on that table are recompiled.

Start SQL Server action

Description
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.

Authorization roles
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

84 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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.

Restrictions
Managed system

Usage notes
Not applicable

Stop SQL Server action

Description
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 roles
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.

Restrictions
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

Description
Corrects inaccuracies in the sysindexes table that can cause incorrect space usage
reports by the sp_spaceused system stored procedure.

Authorization roles
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.

Chapter 7. Take Action commands reference 85

 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. Table 13 shows how entries in the Table Name and
Index Name arguments determine which indexes and tables are updated.
Table 13. 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 Updates all indexes on the specified table.
double quotation
marks “”)
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 Error. Specified table does not exist.
double quotation
marks “”)
Blank (use Exists Updates all indexes that share the specified name.
double quotation
marks “”)
Blank (use Does not exist Error. Specified table does not exist.
double quotation
marks “”)
Blank (use Blank (use Updates all indexes.
double quotation double quotation
marks “”) marks “”)

SQL Server ID (sql_server_id)

Note: For information about specifying the SQL Server login ID, see
Table 10 on page 74.
SQL Server Password (sql_server_password)

Note: For information about specifying the SQL Server login password, see
Table 10 on page 74.

Restrictions
Managed system

Usage notes
This Take Action does not create a report to show whether any corrections to the
sysindexes table should be made. This action is based on the DBCC
UPDATEUSAGE statement, and corrects the USED, RESERVED, and DPAGES
columns of the sysindexes table for any clustered indexes on U (user-defined table)
or S (system table) object types. It does not maintain size information for
nonclustered indexes. You can use this Take Action to synchronize space usage
counters in sysindexes for accurate usage information.

86 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Chapter 8. Policies reference
This chapter contains an overview of policies, references for detailed information
about policies, and descriptions of the predefined policies included in this
monitoring agent.

About policies
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,
refer to the Predefined policies section below and the information in that section
for each individual policy.

Predefined policies
This monitoring agent contains the following predefined policy:
MS_SQL_DB_free_space_critical. See the description in the next section of this
chapter.

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 kddignor command.
v Run the kddmail command as follows:
Where:
database user id
Connection user ID

© Copyright IBM Corp. 2005 87

 password
Password as a sysadmin authority
email id
E-mail address of the database administrator

88 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Appendix A. Workspaces
This appendix includes a summary of the predefined workspaces provided with
the Monitoring Agent for Microsoft SQL Server and describes how to use the data,
historical reports, and workspaces.

The Monitoring Agent for Microsoft SQL Server provides information about each
Microsoft SQL server instance you monitor using five categories of default
workspaces. This appendix gives a high-level description of the groups and
categories for the Monitoring Agent for Microsoft SQL Server and tells you where
to look for detailed information.

Determining which category of workspaces to use

Use the following chart to determine which category in the Navigator to select for
a given situation.
Table 14. Determining which category of workspaces to use

Errorlog Alerts
Databases

Locking
Servers

Process
If you want to...
Analyze the performance of your system U U U U
Evaluate how your tuning decisions affect U U
the performance of your system
Get the information you need to tune U U U U
your system
Identify and anticipate times of peak U U
usage
Identify problem areas and bottlenecks in U U U
your system
Monitor database activity U U
Select optimum threshold values for U U
situation monitoring

Determining where to find the information you need

The following table describes the workspaces for Monitoring Agent for Microsoft
SQL Server and indicates the section to use in this guide to find the information
you need.
Table 15. Determining where to find the information you need
Type of information
you need Provides information on... For more information, see...
Databases Your databases (such as log and “Displaying information for
space information and device databases” on page 90.
usage)

© Copyright IBM Corp. 2005 89

 Table 15. Determining where to find the information you need (continued)
Type of information
you need Provides information on... For more information, see...
Error log alerts Errorlog alerts, both in summary “Displaying information for
and detail formats error log alerts” on page 92.
Locks Database locking (such as “Displaying information for
conflicts and lock processes) locks” on page 94.
Processes Processes, both in summary and “Displaying information for
detail formats processes” on page 96.
Servers Server, remote server or “Displaying information for
statistics for the server (such as Microsoft SQL servers” on page
options and configuration) 98.

Displaying information for databases

The workspaces for databases provide information to help you monitor the
databases for your SQL servers. The workspaces provide information about
databases, including the following:
v Number of databases
v Names and IDs of the databases
v Number of devices

Determining the predefined workspace to use

Use the following table to determine which report or predefined workspace to use
to access information about the databases. The tasks are listed in alphabetical
order.
Table 16. Determining the workspace to use for databases
Type of information to display Workspace to use
Detailed information about database activity for Included as a table view in Databases
a specific SQL server
Information about the devices for a selected Included as a table view in Log and
database Space Information
Information about the transaction log and space Log and Space Information
usage on a selected database
Overview of the database activity for all the Entropies Database Summary
SQL servers
Summary information about a selected database Databases

Relationship to the attribute groups

In most cases, a predefined workspace contains data or columns that have similar
attributes in an attribute group. The tables show the relationship of the workspaces
to the attribute groups.
Table 17. Workspaces for databases and the relationship to attribute groups
Workspace Associated attribute group
Databases For the Databases Summary table view, MS SQL
Database Summary For the Database Detail table
view, MS SQL Database Detail

90 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table 17. Workspaces for databases and the relationship to attribute groups (continued)
Workspace Associated attribute group
Enterprise Database Summary None (The workspace does not have an associated
attribute group.)
Log and Space Information For the Log and Space Information table view, MS
SQL Database Detail For the Devices table view, MS
SQL Device Detail

Example tasks and the predefined workspaces available

The following table contains examples of tasks. Use the table to determine which
workspace to use in a given situation.
Table 18. Example tasks and the predefined workspaces available for databases

Enterprise database summary

Log and space information

Databases
If you want to...
View summary information about the databases in your U
environment
Know the number of databases in your system U U
Determine the percentage of free space on a database U U
Find out the type of device U

Typical scenarios
These scenarios describe some of the many ways you can monitor databases.

Scenario 1: Do any databases have an error status?

Databases with an error status are in a suspect, crashed, or recover state. You can
quickly identify any databases with an error status as follows: check the Total DBs
in Error column in the Databases workspace. Use the MS_SQL_DB_Error_Status
situation to issue an alert whenever a database has an error status.

Scenario 2: Are any devices running short of free space?

Maintaining adequate free space on the devices in your system is important.
Determining your space needs in advance lets you plan expansion. You can add a
new device and expand the database on the new device at your convenience. You
can monitor the free space on devices in two ways.
v Check the Device Free Space Percent and Device Free Space (MB) columns by
opening the Log and Space Information workspace. From these columns, you
can determine the percentage of free space remaining on the device and assess
the size in megabytes.
v Use the MS_SQL_Device_Free_Pct_Warning situation to issue an alert whenever
a device reaches the threshold you set for free space.

Appendix A. Workspaces 91
 Scenario 3: Is a full transaction log preventing an application
from running?
You can monitor the status of the transaction log in two ways.
v Check the Log free space Percent column by opening the Log and Space
Information workspace. The column shows what percentage of the log is full.
You can then check the Log Size and Log free space columns to evaluate the size
of the log.
v Use the MS_SQL_Log_free space_Critical situation to issue alerts whenever the
transaction log is becoming too full. You can take action to empty the log and
avoid the problem.

Displaying information for error log alerts

The workspaces for error log alerts provide information to help you monitor the
error log alerts for your SQL servers. The workspaces provide information about
error log alerts, including the following:
v Size of the error log
v Number of error messages with a high severity level
v Highest severity level encountered since start up

Determining the predefined workspace to use

Use the following table to determine which predefined workspace to use to access
information about the error log alerts. The tasks are listed in alphabetical order.
Table 19. Determining the workspace to use for error log alerts
Type of information to display Workspace to use
Detailed information about each error message for a Included as a table view in Errorlog
selected SQL server Alerts
Overview of information about the error log for each Enterprise Errorlog Alerts
SQL server
Summary information about the error messages for Errorlog Alerts
the selected SQL server

Relationship to the attribute groups

In most cases, a predefined workspace contains data or columns that have similar
attributes in an attribute group. The tables show the relationship of the workspaces
to the attribute groups.
Table 20. Workspaces for error log alerts and the relationship to attribute groups
Workspace Associated attribute group
Errorlog Alerts For the Alert Summary table view, MS SQL Problem
Summary For the Alert Detail table view, MS SQL Problem
Detail
Enterprise Errorlog Alerts None (The workspace does not have an associated
attribute group.)

Example tasks and the predefined workspaces available

The following table contains examples of tasks. Use the table to determine which
workspace to use in a given situation.

92 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table 21. Example tasks and the predefined workspaces available for error log alerts

Enterprise error log alerts

Error log alerts

If you want to...
Determine the level of severity for a specific error U
Determine the size of the error log U U
Find out how many errors have occurred during the current interval U
View summary information about the error log for an SQL server U

Typical scenarios
These scenarios describe some of the many ways you can monitor processes.

Scenario 1: Monitor severity level 17 error messages

To read the error log file, you must be authorized and able to use UNIX
commands to review its messages. The reports and workspaces for error log alerts
provide a faster and simpler means of detecting severe error messages. You can
easily monitor severe error messages in the following ways.
v Check the highest severity level for any error message by looking at the
Maximum Sev Level column after opening the Errorlog Alerts workspace.
v Use the following situations:
– MS_SQL_Severe_Error_Warning (This situation issues an alert whenever it
detects an error message of severity level 17 or higher.)
– MS_SQL_ProbAge_GT_17_Warning (This situation issues an alert whenever it
detects an error message of severity level 17 that is 30 or more minutes old.)

Scenario 2: Monitor less severe error messages

You can easily monitor other error messages in the following ways.
v Check for the highest severity level for the current interval in the Maximum Sev
Current Interval column by opening the Errorlog Alerts workspace.
The number in this column indicates what the highest severity level is for the
current interval.
v Use the MS_SQL_ProbAge_LT_17_Warning situation. This situation issues an
alert whenever it detects an error message of severity level 16 or less.

Scenario 3: Determine when to prune the error log

The error log file continues to grow in size as SQL server continues to append
messages to it. Periodically, pruning the error log saves disk space and makes it
easier to find error messages within the file. You can easily determine if
maintenance is needed in the following ways.
v Check the Error Log Size (Bytes) column by opening the Errorlog Alerts
workspace. Prune the file if the number of bytes indicate it is time to reduce its
size.
v Use the MS_SQL_ErrorLog_Size_Warning situation to issue an alert whenever
the number of bytes in the file.

Appendix A. Workspaces 93
 Scenario 4: Monitor application-generated messages
You can easily monitor messages generated by applications in the following ways.
v Display details for a message, such as the error ID and text by opening the
Errorlog Alerts workspace.
v Create a situation to issue an alert for a specific message ID.

Displaying information for locks

The workspaces for locks provide information to help you monitor the locks for
your SQL servers. The workspaces provide information about locks, including the
following:
v Number of locks on processes
v Number of lock conflicts
v Percent of locks that resulted in deadlocks
v Type of lock on a process

Determining the predefined workspace to use

Use the following table to determine which predefined workspace to use to access
information about the locks. The tasks are listed in alphabetical order.
Table 22. Determining the workspace to use for locks
Type of information to display Workspace to use
Detailed information about a lock on a selected SQL Included as a table view in Server
server Locking
Information about the lock conflicts for a selected Server Locking
SQL server
Overview of the lock conflicts for SQL servers Enterprise Server Locking
SQL text strings for the process holding the lock Process Holding Lock SQL Text
SQL text strings for the selected blocking or waiting SQL Text for Process ID
process

Relationship to the attribute groups

In most cases, a predefined workspace contains data or columns that have similar
attributes in an attribute group. The tables show the relationship of the workspaces
to the attribute groups.
Table 23. Workspaces for locks and the relationship to attribute groups
Workspace Associated attribute group
Enterprise Server Locking None (The workspace does not have an associated
attribute group.)
Process Holding Lock SQL Text MS SQL Text
SQL Text for Process ID MS SQL text
Server Locking For the Lock Conflict table view, MS SQL Lock
Conflict Detail For the Lock Detail table view, MS
SQL Lock Detail

Example tasks and the predefined workspaces available

The following table contains examples of tasks. Use the table to determine which
workspace to use in a given situation.

94 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table 24. Example tasks and the predefined workspaces available for locks

Enterprise Server Locking

SQL Text for Process ID

Server Locking
If you want to...
Find out what type of lock is being held on a resource U
Identify a blocking process U
Know the number of seconds that a process has been blocked U
View SQL text strings for a process U
View summary information about locks in your environment U

Typical scenarios
These scenarios describe some of the many ways you can monitor processes.

Scenario 1: Identify the cause of a user being unable to complete

a procedure
Often, the cause of a blocked application is another process holding locks on
resources. You can quickly determine if this is the case in the following way:
v See if conflicts exist in the Total Locks column by opening the Server Locking
workspace.
v Review its columns for information that enables you to take action to resolve the
problem. The Lock Detail table view in the Server Locking workspace identify
such items as the
– ID of the blocking process
– IDs of the client process and client user
– ID and name of the user process
– Name of the program
– User ID assigned by the server

This procedure eliminates the need to set a trace and delivers the detailed
information quickly enough to be useful.

Scenario 2: Simplify procedures for analyzing locking problems

Lock conflicts often slow processing and cause applications to hang. They can also
reveal improperly indexed tables. This scenario helps you avoid using lengthy
traces and tedious analysis methods. Analyze potential locking problems in a
real-time environment in the following ways:
v Analyze the data in the following columns in Enterprise Server Locking
workspace:
– Percent Process Blocked
– Total Locks
Use this information to identify potential locking problems.

Appendix A. Workspaces 95
 v Use the MS_SQL_AVG_Blocked_ Warning and MS_SQL_Max_Blocked_Warning
situations to issue alerts whenever the number of locks and their age exceed
threshold values.
This early detection lets you take proactive action to fix long waits and minimize
outages from lock conflicts.

Scenario 3: Identify deadlocks in your system

SQL server automatically eliminates deadlocks by killing one of the processes.
However, you might want to resolve deadlocks before they incur overhead. You
might also want to change the design of applications that repeatedly cause
deadlocks. You can easily determine the existence and frequency of deadlocks in
two ways.
v Check the Total Locks column by opening the Enterprise Server Locking
workspace.
v Use the MS_SQL_Deadlock_Count_Warning situation to issue an alert whenever
the number of deadlocks exceeds a threshold limit.

Scenario 4: Perform detailed locking analysis

Obtaining detailed information about a locking situation is equally as important as
detecting it. Gathering pertinent information before changing circumstances
interfere can be difficult. To gather the details about a lock, do the following:
v Check information about the lock, locking process, and requestor process by
opening the Server Locking workspace. (The Lock Detail table view contains
detailed information about the processes, SQL command, transaction, client, and
other elements.)
Use this information to resolve the conflict or modify application design.
v Use the MS_SQL_Lock_Blocked_Warning and MS_SQL_Lock_Blocked_Critical
situations to issue alerts whenever a blocking lock exceeds the time limit for the
threshold.
This analysis enables you to capture an immediate snapshot of the locking
situation and process details. You acquire the information before it is lost to
changing conditions, and you avoid interrupting your operations.

Displaying information for processes

The workspaces for processes provide information to help you monitor the
processes for your SQL servers. The workspaces provide information about the
following processes:
v Number of blocked processes
v Percentage of CPU time used by SQL server processes
v Percentage of CPU time used by application processes

Determining the predefined workspace to use

Use the following table to determine which predefined workspace to use to access
information about the processes. The tasks are listed in alphabetical order.
Table 25. Determining the workspace to use for processes
Type of information to display Workspace to use
Detailed information about each process running on Included as a table view in
the selected SQL server Processes
Overview of processes for the SQL servers Enterprise Processes Summary

96 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table 25. Determining the workspace to use for processes (continued)
Type of information to display Workspace to use
Summary information about the processes running on Processes
the selected SQL server
SQL text string for a process running on a selected SQL Text for Process ID
SQL server

Relationship to the attribute groups

In most cases, a predefined workspace contains data or columns that have similar
attributes in an attribute group. The tables show the relationship of the workspaces
to the attribute groups.
Table 26. Workspaces for processes and the relationship to attribute groups
Workspace Associated attribute group
Enterprise Process Summary None (There is no attribute group associated
with this workspace.)
Processes For the Process Summary table view, MS
SQL Process Summary

For the Process Detail table view, MS SQL

Process Detail
SQL Text for Process ID MS SQL Text

Example tasks and the predefined workspaces available

The following table contains examples of tasks. Use the table to determine which
workspace to use in a given situation.
Table 27. Example tasks and the predefined workspaces available for processes
Enterprise processes summary

SQL Text for Process ID

Processes

If you want to...

Determine the number of blocked, infected, or U
locked processes
Determine the status of a selected SQL server U
process
View partial SQL text strings for a process U
View summary information about SQL server U
processes

Typical scenarios
These scenarios describe some of the many ways you can monitor processes.

Appendix A. Workspaces 97
 Scenario 1: Are any processes infected?
Processes that exceed their CPU grace time are tagged as infected and removed
from the processing queues. You can easily determine if any infected processes
exist in two ways:
v Check the Percent Processes Infected and Total Processes Infected columns in the
Processes workspace.
v Use the MS_SQL_Process_Infected_Warning situation to issue an alert whenever
a process becomes infected. You might want to resolve the problem by
increasing the CPU grace time setting for the infected process.

Scenario 2: Are any processes blocked?

Processes that hold exclusive locks on resources block other processes from
accessing these resources. You can easily determine if any processes are blocked in
two ways:
v Check the Percent Processes Blocked and Total Processes Blocked columns in the
Processes workspace. The columns show the percentage and number of blocked
processes.
v Use the MS_SQL_Process_Blocked_ Warning situation to issue an alert whenever
a process blocks another. You might want to take action against the processes
that are causing the contention.

Scenario 3: Are any processes bad?

You can easily determine if any bad processes exist in two ways:
v Check the Percent Processes Bad and Total Processes Bad columns by opening
the Processes workspace. The columns show the percentage and number of bad
processes.
v Use the MS_SQL_Processes_Bad_Warning situation to issue an alert whenever a
bad process is found.

Displaying information for Microsoft SQL servers

The workspaces in this group provide information about an SQL server, including
the following:
v Version of the SQL server
v Time, in seconds since startup

Determining the predefined workspace to use

Use the following table to determine which predefined workspace to use to access
information about the Microsoft SQL servers. The tasks are listed in alphabetical
order.
Table 28. Determining the workspace to use for servers
Type of information you want to display Workspace to use
Detailed information about a selected SQL server Included as a table view in Server
Configuration
Detailed information about each statistic for a Included as a table view in Server
selected SQL server Statistics
Information about the configuration of a selected Server Configuration
SQL server
Overview of remote SQL server activity Included as a table view in
Enterprise Server Summary

98 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 Table 28. Determining the workspace to use for servers (continued)
Type of information you want to display Workspace to use
Overview of SQL server activity for your Enterprise Server Summary
environment
Overview of SQL server statistics for your Server Statistics
environment
Summary information about a selected SQL server Servers
Summary information about the statistics for a Enterprise Server Statistics
selected SQL server

Relationship to the attribute groups

In most cases, a predefined workspace contains data or columns that have similar
attributes in an attribute group. The tables show the relationship of the workspaces
to the attribute groups.
Table 29. Workspaces for servers and the relationship to attribute groups
Workspace Associated attribute group
Enterprise Server Statistics None (This workspace does not have a
corresponding attribute group.)
Enterprise Server Summary MS SQL Remote Servers
Server Statistics For the Statistics Summary table view, MS
SQL Statistics Summary Attributes For the
Statistics Detail table view, MS SQL Statistics
Detail Attributes
Servers MS SQL Server Summary
Server Configuration For the Server Summary table view, MS SQL
Server Summary For the Server Options
table view, MS SQL Server Detail For the
Server Configuration table view, MS SQL
Server Configuration

Example tasks and predefined workspaces available

The following table contains examples of tasks. Use this table to determine which
workspace to use in a given situation.
Table 30. Example tasks and predefined workspaces available for servers
Enterprise Server Summary
Enterprise Server Statistics

Server Configuration

Server Statistics
Server

If you want to...

Determine the average value reported for a statistic U
Determine the data cache or procedure cache size U
Determine the duration of the current interval U

Appendix A. Workspaces 99
 Table 30. Example tasks and predefined workspaces available for servers (continued)

Enterprise Server Summary

Enterprise Server Statistics

Server Configuration

Server Statistics
Server
If you want to...
Determine the number of active connections U
Determine the percentage of maximum locks U
Determine the server version U U
Determine whether a configuration parameter is U
dynamic or static
Find out how long it has been since the server started U U
Find out how much of the CPU the server is using U U
View summary information about SQL servers U
View summary information about SQL server statistics U
View the status of the server and its activity U

Typical scenarios
These scenarios describe some of the many ways you can monitor servers using
the workspaces provided for the following:
v Servers
v Server statistics
v Remote servers

Scenario 1: Is the SQL server up and running?

You can monitor the status of an SQL server in three ways.
v Check the Server Status column by opening the Servers workspace. The column
either contains a value of Active if the server is active or is blank if the status is
unknown.
v Use the MS_SQL_Status_ Inactive situation to set up reflex automation. The
system administrator can make copies of this situation and have one
automatically call a pager and one automatically send UNIX e-mail if the SQL
server is not active. You can then identify which server is not active by checking
the Servers workspace.
v Use the MS_SQL_Status_Critical situation to issue an alert whenever the SQL
server is not active. You can then identify which server is not active by checking
the Servers workspace.

Scenario 2: Is the number of locks in use causing problems?

The SQL server prevents users from logging on if the maximum number of
configured locks is reached. To monitor the use of locks, use the following
situations to issue alerts when the number of locks in use is getting too high.
v MS_SQL_Pct_Max_Locks_Warning
v MS_SQL_Pct_Max_Locks_Critical

100 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
An alert allows you to take action before the server hangs. For details on the alert,
check the Servers workspace.

Scenario 3: Is CPU usage by the SQL server too high?

You can monitor the CPU usage by the SQL server in two ways:
v Check the Server CPU Percent column in the Servers workspace. This column
shows the percentage of CPU time the SQL server is using.
v Use the following situations to issue alerts when the percentage of CPU used by
the SQL server is getting too high.
– MS_SQL_CPU_Warning
– MS_SQL_CPU_Critical

Scenario 4: Is the total CPU usage too high?

You can monitor the CPU usage by all processes in two ways.
v Check the Total OS CPU Percent column in the Servers workspace. This column
shows the percentage of CPU time being used by all processes on the host.
v Use the following situations to issue alerts when the percentage of CPU used by
all the processes is too high:
– MS_SQL_CPU_Warning
– MS_SQL_CPU_Critical

Scenario 5: Is high I/O activity causing a slow response time?

High I/O activity can slow response time. You can quickly determine if I/O
activity is causing this problem in the following ways:
v Check the Disk IO Current Interval and Total OS Pct Busy columns by opening
the Server Statistics workspace. The values in these columns indicate if I/O
activity is the likely cause of slow response time.
v Use the MS_SQL_Server_Pct_IO_Warning situation. This situation issues a
warning alert whenever I/O activity exceeds a specified percentage.

Scenario 6: Are numerous I/O errors causing a slow response

time?
Numerous I/O errors can greatly slow response time. You can quickly determine if
errors are causing this problem in the following ways.
v Check the IO Errors Current Interval and IO Errors Since Startup columns in the
Server Statistics workspace. The values in these columns indicate if I/O errors
are the likely cause of slow response time.
v Use one of the following situations.
– MS_SQL_Server_IO_Error_Curintvl_Warning (This situation issues a warning
alert whenever I/O errors for the current interval exceed a threshold.)
– MS_SQL_Server_IO_Error_Curintvl_Warning (This situation issues a warning
alert whenever I/O errors for the current interval exceed a threshold.)

Scenario 7: Is the setting for maximum logons causing users

problems?
If the setting for the maximum number of logons is too low, users cannot log on.
You can quickly determine if this is the case in the following ways.
v Check the Max User Connection Allowed and Pct Max Logons Active columns
in the Server Statistics workspace. The values in these columns indicate if a
problem exists for user logons. Schedule maintenance to increase the
configuration parameter for user logons if necessary.

Appendix A. Workspaces 101

 v Use the MS_SQL_Server_LogonPct_Warning situation. This situation issues a
warning alert whenever logons exceed the threshold.

Scenario 8: Are any remote servers not active?

You can determine if any remote servers are not active in two ways.
v Check the Remote Server Status column in the Remote Servers table view in the
Enterprise Server Summary workspace. This column contains a value of Active if
the remote server is active or a value of 0 if it is any other state. Look in the
Remote Server Name column to identify which remote servers are not active.
v Use the MS_SQL Server_Rem_Serv_Stat_Critical situation to issue an alert
whenever a remote server is not active.

102 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Appendix B. IBM Tivoli Enterprise Console event mapping
Generic event mapping provides useful event class and attribute information for
situations that do not have specific event mapping defined. Each event class
corresponds to an attribute group in the monitoring agent. For a description of the
event slots for each event class, see Table 31 on page 104. For more information
about mapping attribute groups to event classes, see the IBM Tivoli Monitoring
Administrator’s Guide.

BAROC files are found on the Tivoli Enterprise Monitoring Server in the
installation directory in TECLIB (that is, install_dir/cms/TECLIB for Windows
systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM
Tivoli Enterprise Console event synchronization provides a collection of
ready-to-use rule sets that you can deploy with minimal configuration. Be sure to
install IBM Tivoli Enterprise Console event synchronization to access the correct
Sentry.baroc, which is automatically included during base configuration of IBM
Tivoli Enterprise Console rules if you indicate that you want to use an existing
rulebase. See the IBM Tivoli Monitoring Installation and Setup Guide for details.

Each of the event classes is a child of KOQ_Base. The KOQ_Base event class can be
used for generic rules processing for any event from the Monitoring Agent for
Microsoft SQL Server.

© Copyright IBM Corp. 2005 103

 Table 31. Overview of event slots to event classes
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 procedure_cache_size: INTEGER
v percent_max_locks: REAL
v server_cpu_percent: REAL
v total_os_cpu_percent: REAL
v time_since_startup: INTEGER
v server_version: STRING
v current_interval: INTEGER
v sample_timestamp: STRING
v cache_average_free_scan: INTEGER
v cache_hit_ratio: REAL
v cache_maximum_free_page_scan:
INTEGER
v cache_free_buffers: INTEGER
v sqlserveragent_failed_jobs: INTEGER
v server_cpu_percent_io: REAL
v cpu_percent_idle: REAL
v total_blocking_lock_requests: INTEGER
v total_locks_remaining: INTEGER

104 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 31. Overview of event slots to event classes (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_version: STRING
v server_status: STRING
v server_status_enum: STRING
v current_locks: INTEGER
v max_locks_allowed: INTEGER
v percent_max_locks: REAL
v data_cache_size: INTEGER
v procedure_cache_size: INTEGER
v procedure_cache_percent: REAL
v startup_timestamp: STRING
v time_since_startup: INTEGER
v error_log_name: STRING
v error_log_size: INTEGER
v os_type: STRING
v os_version: STRING
v sample_timestamp: STRING
v procedure_buffers_percent_active: REAL
v procedure_buffers_total: INTEGER
v procedure_buffers_percent_used: REAL
v procedure_cache_percent_active: REAL
v procedure_cache_pages: INTEGER
v procedure_cache_percent_used: REAL
v error_log_name_u: 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_log_freespace: REAL
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

Appendix B. IBM Tivoli Enterprise Console event mapping 105

 Table 31. Overview of event slots to event classes (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 db_id: 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 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 log_size: REAL
v data_freespace: REAL
v log_freespace: REAL
v data_freespace_percent: REAL
v log_freespace_percent: REAL
v total_devices: INTEGER
v sample_timestamp: INTEGER
v database_space_percent_used: REAL
v database_status: INTEGER
v database_status_enum: STRING
v log_space_percent_used: REAL
v oldest_open_transaction: INTEGER
v suspect_database: INTEGER
v suspect_database_enum: STRING
v replicated_transaction_rate: REAL
v replicated_transactions: INTEGER
v replication_latency: INTEGER
v db_owner_u: STRING
v database_name_u: STRING

106 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 31. Overview of event slots to event classes (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_free_space: REAL
v device_free_space_percent: REAL
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
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 process_holding_lock: INTEGER
v database_name: STRING
v database_id: INTEGER
v table_name: STRING
v page_number: INTEGER
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_num: STRING
v database_name_u: STRING
v table_name_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 107

 Table 31. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
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
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

108 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 31. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
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

Appendix B. IBM Tivoli Enterprise Console event mapping 109

 Table 31. Overview of event slots to event classes (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
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

110 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 31. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
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
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 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

Appendix B. IBM Tivoli Enterprise Console event mapping 111

 Table 31. Overview of event slots to event classes (continued)
IBM Tivoli Enterprise Console event class event slots
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
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_status: STRING
v remote_server_name: STRING
v network_name: STRING
v connection_level: INTEGER
v current_interval: INTEGER
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 config_value: STRING
v run_value: STRING
v minimum_value: STRING
v maximum_value: STRING
v sample_timestamp: STRING

112 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 31. Overview of event slots to event classes (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 server_cpu_percent: REAL
v total_os_cpu_percent: REAL
v time_since_startup: INTEGER
v server_version: STRING
v total_databases: INTEGER
v minimum_pct_data_freespace: REAL
v minimum_pct_log_freespace: REAL
v total_locks: INTEGER
v total_lock_conflicts: INTEGER
v database_max_locks: STRING
v database_max_blocks: STRING
v table_max_locks: STRING
v percent_process_block: REAL
v server_cpu_percent_system: REAL
v server_cpu_percent_application: REAL
v total_processes: INTEGER
v total_processes_blocked: INTEGER
v age_of_last_error: INTEGER
v maximum_sev_level: STRING
v maximum_sev_timestamp: STRING
v total_errors_high_sev: INTEGER
v error_log_size: INTEGER
v current_logons: INTEGER
v percent_max_logons_active: REAL
v physical_reads_per_second: REAL
v physical_writes_per_second: REAL
v io_errors_current_interval: INTEGER
v sample_timestamp: STRING
v server_status: STRING
v server_status_enum: STRING
v database_max_locks_u: STRING
v database_max_blocks_u: STRING
v table_max_locks_u: STRING

Appendix B. IBM Tivoli Enterprise Console event mapping 113

 Table 31. Overview of event slots to event classes (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 table_name: STRING
v table_name_enum: STRING
v table_id: INTEGER
v index_name: STRING
v index_name_enum: STRING
v index_id: INTEGER
v optimizer_statistics_age: INTEGER
v fragmentation: REAL
v space_used__mb: REAL
v sample_timestamp: STRING
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

114 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Appendix C. Problem determination
This appendix explains how to troubleshoot the IBM Tivoli Monitoring for
Databases: Microsoft SQL Server Agent. Troubleshooting, or problem
determination, 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 Chapter 2, “Requirements and configuration
for the monitoring agent,” on page 5.

This appendix provides agent-specific problem determination information. See the

IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information. Also see “Support information” on page 135 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 32. 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 116 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 (Select the About... item in the Help menu to see this
information 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 Monitoring for Databases: Microsoft SQL Server Agent
Screen captures Screen captures of incorrect output, if any.

Upload files for review to the following FTP site: ftp.emea.ibm.com. Log in as
anonymous and place your files in the directory that corresponds to the IBM Tivoli
Monitoring component that you use. See “Contacting IBM Software Support” on
page 137 for more information about working with IBM Software Support.

Built-in problem determination features

The primary troubleshooting feature in the IBM Tivoli Monitoring for Databases:
Microsoft SQL Server Agent is logging. Logging refers to the text messages and
trace data generated by the IBM Tivoli Monitoring for Databases: Microsoft SQL
Server Agent. Messages and trace data are sent to a log file.

© Copyright IBM Corp. 2005 115

 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” for more information.

Problem classification
The following types of problems might occur with the IBM Tivoli Monitoring for
Databases: Microsoft SQL Server Agent:
v Installation and configuration
v General usage and operation
v Display of monitoring data
v Take Action commands

This appendix 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 Problem Determination Guide for general problem
determination 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 117
v “Viewing trace logs” on page 119
v “Enabling detailed tracing in the collector trace log” on page 120
v “Setting RAS trace parameters” on page 121

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 33 on page 118 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 machine on which the monitoring component is
running.
v product is the two-character product code. For Monitoring Agent for Microsoft
SQL Server, the product code is oq.

116 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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 Monitoring Agent for Microsoft SQL Server
might be named as follows:
server01_oq_dbinst02_koqagent_437fc59-01.log

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 Monitoring Agent for Microsoft SQL
Server 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 Monitoring
Agent for Microsoft SQL Server 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 33 on page 118 contains locations, file names, and descriptions of trace logs
that can help determine the source of problems with agents.

Appendix C. Problem determination 117

Table 33. Trace log files for troubleshooting agents
System where log File name and path Description
is located
On the computer The RAS1 log files are named Traces activity of the monitoring agent.
that hosts the hostname_oq_instance_program_timestamp-nn.log Note: Other logs, such as logs for
monitoring agent and are located in the install_dir\tmaitm6\logs collector processes and Take Action
path: commands (if available), have a similar
See “Definitions of Note: File names for RAS1 logs include a syntax and are located in this directory
variables” on page hexadecimal time stamp. path.
119 for
descriptions of the The collector trace log file is named A collector trace log file is produced by
variables in the file hostname_oq_instance_col.out. The file is located in Monitoring Agent for Microsoft SQL
names in column the install_dir\tmaitm6\logs path. Server. New log files are created each
two. time the agent is started. One backup
Note: A hostname_oq_instance_col.out log file also copy, renamed from *.out to *.ou1, is
exists and contains stderr and stdout messages. kept for historical purposes. The log file
is not pruned. See “Enabling detailed
tracing in the collector trace log” on
page 120 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 Monitoring Agent for Microsoft SQL
the install_dir\tmaitm6\logs path. Server. New log 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 A new version of this file is generated
install_dir\tmaitm6\logs path. 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.

118 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 33. Trace log files for troubleshooting agents (continued)
System where log File name and path Description
is located
On the Tivoli On UNIX: The candle_installation.log file in the Provides details about products that are
Enterprise install_dir/logs path. installed.
Monitoring Server Note: Trace logging is enabled by
On Windows: The file in the default. A configuration step is not
See “Definitions of install_dir\InstallITM path. Unlike RAS1 log files, required to enable this tracing.
variables” for the name of the file displays a decimal time stamp. *
descriptions of the
The Warehouse_Configuration.log file is located in Provides details about the configuration
variables in the file
the following path on Windows: of data warehousing for historical
names in column
install_dir\InstallITM. reporting.
two.
The RAS1 log file is named hostname_ms_timestamp- Traces activity on the monitoring server.
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 number.
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
number.
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 machine 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 Monitoring Agent for Microsoft SQL Server, 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 117 for details of log rolling.

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

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

Appendix C. Problem determination 119

 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:
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

Perform 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 33 on page 118.
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 the environment variables

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 30,000 lines by default (about 2 MB).
COLL_NUMOUTBAK
By default, the product creates one backup copy of the collector log file.

120 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 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.

Set the environment variables as follows:

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 pulldown 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.

Setting RAS trace parameters

Objective
Pinpoint a problem by setting detailed tracing of individual components of the
monitoring agent and modules.

Background Information
Monitoring Agent for Microsoft SQL Server uses RAS1 tracing and generates the
logs described in Table 33 on page 118. The default RAS1 trace level is ERROR.

RAS1 tracing has control parameters to manage to the size and number of RAS1
logs. Use the procedure described in this section to set the parameters.

Note: The KBB_RAS1_LOG parameter also provides for the specification of the
log file directory, log file name, and the inventory control file directory and
name. Do not modify these values or log information can be lost.

Before you begin

See “Overview of log file management” on page 116 to ensure that you understand
log rolling and can reference the correct log files when you managing log file
generation.

After you finish

Monitor the size of the logs directory. Default behavior can generate a total of 45 to
60 MB for each agent that is running on a computer. For example, each database
instance that you monitor could generate 45 to 60 MB of log data. See the

Appendix C. Problem determination 121

 ″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 which are pruned automatically, other log types can grow
indefinitely, for example, the logs in Table 33 on page 118 that include a process ID
number (PID).

Consider using collector trace logs (described in Table 33 on page 118) as an

additional source of problem determination information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can
generate a large amount of trace logging. Use them only temporarily, while
you are troubleshooting problems. Otherwise, the logs can occupy excessive
amounts of hard disk space.

Procedure
Specify RAS1 trace options in the install_dir\tmaitm6\KOQENV file. Use one of the
following methods to modify trace options:
v Manually edit the configuration file to set trace logging
1. Open the trace options file: install_dir\tmaitm6\KOQENV.
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 as follows:
KBB_RAS1=ERROR (UNIT:kdd ALL) (UNIT:koq ALL) (UNIT:kra ALL)
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation
of log files:
– Edit the following parameters to adjust the number of rolling log files and
their size.
- MAXFILES: the total number of files that are to be kept for all startups
of a given program. Once this value is exceeded, the oldest log files are
discarded. Default value is 9.
- LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file.
Default value is 5.
– IBM Software Support might guide you to modify the following
parameters:
- COUNT: the number of log files to keep in the rolling cycle of one
program startup. Default value is 3.
- PRESERVE: the number of files that are not to be reused in the rolling
cycle of one program startup. Default value is 1.

Note: The KBB_RAS1_LOG parameter also provides for the specification of

the log file directory, log file name, and the inventory control file
directory and name. Do not modify these values or log information
can be lost.
4. Restart the monitoring agent so that your changes take effect.
v (Windows only) Alternate method to edit trace logging parameters:
1. Open the Manage Tivoli Enterprise Monitoring Services window.
2. Right-click the icon of the monitoring agent whose logging you want to
modify.

122 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
 3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring
Server Trace Parameters window is displayed.
4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters
field or type a valid string.
The selections are as follows:
– No error tracing. KBB_RAS1=-none-
– General error tracing. KBB_RAS1=ERROR
– Intensive error tracing. KBB_RAS1=ERROR (UNIT:koq ALL)
– Maximum error tracing. KBB_RAS1=ERROR (UNIT:koq ALL) (UNIT:kra ALL)

Note: As this example shows, you can set multiple RAS tracing options in
a single statement.
5. Modify the value for ″Maximum Log Size Per File (MB)″ to change the log
file size (changes LIMIT value).
6. Modify the value for ″Maximum Number of Log Files Per Session″ to change
the number of logs files per startup of a program (changes COUNT value).
7. Modify the value for ″Maximum Number of Log Files Total″ to change the
number of logs files for all startups of a program (changes MAXFILES
value).
8. (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.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can
generate a large amount of trace logging. Use them only temporarily,
while you are troubleshooting problems. Otherwise, the logs can
occupy excessive amounts of hard disk space.
9. Click OK. You see a message reporting a restart of the monitoring agent so
that your changes take effect.

Problems and workarounds

The following sections provide symptoms and workarounds for problems that
might occur with Monitoring Agent for Microsoft SQL Server:
v “Installation and configuration problem determination” on page 124
v “Agent problem determination” on page 128
v “Workspace problem determination” on page 129
v “Problem determination for remote deployment” on page 128
v “Situation problem determination” on page 130
v “Take Action command problem determination” on page 134
v “Problem determination for SQL Server” on page 135

Note: You can resolve some problems by ensuring that your system matches the
system requirements listed in Chapter 2, “Requirements and configuration
for the monitoring agent,” on page 5.
This appendix provides agent-specific problem determination information. See the
IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.

Appendix C. Problem determination 123

 Installation and configuration problem determination
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
Table 34. Problems and solutions for installation and configuration
Problem Solution
When you upgrade to IBM Tivoli Fixpacks for Candle, Version 350, are delivered as each monitoring agent
Monitoring, you might need to apply is upgraded to IBM Tivoli Monitoring.
fixpacks to Candle, Version 350, agents. Note: The IBM Tivoli Monitoring download image or CD provides
application fixpacks 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.
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.
(UNIX only) During a command-line You must exit and restart the installation process. You cannot return to
installation, you choose to install a the list where you selected components to install. When you run the
component that is already installed, and installer again, do not attempt to install any component that is already
you see the following warning: installed.
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.

124 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 34. Problems and solutions for installation and configuration (continued)
Problem Solution
A problem can arise when you install You must reconfigure the previously existing agents to restore their
and configure a new monitoring agent to communication connection with TEMS1. For example, you can
a computer where other agents are right-click the row for a specific agent in the Manage Tivoli Enterprise
running as described in this example: Monitoring Services, and select Reconfigure. See the IBM Tivoli
v Agents are running on computer and Monitoring Installation and Setup Guide for more information on
communicating with a Tivoli reconfiguration.
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 on 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 If a message similar to ″Unable to find running CMS on CT_CMSLIST″
running CMS on CT_CMSLIST″ in the is displayed in the Log file, the agent is not able to connect to the
log file is displayed. 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 migrate a Candle Copy the attribute files for the upgraded Candle monitoring agent to
monitoring agent to IBM Tivoli install_dir\tmaitm6\attrlib on the computer where you have installed
Monitoring, Version 6.1.0. 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.
The monitoring agent does not start in a Check the agent configuration to ensure that all the values are correctly
non-ASCII environment. represented. To view these parameters, go to the Manage Tivoli
Enterprise Monitoring Services window, select the agent template, and
choose the Configure using defaults. From the resulting window, select
and edit the database instance to view its parameters.

Appendix C. Problem determination 125

Table 35. Problems and solutions for installation and configuration of the database agent
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, “Requirements and
configuration for the monitoring agent,” on page 5.
The procedure for launching Monitoring This problem happens when the KOQENV file is missing. If the
Agent for Microsoft SQL Server Trace KOQENV file is missing from the install_dir\tmaitm6 directory, the
Parameters window in “Setting RAS Monitoring Agent for Microsoft SQL Server must be reinstalled.
trace parameters” on page 121 fails
because no trace settings are available in
the Enter RAS1 Filters field.
Collector trace logs are not receiving Review the information in “Trace logging” on page 116 to ensure that
error information. you are consulting the correct log file. The file is located in the following
path: install_dir\tmaitm6, where install_dir is the location of IBM Tivoli
Monitoring.
After running the agent successfully, you Consult the list of supported versions in the configuration chapter of the
reinstall the agent software, and agent user’s guide for SQL Server. Confirm that you are running a valid
collection of monitoring data stops. 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 115.
Alert summary report of Tivoli Ensure that the configuration setting of agent’s error log file defines a
Enterprise Portal shows no information. 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, “Requirements and configuration
for the monitoring agent,” on page 5.
Error counts are displayed in the Alert Check the time stamp for the reports. If you have set up historical data
summary report in the Tivoli Enterprise collection for Alert summary report, it is recommended that you set up
Portal, however, error messages are not historical data collection for the Alert detail report, too.
displayed in the Alert detail report.
Unique names for monitoring IBM Tivoli Monitoring might not be able to generate a unique name for
components: ORIGINNODE is truncated monitoring components due to the truncation of names that the product
and doesn’t show the product code. 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:OQ).
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 in the
following row:

126 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 35. Problems and solutions for installation and configuration of the database agent (continued)
Problem Solution

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) For the step 4 -6, if user can’t find
CTIRA_SUBSYSTEM_ID, add it.
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.
The monitoring agent does not start in a Check the agent configuration to ensure that all the values are correctly
non-ASCII environment. represented. To view these parameters, go to the Manage Tivoli
Enterprise Monitoring Services window, select the agent template, and
choose the Configure using defaults. From the resulting window, select
and edit the database instance to view its parameters.

Table 36. 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 Databases.
2. Uninstall IBM Tivoli Monitoring.

Appendix C. Problem determination 127

Table 36. General problems and solutions for uninstallation (continued)
Problem Solution
The way to remove inactive managed When you want to remove, but not uninstall, an offline managed system
systems (systems whose status is from the navigation tree, select the Enterprise navigation tree item. Then
OFFLINE) from the Enterprise navigation select the Managed System Status workspace, and right-click the item
tree in the portal is not obvious. that you want to remove, 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.

Agent problem determination

This section lists problems that might occur with agents.

This appendix provides agent-specific problem determination information. See the

IBM Tivoli Monitoring Problem Determination Guide for general problem
determination information.
Table 37. General agent problems and solutions
Problem Solution
When you edit the configuration for an The original configuration settings might include non-ASCII characters.
existing monitoring agent, the values These values were stored incorrectly and result in the incorrect display.
displayed are not correct. Enter new values using only ASCII characters.
The system experiences high CPU usage View the memory usage of the KOQCMA process. If CPU usage seems to
after you install or configure Monitoring be excessive, recycle the monitoring agent.
Agent for Microsoft SQL Server.
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.
Attribute values are missing and the Verify that the required performance counters are enabled. Chapter 2,
hostname_OQ_instancename_regtitls.txt “Requirements and configuration for the monitoring agent,” on page 5
file in the install_dir\tmaitm6\logs lists these requirements.
directory.

Problem determination for remote deployment

Table 38 on page 129 lists problems that might occur with remote deployment. This
appendix provides agent-specific problem determination information. See the IBM
Tivoli Monitoring Problem Determination Guide for general problem determination
information.

This section describes problems and solutions for remote deployment and removal
of agent software Agent Remote Deploy:

128 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 38. 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 Problem Determination Guide.The
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 parameters in the tacmd addSystem command. For example,
remote 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, “Requirements and configuration for the
monitoring agent,” on page 5 for more information on these
parameters.
While you are using the remote deployment feature Do not close or modify this window. It is part of the
to install Monitoring Agent for Microsoft SQL Server, installation process and will be dismissed automatically.
an empty 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 allow time for
the monitoring agent to refresh its connection with the Tivoli
Enterprise Monitoring Server before you begin the remote
removal process.

Workspace problem determination

Table 39 shows problems that might occur with workspaces. This appendix
provides agent-specific problem determination information. See the IBM Tivoli
Monitoring Problem Determination Guide for general problem determination
information.
Table 39. Workspace problems and solutions
Problem Solution
You see the following message: You see this message because some links do not have default workspaces.
KFWITM083W Default link is disabled Right-click the link to access a list of workspaces to select.
for the selected object; please
verify link and link anchor
definitions.
Attributes associated with a database The database name must be less than 128 characters.
whose name is 128 characters long or
longer are not displayed.

Appendix C. Problem determination 129

Table 39. Workspace problems and solutions (continued)
Problem Solution
You start collection of historical data but Managing options for historical data collection:
the data cannot be seen. v Basic historical data collection populates the Warehouse with raw data.
This type of data collection is turned off by default. See Chapter 2,
“Requirements and configuration for the monitoring agent,” on page 5
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 The workspaces containing these views only display valid data when the
column headers, but no data: Process workspace is accessed from a workspace link. Workspace Administrators
Holding Lock SQL Text, Blocking may access these workspaces directly (without following the correct
Process SQL Text, Waiting Process SQL workspace link) and this will result in no data being displayed for these
Text, and SQL Text 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, “Requirements and configuration for the
monitoring agent,” on page 5 section in this book.

Situation problem determination

This section provides information about both general situation problems and
problems with the configuration of situations. See the IBM Tivoli Monitoring
Problem Determination Guide for more information about problem determination for
situations.

General situation problems

Table 40 lists problems that might occur with specific situations.
Table 40. 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 “Setting RAS
disk space. trace parameters” on page 121. For example, trace logs grow rapidly
when you apply the ALL logging option.

130 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 40. Specific situation problems and solutions (continued)
Problem Solution
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.
You see the 'Unable to get attribute Ensure that the agent attribute files are installed on the Tivoli Enterprise
name' error in the Tivoli Enterprise Monitoring Server.
Monitoring Server log after creating a
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.

Demand-based versus Interval-based attribute groups

An attribute group that is a Demand-based attribute group collects its attribute
data on demand. When a workspace is opened or refreshed and there is data in a
view being supplied by a demand attribute group, the data associated with that
group is provided from either the data source (in other words, Microsoft SQL
Server) or a data cache. Demand-based attribute groups only cache their attribute
data if a cache retention period is specified. Demand-based attribute groups also
provide data when an associated situation is evaluated or when historical data is
collected.

An attribute group that is an Interval-based attribute group collects its attribute

data on a fixed interval. Requests for this data (workspace refresh, situation
evaluation, historical data collection) always obtain the data values from the data
cache. The cache is updated when the attribute collection interval expires.

An attribute group sample may return one or more rows of data, one row for each
unique set of applicable attribute group data. For performance reasons, the amount
of data (number of attribute group rows) collected for an attribute group is limited.
For instance, if a Microsoft SQL Server instance has 3000 databases, Database
Detail attribute data is only returned for 2000 of these, thus limiting the number of
databases that can be monitored.
Table 41. Sample frequency and collection limitation for attribute groups
Attribute group Sample frequency Collection limitation
Configuration Demand; cached for 30 seconds 300 configuration settings

Appendix C. Problem determination 131

Table 41. Sample frequency and collection limitation for attribute groups (continued)
Attribute group Sample frequency Collection limitation
Database Detail Demand; cached for 10 seconds 2000 databases
Database Summary Interval 180 seconds 1 database summary
Device Detail Demand 500 devices
Lock Conflict Interval 180 400 locks
Lock Detail Interval 180 400 locks
Lock Summary Demand 1 lock summary
Problem Detail Demand; cached for 60 seconds 200 error message entries in SQL
Server error log
Problem Summary Demand; cached for 60 seconds 1 problem summary
Process Detail Demand; cached for 10 seconds 2000 processes
Process Summary Interval 180 seconds 1 process summary
Remote Servers Interval 60 seconds 200 remote servers
Server Detail Demand; cached for 60 seconds 1 server detail
Server Enterprise This attribute group is populated by
attribute values from the other MS
SQL attribute groups; therefore, it’s
sample frequency is the set of sample
frequencies of the other MS SQL
attribute groups supplying the data
values for this attribute group.
Server Summary Interval 180 seconds 1 server summary
Statistics Detail Demand; cached for 300 seconds 400 statistics
Statistics Summary Interval 60 seconds 1 statistics summary
Table Detail Demand 2000 table indexes
Text Demand 1 SQL statement

Problems with configuration of situations

Table 42 lists problems that might occur with situations.

This section provides information for problem determination for agents. Be sure to
consult the IBM Tivoli Monitoring Problem Determination Guide for more general
problem determination information.
Table 42. 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.

132 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 42. Problems with configuring situations that you solve in the Situation Editor (continued)
Problem Solution
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 Monitoring Agent
Portal. for Microsoft SQL Server 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.
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.

Appendix C. Problem determination 133

Table 43. Problems with configuration of situations that you solve in the Workspace area
Problem Solution
Situation events are not displayed Associate the situation with a workspace.
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 workspace.
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.
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 44. 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 problem determination

Table 45 lists general problems that might occur with Take Action commands.
When each Take Action command runs it generates the log file listed in Table 33 on
page 118. This appendix provides agent-specific problem determination
information. See the IBM Tivoli Monitoring Problem Determination Guide for general
problem determination information.
Table 45. 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 IBM Tivoli Monitoring Problem Determination 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 7, “Take Action commands
reference,” on page 73.

134 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Table 45. Take Action commands problems and solutions (continued)
Problem Solution
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

Problem determination for SQL Server

Table 46 lists problems that might occur on the system or application that you are
monitoring. See the IBM Tivoli Monitoring Problem Determination Guide for general
problem determination information.
Table 46. 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 Web site for Microsoft
v Procedure Buffers Percent Active SQL Server for updated information on this problem.
v Procedure Cache Percent Active

Support information
If you have a problem with your IBM software, you have the following options for
obtaining support for software products:
v “Searching knowledge bases”
v “Obtaining fixes” on page 136
v “Receiving weekly support updates” on page 136
v “Contacting IBM Software Support” on page 137

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Appendix C. Problem determination 135

 Searching the Internet
If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

The IBM Software Support Web site provides the latest information about known
product limitations and workarounds in the form of technotes for your product.
You can view this information at the following Web site:

http://www.ibm.com/software/support

To search for information on IBM products through the Internet (for example, on
Google), be sure to consider the following types of documentation:
v IBM technotes
v IBM downloads
v IBM Redbooks
v IBM developerWorks
v Forums and newsgroups

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the Software support Web site at
http://www.ibm.com/software/support.
2. Click the Download tab.
3. Select the operating system in the Operating system menu.
4. Type search terms in the Enter search terms field.
5. As appropriate, use other search options to further define your search.
6. Click Search.
7. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at
http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at
http://www.ibm.com/software/support.
2. Click My account in the upper right corner of the page.
3. Click Subscribe to IBM e-news. (If you have already subscribed and want to
modify your subscription preferences, click Modify subscriptions and follow
the instructions on screen.)
4. Follow the instructions on screen to provide the following data:
v Your personal contact information.
v Your areas of interest.
v The types of subscriptions and regional versions that you want to receive.
5. Review the subscription confirmation to confirm your settings.

136 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Contacting IBM Software Support
IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus, and Rational products, as well as DB2 and WebSphere products that run
on Windows, or UNIX operating systems), enroll in Passport Advantage in one
of the following ways:
Online
Go to the Passport Advantage Web site at
http://www.lotus.com/services/passport.nsf/
WebDocs/Passport_Advantage_Home and click How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/login.
v For customers with IBMLink, CATIA, Linux, OS/390, iSeries, pSeries, z/Series,
and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer software products (including, but not limited to, DB2 and
WebSphere products that run in z/Series, pSeries, and iSeries environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact”
2. “Describing problems and gathering information” on page 138
3. “Submitting problems” on page 138

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:

Appendix C. Problem determination 137

 Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you re-create the problem? If so, what steps were performed to re-create the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.
See “Gathering product information for IBM Software Support” on page 115 for
further tips for gathering information for IBM Software Support.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site at
http://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround that you can implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.

138 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Appendix D. 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 to do the following:
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. Refer to the documentation provided by
your operating system for more information.

Magnifying what is displayed on the screen

You can enlarge information on 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 lower the resolution of the screen to enlarge the
font sizes of the text on the screen. Refer to the documentation provided by your
operating system for more information.

© Copyright IBM Corp. 2005 139

140 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Appendix E. 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:

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, 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.

© Copyright IBM Corp. 2005 141

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

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.

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 systems. 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
system 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.

If you are viewing this information in softcopy form, the photographs and color
illustrations might not appear.

Trademarks
IBM, the IBM logo, IBMLink™, AIX, Candle®, CandleNet Portal, DB2,
developerWorks®, eServer™, iSeries™, Lotus®, MVS, OMEGAMON, OS/390,
Passport Advantage®, pSeries®, Rational®, Redbooks™, Tivoli, the Tivoli logo,
Tivoli Enterprise, Tivoli Enterprise Console, WebSphere®, and zSeries® are
trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both.

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.

142 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.

Microsoft, and Windows are registered 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.

Appendix E. Notices 143

144 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
Index
A customizing (continued)
situations 18
accessibility xi, 139
agent
problem determination 128
trace logs 117 D
application version requirements 5 data
attribute groups collecting 19
demand- versus interval-based 131 trace logs 116
list of all 28 viewing 19
Microsoft SQL Configuration 28 data provider
Microsoft SQL Database Detail 29 See agent
Microsoft SQL Database Summary 32 database agent installation problems 124
Microsoft SQL Device Detail 33 Database Check-up and Tune-up action 74
Microsoft SQL Lock Conflict Detail 35 databases
Microsoft SQL Lock Detail 36 attribute groups 90
Microsoft SQL Problem Detail 38 displaying information 90, 96
Microsoft SQL Problem Summary 39 example tasks and workspaces 91
Microsoft SQL Process Detail 40 scenarios for monitoring 91
Microsoft SQL Process Summary 42 workspaces
Microsoft SQL Remote Servers 44 descriptions 22
Microsoft SQL Server Detail 45 workspaces available 90
Microsoft SQL Server Enterprise 47 Databases workspace 22, 90
Microsoft SQL Server Summary 49 demand-based attribute groups 131
Microsoft SQL Statistics Detail 51 detecting problems, modifying situation values 18
Microsoft SQL Statistics Summary 52 directory names, notation xii
Microsoft SQL Table Detail 54 disk capacity planning for historical data 56
Microsoft SQL Table Summary 37 disk space requirements 5
Microsoft SQL Text 55 Dump Database action 75
more information 27 Dump Transaction Log action 78
overview 27
attributes
more information 27 E
overview 27 education
see Tivoli technical training xii
Enterprise Database Summary workspace 22, 90
B Enterprise Errorlog Alerts workspace 23, 92
books Enterprise Processes Summary workspace 24, 96
feedback x Enterprise Server Locking workspace 23, 94
online x Enterprise Server Statistics workspace 25, 99
ordering x Enterprise Server Summary workspace 25, 99
see publications xi environment
built-in problem determination features 115 customizing 17
features 1
monitoring real-time 15
C real-time monitoring 15
environment variables, notation xii
calculate historical data disk space 56 error log alerts
capacity planning for historical data 56 attribute groups 92
collecting data 19 displaying information 92
commands, Take Action 73 example tasks and workspaces 92
components 2 scenarios for monitoring 93
configuration 5 workspaces
contacting support 137 descriptions 23
conventions workspaces available 92
operating system xii Errorlog Alerts workspace 23, 92
typeface xii event
creating user ID 12 mapping 103
customer support events
See support investigating 16
customizing workspaces 16
monitoring environment 17

© Copyright IBM Corp. 2005 145

F locking (continued)
workspaces available 94
features, Monitoring Agent for Microsoft SQL Server 1 locks
files example tasks and workspaces 94
agent trace 117 Log and Space Information workspace 22, 90
installation trace 117 logging
other trace log 118 agent trace logs 117, 118
trace logs 116 built-in features 115
fixes, obtaining 136 installation log files 117
location and configuration of logs 116
trace log files 116
G
gathering support information 115
granting permission 12 M
manuals
feedback x
H online x
historical data ordering x
calculate disk space 56 see publications xi
disk capacity planning 56 memory requirements 5
historical data, collecting and viewing 19 messages
built-in features 115
Microsoft SQL Configuration attribute group 28
I Microsoft SQL Database Detail attribute group 29
Microsoft SQL Database Summary attribute group 32
IBM Software Support Microsoft SQL Device Detail attribute group 33
See support Microsoft SQL Lock Conflict Detail attribute group 35
IBM Tivoli Enterprise Console Microsoft SQL Lock Detail attribute group 36
event mapping 103 Microsoft SQL Problem Detail attribute group 38
IBM Tivoli Monitoring for Databases: Microsoft SQL Server Microsoft SQL Problem Summary attribute group 39
Agent Microsoft SQL Process Detail attribute group 40
performance considerations 130 Microsoft SQL Process Summary attribute group 42
IBM Tivoli Monitoring for Databases: Microsoft SQL Server Microsoft SQL Remote Servers attribute group 44
Agent User’s Guide Microsoft SQL Server Detail attribute group 45
workspaces overview 89 Microsoft SQL Server Enterprise attribute group 47
information centers for support 135 Microsoft SQL Server Summary attribute group 49
information, additional Microsoft SQL Statistics Detail attribute group 51
attributes 27 Microsoft SQL Statistics Summary attribute group 52
policies 87 Microsoft SQL Table Detail attribute group 54
procedural 15 Microsoft SQL Table Summary attribute group 37
situations 60 Microsoft SQL Text attribute group 55
Take Action commands 73 modifying situation values to detect problems 18
workspaces 21 monitoring
installation 5 inactive remote servers 102
log file 117 scenarios for databases 91
problems 124 scenarios for error log alerts 93
interface, user 2 scenarios for locking 95
Internet scenarios for processes 97
for product support 136 scenarios for servers 100
interval-based attribute groups 131 Monitoring Agent for Microsoft SQL Server
investigating an event 16 components 2
features 1
performance considerations 131
K purposes 15
knowledge bases for support 135 using 15
monitoring, viewing the real-time environment 15
MS_SQL Total_Locks_Critical situation 72
L MS_SQL Total_Locks_Warning situation 72
MS_SQL_Block_Critical situation 62
legal notices 141 MS_SQL_Block_Warning situation 62
lock MS_SQL_Cache_Ave_FreePage_Crit situation 62
workspaces MS_SQL_Cache_Ave_FreePage_Warn situation 62
descriptions 23 MS_SQL_Cache_Hit_Ratio_Crit situation 62
locking MS_SQL_Cache_Hit_Ratio_Warn situation 62
attribute groups 94 MS_SQL_Cache_Max_FreePage_Crit situation 62
displaying information 94 MS_SQL_Cache_Max_FreePage_Warn situation 63
scenarios for monitoring 95 MS_SQL_Client_Cnt_Pct_Used_Crit situation 63

146 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
MS_SQL_Client_Cnt_Pct_Used_Warn situation 63
MS_SQL_Collection_Status_Warning situation 63
N
MS_SQL_CPU_Critical situation 63 notation
MS_SQL_CPU_Warning situation 63 environment variables xii
MS_SQL_DB_Error_Status situation 63 path names xii
MS_SQL_DB_free space_Critical situation 64 typeface xii
MS_SQL_DB_free space_Warning situation 64
MS_SQL_DB_free_space_critical policy 87
MS_SQL_DB_Num_Errors_Warning situation 64 O
MS_SQL_DB_Space_Pct_Used_Crit situation 64 online publications
MS_SQL_DB_Space_Pct_Used_Warn situation 64 accessing xi
MS_SQL_DB_Status_Critical situation 64 for support 135
MS_SQL_DB_Suspect_Crit situation 64 operating systems 5
MS_SQL_Device_Free_PCT_Warning situation 65 operation of resource, recovering 16
MS_SQL_Error_Warning situation 65 ordering publications xi
MS_SQL_ErrorLog_Size_Warning situation 65 other requirements 6
MS_SQL_Failed_Jobs_Crit situation 65
MS_SQL_Fragmentation_Crit situation 65
MS_SQL_Fragmentation_Warn situation 65
MS_SQL_IO_Disk_Errors_Crit situation 65
P
MS_SQL_IOERR_Startup_Warning situation 65 path names, for trace logs 116
MS_SQL_IOError_Curintvl_Warning situation 66 path names, notation xii
MS_SQL_Log_free space_Critical situation 66 performance considerations 130
MS_SQL_Log_free space_Warning situation 66 permission, granting 12
MS_SQL_Log_Space_Pct_Used_Crit situation 66 policies
MS_SQL_Log_Space_Pct_Used_Warn situation 66 list of all 87
MS_SQL_Log_Suspend_Warning situation 66 more information 87
MS_SQL_LogonPct_Crit situation 66 MS_SQL_DB_free_space_critical_NAME 87
MS_SQL_LogonPct_Warning situation 67 overview 87
MS_SQL_Network_Read_Rate_Crit situation 67 predefined 87
MS_SQL_Network_Read_Rate_Warn situation 67 problem determination 115, 123
MS_SQL_Network_Write_Rate_Crit situation 67 agents 128
MS_SQL_Network_Write_Rate_Warn situation 67 built-in features 115
MS_SQL_Num_Process_Blocked_Crit situation 67 describing problems 138
MS_SQL_Num_Process_Blocked_Warn situation 67 determining business impact 137
MS_SQL_Oldest_Transaction_Crit situation 68 information centers for 135
MS_SQL_Oldest_Transaction_Warn situation 68 installation 124
MS_SQL_Opt_Stats_Age_Crit situation 68 installation logs 117
MS_SQL_Opt_Stats_Age_Warn situation 68 knowledge bases for 135
MS_SQL_Pct_Block_Warning situation 68 remote deployment 128
MS_SQL_Pct_CPU_Yields_Warning situation 68 situations 130, 132
MS_SQL_Pct_IO_Warning situation 68 submitting problems 138
MS_SQL_PCT_MAX_Locks_Critical situation 69 Take Action commands 134
MS_SQL_PCT_MAX_Locks_Warning situation 69 uninstallation 124
MS_SQL_ProbAge_GT_17_Warning situation 69 uninstallation logs 117
MS_SQL_Proc_Buffs_Active_Crit situation 69 workspaces 129
MS_SQL_Proc_Buffs_Active_Warn situation 69 problems
MS_SQL_Proc_Buffs_Used_Crit situation 69 detecting 18
MS_SQL_Proc_Buffs_Used_Warn situation 69 problems and workarounds 123
MS_SQL_Proc_Cache_Active_Crit situation 70 problems with monitoring SQL Server 135
MS_SQL_Proc_Cache_Active_Warn situation 70 procedures 15
MS_SQL_Proc_Cache_Used_Crit situation 70 Process Holding Lock SQL Text workspace 23, 94
MS_SQL_Proc_Cache_Used_Warn situation 70 processes
MS_SQL_Process_Blocked_Warning situation 70 attribute groups 97
MS_SQL_Process_Infected_Warning situation 70 example tasks and workspaces 97
MS_SQL_Processes_Bad_Warning situation 71 scenarios for monitoring 97
MS_SQL_Processes_Stop_Warning situation 71 workspaces
MS_SQL_ProcessLockSleep_Warning situation 70 descriptions 24
MS_SQL_ProcessOthSleep_Warning situation 71 workspaces available 96
MS_SQL_Rem_Serv_Stat_Critical situation 71 Processes workspace 24, 97
MS_SQL_Repl_Latency_Crit situation 71 publications
MS_SQL_Repl_Latency_Warn situation 71 accessing online xi
MS_SQL_Status_Critical situation 72 feedback x
MS_SQL_Status_Inactive situation 72 for support 135
online x
ordering x, xi
purposes
collecting data 19

Index 147
purposes (continued) situations (continued)
customizing monitoring environment 17 MS_SQL_DB_Status_Critical 64
investigating events 16 MS_SQL_DB_Suspect_Crit 64
monitoring with custom situations 18 MS_SQL_Device_Free_PCT_Warning 65
problem determination 115 MS_SQL_Error_Warning 65
recovering resource operation 16 MS_SQL_ErrorLog_Size_Warning 65
viewing data 19 MS_SQL_Failed_Jobs_Crit 65
viewing real-time monitoring environment 15 MS_SQL_Fragmentation_Crit 65
MS_SQL_Fragmentation_Warn 65
MS_SQL_IO_Disk_Errors_Crit 65
Q MS_SQL_IOERR_Startup_Warning 65
MS_SQL_IOError_Curintvl_Warning 66
queries, using attributes 27
MS_SQL_Log_free space_Critical 66
MS_SQL_Log_free space_Warning 66
MS_SQL_Log_Space_Pct_Used_Crit 66
R MS_SQL_Log_Space_Pct_Used_Warn 66
real-time data, viewing 15 MS_SQL_Log_Suspend_Warning 66
Rebuild Fragmented Indexes action 81 MS_SQL_LogonPct_Crit 66
recovering the operation of a resource 16 MS_SQL_LogonPct_Warning 67
Refresh Query Optimizer Statistics action 83 MS_SQL_Network_Read_Rate_Crit 67
remote deployment MS_SQL_Network_Read_Rate_Warn 67
problem determination 128 MS_SQL_Network_Write_Rate_Crit 67
requirements MS_SQL_Network_Write_Rate_Warn 67
application versions 5 MS_SQL_Num_Process_Blocked_Crit 67
disk space 5 MS_SQL_Num_Process_Blocked_Warn 67
memory 5 MS_SQL_Oldest_Transaction_Crit 68
operating system 5 MS_SQL_Oldest_Transaction_Warn 68
other 6 MS_SQL_Opt_Stats_Age_Crit 68
resource, recovering operation 16 MS_SQL_Opt_Stats_Age_Warn 68
MS_SQL_Pct_Block_Warning 68
MS_SQL_Pct_CPU_Yields_Warning 68
S MS_SQL_Pct_IO_Warning 68
MS_SQL_PCT_MAX_Locks_Critical 69
Server Configuration workspace 25, 98
MS_SQL_PCT_MAX_Locks_Warning 69
Server Locking workspace 23, 94
MS_SQL_ProbAge_GT_17_Warning 69
Server Statistics workspace 25, 99
MS_SQL_Proc_Buffs_Active_Crit 69
servers
MS_SQL_Proc_Buffs_Active_Warn 69
attribute groups 99
MS_SQL_Proc_Buffs_Used_Crit 69
displaying information 98
MS_SQL_Proc_Buffs_Used_Warn 69
example tasks and workspaces 99
MS_SQL_Proc_Cache_Active_Crit 70
scenarios for monitoring 100
MS_SQL_Proc_Cache_Active_Warn 70
workspaces 98
MS_SQL_Proc_Cache_Used_Crit 70
descriptions 25
MS_SQL_Proc_Cache_Used_Warn 70
Servers workspace 25, 99
MS_SQL_Process_Blocked_Warning 70
situations
MS_SQL_Process_Infected_Warning 70
general problem determination 132
MS_SQL_Processes_Bad_Warning 71
more information 60
MS_SQL_Processes_Stop_Warning 71
MS_SQL Total_Locks_Critical 72
MS_SQL_ProcessLockSleep_Warning 70
MS_SQL Total_Locks_Warning 72
MS_SQL_ProcessOthSleep_Warning 71
MS_SQL_Block_Critical 62
MS_SQL_Rem_Serv_Stat_Critical 71
MS_SQL_Block_Warning 62
MS_SQL_Repl_Latency_Crit 71
MS_SQL_Cache_Ave_FreePage_Crit 62
MS_SQL_Repl_Latency_Warn 71
MS_SQL_Cache_Ave_FreePage_Warn 62
MS_SQL_Status_Critical 72
MS_SQL_Cache_Hit_Ratio_Crit 62
MS_SQL_Status_Inactive 72
MS_SQL_Cache_Hit_Ratio_Warn 62
overview 59
MS_SQL_Cache_Max_FreePage_Crit 62
predefined 60
MS_SQL_Cache_Max_FreePage_Warn 63
specific problem determination 130
MS_SQL_Client_Cnt_Pct_Used_Crit 63
values, modifying 18
MS_SQL_Client_Cnt_Pct_Used_Warn 63
situations, using attributes 27
MS_SQL_Collection_Status_Warning 63
SQL Server problems 135
MS_SQL_CPU_Critical 63
SQL Text for Process ID workspace 24, 94, 97
MS_SQL_CPU_Warning 63
Start SQL Server action 84
MS_SQL_DB_Error_Status 63
Stop SQL Server action 85
MS_SQL_DB_free space_Critical 64
support
MS_SQL_DB_free space_Warning 64
about 135
MS_SQL_DB_Num_Errors_Warning 64
contacting 137
MS_SQL_DB_Space_Pct_Used_Crit 64
describing problems 138
MS_SQL_DB_Space_Pct_Used_Warn 64

148 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide
support (continued) views (continued)
determining business impact of problems 137 Enterprise Server Statistics workspace 25
gathering information for 115 Enterprise Server Summary workspace 25
information centers for 135 Errorlog Alerts workspace 23
knowledge bases for 135 Log and Space Information workspace 22
obtaining fixes 136 Process Holding Lock SQL Text workspace 23
on Internet 136 Processes workspace 24
submitting problems 138 Server Configuration workspace 25
weekly update option 136 Server Locking workspace 23
Server Statistics workspace 25
Servers workspace 25
T SQL Text for Process ID workspace 24
Take Action commands 16
Database Check-up and Tune-up 74
Dump Database 75 W
Dump Transaction Log 78 weekly update support option 136
list of all 73 Windows agent installation problems 124
more information 73 Windows operating systems 5
overview 73 workarounds 123
predefined 73 agents 128
problem determination 134 remote deployment 128
Rebuild Fragmented Indexes 81 situations 130
Refresh Query Optimizer Statistics 83 Take Action commands 134
Start SQL Server 84 workspaces 129
Stop SQL Server 85 workspaces
Update Space Usage Information 85 database examples 91
target application databases 22, 90
problems 135 Databases 22
tasks descriptions 89
examples for database workspaces 91 determining which to use 89
examples for error log alert workspaces 92 Enterprise Database Summary 22
examples for lock workspaces 94 Enterprise Errorlog Alerts 23
examples for process workspaces 97 Enterprise Processes Summary 24
examples for server workspaces 99 Enterprise Server Locking 23
tasks for using 15 Enterprise Server Statistics 25
Tivoli software information center xi Enterprise Server Summary 25
Tivoli technical training xii error log alert examples 92
trace logs 116 error log alerts 23, 92
directories 116 Errorlog Alerts 23
trademarks 142 event 16
training, Tivoli technical xii list of all 21
transport command 135 lock 23
troubleshooting 115 lock examples 94
typeface conventions xii locking 94
Log and Space Information 22
more information 21
U overview 21
predefined 21
uninstallation
problem determination 129
log file 117
process examples 97
problems 124
Process Holding Lock SQL Text 23
Update Space Usage Information action 85
processes 24, 96
user ID, creating 12
Processes 24
user interfaces options 2
scenarios
databases 91
error log alerts 93
V locks 95
values, modifying situations 18 processes 97
variables, notation for xii servers 100
viewing data 19 Server Configuration 25
viewing real-time monitoring environment 15 server examples 99
views Server Locking 23
Databases workspace 22 Server Statistics 25
Enterprise Database Summary workspace 22 servers 25, 98
Enterprise Errorlog Alerts workspace 23 Servers 25
Enterprise Processes Summary workspace 24 SQL Text for Process ID 24
Enterprise Server Locking workspace 23 where to find information 89

Index 149
150 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User’s Guide



Printed in USA

SC32-9452-00