Tivoli Monitoring for Databases: Microsoft SQL Server Agent

Transcription

1 Tivoli Monitoring for Databases: Microsoft SQL Server Agent Version User s Guide SC

2

3 Tivoli Monitoring for Databases: Microsoft SQL Server Agent Version User s Guide SC

4 Note Before using this information and the product it supports, read the information in Appendix H, Notices, on page 193. This edition applies to version 6.2 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.

5 Contents Tables vii Chapter 1. Overview of the Monitoring Agent for Microsoft SQL Server IBM Tivoli Monitoring overview Features of the Monitoring Agent for Microsoft SQL Server New in this release Components of Monitoring Agent for Microsoft SQL Server User interface options Chapter 2. Requirements and configuration for the monitoring agent. 5 Requirements for the monitoring agent Configuration Granting permissions Basic installation and configuration Reconfiguration Configuration settings Starting and stopping the Monitoring Agent for Microsoft SQL Server Setting up the Monitoring Agent for Microsoft SQL Server in a cluster environment Chapter 3. How to use a monitoring agent View real-time data that the agent collects Investigate an event Recover the operation of a resource Customize your monitoring environment Monitor with custom situations that meet your requirements Collect and view historical data Chapter 4. Workspaces reference About workspaces More information about workspaces Organization of the predefined workspaces Databases Information workspace Enterprise Database Summary workspace...29 Enterprise Errorlog Alerts workspace Enterprise Server Locking workspace Enterprise Processes Summary workspace...30 Enterprise Server Summary workspace Enterprise Server Statistics workspace Enterprise Servers Overview Errorlog Alerts workspace MS SQL Server Historical Summarized Availability workspace MS SQL Server Historical Summarized Availability Daily workspace MS SQL Server Historical Summarized Availability Hourly workspace MS SQL Server Historical Summarized Availability Weekly workspace MS SQL Server Historical Summarized Capacity workspace MS SQL Server Historical Summarized Capacity Daily workspace MS SQL Server Historical Summarized Capacity Hourly workspace MS SQL Server Historical Summarized Capacity Weekly workspace MS SQL Server Historical Summarized Performance workspace MS SQL Server Historical Summarized Performance Daily workspace MS SQL Server Historical Summarized Performance Hourly workspace MS SQL Server Historical Summarized Performance Weekly workspace MS SQL Server Overview Log and Space Information workspace Process Holding Lock SQL Text workspace...37 Processes workspace Server Configuration workspace Server Locking workspace Server Statistics workspace Server Summary workspace SQL Text for Process ID workspace Chapter 5. Attributes reference About attributes More information about attributes Attribute groups and attributes for the Monitoring Agent for Microsoft SQL Server MS SQL Configuration attributes MS SQL Database Detail attributes MS SQL Database Summary attributes MS SQL Device Detail attributes MS SQL Filegroup Detail attributes MS SQL Job Detail attributes MS SQL Job Summary attributes MS SQL Lock Conflict Detail attributes MS SQL Lock Detail attributes MS SQL Lock Summary attributes MS SQL Lock Resourcetype Summary attributes 57 MS SQL Problem Detail attributes MS SQL Problem Summary attributes MS SQL Process Detail attributes MS SQL Process Summary attributes MS SQL Remote Servers attributes MS SQL Server Detail attributes MS SQL Server Enterprise View attributes...70 MS SQL Server Summary attributes MS SQL Services Detail attributes MS SQL Statistics Detail attributes MS SQL Statistics Summary attributes Copyright IBM Corp. 2005, 2007 iii

