SQL SVR KM

www.bmc.com

PATROL for Microsoft SQL ServerGetting Started

Supporting

PATROL for Microsoft SQL Server version 4.3Oct 2007

Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

Copyright 2007 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

DB2 is a registered trademark of International Business Machines Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

UNIX is a registered trademark of The Open Group.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

3Customer support

You can obtain technical support by using the BMC Software Customer Support website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.

Support website

You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can

read overviews about support services and programs that BMC offers find the most current information about BMC products search a database for issues similar to yours and possible solutions order or download product documentation download products and maintenance report an issue or ask a question subscribe to receive proactive e-mail alerts when new product notices are released find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, and

telephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to [email protected]. (In the subject line, enter SupID:, such as SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

product information

product name product version (release number) license number and password (trial or permanent)

operating system and environment information

machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or

maintenance level

sequence of events leading to the issue

commands and options that you used

messages received (and the time and date that you received them)

product error messages messages from the operating system, such as file system full messages from related software

4 PATROL for Microsoft SQL Server Getting Started

ContentsChapter 1 Product components and capabilities 15

Overview and intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Discovers SQL Servers automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Provides global channel access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Supports and monitors clustered environments . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Monitors cache-hit ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Monitors page reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors free buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors space used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors blocking locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors row-level locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors user connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors log space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors files and file groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors error logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Applications and icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Icon hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 2 Installing and migrating PATROL for Microsoft SQL Server 33

Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Checking for product patches or fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Determining how you should monitor a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Determining whether to install locally or remotely . . . . . . . . . . . . . . . . . . . . . . . . . 40Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . 40Determining the PATROL security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Contents 5

Determining how to upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Determining the roles that each computer performs . . . . . . . . . . . . . . . . . . . . . . . . 42Determining where to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Planning for the installation of a language pack . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing for the first time or upgrading over an existing installation . . . . . . . . . . . . 46

6Installing a language pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Upgrading and saving customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Preparing to upgrade and migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Migrating customizations with the PATROL Configuration Manager . . . . . . . . . 51Migrating customizations manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Creating an installation package of the migrated and merged KM . . . . . . . . . . . . 53First-time installation using the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . 54Importing a CD or customized installation package into Distribution Server . . . 55Installing with the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Installing the online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installing the UNIX version of the Help browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Setting environment variables for the browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Additional considerations for using online Help for UNIX . . . . . . . . . . . . . . . . . . 59

Uninstalling PATROL for Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 3 Configuring PATROL for Microsoft SQL Server 63

Setting up and configuring PATROL for Microsoft SQL Server . . . . . . . . . . . . . . . . . . 64Loading and unloading PATROL for Microsoft SQL Server . . . . . . . . . . . . . . . . . 64Verifying that the SQL Server is discovered and online . . . . . . . . . . . . . . . . . . . . . 69Configuring a SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Configuring a SQL Server instance without an sa password . . . . . . . . . . . . . . . . . 76Accelerating discovery and reviewing error messages . . . . . . . . . . . . . . . . . . . . . . 79

Reviewing the default settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80SQL Server Agent monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Error log monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Database monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Object monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82File and file group monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Replication monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82User and process monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Parameter defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Setting up PATROL in a clustered environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Determining how you should configure a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 86Monitoring a cluster by using a virtual PATROL Agent . . . . . . . . . . . . . . . . . . . . . 87Installing and configuring a cluster with a virtual PATROL Agent . . . . . . . . . . . 87Monitoring a cluster by using a PATROL Agent on each node . . . . . . . . . . . . . . . 89Installing and configuring a node-level cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Reviewing how PATROL for Microsoft SQL Server handles clustering events. . 90

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 4 Using PATROL Configuration Manager with PATROL for Microsoft SQL Server 95

Overview of PATROL Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Saving backups in PATROL Configuration Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 97Configuring for PATROL for Microsoft SQL Server instances . . . . . . . . . . . . . . . . . . . 97Modifying PATROL for Microsoft SQL Server instances. . . . . . . . . . . . . . . . . . . . . . . . 98

Do not deactivate application classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99PATROL for Microsoft SQL Server Getting Started

Do not modify configuration variables that are for internal use only. . . . . . . . . . 99Modifying an instance and deploying the changes to other instances . . . . . . . . 100Adding or modifying pconfig variables manually. . . . . . . . . . . . . . . . . . . . . . . . . 102

Modifying parameters using PATROL Configuration Manager and PATROL for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Deactivating parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Changing parameter polling cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Changing parameter thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Modifying parameter properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Verifying changes to configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 5 Working with PATROL for Microsoft SQL Server 115

Monitoring SQL Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Excluding SQL Servers from monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Starting and stopping the monitoring of a SQL Server . . . . . . . . . . . . . . . . . . . . . 118Starting and stopping a SQL Server from PATROL. . . . . . . . . . . . . . . . . . . . . . . . 118Reviewing the status of a SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Viewing reports about a SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Changing the PATROL login account for a server . . . . . . . . . . . . . . . . . . . . . . . . . 120Changing a server instance name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Enabling SQL Server instance discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Monitoring SQL Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Enabling the monitoring of the SQL Server Agent. . . . . . . . . . . . . . . . . . . . . . . . . 122Starting and stopping the SQL Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Using the SQL Server Agent parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Monitoring the SQL Server Agent job failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Filtering SQL Server Agent job failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Setting up SQL Server Agent jobs for monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 124

Monitoring error logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Enabling the monitoring of error logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Setting up error log monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Viewing reports about the error logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Reviewing the status of an error log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127About the error log parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Monitoring databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Starting and stopping the monitoring of databases . . . . . . . . . . . . . . . . . . . . . . . . 130Checking the consistency of a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Adding the PATROL user to a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Reviewing the status of a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Viewing reports about databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Monitoring files and file groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Enabling the monitoring of files and file groups . . . . . . . . . . . . . . . . . . . . . . . . . . 133Reviewing the status of files and file groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Viewing reports about files and file groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Monitoring objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Setting up the monitoring of objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Reviewing the status of an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Viewing reports about objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Contents 7

8Monitoring replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Enabling the monitoring of replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Reviewing the status of Subscribers or Published Articles . . . . . . . . . . . . . . . . . . 136Viewing reports about Subscribers and Published Articles . . . . . . . . . . . . . . . . . 136Using SQL commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Monitoring users and processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Changing the automatic monitoring of users and processes. . . . . . . . . . . . . . . . . 138Monitoring specific users and processes manually . . . . . . . . . . . . . . . . . . . . . . . . 141Using parameters to monitor specific users and processes . . . . . . . . . . . . . . . . . . 142Reviewing the status of a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Viewing reports about users and processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Killing a process from PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Creating customized reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Accessing the predefined reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Adding customized reports to the predefined list . . . . . . . . . . . . . . . . . . . . . . . . . 144

Working with parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Viewing parameter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Activating and deactivating parameters and alarms . . . . . . . . . . . . . . . . . . . . . . . 145Clearing, snoozing, and blacking out parameter alarms . . . . . . . . . . . . . . . . . . . . 146Refreshing parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Creating customized parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Creating and managing parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Accessing the predefined parameter charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Using automatic recovery actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Reviewing the ARA settings and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Viewing the parameter recovery process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Using the ARA Settings menu commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Parameters affected in general user monitoring mode . . . . . . . . . . . . . . . . . . . . . 155Parameters partially affected in a recovery action . . . . . . . . . . . . . . . . . . . . . . . . . 155

Viewing SQL information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Viewing SQL commands with SQL Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Managing the global channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Accessing the Global Channel menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . 158Monitoring the Global Channel lock requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Where to go from here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Appendix A Accessing menu commands, InfoBoxes, and online Help 161

Accessing KM commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Appendix B Parameter definitions and defaults 165

Column headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Abbreviations defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Parameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168PATROL for Microsoft SQL Server Getting Started

Appendix C Consumer-collector parameter dependencies 197

Appendix D Agent configuration variables 203

Index 221Contents 9

FiguresWindow showing PATROL icons for an instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24PATROL for Microsoft SQL Server icon hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Collector application, parameters, and a graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Server application menu in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29InfoBox for a Server application instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Computer, SQL Server, and application icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Database application instance icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72SQL Server Instance Setup dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Configure => Get command in PATROL Configuration Manager . . . . . . . . . . . . . . 101Parameter recovery process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Figures 11

TablesPATROL for Microsoft SQL Server applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21System requirements for PATROL for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . 34Supported configurations for a clustered environment . . . . . . . . . . . . . . . . . . . . . . . . 39Choosing an installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42SQL Server Config Setup authentication mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Supported configurations for a clustered environment . . . . . . . . . . . . . . . . . . . . . . . . 86Variables that are for internal use only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99ARA options, their values, and the value of the araAction variable . . . . . . . . . . . . . 104PATROL for Microsoft SQL Server parameters with fixed thresholds . . . . . . . . . . . 110Parameters that monitor the SQL Server Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Parameters that monitor the SQL Server and SQL Server Agent error logs . . . . . . 128Database consistency menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Parameters affected in the general monitoring user mode . . . . . . . . . . . . . . . . . . . . . 155Parameters partially affected in a recovery action . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Tasks for displaying SQL for processes and users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Accessing KM commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Accessing online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163PATROL for Microsoft SQL Server parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Consumer-collector parameter dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Agent configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Obsolete variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Tables 13

1 PC h a p t e r 1roduct components and capabilities

This chapter presents the following topics:

Overview and intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Discovers SQL Servers automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Provides global channel access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Monitors cache-hit ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Monitors page reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors free buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors blocking locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors user connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors log space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors space used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Monitors row-level locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Monitors files and file groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Applications and icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Icon hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Chapter 1 Product components and capabilities 15

Overview and intended audience

16

O

Fverview and intended audienceThe PATROL for Microsoft SQL Server product operates with a PATROL Agent and one or more of the PATROL consoles to monitor Microsoft SQL Server products. PATROL for Microsoft SQL Server contains knowledge in the form of applications, commands, parameters, and recovery actions. PATROL uses this knowledge to monitor, analyze, and manage Microsoft SQL Servers.

PATROL for Microsoft SQL Server was created for use by Microsoft SQL Server database administrators, system administrators, and PATROL administrators in the daily administration and management of the Microsft SQL Server products. PATROL for Microsoft SQL Server and PATROL for Microsoft SQL Server Getting Started were created for users who have an understanding of the underlying Microsoft SQL Server products. If you have any questions regarding the operation or management of Microsoft SQL Server, refer to the Microsoft SQL Server manuals and website.

eaturesPATROL for Microsoft SQL Server discovers SQL Servers automatically, provides global channel access to SQL Servers, and provides commands that allow you to perform SQL Server administrative functions directly from the PATROL consoles. PATROL for Microsoft SQL Server also helps you to monitor and manage the following key features:

global channel access clustered environments cache-hit ratio page-reads free buffers space used blocking locks row-level locking user connections log space files and file groups error logsPATROL for Microsoft SQL Server Getting Started

Discovers SQL Servers automatically

D

P

S

Miscovers SQL Servers automatically

The MSSQL_Server (Server) application automatically discovers the SQL Servers in your environment. This application detects the presence of the SQL Servers and creates an icon for each.

rovides global channel access

PATROL for Microsoft SQL Server establishes a global channel to each SQL Server that it discovers in your environment. Through this global channel, PATROL for Microsoft SQL Server gathers the information that PATROL uses to monitor those SQL Servers.

To help maintain the global channel, PATROL for Microsoft SQL Server provides the following features:

locks that synchronize access to the global channel automatic close and reopen feature to recover from global channel problems status of the global channel method for resetting the global channel

upports and monitors clustered environments

PATROL for Microsoft SQL Server monitors SQL Servers (see the release notes for specific versions) in a clustered environment. See Setting up PATROL in a clustered environment on page 85 or the PATROL for Microsoft SQL Server online Help for more information.

onitors cache-hit ratio

PATROL for Microsoft SQL Server monitors the cache-hit ratio, which provides an important benchmark about data throughput and overall database performance.

The cache-hit ratio expresses the relationship between the number of requests for data that are read from cache and the total number of requests for data. A drop in this ratio indicates an increase in the number of requests that the SQL Server must read from the physical disk (I/O) because the pages containing the requested data are not Chapter 1 Product components and capabilities 17

Monitors page reads

18

M

M

M

Mstored in cache memory. When this ratio drops below a predetermined low, PATROL for Microsoft SQL Server triggers alarms and warnings. Once notified, administrators can improve database performance by adjusting the available cache or the amount of physical RAM used by SQL Server to optimize availability and throughput.

onitors page reads

PATROL for Microsoft SQL Server tracks how long it takes a SQL Server to read a page of data from the physical disk into cache memory or from memory to the physical disk. With this information, PATROL for Microsoft SQL Server can identify the areas where excessive I/O waits are taking place.

onitors free buffers

PATROL for Microsoft SQL Server monitors the percentage of free buffers (or database pages) available in memory (see the NumberofFreeBuffers parameter). If this number is too low, excessive waits, disk read, and disk write times result. If SQL Servers memory size is greater than physical RAM, paging can occur, which degrades database performance. Administrators can use this information to maintain an optimum number of free buffers for peak database performance, and to keep page faults to a minimum. When demand exceeds availability during normal or subnormal periods of activity, this parameter can also indicate a need for additional resource tuning or an increase in capacity to maintain user productivity.

onitors space used

PATROL for Microsoft SQL Server monitors the percentage of database space used (SpaceUsedPCT) and the megabytes of database space used (SpaceUsedMB). Administrators can use these values to gauge and maintain database space.

onitors blocking locks

PATROL for Microsoft SQL Server monitors the total number of blocking locks. A high number of blocking locks could indicate an increase in the number of processes currently waiting for a specific page or table that is exclusively locked by another process. Using this information, administrators can more accurately develop capacity plans to determine whether additional resources should be allocated to increase database availability and user productivity.PATROL for Microsoft SQL Server Getting Started

Monitors row-level locking

M

M

M

Monitors row-level locking

PATROL for Microsoft SQL Server monitors row-level locking. The following parameters provide information on row-level locking:

RIDLockAvgWaitTime provides the average amount of wait time (in milliseconds) that was caused by row ID lock requests.

RIDLockRequestsPerSec provides the number of new row ID locks and lock conversions that the lock manager requested per second.

RIDLockRequestWaitPercent provides the percentage of row ID lock requests that required a caller to wait.

onitors user connections

By tracking the number of user connections to SQL Server, PATROL for Microsoft SQL Server provides an important indicator of ongoing demand versus capacity. When the SQL Server is running low on available user connections, the UserConnections parameter goes into an alarm state. Because each connection requires memory, an increase in the number of user connections can coincide with a decrease in performance, which indicates the need to restrict user connections, lower the number of worker threads, or increase memory.

onitors log space

When the transaction log becomes completely full, SQL Server cannot run because it cannot record modifications to data (update, modify, delete, or add) and, therefore, you cannot dump the transaction log. PATROL for Microsoft SQL Server tracks the percentage of log space that is used with the LogSpaceUsedPCT parameter and the megabytes of log space used with the LogSpaceUsedMB parameter. The values provided by these parameters help you manage transaction log space.

onitors files and file groups

SQL Server stores data and log files in files and file groups. A database can have one or more file groups, and each file group can have one or more files that are associated with it. PATROL for Microsoft SQL Server can monitor files and file groups, but this feature is turned off by default. For details about this feature, see Monitoring files and file groups on page 133.Chapter 1 Product components and capabilities 19

Monitors error logs

20

M

P

Aonitors error logs

The MSSQL_SERVER_ERRORLOG (Error Log) application class provides menu commands, parameters, and InfoBox items specifically designed to help you monitor the SQL Server and SQL Server Agent error logs for the error log strings and problems you want to monitor. For details about this feature, see Monitoring error logs on page 124.

roduct componentsPATROL for Microsoft SQL Server provides functionality in the form of parameters, menu commands, and InfoBoxes that are organized and presented under application classes. Most application classes are represented by icons. The following sections describe each of these functional components of PATROL for Microsoft SQL Server and how they are accessed.

pplications and icons

PATROL for Microsoft SQL Server applications fall into the following types:

Table 1 contains a short description of each application class and a graphic of the icon that represents each application class. See Icon hierarchy on page 24 for a description of how these icons appear in your interface.

Application type Description

discovery discovers the SQL Servers in your environment and stores the configuration and setup information

administrative stores the SQL Server logins

container contains and organizes the instances and parameters for specific functions

functional uses specific parameters, menu commands, and InfoBox items to provide information about a specific database objectPATROL for Microsoft SQL Server Getting Started

Applications and icons

Ta

A

Se

A

(Tic

L

(Tic

A

C

C

CFor more detailed information about the application classes, see the online Help for PATROL for Microsoft SQL Server and Appendix A, Accessing menu commands, InfoBoxes, and online Help.

ble 1 PATROL for Microsoft SQL Server applications (Part 1 of 4)

pplication name and icon Definition

rver The MSSQL_SERVER (Server) discovery application is the main application class for PATROL for Microsoft SQL Server. This application discovers the SQL Servers in your environment and provides the setup or configuration of PATROL for Microsoft SQL Server and the SQL Server control functions.

For more about monitoring SQL Servers, see Monitoring SQL Servers on page 117.

dministrative

his application does not display an on.)

The MSSQL_SERVER_ADMIN (Administration) administrative application stores a second user ID and password that PATROL uses to connect to the selected SQL Server.

ogin Management

his application does not display an on.)

The MSSQL_SERVER_LOGIN_MGMT (Login Management) administrative application handles the security modes when you configure PATROL for Microsoft SQL Server.

vailability The MSSQL_SERVER_AVAILABILITY (Availability) container application holds the parameters that pertain to the availability of the selected server.

For more information about the Availability application parameters, see Appendix B, Parameter definitions and defaults.

ache The MSSQL_SERVER_CACHE (Cache) container application holds the parameters that pertain to the database cache for the selected server.

For more information about the Cache application parameters, see Appendix B, Parameter definitions and defaults.

apacity The MSSQL_SERVER_CAPACITY (Capacity) container application holds the parameters that pertain to the capacity of the selected server, such as the number of user connections, the number of locks remaining, and the number of idle processes.

For more information about the Capacity application parameters, see Appendix B, Parameter definitions and defaults.

ollectors The MSSQL_SERVER_COLLECTORS (Collectors) container application holds the collector and the standard collector parameters that set the values for the majority of the consumer parameters.

For more information about the Collectors application parameters, see Appendix B, Parameter definitions and defaults.Chapter 1 Product components and capabilities 21


22

D

D

E

Fi

Fi

L

M

Ta

Aatabase The MSSQL_SERVER_DB (Database) functional application provides specific parameters, menu commands, and InfoBox items pertaining to the database that the Database application icon represents.

Database monitoring is not activated unless you select automatic database monitoring or a database for monitoring. For more about database monitoring, see Monitoring databases on page 129.

isk The MSSQL_SERVER_DISK (Disk) container application holds the parameters that pertain to the disk i/o for the selected server.

For more information about the Disk application parameters, see Appendix B, Parameter definitions and defaults.

rror Log The MSSQL_SERVER_ERROR_LOG (Error Log) functional application provides specific parameters, menu commands, and InfoBox items that pertain to the error log that the instance represents.

Error log monitoring is partially enabled by default. To enable all of the functionality of error log monitoring, see Monitoring error logs on page 124.

le The MSSQL_SERVER_FILE (File) functional application provides specific parameters, menu commands, and InfoBox items pertaining to the file that it represents.

File monitoring is disabled by default. For more information, see Monitoring files and file groups on page 133.

legroup The MSSQL_SERVER_FILEGROUP (Filegroup) functional application provides specific parameters, menu commands, and InfoBox items pertaining to the file group that it represents.

File group monitoring is disabled by default. For more information, see Monitoring files and file groups on page 133 and the online Help for PATROL for Microsoft SQL Server.

ocks The MSSQL_SERVER_LOCKS (Locks) container application holds the parameters that pertain to the locks for the selected server.

For more information about the Locks application parameters, see Appendix B, Parameter definitions and defaults.

SSQL_SERVER The MSSQL_SERVER_SQLSERVER_SETUP (MSSQL_SERVER) container application holds the SQL Server instances discovered on a monitored host.



SQLErrorLogPATROL for Microsoft SQL Server Getting Started


N

O

Pe

P

P

Su

Ta

Aetwork The MSSQL_SERVER_NETWORK (Network) container application holds the parameters that pertain to the network i/o for the selected server.

For more information about the Network application parameters, see Appendix B, Parameter definitions and defaults.

bjects The MSSQL_SERVER_OBJECTS (Objects) application is a functional application that provides specific parameters and InfoBox items that pertain to the objects (tables and indexes) selected for monitoring.The Objects application icon does not display unless you select objects for monitoring. For more information, see Monitoring objects on page 134 and the online Help for PATROL for Microsoft SQL Server.

rformance The MSSQL_SERVER_PERFORMANCE (Performance) application is a container application that holds the parameters that pertain to the performance of the selected server.

For more information about the Performance application parameters, see Appendix B, Parameter definitions and defaults.

rocedure Cache The MSSQL_SERVER_PROC_CACHE (Procedure Cache) application is a container application that holds the parameters that pertain to procedure cache for the selected server.

For more information about the Procedure Cache application parameters, see Appendix B, Parameter definitions and defaults.

ublished The MSSQL_SERVER_PUBLISHED (Published) application is a functional application that provides specific parameters and InfoBox items that pertain to the articles published for replication.

Replication monitoring is disabled by default. For more information, see Monitoring replication on page 135 and the online Help for PATROL for Microsoft SQL Server.

bscribers The MSSQL_SERVER_SUBSCRIBERS (Subscribers) application is a functional application that provides specific parameters and InfoBox items that pertain to the database servers that subscribe to receive published articles in your SQL Server replication environment.

Replication monitoring is disabled by default. For more information, see Monitoring replication on page 135 and the online Help for PATROL for Microsoft SQL Server.


pplication name and icon DefinitionChapter 1 Product components and capabilities 23

Icon hierarchy

24

Ic

U

U

Ta

Aon hierarchy

Figure 1 displays the PATROL Console for Microsoft Windows Server (Developer mode) window.

Figure 1 Window showing PATROL icons for an instance

ser-Defined Counters The MSSQL_SERVER_USER_DEF_CNTRS (User-Defined Counters) application is a container application that holds the ten user-defined counters of the selected server.

For more information about the User-Defined Counters application parameters, see Appendix B, Parameter definitions and defaults.

sers The MSSQL_SERVER_USERS (Users) application is a functional application that provides specific parameters, menu commands, and InfoBox items to monitor the SQL Server users or processes.

Users application icons do not display unless you select User Instance as a problem alert method in the Configure Auto User Monitoring dialog box, or you manually select specific users or processes for monitoring. For more information, see Monitoring users and processes on page 137 and the online Help for PATROL for Microsoft SQL Server.

NOTE The SQL Server icon looks the same, but it is displayed by itself or with other applications in the PATROL Central Operator Microsoft Windows Edition, PATROL Central Operator Web Edition, and PATROL Console for UNIX.



SQL Server icon

operatingsystemicons

PATROLAgenticonPATROL for Microsoft SQL Server Getting Started

Icon hierarchyPATROL for Microsoft SQL Server provides a hierarchy of icons that groups all Server application icons under the MSSQL_SERVER application icon. When you double-click on a Server application icon, a window opens that contains other applications.

Figure 2 displays all of the PATROL for Microsoft SQL Server application icons to demonstrate the hierarchy of the applications.

Figure 2 PATROL for Microsoft SQL Server icon hierarchy

Server application icon

Users application icon

Published application icon

Subscribers application icon

Database application icons

Filegroup application iconFile application icon

Objects application icon

File application icon

Error Log application icon

SQLErrorLogChapter 1 Product components and capabilities 25

Parameters

26

Parameters

A parameter is a command that periodically obtains data on a monitored system resource. Parameter data values are collected, summarized, and stored on the computer where the PATROL Agent resides. The collected parameter information is available for review by a PATROL console.

PATROL for Microsoft SQL Server organizes parameters into application classes by function or by the objects that they monitor. PATROL uses several types of parameters and stores parameter history data in a file.

See Appendix B, Parameter definitions and defaults, Appendix C, Consumer-collector parameter dependencies,and the online Help for PATROL for Microsoft SQL Server for more information about the PATROL for Microsoft SQL Server parameters. For more general information about parameters and their functions, see the PATROL user guide for your console.

Parameter types

PATROL for Microsoft SQL Server uses the following types of parameters:

A collector parameter executes commands at regular intervals (poll times) to gather data that it sends to the consumer parameters. Collector parameters do not display the values that they collect, nor do they generate alarms or recovery actions.

A standard parameter collects a single value of data as numeric or text and displays that value. Many of the standard parameters used by PATROL for Microsoft SQL Server have collector properties; they execute commands and gather the data that consumer parameters display.

A consumer parameter displays a value that was collected by a collector parameter (or a standard parameter with collector properties) and can generate alarms or warnings and recovery actions if those values exceed predefined thresholds. Consumer parameters do not issue commands.

The use of standard parameters with collector properties (standard collectors) and consumer parameters enables PATROL to set an almost unlimited number of parameters with one data retrieval query to the server, creating an extremely efficient and flexible data retrieval system.

The Collectors application contains all but two of the standard collectors used by PATROL for Microsoft SQL Server. UserColl is found under the User application and ErrorLog Coll is found under the Error log application. Double-clicking the Collector application icon opens a window that contains all of the standard collector parameters and one standard parameter, CheckConfiguration. PATROL for Microsoft SQL Server Getting Started

ParametersThese standard collectors are represented by an icon that contains a check mark and an X. The check mark is green when the standard collector parameter is in an okay state and the X turns red when the standard collector parameter goes into an alarm state. (See the PATROL user guide for your console for detailed information on alarm states and icons.) These standard collector parameters go into an alarm state if a scheduled collection fails. Double-clicking on a standard collector icon opens a graph or timetable that displays a mark for each collection that the standard collector parameter completed. Standard collector parameters do not display the data that they collect, but display only information about their collections.

The data collected by the standard collector parameters is distributed to related consumer parameters. Appendix C, Consumer-collector parameter dependencies,provides a table that cross-references the consumer parameters with the standard collector parameter that sets its value. Disabling a standard collector parameter also disables the consumer parameters that it sets.

Figure 3 shows the Collector Application icon, the parameters it contains, and an example of a graph that standard collector parameters use to display collection information.

Figure 3 Collector application, parameters, and a graph

The timetable displays a mark for each data collection cycle that the standard collector parameter completed.

Double-clicking on one of the standard collectors opens a graph or timetable for that standard collector parameter.

Double-clicking the Collector application icon displays the standard collector icons.Chapter 1 Product components and capabilities 27

Menu commands

28

MParameter History file

All parameter history data is stored in a single file named param.hist, which is located in the following directory on the computer where the PATROL Agent resides:

stored in a single file named param.hist, which is located in the following directory on the computer where the PATROL Agent resides:

$PATROL_HOME\log\history\computername\portnumber

See the PATROL user guide for your console for detailed information about the parameter history file.

enu commands

The PATROL for Microsoft SQL Server menu commands allow you to perform the following tasks:

define and manage PATROL for Microsoft SQL Server manage your SQL Servers from PATROL view reports about your SQL Servers

The Server application class provides the majority of the PATROL for Microsoft SQL Server menu commands. The following application classes provide menu commands more specific to the objects that these application classes represent:

Database Filegroup Error Log Published Subscribers UsersPATROL for Microsoft SQL Server Getting Started

Menu commandsFigure 4 shows a Server application icon, the PATROL Console for Microsoft Windows Servers menu, and the Server application menu. Right-clicking the Server application icon opens the console menu, and KM Commands is an option available from that menu. You can access the Database, Filegroup, Published, Subscribers, and Users menus from their respective application icons.

Figure 4 Server application menu in Windows

The Server application menu shown in Figure 4 is at the top level of the menu tree hierarchy for the Server application menu.

PATROL for Microsoft SQL Server online Help provides further details about menu commands. For information about how to access menu commands and online Help from the various PATROL consoles, see Appendix A, Accessing menu commands, InfoBoxes, and online Help.

Server application icon

console menu

Server application menuChapter 1 Product components and capabilities 29

InfoBoxes

30

InfoBoxes

PATROL for Microsoft SQL Server uses InfoBoxes to provide attributes specific to the objects in your SQL Servers. InfoBoxes are tables of attributes accessed from the icons that represent parameters and application classes. The PATROL consoles and PATROL Agent populate all of the attributes that appear in the parameter InfoBoxes and some of the attributes, such as icon type or status, that appear in the application InfoBoxes.

In each of the application InfoBoxes, the items generated by PATROL for Microsoft SQL Server appear below the items generated by the PATROL console, and they are preceded by a check mark (PATROL Console for Microsoft Windows) or are separated from the console items by a horizontal rule (PATROL Console for UNIX). The PATROL Central Operator consoles differentiate between the items in a similar fashion. Figure 5 is an example of an InfoBox for a Server application instance.

Figure 5 InfoBox for a Server application instance

The attributes that populate the InfoBoxes are gathered and updated periodically. Some of the attributes that appear in the application InfoBoxes remain static (for example, SQL Server Name) and some of the attributes change as your SQL Server environment changes (for example, Blackout End Time). Each InfoBox provides an Update button that you can use to force a refresh of the attributes in that InfoBox.

PATROL for Microsoft SQL Server online Help provides further details about the application InfoBoxes. For information about how to access InfoBoxes and online Help, see Appendix A, Accessing menu commands, InfoBoxes, and online Help.

Check marked items

Update buttonPATROL for Microsoft SQL Server Getting Started

Related publications

R

Welated publicationsThe PATROL for Microsoft SQL Server online Help is installed with the product when you install from the Electronic Product Download (EPD) website. The following publications contain information about installing, migrating, and deploying PATROL for Microsoft SQL Server:

Distribution Server Getting Started Installation Utility Reference Manual PATROL Configuration Manager User Guide

For more detailed information about the PATROL Agent and consoles, see the documentation CDs provided with your PATROL Agent and console products and the online Help for those products.

here to go from hereThe following table suggests topics that you should read next:

Topic Source of information

how to install and migrate PATROL for Microsoft SQL Server

Chapter 2, Installing and migrating PATROL for Microsoft SQL Server on page 33

how to setup and configure PATROL for Microsoft SQL Server

Chapter 3, Configuring PATROL for Microsoft SQL Server, and PATROL for Microsoft SQL Server online Help

how to use PATROL Configuration Manager with PATROL for Microsoft SQL Server to change configuration variables or parameter properties

Chapter 4, Using PATROL Configuration Manager with PATROL for Microsoft SQL Server on page 95

how to use PATROL for Microsoft SQL Server functionality to monitor and manage SQL Servers

Chapter 5, Working with PATROL for Microsoft SQL Server, and PATROL for Microsoft SQL Server online Help

how to access the KM menu commands, InfoBoxes, and online Help

Appendix A, Accessing menu commands, InfoBoxes, and online Help

definitions and default values for parameters

Appendix B, Parameter definitions and defaults

consumer and collector parameter dependencies

Appendix C, Consumer-collector parameter dependencies

PATROL Agent configuration variables Appendix D, Agent configuration variables

detailed descriptions of the applications, menu commands, parameters, and InfoBoxes

PATROL for Microsoft SQL Server online HelpChapter 1 Product components and capabilities 31

Where to go from here


2 IMC h a p t e r 2nstalling and migrating PATROL for icrosoft SQL Server

This chapter presents the following topics:

Verifying installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Determining how you should monitor a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Determining whether to install locally or remotely . . . . . . . . . . . . . . . . . . . . . . . . . 40Determining the version of the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . 40Determining the PATROL security levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Determining how to upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Planning for the installation of a language pack . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing for the first time or upgrading over an existing installation . . . . . . . . . . . . 46Installing a language pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Upgrading and saving customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Preparing to upgrade and migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Migrating customizations with the PATROL Configuration Manager. . . . . . . . . 51Migrating customizations manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Creating an installation package of the migrated and merged KM. . . . . . . . . . . . 53First-time installation using the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . 54Importing a CD or customized installation package into Distribution Server. . . 55Installing with the Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Installing the online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installing the UNIX version of the Help browser. . . . . . . . . . . . . . . . . . . . . . . . . . . 57Setting environment variables for the browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Additional considerations for using online Help for UNIX . . . . . . . . . . . . . . . . . . 59

Uninstalling PATROL for Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Chapter 2 Installing and migrating PATROL for Microsoft SQL Server 33

To uninstall PATROL for Microsoft SQL Server from a Windows environment 60To uninstall PATROL for Microsoft SQL Server from a UNIX environment. . . . 60

Where to go from here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Verifying installation requirements

34

V

Ta

Re

SQpob

Panerifying installation requirementsBefore installing PATROL for Microsoft SQL Server, verify that the target computer meets the minimum installation requirements listed in Table 2.

NOTE For specific version numbers for the products that are supported by PATROL for Microsoft SQL Server, refer to the release notes for the version of PATROL for Microsoft SQL Server that you are using.

ble 2 System requirements for PATROL for Microsoft SQL Server (Part 1 of 4)

source Requirements Comments

L Server erformance jects

The Microsoft SQL Servers you want to monitor must have the SQL Server performance objects installed and available to PATROL in order for all of the functions in PATROL for Microsoft SQL Server to operate.

If PATROL for Microsoft SQL Server cannot find the SQL Server performance objects, it cannot configure the instance, and it generates the following message: The SQL Server performance objects are not available. If you cannot resolve this issue, refer to your SQL Server manual, see the Microsoft technical information website, or call Microsoft support.

ATROL Agent d consoles

at least one of the following PATROL consoles: PATROL Console for UNIX PATROL Console for Microsoft

Windows Servers PATROL Central Operator Microsoft

Windows Edition PATROL Central Operator Web

Edition PATROL Agent PATROL Console Server

PATROL Central consoles are not required, but a PATROL Agent is required for each monitored instance and a PATROL Console for UNIX or PATROL Console for Microsoft Windows is required to initially configure PATROL for Microsoft SQL Server.PATROL for Microsoft SQL Server Getting Started


otpr

dne

br

se

lic

inUenwbr

Ta

Reher PATROL oducts

PATROL installation utility See Determining the version of the installation utility on page 40.

PATROL Cluster Configuration Wizard (a component of PATROL for Microsoft Windows Servers)

This product is required if you plan to monitor a clustered SQL Server. For more information, see Setting up PATROL in a clustered environment on page 85.

Use the following PATROL products to configure and modify PATROL for Microsoft SQL Server:

PATROL Configuration Manager PATROL Knowledge Module for Event

Management

For more information, see Chapter 4, Using PATROL Configuration Manager with PATROL for Microsoft SQL Server.

Distribution Server You can use this product to distribute PATROL for Microsoft SQL Server throughout your enterprise.

isk space eded to install

40 MB are required to install on a computer that is acting as a Managed System, Common System, and Console System

Fewer megabytes are required if you are installing only on a Managed System (37 MB), or only on a Console System (21 MB). For more information about the roles that each computer performs, see page 48.

owser Netscape Navigator for UNIX and Red Hat Linux platforms.

Install Netscape Navigator on the computer where the console resides.

curity levels PATROL for Microsoft SQL Server can operate at any of the security levels provided by PATROL

See Determining the PATROL security levels on page 41.

ense You must have a valid demonstration license (typically good for 30 days) or a permanent license to run your PATROL products.

If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department for licensing information.

stalling into a NIX vironment ithout a owser

You must launch the installation utility from the command line and use the -serveronly command line option.


source Requirements CommentsChapter 2 Installing and migrating PATROL for Microsoft SQL Server 35


36

ac

Ta

Recounts PATROL Windows account You must create a dedicated user account before PATROL is installed. Use the following guidelines:

Stand-alone workgroup servers must use a local user account.

Servers that are trusted members of a domain can use either a local or domain account.

The account on a domain controller must be a member of the domain Administrators group.

The PATROL account must be a member of the local Administrators group of the computer where the PATROL Agent resides.

If you use a domain account, no local account on that computer can have the same name.

Do not use a built-in Administrator account.

Warning: If you use a built-in Windows domain or local Administrator account as the PATROL default account, files created by PATROL are owned by the Administrator, and security or file access problems can result.

Note: If you are installing PATROL for Microsoft SQL Server in a cluster, verify that the account you are using to install PATROL has local administrator rights on each cluster node.


source Requirements CommentsPATROL for Microsoft SQL Server Getting Started


ac(c

Ta

Recounts ontinued)

PATROL UNIX account The account .login, .profile, .cshrc, and .kshrc files should not contain any customizations such as aliases, nondefault prompts, or unmask settings other than 022.

Do not use the root account.

The account must have permission to create directories and write the installation logs to the $HOME and /tmp directories on the computer where you are installing products.

The account must have ftp and telnet enabled.

The account must have access to a root account on the computer where PATROL is installed.

(recommended) Install PATROL on local partitions. If PATROL is installed on NFS-mounted partitions, the root account must have root access permissions on the NFS server.

PATROL requires the following accounts to monitor SQL Server:

a SQL Server login account with system administrator privileges when standard security is selected or a Windows login account with system administrator (sa) privileges when integrated security is selected

a SQL Server login account with user privileges

PATROL automatically uses the appropriate login for each function.

PATROL uses the SQL Server or Windows account with system administrator privileges for the following functions:

SQL Snapshot configuration DBStructureColl and

LongRunningTrans parameters

PATROL uses the SQL Server user account for the following functions:

all other parameters all other menu commands


source Requirements CommentsChapter 2 Installing and migrating PATROL for Microsoft SQL Server 37

Preparing for installation

38

P

In

Creparing for installationBMC Software recommends that you first install PATROL for Microsoft SQL Server on a limited number of development or test computers, and then configure and test PATROL for Microsoft SQL Server before installing it onto production computers.

stallation prerequisites

Before you install, you should complete the following tasks:

check for product patches or fixes (see page 38) determine how you should monitor a cluster (see page 39) determine whether to install locally or by using an installable image (see page 40) ensure that you are using the correct version of the installation utility (see page 40) determine the PATROL security level (see page 41) determine which roles your computers perform (see page 42) determine whether to upgrade without saving any customizations or to upgrade

and save your customizations (see page 41) plan for the installation of a language pack, if required (see page 46)

hecking for product patches or fixes

Product fixes or patches, which correct problems that are found after a product is released, are usually available through the BMC Software website. BMC Software recommends that you check the web page for your version of the product.

If fixes or patches are available for PATROL for Microsoft SQL Server 4.2.30, install the product, and then apply the patch or fix using the installation instructions provided in the technical bulletin or flash that describes the patch or fix.PATROL for Microsoft SQL Server Getting Started

Determining how you should monitor a cluster

D

Ta

Co

viACWPtothSem

PinAnoetermining how you should monitor a cluster

Before you begin installing the product in a clustered environment, decide which of the supported configurations shown in Table 3 you should use to monitor your clustered environment.

BMC Software recommends that you use the virtual PATROL Agent configuration. If you choose the virtual PATROL Agent configuration, you must install and run a PATROL Agent and PATROL for Microsoft SQL Server on each cluster node, and use the PATROL Cluster Configuration Wizard to create a virtual PATROL Agent resource on each cluster group that contains a SQL Server that you want to monitor.

The PATROL Cluster Configuration Wizard defines the PATROL Agent environment variables that make the history data and configuration settings available upon failover. For more information about configuring the PATROL Agent as a resource in a cluster, see Setting up PATROL in a clustered environment on page 85.

ble 3 Supported configurations for a clustered environment

nfiguration Advantage Disadvantage

rtual PATROL gentuse the PATROL luster Configuration izard to add the

ATROL Agent resource the cluster group(s) at contains the SQL rvers you want to onitor

No need to configure the SQL Server instances on each cluster node. Instead, you configure PATROL for Microsoft SQL Server on the active nodes (that is, the virtual SQL Server)

Parameter history and configuration settings are stored on a shared drive and are, therefore, available after failover

the Failover parameter is available in this environment

Only SQL Server instances belonging to the same cluster resource group as the virtual PATROL Agent are discovered

You must run a virtual PATROL Agent on each cluster resource group that has a SQL Server to monitor.

ATROL Agentrun dependent PATROL gents on each cluster de

Only one PATROL Agent runs on each node

Because PATROL configuration data and parameter history data are not shared between the PATROL Agents on the cluster nodes, the following disadvantages apply:

you must configure each SQL Server to which the instance can fail over

you cannot view parameter history that was collected on another cluster nodeChapter 2 Installing and migrating PATROL for Microsoft SQL Server 39

Determining whether to install locally or remotely

40

D

Determining whether to install locally or remotely

You can install products on the computer on which you are running the installation utility (local installation), or you can create an installable image of products so that you can install them at a later time on multiple computers (remote installation functionality). An installable image is a fully configured product image that you can use to install products to multiple computers. With an installable image, you can create one product image with one pass through the installation utility and then use that image to install to remote computers in your environment.

If you create an installable image, the computers upon which you install the image must have identical values entered for the following configuration settings:

BMC Software products installation directory account names passwords PATROL Agent port number security options

If you want to specify different settings for different computers, you must either create a separate image for each set of values that you want to implement or edit the variables in the control file for the installable image by using the ctltool. For more information about creating, distributing, and installing installable images, and about using the ctltool, see the PATROL Installation Reference Manual.

etermining the version of the installation utility

The version of the installation utility included on the CD or Electronic Product Download (EPD) image you use to install PATROL for Microsoft SQL Server might differ from a version included on another product CD or from a version that you downloaded from the BMC Software Electronic Product Download (EPD) website. You should use the version of the installation utility that comes with the product that you are installing.

To determine the version of an installation utility

1 Open a command prompt.

2 Navigate to the directory where the installation utility is located.

3 Enter the command that is appropriate for your system:

Setup.exe -v (Windows) setup sh -v (UNIX)PATROL for Microsoft SQL Server Getting Started

Determining the PATROL security levels

D

Determining the PATROL security levels

PATROL security is installed as part of the agent, console server, and consoles. PATROL for Microsoft SQL Server inherits the security policy from the agent, console server, and console on which it is installed and can operate at any of the PATROL security levels. However, the higher security levels require more overhead, which can affect performance. If this is a concern, you might want to verify which level of security is installed and how it was implemented.

To check the security level of a previously installed agent, console server, or console

1 From the command line, switch to the path on the computer that you want to check: %BMC_ROOT\..\common\security\bin\OS (Windows) or $BMC_ROOT/../common/security/bin/OS (UNIX)

2 To display the security policy of the current computer, run the following command:

esstool policy -a

For more information about PATROL security, see the PATROL Security User Guide.

etermining how to upgrade

If you already have a version of PATROL for Microsoft SQL Server installed in your environment, you need to determine whether or not there are any customizations in the installed product that you want to save.

Customizations to Knowledge Modules (.km) and PSL (.psl) files are stored in cache, but they are not preserved and incorporated automatically. PATROL for Microsoft SQL Server can include the following customizations:

new Knowledge Modules (.km files) that you created modified PSL code, whether it is embedded in .km or .psl files

Customizations that were applied by using PATROL Configuration Manager or operator overrides created with a PATROL Operator Console (unless you are upgrading from a PATROL console version 3.4.11 or earlier) are saved in the agent configuration database automatically. The customizations take effect automatically. For more information, see Chapter 4, Using PATROL Configuration Manager with PATROL for Microsoft SQL Server.Chapter 2 Installing and migrating PATROL for Microsoft SQL Server 41

Determining the roles that each computer performs

42

D

Ta

Si

Ocuanne

IfPUse Table 4 to determine whether you should upgrade and save your customizations or upgrade without saving any customizations, and use the appropriate procedure.

etermining the roles that each computer performs

The installation utility prompts you to select the roles performed by the computer on which you are installing BMC Software products (the target computer). Before beginning the installation process, review the following definitions of the roles that are presented in the installation utility and decide which of these roles is performed by each computer in your environment.

ble 4 Choosing an installation procedure

tuation Installation Procedure

No customizations were made to your previous version of PATROL for Microsoft SQL Server

One or more of the following customizations were made to your previous version of PATROL for Microsoft SQL Server, but you plan to migrate those customizations manually:

new Knowledge Modules were created PSL code was modified

One or more of the changes or customizations listed above were made by using the PATROL Configuration Manager (in which case, they are saved in the Agent configuration file and applied to the new version automatically).

You want to overwrite customizations with the default values of the new version of PATROL for Microsoft SQL Server.

The currently installed version of PATROL for Microsoft SQL Server is a version earlier than 2.1.00.

Installing for the first time or upgrading over an existing installation on page 46

ne or more of the following customizations were made to your rrently installed version of PATROL for Microsoft SQL Server d you plan to save those customizations and migrate them to the w version of PATROL for Microsoft SQL Server manually:

new Knowledge Modules were created PSL code was modified

Upgrading and saving customizations on page 50

you are using the Distribution Server to install and distribute ATROL for Microsoft SQL Server throughout your environment

First-time installation using the Distribution Server on page 54PATROL for Microsoft SQL Server Getting Started

Determining the roles that each computer performsRoles performed by computers in the PATROL architecture

The following roles are performed by computers in the PATROL architecture:

Console Systems (also referred to as console computers) host user desktop applications such as consoles, user interfaces, viewers, and browsers. Select this option if the computer to which you are installing performs any of the following roles:

monitors and manages on Windows by using a PATROL Central Operator Microsoft Windows Edition console (PATROL 7.x architecture)

monitors and manages on UNIX by using a PATROL Console for UNIX (PATROL 3.x architecture)

monitors and manages on Windows by using a PATROL Console for Windows (PATROL 3.x architecture)

Managed Systems (also referred to as agent computers) host software that manages the resources on the computer, such as a PATROL Agent, PATROL Knowledge Modules, and Service Reporting Retrievers. Select this option if the computer to which you are installing will perform any of the following roles:

host a PATROL Agent 3.5 (works with both the PATROL 3.x and PATROL 7.x architecture)

host KMs and components that contain the knowledge that PATROL uses to monitor the resources on this computer

Common Services (new with PATROL 7.x architecture) computer hosts services that are shared among managed systems and console systems. You can install each of these common services on any computer in the network. Select this option if the computer to which you are installing will perform any of the following roles:

host the PATROL Central Operator Web Edition (PATROL 7.x) server host the PATROL Console Servers host the RTserversChapter 2 Installing and migrating PATROL for Microsoft SQL Server 43

Determining where to install

44

DAdditional information

For more information about the PATROL consoles and PATROL Console Server or RTserver, see the online Help systems for each product and the following documents:

PATROL Central Operator - Web Edition Getting Started PATROL Central Operator - Microsoft Windows Edition Getting Started PATROL Console Server and RTserver Getting Started PATROL Configuration Manager User Guide PATROL Console for UNIX User Guide PATROL Console for Microsoft Windows User Guide - Understanding the Basics of

PATROL, Volume 1

etermining where to install

Where you install PATROL for Microsoft SQL Server depends on which system roles you have assigned to a computer and which PATROL infrastructure components are installed on that computer.

This section explains where to install PATROL for Microsoft SQL Server.

PATROL 3.x

In a PATROL 3.x environment, you must install PATROL for Microsoft SQL Server on the following computers:

Computers hosting the PATROL AgentSelect Managed Systems as the System Role in the installation utility when installing PATROL for Microsoft SQL Server. This selection installs the files that run on the PATROL Agent.

Computers hosting the PATROL Console for Windows or PATROL Console for UNIXSelect Console Systems as the System Role in the installation utility when installing PATROL for Microsoft SQL Server on computers hosting the PATROL Console for Windows or PATROL Console for UNIX. This selection installs the files required by the console.PATROL for Microsoft SQL Server Getting Started

Determining where to installPATROL 7.x

In a PATROL 7.x environment, you must install PATROL for Microsoft SQL Server on the following computers:

Computers hosting the PATROL Console ServerSelect Common Services Systems as the System Role in the installation utility. This selection installs the PATROL for Microsoft SQL Server icons, Help files, and resource files that are used by PATROL Central Operator Microsoft Windows Edition and PATROL Central Operator Web Edition.

Computers hosting PATROL Central Operator Microsoft Windows EditionSelect Console Systems as the System Role in the installation utility. This selection installs PATROL for Microsoft SQL Server files for use by PATROL Central Operator Microsoft Windows Edition.

Computers hosting the PATROL AgentSelect Managed Systems as the System Role in the installation utility. This selection installs PATROL for Microsoft SQL Server files that run on the PATROL Agent.

When using PATROL Central Operator Web Edition, install KMs on computers hosting the PATROL Console Server using the Common Services Systems role and computers hosting the PATROL Agent using the Managed Systems role.

If you are using older versions of the following components:

PATROL Console Server prior to version 7.2.36 PATROL Central Operator Web Edition prior to version 7.1.10

You must also install PATROL for Microsoft SQL Server on the computer hosting the PATROL Central Operator Web Edition web server using the Common Services Systems role.

For more information about the PATROL 7.x architecture, see the PATROL Infrastructure Planning Guide.

NOTE If you do not install PATROL for Microsoft SQL Server on the computer hosting the PATROL Console Server, and select Common Services Systems as the System Role in the installation utility, no PATROL for Microsoft SQL Server icons or Help files will be available for the PATROL Central Operator Microsoft Windows Edition or PATROL Central Operator Web Edition consoles.Chapter 2 Installing and migrating PATROL for Microsoft SQL Server 45

Planning for the installation of a language pack

46

P

Inalanning for the installation of a language pack

The a language pack provides translations of all messages and user interface elements. Language pack CDs are always installed after the product has been installed. When the Japanese language pack CD is installed, PATROL for Microsoft SQL Server operates with a Japanese user interface.

There are two requirements you need to consider if you plan to install a language pack:

you must install PATROL for Microsoft SQL Server before you can install the language pack for PATROL for Microsoft SQL Server

you must make the same selections in the installation windows during both installations

To ensure that you make the same selections during both installations, you might want to note your selections and capture the Review Selections and Start Install window (step 9 on page 49).

stalling for the first time or upgrading over n existing installation

Use Table 4 on page 42 to determine whether you should use this installation procedure or proceed to Upgrading and saving customizations on page 50.

Before you begin

Whether this is a first time installation or an upgrade, take the following actions:

create the PATROL default account before installing

install (or upgrade, if required) PATROL Agent and console products before installing or upgrading PATROL for Microsoft SQL Server (If you are installing from a CD that contains Agents, consoles, and PATROL for Microsoft SQL Server, you can install them at the same time.)

install on a limited number of computers in a test environment, test the installation thoroughly, and then install in your production environmentPATROL for Microsoft SQL Server Getting Started

Installing for the first time or upgrading over an existing installationIf you are upgrading, whether you plan to save your changes or not, take the following actions:

move the old PATROL for Microsoft SQL Server to a new directory that is different from PATROL_HOME

remove PATROL for Microsoft SQL Server files from PATROL_CACHE

To back up the current installation and move files from PATROL_CACHE

1 Shut down any PATROL Agents, consoles, and related services that are currently running.

2 Ensure that no one is accessing any PATROL files or directories.

3 Perform a full backup of the following directories where PATROL executables and data are typically stored:

PATROL_HOME for agent and console installation directories PATROL_CACHE for the console working cache

4 Remove all PATROL for Microsoft SQL Server files with the following naming patterns from PATROL_CACHE\knowledge and PATROL_CACHE\psl:

MSSQL*

RA1MSSQL*

To install for the first Time, upgrade without saving customiza

SQL SVR KM

Documents

Transcript of SQL SVR KM