6 MS SQL Table Detail attributes MS SQL Text attributes VMS SQL Remote Servers attributes VMS SQL Server Enterprise View attributes..86 Disk capacity planning for historical data Chapter 6. Situations reference About situations More information about situations Predefined situations MS_SQL_Block_Critical MS_SQL_Block_Warning MS_SQL_Cache_Ave_FreePage_Crit MS_SQL_Cache_Ave_FreePage_Warn MS_SQL_Cache_Hit_Ratio_Crit MS_SQL_Cache_Hit_Ratio_Warn MS_SQL_Cache_Max_FreePage_Crit MS_SQL_Cache_Max_FreePage_Warn MS_SQL_Client_Cnt_Pct_Used_Crit MS_SQL_Client_Cnt_Pct_Used_Warn MS_SQL_Collection_Status_Warning MS_SQL_CPU_Critical MS_SQL_CPU_Warning MS_SQL_DB_Error_Status MS_SQL_DB_Freespace_Critical MS_SQL_DB_Freespace_Warning MS_SQL_DB_Num_Errors_Warning MS_SQL_DB_Space_Pct_Used_Warn MS_SQL_DB_Space_Pct_Used_Crit MS_SQL_DB_Status_Crit MS_SQL_DB_Suspect_Crit MS_SQL_Device_Free_PCT_Warning MS_SQL_Error_Warning MS_SQL_ErrorLog_Size_Warning MS_SQL_Failed_Jobs_Crit MS_SQL_Fragmentation_Crit MS_SQL_Fragmentation_Warn MS_SQL_IO_Disk_Errors_Crit MS_SQL_IOERR_Startup_Warning MS_SQL_IOError_Curintvl_Warning MS_SQL_Log_Freespace_Critical MS_SQL_Log_Freespace_Warning MS_SQL_Log_Space_Pct_Used_Crit MS_SQL_Log_Space_Pct_Used_Warn MS_SQL_Log_Suspend_Warning MS_SQL_LogonPct_Crit MS_SQL_LogonPct_Warning MS_SQL_Network_Read_Rate_Crit MS_SQL_Network_Read_Rate_Warn MS_SQL_Network_Write_Rate_Crit MS_SQL_Network_Write_Rate_Warn MS_SQL_Num_Process_Blocked_Crit MS_SQL_Num_Process_Blocked_Warn MS_SQL_Oldest_Transaction_Crit MS_SQL_Oldest_Transaction_Warn MS_SQL_Opt_Stats_Age_Crit MS_SQL_Opt_Stats_Age_Warn MS_SQL_Pct_Block_Warning MS_SQL_Pct_CPU_Yields_Warning MS_SQL_Pct_IO_Warning MS_SQL_PCT_MAX_Locks_Critical MS_SQL_PCT_MAX_Locks_Warning MS_SQL_ProbAge_GT_Warning MS_SQL_Proc_Buffs_Active_Crit MS_SQL_Proc_Buffs_Active_Warn MS_SQL_Proc_Buffs_Used_Crit MS_SQL_Proc_Buffs_Used_Warn MS_SQL_Proc_Cache_Active_Crit MS_SQL_Proc_Cache_Active_Warn MS_SQL_Proc_Cache_Used_Crit MS_SQL_Proc_Cache_Used_Warn MS_SQL_Process_Blocked_Warning MS_SQL_Process_Infected_Warning MS_SQL_Processes_Bad_Warning MS_SQL_Processes_Stop_Warning MS_SQL_ProcessLockSleep_Warning MS_SQL_ProcessOthSleep_Warning MS_SQL_Rem_Serv_Stat_Critical MS_SQL_Repl_Latency_Crit MS_SQL_Repl_Latency_Warn MS_SQL_Status_Critical MS_SQL_Status_Inactive MS_SQL_Total_Locks_Critical MS_SQL_Total_Locks_Warning Chapter 7. Take Action commands reference About Take Action commands More information about Take Action commands 105 Predefined Take Action commands User ID and password combinations Database Check-up and Tune-up action Dump Database action Dump Transaction Log action Rebuild Fragmented Indexes action Refresh Query Optimizer Statistics action Start SQL Server action Stop SQL Server action Update Space Usage Information action Chapter 8. Policies reference About policies More information about policies Predefined policies MS_SQL_DB_free_space_critical Appendix A. Upgrading for warehouse summarization Tables in the warehouse Effects on summarized attributes Upgrading your warehouse with limited user permissions Appendix B. Workspaces Determining which category of workspaces to use 125 Determining where to find the information you need Displaying information for databases Determining the predefined workspace to use 126 Relationship to the attribute groups iv IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

7 Example tasks and the predefined workspaces available Typical scenarios Displaying information for error log alerts Determining the predefined workspace to use 128 Relationship to the attribute groups Example tasks and the predefined workspaces available Typical scenarios Displaying information for locks Determining the predefined workspace to use 130 Relationship to the attribute groups Example tasks and the predefined workspaces available Typical scenarios Displaying information for processes Determining the predefined workspace to use 132 Relationship to the attribute groups Example tasks and the predefined workspaces available Typical scenarios Displaying information for Microsoft SQL servers 134 Determining the predefined workspace to use 134 Relationship to the attribute groups Example tasks and predefined workspaces available Typical scenarios Appendix C. IBM Tivoli Enterprise Console event mapping Appendix D. Monitoring Agent for Microsoft SQL Server data collection. 157 Collection processes Attribute groups that gather data from Microsoft SQL Server SELECT statements and stored procedures Attribute groups that gather data from operating system or MS SQL Server files Appendix E. Problem determination 161 Gathering product information for IBM Software Support Built-in problem determination features Problem classification Trace logging Overview of log file management Examples of trace logging Principal trace log files Enabling detailed tracing in the collector trace log 166 Option one: modify the settings file Option two: modify the environment variables 166 Setting RAS trace parameters Objective Background Information Before you begin After you finish Procedure Problems and workarounds Installation and configuration problem determination Agent problem determination Problem determination for remote deployment 177 Workspace problem determination Situation problem determination Take Action command problem determination 183 Problem determination for SQL Server Support for problem solving Using IBM Support Assistant Obtaining fixes Receiving weekly support updates Contacting IBM Software Support Appendix F. Documentation library 189 Monitoring Agent for Microsoft SQL Server library 189 Prerequisite publications Related publications Other sources of documentation Appendix G. Accessibility Navigating the interface using the keyboard Magnifying what is displayed on the screen Appendix H. Notices Trademarks Index Contents v

8 vi IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

9 Tables 1. Supported operating system and application versions for the Monitoring Agent for Microsoft SQL Server Memory, disk space, and other requirements for the Monitoring Agent for Microsoft SQL Server.6 3. Additional authorization Names and descriptions of configuration settings for each interface Interfaces for starting and stopping the Monitoring Agent for Microsoft SQL Server locally and remotely View real-time data Investigating an event Recover the operation of a resource Customizing your monitoring environment Monitor with custom situations Collect and view historical data Capacity planning for historical data User ID and password combinations Index and table updates Index and table updates Index and table updates Time periods and suffixes for summary tables and views Additional columns to report summarization information Determining which category of workspaces to use Determining where to find the information you need Determining the workspace to use for databases Workspaces for databases and the relationship to attribute groups Example tasks and the predefined workspaces available for databases Determining the workspace to use for error log alerts Workspaces for error log alerts and the relationship to attribute groups Example tasks and the predefined workspaces available for error log alerts Determining the workspace to use for locks Workspaces for locks and the relationship to attribute groups Example tasks and the predefined workspaces available for locks Determining the workspace to use for processes Workspaces for processes and the relationship to attribute groups Example tasks and the predefined workspaces available for processes Determining the workspace to use for servers Workspaces for servers and the relationship to attribute groups Example tasks and predefined workspaces available for servers Overview of attribute groups to event classes and slots When data is collected and cache duration for attribute groups Key aspects of data gathering for attribute groups Data that is accessed by attribute groups that gather data from operating system or Microsoft SQL Server files Information to gather before contacting IBM Software Support Trace log files for troubleshooting agents Problems and solutions for installation and configuration on UNIX and Windows systems Problems and solutions for installation and configuration of the Monitoring Agent for Microsoft SQL Server General problems and solutions for uninstallation General agent problems and solutions Remote deployment problems and solutions Workspace problems and solutions Specific situation problems and solutions Problems with configuring situations that you solve in the Situation Editor Problems with configuration of situations that you solve in the Workspace area Problems with configuration of situations that you solve in the Manage Tivoli Enterprise Monitoring Services window Take Action commands problems and solutions SQL Server problems and solutions Copyright IBM Corp. 2005, 2007 vii

10 viii IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

11 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 189 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,

12 New in this release 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. For version 6.2 of the Monitoring Agent for Microsoft SQL Server, the following enhancements have been made since version 6.1: v Additional supported operating systems as listed in Requirements for the monitoring agent on page 5 v Additional application versions as listed in Requirements for the monitoring agent on page 5 v New attribute groups Microsoft SQL Filegroup Detail Microsoft SQL Job Summary Microsoft SQL Job Detail Microsoft SQL Lock Resource Type Summary Microsoft SQL Services Detail v New or changed attributes in the following attribute groups Microsoft SQL Database Detail Microsoft SQL Lock Summary Microsoft SQL Problem Detail Microsoft SQL Process Detail Microsoft SQL Server Summary Microsoft SQL Statistics Summary v Updated koq.baroc file to support TEC event mapping v Enabled for IBM Tivoli License Manager reporting Components of Monitoring Agent for Microsoft SQL Server After you install the Monitoring Agent for Microsoft SQL Server (product code "koq" or "oq") as directed in the IBM Tivoli Monitoring Installation and Setup Guide, you have an environment that contains the client, server, and monitoring agent implementation for IBM Tivoli Monitoring that contains the following components: 2 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

13 User interface options 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, which collects and distributes data to a Tivoli Enterprise Monitoring Server. v Operating system agents and application agents installed on the systems or subsystems you want to monitor. These agents collect and distribute data to the Tivoli Enterprise Monitoring Server. v Tivoli Data Warehouse for storing historical data collected from agents in your environment. The data warehouse is located on a DB2, Oracle, or Microsoft SQL database. To collect information to store in this database, you must install the Warehouse Proxy agent. To perform aggregation and pruning functions on the data, install the Warehouse Summarization and Pruning agent. v Tivoli Enterprise Console event synchronization component for synchronizing the status of situation events that are forwarded to the event server. When the status of an event is updated because of IBM Tivoli Enterprise Console rules or operator actions, the update is sent to the monitoring server, and the updated status is reflected in both the Situation Event Console and the Tivoli Enterprise Console event viewer. For more information, see the IBM Tivoli Monitoring Installation and Setup Guide. 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 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

14 4 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

15 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 on page 7 Granting permissions on page 8 Basic installation and configuration on page 12 Reconfiguration on page 13 Configuration settings on page 13 Starting and stopping the Monitoring Agent for Microsoft SQL Server on page 15 Setting up the Monitoring Agent for Microsoft SQL Server in a cluster environment on page 16 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 Tables 1 and 2. This monitoring agent supports monitoring for a maximum of 16 instances of the application versions of MS SQL Server running on the same system. Table 1 shows which application versions run on the different operating system versions. The bit level in the columns for the Microsoft SQL Server versions refers to the monitored application. Note: For the most current information about the operating systems that are supported, see support/tivoli_supported_platforms.html. Table 1. Supported operating system and application versions for the Monitoring Agent for Microsoft SQL Server Operating system versions 2000 Enterprise and Standard Editions Microsoft SQL Server versions 2005 Enterprise and Standard Editions Windows 2000 Server (32-bit) 32-bit 32-bit Windows 2000 Advanced Server (32-bit) Windows Server 2003 Data Center Edition (32-bit) Windows Server 2003 Data Center Edition (x86-64) Windows Server 2003 Data Center Edition SP1 for Itanium (64-bit) 32-bit 32-bit 32-bit 32-bit 32-bit 32-bit 64-bit Not supported 64-bit Copyright IBM Corp. 2005,

16 Table 1. Supported operating system and application versions for the Monitoring Agent for Microsoft SQL Server (continued) Operating system versions Windows Server 2003 Enterprise Edition (32-bit) Windows Server 2003 Enterprise x64 Edition (x86-64) Windows Server 2003 for Itanium (64-bit) Windows Server 2003 Standard Edition (32-bit) Windows Server 2003 Standard x64 Edition (x86-64) 2000 Enterprise and Standard Editions 32-bit 32-bit Microsoft SQL Server versions 2005 Enterprise and Standard Editions 32-bit 32-bit 64-bit Not supported 64-bit 32-bit 32-bit Note: For all operating systems, the monitoring agent is a 32-bit binary. 32-bit 32-bit 64-bit This monitoring agent has the requirements listed in Table 2. Table 2. Memory, disk space, and other requirements for the Monitoring Agent for Microsoft SQL Server Operating system Windows Memory v 32 MB RAM v 150 MB virtual memory, plus 5 MB for each agent instance Disk space v 132 MB for monitoring agent product files if no other agent is installed. 4 MB if other agents such as the OS agent are already installed. v 2 MB agent support files installed on the management server and 1 MB for agent support files installed on the portal server v Agent depot 195 MB (agent deployment 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 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

17 Table 2. Memory, disk space, and other requirements for the Monitoring Agent for Microsoft SQL Server (continued) Other requirements v For remote administration, IBM Tivoli Monitoring: Windows OS Agent must be installed and running. v Grant permissions for Microsoft SQL Server. See Granting permissions on page 8. v The SQL Server must be configured for the SQL Server authentication mode. v Run the Monitoring Agent for Microsoft SQL Server services under an account with Windows Administrator authority. v This monitoring agent requires that the following performance objects are enabled: System Process Thread Memory Physical Disk SQLServer:Buffer Manager SQLServer:General Statistics SQLServer:Locks SQLServer:Databases SQLServer:Cache Manager SQLServer:Memory Manager SQLServer:Replication Dist. SQLServer:Replication Logreader SQLServer:Replication Merge SQLServer:Access Methods If you have a named SQL Server instance, then SQLServer is replaced with MSSQL$instance_name. Configuration When performing the steps to install and configure the Monitoring Agent for Microsoft SQL Server as described in the IBM Tivoli Monitoring Installation and Setup Guide, Installing monitoring agents, use the agent-specific configuration information provided in this chapter. Agent-specific information is provided for the following procedures: v Granting permissions on page 8 v Basic installation and configuration on page 12 Local on page 12 - Using the Managed Tivoli Enterprise Monitoring Services window on page 12 - Silent installation on page 12 Remote on page 12 - Using the Tivoli Enterprise Portal on page 12 - Using the tacmd command line on page 12 v Reconfiguration on page 13 v Configuration settings on page 13 v Starting and stopping the Monitoring Agent for Microsoft SQL Server on page 15 Chapter 2. Requirements and configuration for the monitoring agent 7

18 Granting v Setting up the Monitoring Agent for Microsoft SQL Server in a cluster environment on page 16 Never attempt to start the monitoring agent until you have completed the configuration steps appropriate to installation of the monitoring agent. permissions The Microsoft SQL Server user ID must have access to the Monitoring Agent for Microsoft SQL Server. The procedure described in this section includes creating a Microsoft SQL Server user ID and granting permission to the new user ID, which is the minimum authority required. The SQL Server ID used to configure this monitoring agent must have the following SQL Server authorities: v Required authorization roles Database roles: Public access is required for each database that is being monitored. Server roles: No special Server Role is required. v Optional authorization roles Each Take Action command has a separate set of authorization roles that are required for the SQL Server credentials to pass to the Take Action command. These authorities are listed for each Take Action command in Chapter 7, Take Action commands reference, on page 105. The monitored attributes in Table 3 require additional authorization for the SQL Server ID used to configure the Monitoring Agent for Microsoft SQL Server. If you want to monitor any of these attributes, configure the SQL Server ID used by the monitoring agent with the corresponding authorization. Table 3. Additional authorization Navigation item, Attribute workspace, view Situation Authorization Table Detail attribute group: All attributes in group None predefined v MS_SQL_Fragmentation _Warn v v v MS_SQL_Fragmentation _Crit MS_SQL_Opt_Stats_Age _Warn MS_SQL_Opt_Stats_Age _Crit Database Role: db_owner (for each database) OR Server Role: System Administrator 8 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

19 Table 3. Additional authorization (continued) Attribute Server Detail attribute group: v Procedure Buffers Pct Active v Procedure Buffer Pct Used v Procedure Buffers Total v Procedure Cache Pages v Procedure Cache Pct Used v Procedure Cache Pct Active Navigation item, workspace, view Situation Authorization None predefined v MS_SQL_Proc_Buffs_ Active_Warn SQL Text attribute group v Server Locking, Process Holding Lock SQL Text, 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 v v v v v v v MS_SQL_Proc_Buffs_ Active_Crit MS_SQL_Proc_Buffs_ Used_Warn MS_SQL_Proc_Buffs_ Used_Crit MS_SQL_Proc_Cache_ Active_Warn MS_SQL_Proc_Cache_ Active_Crit MS_SQL_Proc_Cache_ Used_Warn MS_SQL_Proc_Cache_ Used_Crit Database Role: db_owner (on default database associated with the SQL Server ID) OR Server Role: System Administrator None predefined Server Role: System Administrator Chapter 2. Requirements and configuration for the monitoring agent 9

20 Table 3. Additional authorization (continued) Attribute Job Detail attribute group Job Summary attribute group Navigation item, workspace, view Situation Authorization None predefined None predefined Server Role: Server Administrators This authorization enables data collection for all SQL Server jobs. OR Database Role (msdb database): public An SQL Server Agent proxy account must also be defined. The agent can collect job data only on the jobs that this SQL Server ID owns. OR Database Role (msdb database): SQLAgentUserRole (SQL Server 2005 only) The agent can collect job data only on the jobs that this SQL Server ID owns. OR Database Role (msdb database): SQLAgentReaderRole (SQL Server 2005 only) The agent can collect job data on all SQL Server jobs. OR Database Role (msdb database): SQLAgentOperatorRole (SQL Server 2005 only) The agent can collect job data on all SQL Server jobs. You must have the Database administrator authorization role to perform the procedure to grant permissions. Before beginning this procedure, perform the appropriate installation procedures in the IBM Tivoli Monitoring Installation and Setup Guide. If you are configuring locally, perform this procedure between the steps for installing and configuring. If you are configuring remotely, perform this procedure after installing and configuring. Use the procedure for the SQL Server that you are configuring, SQL Server 2000 or SQL Server IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

21 Procedure for SQL Server Click Start Programs Microsoft SQL Server Enterprise Manager to display the SQL Server Enterprise Manager window. 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 in order to give permission to each selected 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 inchapter 7, Take Action commands reference, on page 105. Also, see Table 3 on page 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. Procedure for SQL Server Click Start Programs Microsoft SQL Server 2005 SQL Server Management Studio. 2. In the Tree tab, select Logins in the Security folder (Console Root WindowsName Security Logins). 3. Right-click Logins and select New Login. 4. Select the General Folder option, 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. Select the User Mapping option. 8. In the Specify which databases can be accessed by this login area, select the check box for each database that you currently have in order to give permission to each selected database. 9. Select the Server Roles option. 10. If you are running a Take Action command, you might need additional authority. See the Take Action command descriptions in Chapter 7, Take Action commands reference, on page 105. Also, see Table 3 on page Click OK to display the Confirm Password window. 12. Retype the password you typed for the user ID. 13. Click OK to display the new user ID in the Logins list. When you finish the procedure, configure the Monitoring Agent for Microsoft SQL Server so you can start the monitoring agent and begin monitoring your Microsoft SQL Server application. Chapter 2. Requirements and configuration for the monitoring agent 11

22 Basic installation and configuration You can install and configure the Monitoring Agent for Microsoft SQL Server locally or remotely using a GUI or command line. Local If you are installing and configuring locally, use the steps in the IBM Tivoli Monitoring Installation and Setup Guide, Installing monitoring agents." Also, use the agent-specific configuration information in this section and in Table 4 on page 14 for the Manage Tivoli Enterprise Monitoring Services window. Using the Managed Tivoli Enterprise Monitoring Services window: After you select the databases that you want to monitor in the Configure Database Agents window, the following fields are populated in the Database Server Properties window: v Server Name v Database Version v Home Directory v Error Log File You must enter your login and password in the Login and Password fields using only ASCII characters in the fields in this window. Silent installation: If you are performing a silent installation using a response file, see the IBM Tivoli Monitoring Installation and Setup Guide, "Performing a silent installation of IBM Tivoli Monitoring." Remote If you are installing and configuring remotely, use the steps in the IBM Tivoli Monitoring Installation and Setup Guide, "Deploying non-os agents." Also, use the agent-specific configuration information in this section and in Table 4 on page 14 for the following interfaces: v Tivoli Enterprise Portal v tacmd command line Using the Tivoli Enterprise Portal: To deploy this monitoring agent remotely using the command line, use the procedure, Deploying through the portal, in the IBM Tivoli Monitoring Installation and Setup Guide. In the New Managed System Configuration window, use the settings in Table 4 on page 14 for the Tivoli Enterprise Portal Database Server Properties tab and the Agent tab Run as information. Using the tacmd command line: To deploy this monitoring agent remotely using the command line, use the procedure, Deploying through the command line, in the IBM Tivoli Monitoring Installation and Setup Guide. Also, use the agent-specific configuration information in Table 4 on page 14 for the tacmd addsystem command. The IBM Tivoli Monitoring Command Reference has complete information about the tacmd addsystem command. Use the -t or --type TYPE parameter to specify the Monitoring Agent for Microsoft SQL Server that you are configuring: OQ. Specify the properties with the -p or -property option. For example: 12 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

23 tacmd addsystem -t OQ -n Primary:myhostname:NT -p DBSETTINGS.db_login=sa DBSETTINGS.db_password=sapwd DBSETTINGS.db_ver= DBSETTINGS.db_home=c:\Program Files\Microsoft SQL Server\MSSQL DBSETTINGS.db_errorlog=C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG INSTANCE=MyServer The parameters in the example are shown on separate lines for clarity. When typing the command, type all of the parameters on one line. Reconfiguration If you need to reconfigure the Monitoring Agent for Microsoft SQL Server, ensure that the steps for installing the monitoring agent in the IBM Tivoli Monitoring Installation and Setup Guide were completed. Local If you are reconfiguring an instance locally, use the Manage Tivoli Enterprise Monitoring Services window. See Table 4 on page 14 for the configuration settings. Remote If you are reconfiguring remotely, use one of the following interfaces: v tacmd command line Use the configuresystem command. See the IBM Tivoli Monitoring Command Reference Guide for complete information about this command. When reconfiguring, enter the information for the property that you are changing as well as the INSTANCE property. v Tivoli Enterprise Portal See Table 4 on page 14 for the configuration settings. Configuration settings Table 4 on page 14 contains a list of the configuration settings for each of the interfaces where you can specify these settings and a description of each setting. Chapter 2. Requirements and configuration for the monitoring agent 13

24 Table 4. Names and descriptions of configuration settings for each interface Interfaces where configuration settings are specified Manage Tivoli Enterprise Monitoring Services window Tivoli Enterprise Portal Server Name Database Server Instance Name 1 Login Database Server User Id 1 tacmd command line INSTANCE= InstanceName DBSETTINGS.db_ login=userid Description 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. The name must be short enough to fit within the total managed system name, which must be between 2 and 32 characters in length. SQL Server user ID to be used to connect to the SQL Server. See Granting permissions on page 8 for more information. Examples If the SQL Server instance being monitored is the default SQL Server instance and the hostname is popcorn, 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. Password Password 1 Database Version Home Directory Database Server Version 1 Database Server Home Directory Path 1 DBSETTINGS.db_ password= Password DBSETTINGS.db_ ver=version DBSETTINGS.db_ home= HomeDirPath Use only ASCII characters. Password for the SQL Server user ID Use only ASCII characters. SQL Server version. See the application versions in Table 2 on page 6 for valid values. Install directory Server instance monitored. 8 OR 9 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 in the format C:\Program Files\Microsoft SQL Server\ MSSQL$instance_name, where instance_name is the SQL Server instance name. 14 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

25 Table 4. Names and descriptions of configuration settings for each interface (continued) Interfaces where configuration settings are specified Manage Tivoli Enterprise Monitoring Services window Error Log File Tivoli Enterprise Portal Database Server Error Log File 1 tacmd command line DBSETTINGS.db_ errorlog= ErrorlogPath Description Fully qualified location and name of the SQL Server Error Log Examples The default error log path for the default SQL Server 2000 instance is C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG. Right-click the agent instance, and select Change Startup... to set the ID under which the agent instance is to run. 1 2 Use this account 2 If selecting this option complete the following fields as described: v Account: ID under which the agent instance is to run v Password and Confirm password: password Database Server Properties tab Agent tab Run as area _WIN32_ STARTUP_. Username and _WIN32_ STARTUP_. Password or _WIN32_ STARTUP_. LocalSystem The ID and passwords must have Windows Administrator authority for the system on which the monitoring agent is to run. See Granting permissions on page 8 for information about the required user ID permissions. The LocalSystem account is the default ID used by the monitoring agent. 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. The following tacmd command property, explicitly sets the user ID for the monitoring agent to the LocalSystem account: _WIN32_STARTUP_. LocalSystem=1. When setting the _WIN32_STARTUP_. LocalSystem property, the _WIN32_STARTUP_. InteractWithDesktop property must also be set. Starting and stopping the Monitoring Agent for Microsoft SQL Server Table 5 on page 16 shows which interfaces you can use on Windows operating systems locally or remotely to start the monitoring agent. Chapter 2. Requirements and configuration for the monitoring agent 15

26 Table 5. Interfaces for starting and stopping the Monitoring Agent for Microsoft SQL Server locally and remotely Local Remote v Manage Tivoli Enterprise Monitoring Services v tacmd startagent v tacmd stopagent v tacmd restartagent v Tivoli Enterprise Portal v tacmd startagent v tacmd stopagent v tacmd restartagent Manage Tivoli Enterprise Monitoring Services Enter only ASCII characters in the fields for the Manage Tivoli Enterprise Monitoring Services window. Tivoli Enterprise Portal See the "Working with monitoring agents," "Starting and stopping a monitoring agent" in the IBM Tivoli Monitoring Administrator s Guide for information about using the Tivoli Enterprise Portal to start or stop the monitoring agent. tacmd command line In the following examples, the tacmd command is used to start, stop, or restart the MS SQL Server instance named Primary. The instance is on a Windows system where myhostname is the short hostname for the system on which the monitoring agent is running: v v Local tacmd startagent -t oq tacmd stopagent -t oq tacmd restartagent -t oq Remote tacmd stopagent -t oq -n Primary:hostname:NT tacmd startagent -t oq -n Primary:hostname:NT tacmd restartagent -t oq -n Primary:hostname:NT For information about using the tacmd commands, see the IBM Tivoli Monitoring Command Reference. Setting up the Monitoring Agent for Microsoft SQL Server in a cluster environment To use this monitoring agent in a Microsoft Cluster Server environment requires special configuration. The IBM Tivoli Monitoring Installation and Setup Guide contains an overview of clustering. The information provided here is specifically for installing and setting up the Monitoring Agent for Microsoft SQL Server in a Microsoft Cluster Server environment. Requirements You can set up a cluster environment for Microsoft SQL Server 2000 Enterprise Edition and Microsoft SQL Server In addition to installing and setting up the Monitoring Agent for Microsoft SQL Server, the following three additional steps are required for the cluster environment: 16 IBM Tivoli Monitoring for Databases: Microsoft SQL Server Agent: User s Guide

27 v Setting CTIRA_HOSTNAME to a common value for all monitoring agents (usually the cluster name) v Setting CTIRA_HIST_DIR to a common disk location if history is stored at the monitoring agents (if history for the Monitoring Agent for Microsoft SQL Server is configured to be stored at the monitoring agent) v Creating a monitoring agent cluster resource in the Resource Group of the Virtual Server3 On Windows systems, IBM Tivoli Monitoring requires that monitoring agents are installed in the same directory path as the OS agent. Therefore, each node in a cluster must have installed all monitoring agents (on the nodes system disk) that are required to support the cluster applications that can run on that cluster node. Installing and configuring the monitoring agent Install the Monitoring Agent for Microsoft SQL Server on each node in the cluster where it is possible for the Microsoft SQL Virtual Servers to run. 1. Setting CTIRA_HOSTNAME Because there can be multiple instances of the Monitoring Agent for Microsoft SQL Server, each instance must be configured with a CTIRA_HOSTNAME. Set the CTIRA_HOSTNAME environmental variable to the name of the Microsoft Cluster Server cluster for all monitoring agents running in that cluster. By setting the CTIRA_HOSTNAME for all agents in the cluster to the same name, you can navigate to all of the monitoring agents for that cluster in the Tivoli Enterprise Portal. When deciding on the value for CTIRA_HOSTNAME, consider that the managed system name is comprised of three parts: CTIRA_SUBSYSTEM_ID, CTIRA_HOSTNAME, and CTIRA_NODETYPE. Also, the name is limited to 31 characters. By default for the Microsoft SQL Server Agent, CTIRA_NODETYPE is set to MSS, and CTIRA_SUBSYSTEM_ID is set to the Microsoft SQL Virtual Server name. The CTIRA_SUBSYSTEM_ID is used to distinguish the multiple instances of the Monitoring Agent for Microsoft SQL Server. 2. Setting CTIRA_HIST_DIR If history for the Monitoring Agent for Microsoft SQL Server is configured to be stored at the monitoring agent, each instance of the monitoring agent must be configured with common CTIRA_HIST_DIR that points to a shared disk directory. If history is stored at the Tivoli Enterprise Management Server, setting CTIRA_HIST_DIR is not required. Storing history at the Tivoli Enterprise Management Server puts a higher burden on that server. 3. Creating a monitoring agent cluster resource Set each Monitoring Agent for Microsoft SQL Server startup parameter to manual so the cluster resource can control the starting and stopping of the monitoring agent. After these parameters are set for each Monitoring Agent for Microsoft SQL Server, instance cluster resources to control the monitoring agents must be created. Each Monitoring Agent for Microsoft SQL Server is comprised of two Windows Services: KOQAGENTx and KOQCOLLx, where x is the agent instance number. Example of Windows Services names: Monitoring Agent for Microsoft SQL Server SQLTEST Monitoring Agent for Microsoft SQL Server - Collector SQLTEST Monitoring Agent for Microsoft SQL Server SQLTEST2 Chapter 2. Requirements and configuration for the monitoring agent 17