tivoli manager for microsoft sql server** reference...

Tivoli Manager for Microsoft SQL Server** Reference Guide

Version 1.3

Tivoli Manager for Microsoft SQL Server** Reference Guide (September 1999)Copyright NoticeCopyright © 1998, 1999 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RISC System/6000, Tivoli Management Environment, TME 10, TME Enterprise Console, TME 10 Framework, and TME 10 Distributed Monitoring.

Microsoft, Windows, and the Windows 95/98 logo, SQL Server, and Transact-SQL are trademarks or registered trademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli Systems’ or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York 10594.

Contents

Preface................................................................................................................... ix

Chapter 1—IntroductionUsing the Reference Manual............................................................................... 1-2

How this Manual is Organized................................................................... 1-2

Standard Information in Reference Entries ................................................ 1-2

Using the Manual Online ........................................................................... 1-4

Getting Online Help ................................................................................... 1-4

Working with Tivoli Software ............................................................................ 1-5

Using the Desktop ...................................................................................... 1-5

Using the Command Line Interface ........................................................... 1-5

Specifying Path Names...................................................................... 1-5

Commands Used with This Product .................................................. 1-6

Chapter 2—The MSSQLManagerTasks LibraryCommon Task Dialogs ....................................................................................... 2-2

Common CLI Arguments........................................................................... 2-2

List of Tasks by GUI and CLI Names ................................................................ 2-3

ADSMFullBackup .............................................................................................. 2-5

ADSMIncBackup.............................................................................................. 2-15

ConfigureTECMSSQL ..................................................................................... 2-25

Customize TEC NT Event Adapter MSSQL.................................................... 2-33

Database Check-up and Tune-up ...................................................................... 2-41

Disable NT Disk Performance Counters........................................................... 2-50

Discover MS SQL Servers................................................................................ 2-54

Dump Database ................................................................................................. 2-61

Dump Transaction Log ..................................................................................... 2-71

Enable NT Disk Performance Counters............................................................ 2-82

Execute SQL ..................................................................................................... 2-86

Tivoli Manager for Microsoft SQL Server Reference Guide iii

MS SQL Server Warnings and Indicators ........................................................ 2-91

NT Event Logging .......................................................................................... 2-103

Rebuild Fragmented Indexes .......................................................................... 2-109

Recovery Preparation...................................................................................... 2-115

Refresh Databases........................................................................................... 2-124

Refresh Query Optimizer Statistics ................................................................ 2-127

Restore TEC NT Event Adapter MSSQL....................................................... 2-132

Set and Retrieve Database Options................................................................. 2-137

Start MS SQL Server Services and TME Monitors........................................ 2-149

Stop MS SQL Server Services and TME Monitors........................................ 2-155

Update Space Usage Information ................................................................... 2-164

Chapter 3—The MSSQLServer Monitoring CollectionList of MSSQLServer Monitoring Sources by GUI and CLI Names................. 3-2

Cache Average Free Page Scan .......................................................................... 3-6

Cache Configured Free Buffers Percent Used.................................................... 3-9

Cache Hit Ratio................................................................................................. 3-12

Cache Maximum Free Page Scan ..................................................................... 3-15

Cache Number of Free Buffers......................................................................... 3-18

Client Count...................................................................................................... 3-21

Client Count Percent Used................................................................................ 3-23

CPU Percent Busy ............................................................................................ 3-25

CPU Percent Busy Doing I/O ........................................................................... 3-27

CPU Percent Idle .............................................................................................. 3-29

Database Status (Server)................................................................................... 3-31

Data Space Percent Used (Server) .................................................................... 3-34

Delivered Latency............................................................................................. 3-38

Delivered Transaction Rate .............................................................................. 3-43

Delivered Transactions ..................................................................................... 3-48

Extent Locks Exclusive .................................................................................... 3-53

Extent Locks Total............................................................................................ 3-56

Extent Locks Update......................................................................................... 3-59

iv Version 1.3

Freeform SQL Numeric .................................................................................... 3-62

Freeform SQL String ........................................................................................ 3-68

I/O Batch Average Size .................................................................................... 3-74

I/O Batch Maximum Size ................................................................................. 3-77

I/O Batch Write Rate ........................................................................................ 3-80

I/O Disk Errors.................................................................................................. 3-83

I/O Disk Reads .................................................................................................. 3-85

I/O Disk Writes ................................................................................................. 3-88

I/O Log Write Rate ........................................................................................... 3-91

I/O Outstanding Reads ...................................................................................... 3-94

I/O Outstanding Writes ..................................................................................... 3-97

I/O Page Read Rate ......................................................................................... 3-100

I/O Single Page Write Rate............................................................................. 3-103

I/O Transaction Rate ....................................................................................... 3-106

I/O Transactions Per Log Record ................................................................... 3-109

Intent Locks Exclusive.................................................................................... 3-112

Intent Locks Shared ........................................................................................ 3-115

Intent Locks Total ........................................................................................... 3-118

Log Space Percent Used (Server) ................................................................... 3-121

Network Read Rate ......................................................................................... 3-124

Network Write Rate ........................................................................................ 3-127

NT Application Log........................................................................................ 3-130

NT Application Log Age ................................................................................ 3-135

NT Application Log Percent Full ................................................................... 3-138

Number of Blocked Processes ........................................................................ 3-141

Number of Deadlocks ..................................................................................... 3-143

Oldest Open Transaction (Server) .................................................................. 3-146

Page Locks Exclusive ..................................................................................... 3-149

Page Locks Shared.......................................................................................... 3-152

Page Locks Total............................................................................................. 3-155

Page Locks Update ......................................................................................... 3-158

Tivoli Manager for Microsoft SQL Server Reference Guide v

Procedure Buffers Active ............................................................................... 3-161

Procedure Buffers Total.................................................................................. 3-164

Procedure Buffers Used.................................................................................. 3-167

Procedure Cache Active ................................................................................. 3-170

Procedure Cache Size ..................................................................................... 3-173

Procedure Cache Used.................................................................................... 3-176

RA Effectiveness ............................................................................................ 3-179

RA Pages Fetched into Cache Per Second ..................................................... 3-182

RA Pages Found in Cache Per Second ........................................................... 3-185

RA Physical Read Rate................................................................................... 3-188

RA Slots Used................................................................................................. 3-191

Service State ................................................................................................... 3-193

SQL Server State ............................................................................................ 3-199

SQLServerAgent Failed Jobs ......................................................................... 3-202

Table Locks Exclusive.................................................................................... 3-205

Table Locks Shared ........................................................................................ 3-208

Table Locks Total ........................................................................................... 3-211

Total Blocking Locks ..................................................................................... 3-214

Total Exclusive Locks .................................................................................... 3-217

Total Locks ..................................................................................................... 3-220

Total Locks Percent Used ............................................................................... 3-224

Total Locks Remaining................................................................................... 3-227

Total Shared Locks ......................................................................................... 3-230

Undelivered Transactions ............................................................................... 3-233

User Connections............................................................................................ 3-238

User Connections Percent Used...................................................................... 3-241

User Connections Remaining ......................................................................... 3-244

Chapter 4—MSSQLDatabase Monitoring CollectionList of MSSQLDatabase Monitoring Sources by GUI and CLI Names ............ 4-2

Data Space Percent Used (Database).................................................................. 4-3

Data Space Used ................................................................................................ 4-7

vi Version 1.3

Database Status (Database)............................................................................... 4-11

Fragmentation ................................................................................................... 4-14

Log Space Percent Used (Database) ................................................................. 4-18

Log Space Used ................................................................................................ 4-21

Oldest Open Transaction (Database) ................................................................ 4-24

Optimizer Statistics Age ................................................................................... 4-27

PeopleSoft Fragmentation................................................................................. 4-31

PeopleSoft Optimizer Statistics Age................................................................. 4-35

PeopleSoft Space Used Table ........................................................................... 4-39

Replicated Transaction Rate ............................................................................. 4-44

Replicated Transactions .................................................................................... 4-48

Replication Latency .......................................................................................... 4-51

Space Used (Table) ........................................................................................... 4-54

Suspect Database .............................................................................................. 4-59

Tivoli Manager for Microsoft SQL Server Reference Guide vii

viii Version 1.3

Preface

s to

ts r.

PrefaceThe Tivoli Manager for Microsoft SQL Server Reference Guide provides detailed information about the tasks and monitors for Tivoli Manager for Microsoft SQL Server. Use this manual in conjunction with the Tivoli Manager for Microsoft SQL Server User’s Guide.

Who Should Read This ManualThis manual is intended for system architects (for planning) and system administrators and database administrators (for implementation and operation). Readers should have administrator-level understanding of the Windows NT operating system, Tivoli software, and Microsoft SQL Server software.

You will notice that the terms “Tivoli” and “TME 10” are used in thedocumentation. These terms are interchangeable. Reference“TME 10” will be removed in future product releases.

Related DocumentsYou must be familiar with the information in the related documenbefore you install and use Tivoli Manager for Microsoft SQL Serve

The TME 10 Framework User’s Guide contains more detailed information about jobs, tasks, profiles, and profile management.

The TME 10 Framework Planning and Installation Guide contains more detailed information about server and hardware requirements.

The TME 10 Framework Reference Guide contains additional information about command line commands, such as the winstall command.

The TME 10 Distributed Monitoring User’s Guide contains more information about distributed monitoring.

The TME 10 Enterprise Console User’s Guide contains more detailed information about using the TEC.

The TME 10 MCSL Developer’s Guide explains how to create your own monitoring sources and collections.

The TME 10 Global Enterprise Manager Installation and User’s Guide contains more detailed information about GEM.

Tivoli Manager for Microsoft SQL Server Reference Guide ix

Preface

The Microsoft SQL Server Administrator’s Companion contains information about SQL Server administration.

Microsoft SQL Server Books On-line contains information about SQL Server administration.

Microsoft SQL Server Transact-SQL Reference contains information about Transact-SQL, the enhanced version of SQL. For Version 7.0, the manual is named Microsoft SQL Server Transact-SQL and Utilities Reference, Volumes 1 and 2.

ADSTAR Distributed Storage Manager Administrators Reference Manual contains information about using ADSM commands.

What This Guide ContainsThe Tivoli Manager for Microsoft SQL Server Reference Guide contains the following chapters:

■ Chapter 1, “Introduction”

Contains information on how to use this manual and information on working with this product, including a list of Tivoli commands commonly used with this product.

■ Chapter 2, “The MSSQLManagerTasks Library”

Describes the individual tasks in the MSSQLManagerTasks library. This chapter also describes how to use two common dialogs (Create a Report File and TEC) that you access from the MSSQLManagerTasks task argument dialogs, and it provides the command line interface arguments for these two dialogs.

■ Chapter 3, “The MSSQLServer Monitoring Collection”

Describes the individual monitors in the MSSQLServer monitoring collection, each of which enables you to manage a different aspect of a Microsoft SQL Server server, such as server state, locks, I/O, and network statistics.

■ Chapter 4, “MSSQLDatabase Monitoring Collection”

x Version 1.3

Preface

Describes the individual monitors in the MSSQLDatabase monitoring collection, each of which enables you to manage a different aspect of a Microsoft SQL Server database, such as database status, replication latency, and transaction log size.

Typeface ConventionsThis guide uses several typeface conventions for special terms and actions. These conventions have the following meaning:

Bold Commands, keywords, file names, or other information that you must use literally appear in bold. Names of windows, dialogs, and other controls also appear in bold.

Italics Variables and values that you must provide appear in italics.

Bold Italics New terms appear in bold italics when they are defined in the text.

Monospace Code examples appear in a monospace font.

Operating System InformationThe operating systems under which the Tivoli Manager for Microsoft SQL Server run are the same as the operating systems for the Tivoli Framework. Endpoints (Microsoft SQL Server servers and databases) run only on Windows NT. See the appropriate Tivoli Framework documentation for additional information.

The Tivoli Manager for Microsoft SQL Server does not run under OSF.

Contacting Customer SupportIf you encounter difficulties with any Tivoli products, you can enter http://www.tivoli.com/support/ to view the Tivoli Support home page. After you link to and submit the customer registration form, you will be able to access many customer support services on the Web.

Use the following phone numbers to contact customer support in the United States: the Tivoli number is 1-800-848-6548

Tivoli Manager for Microsoft SQL Server Reference Guide xi

Preface

(1-800-TIVOLI8) and the IBM number is 1-800-237-5511 (press or say 8 after you reach this number). Both of these numbers direct your call to the Tivoli Customer Support Call Center.

We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send e-mail to [email protected].

xii Version 1.3

Intro

du

ction

1Introduction

This book is a reference manual designed for use with the procedures described in the Tivoli Manager for Microsoft SQL Server User’s Guide. It provides alphabetical listings and detailed descriptions of the following:

■ Tasks in the MSSQLManagerTasks library

■ MSSQLServer monitors. The MSSQLServer monitoring collection provides server availability and performance monitoring facilities.

■ MSSQLDatabase monitors. The MSSQLDatabase monitoring collection provides database availability and performance monitoring facilities.

Tivoli Manager for Microsoft SQL Server provides the ability to manage and monitor Microsoft SQL Server database servers and databases by extending or working with the following Tivoli software products:

■ Framework

■ Distributed Monitoring

■ TEC (Tivoli Enterprise Console)

■ User Administration

■ Global Enterprise Manager (GEM)

■ Tivoli Manager for PeopleSoft

1

Tivoli Manager for Microsoft SQL Server Reference Guide 1–1

Using the Reference Manual

Using the Reference ManualThis section contains information on how to use this reference manual. It includes the following information:

■ How this manual is organized

■ Standard information (headings) for all reference entries in this manual

■ How to view this manual online

■ Conventions used in this manual

How this Manual is OrganizedThe manual is organized into three reference sections:

■ Tasks

■ MSSQLServer monitors

■ MSSQLDatabase monitors

Within each reference section, reference entries appear alphabetically by name. In most cases, the CLI command (tasks) or keyword (monitors) is the same as the name but run together. In some cases the names are different. For example, the MS SQL Warnings and Indicators task has the CLI command name SQLWarnings.

Standard Information in Reference EntriesEach task or monitor reference entry contains the following information:

DESCRIPTION

A brief description of the task or monitor that concisely summarizes its purpose.

AUTHORIZATION ROLE

The required TIVOLI authorization role, plus any required Microsoft SQL Server authorization.

1–2 Version 1.3


Intro

du

ction

TARGET ENDPOINT

The kind(s) of endpoint on which the task or monitor operates. In this product, target endpoints are database servers, databases, or managed nodes.

GUI DATA ENTRY FIELDS

Descriptions of each argument that is represented by a field in the desktop (GUI) interface. Some tasks and monitors do not have arguments.

CLI SYNTAX

The CLI (command line interface) syntax, which includes definitions for each of the arguments, and an example of the syntax. Note the following:

■ The CLI command for a task may be different than the GUI name shown in the heading.

■ The GUI data entry field names may be slightly different than the CLI argument names.

■ The description given for the GUI data entry field may contain more information than the description for the CLI argument.

CLI EXAMPLE

An example of using the CLI to execute a task or add the monitor. Task examples use the wruntask command, but you may also use the wexectask command. Monitor examples use the waddmon command.

SUGGESTED RESPONSE LEVELS

(Monitors only.) Suggested monitor threshold values for severity levels, plus a suggested monitoring interval.

OUTPUT

Example output for each task and monitor. Output for a task consists of messages that are generated when the task executes. Output for a monitor consists of the messages displayed when a monitor threshold level is triggered. Messages shown in a pop-up dialog box are shown



for the example. However, that is only one of several ways that a monitor can be configured to respond.

USAGE NOTES

Additional information about using each task and monitor. This section may also include warnings, information about special cases, and explanations of how Tivoli or Microsoft SQL Server behave.

SEE ALSO

A list of related tasks and monitors.

Using the Manual OnlineA PDF file of this manual is provided on the product CD. Use Adobe Acrobat Reader Version 3.0 or later to view and print the manual. Acrobat Reader is available free from Adobe at http://www.adobe.com.

Acrobat Reader provides navigational features that make accessing the manual more convenient:

■ Navigation: Select View > Bookmarks and Page from the menu to see a hierarchical table of contents to the left of the manual pages. Clicking on an item in the contents positions the manual to the corresponding page. You can open and close higher levels to show and hide lower levels.

■ Hyperlinks: The table of contents, index, table of entries (tasks or monitors), cross references in text, and entries in the SEE ALSO section of the book contain hyperlinks. Click on a link to go to the page it refers to.

■ Search: Choose Tools > Find from the menu to search the manual.

Getting Online HelpOnline help has been provided for each task and monitor. The help consists of the reference entry, specially formatted for the text format used in Tivoli help.

Help is available online from the desktop as follows:

1–4 Version 1.3

Working with Tivoli Software

Intro

du

ction

■ Tasks: In the task argument dialog, click the Task Description button.

■ Monitors:

a. In a profile manager, double-click a profile to open it.

b. In the TME 10 Distributed Monitoring Profile Properties window, click Add Monitor.

c. In the Add Monitor dialog, select the desired collection and monitor, then click the About This Monitor button.

Help for tasks is also available online from the command line: use the gettaskhelp command with the CLI name for the task. For example, the following command returns help on the Dump Database task:

gettaskhelp dumpdatabase

Working with Tivoli SoftwareThis section describes several aspects of using Tivoli software that are important to this product.

You can work with monitors and tasks from both the desktop (GUI) or the command line (CLI).

Using the Desktop Use the GUI when you want to take advantage of a point-and-click interface. The GUI provides defaults for many options when executing tasks or setting up monitors.

Using the Command Line InterfaceUse the CLI when you want to create scripts, respond to distributed monitors, or if you prefer to work from a command line.

Specifying Path Names

Depending on the platform on which you run Tivoli Manager for Microsoft SQL Server, you use either forward (/) or backward slashes (\) in path names. Examples in this documentation use both forward and backward slashes.


Working with Tivoli Software

w

o

g

d

the

Commands Used with This Product

There are a number of commands that you can use to run tasks and jobs from the command line. These include the following:

■ waddmon to add a monitor to a monitoring profile. The CLI Example section of each monitor’s reference entry shows hoto add the monitor using this command.

■ wruntask to run a task from the command line. The CLI Example section of each task’s reference entry shows how texecute the task using this command.

■ wexectask run a customized task from the command line usinarguments stored with the customized task in addition to arguments provided on the command line

■ wgettaskhelp to view the help text for a task from the commanline

■ wcrtjob to create a job

■ wrunjob to run an existing job

■ wschedjob to schedule an existing job

See the TME 10 Framework Reference Manual for more information on these commands, except wexectask and wgettaskhelp, which are unique to this product. See Chapter 8, “Using Tasks and Jobs inTivoli Manager for Microsoft SQL Server User’s Guide for more information on those commands.

1–6 Version 1.3

Th

e MS

SQ

LM

anag

erTasks L

ibrary

, as

.

2The MSSQLManagerTasks Library

This chapter includes the following information:

■ Identification of features that are common to every task

■ A table that lists all tasks by GUI name and CLI name

■ Reference entries for each task in the MSSQLManagerTasks library, sorted alphabetically by GUI name

You can find additional information about tasks in the Tivoli Manager for Microsoft SQL Server User’s Guide. Chapter 8, “Using Tasks and Jobs” describes how to set up and run tasks and jobswell as how to create customized tasks from the standard MSSQLManagerTasks.

2


Common Task Dialogs

Common Task Dialogs Two dialogs are used by all tasks.

■ When you press the Report to File button on a task argument dialog, the system displays the Create a Report File dialog.

■ When you press the Notify TEC button on a task argument dialog, the system displays the TEC dialog.

Common CLI ArgumentsThe following arguments provided the equivalent functionality as the common task dialogs. The arguments can be specified with all tasks when using the command line.

NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If Y, specify TECServer or no message is sent.

TECServer <servername> the name of the TEC server to send the message to.

ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the default. If Y, specify ReportFileName and SaveReportFileOn.

ReportFileName <filename> is the path to and the name of the file to create as the task output.

SaveReportFileOn

Use one of the following:

MonitoredHost puts the output file on the host the task was run against.

SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName.

ReportHostName <hostname> is the name of the host on which to save the file created when you use the SpecifiedHost argument.

2–2 Version 1.3

List of Tasks by GUI and CLI Names

Th

e MS

SQ

LM

anag

erTasks L

ibrary

For more information, see Chapter 8, “Running Tasks” in the Tivoli Manager for Microsoft SQL Server User’s Guide.

List of Tasks by GUI and CLI NamesThe following table lists the MSSQLManagerTasks by both their GUI and CLI names.

GUI Name CLI Name

ADSMFullBackup ADSMFullBackup

ADSMIncBackup ADSMIncBackup

ConfigureTECMSSQL ConfigureTECMSSQL

Customize TEC NT Event Adapter MSSQL

CustomizeTECNTEventAdapter

Database Check-up and Tune-up DBCheckup

Disable NT Disk Performance Counters

DisableDiskCounters

Discover MS SQL Servers DiscoverSQLSRVR

Dump Database DumpDatabase

Dump Transaction Log DumpTransactionLog

Enable NT Disk Performance Counters EnableDiskCounters

Execute SQL ExecuteSQL

MS SQL Server Warnings and Indicators

SQLWarnings

NT Event Logging NTEventLogging

Rebuild Fragmented Indexes RebuildIndex

Recovery Preparation RecoveryPrep

Refresh Databases RefreshDB

Refresh Query Optimizer Statistics RefreshStats


List of Tasks by GUI and CLI Names

Restore TEC NT Event Adapter MSSQL

RestoreTECNTEventAdapterMSSQL

Set and Retrieve Database Options DBOption

Start MS SQL Server Services and TME Monitors

StartServMon

Stop MS SQL Server Services and TME Monitors

StopServMon

Update Space Usage Information UpdateUsage

GUI Name CLI Name

2–4 Version 1.3

ADSMFullBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

ADSMFullBackup

DESCRIPTION

Performs a backup of an entire database and its associated transaction log. You have the option to truncate the transaction log after the backup.

Note: The backup is performed correctly regardless of whether the transaction log is on the same device fragment as the database or not.

AUTHORIZATION ROLE

mssqlserver_dba

TARGET ENDPOINT

Database


ADSMFullBackup


The following shows the ADSMFullBackup dialog; a description of each field follows.

Truncate Log After Backup

Clears out the inactive part of the transaction log. The default is not to truncate the log after a backup.

SQLSecure Uses Windows NT to authenticate the user. If you select this option, the system ignores SQL User and SQL Password values.

Compress Compresses data prior to sending it to ADSM storage. This option can lower network bandwidth utilization, but it increases CPU utilization.

Mountwait SQL Agent should wait for the ADSM server to complete mount requests.

Quiet Prevents status information from displaying.

2–6 Version 1.3

ADSMFullBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

, ns

M re

.

L

SQL User Name the SQL Agent uses to logon to the database server. If you do not specify a value for SQL User, the task uses sa, the default. If you specify a value for SQL User, you also must specify the SQL Password value. If the value for SQL Password does not match the password assigned to SQL User, the task fails. If you select SQL Secure, the task ignores this value.

SQL Password

Password the SQL Agent uses to logon to the database server. If you specify Sql User, you must specify what that user’s password is at SQL Password. If the value for SQL Password does not match the password for the user specified with SQL User, the task fails. If you select SQL Secure, this value is ignored.

ADSM Node Name the SQL Agent uses to logon to the ADSM server. If you do not specify a value for ADSM Node, the task uses the default value, which is client.You can store a password in the options filebut this parameter overrides the value in the optiofile. If you enter a value for ADSM Node you also must enter a value for ADSM Password. If the value for ADSM Password does not match the passwordassigned to ADSM Node, the task fails.

ADSM Password

Password the SQL Agent uses to logon to the ADSserver. The default password is blank. You can stoa password in the options file, but this parameter overrides the value in the options file.

ADSM Options File

Name of the ADSM options file the SQL Agent usesEnter only the filename with the .opt extension. The file must already exist in the install path of the SQAgent. If you enter a full path name, the task fails.


ADSMFullBackup

ADSM Activity Log File

Name of the activity log. Statistics about backed up and restored database objects are written to the specified log file. This option requires only the filename. If you do not specify a path, ADSM stores the file in a default location in its install path. You can force the file to be saved to a specific directory with forward slashes (/). The task ignores a back slash (\) and cannot interpret double (escape) back slashes (\\).

If you specify only the filename without a path name, ADSM stores the file in a default location in its install path.

Number of Buffers

Number of buffers the SQL Agent uses to improve asynchronous communications with the ADSM and database servers.

Report to File

Displays the Create a Report File dialog so that you can save the output information for this task to a file.

Notify TEC Displays the TEC dialog so that you can forward the success or failure of the task to a TEC server.

CLI SYNTAX

This task can be run with no arguments; it uses default values.

ADSMFullBackup

[–a SqlUser=<sqlusername> –a SqlPwd=<sqluserpassword>]

[–a SQLSecure=Y|N]

[–a Truncate=Y|N]

[–a AdsmNode=<nodename>]

[–a AdsmPwd=<node password>]

[–a AsdmOptFile=<options file>.opt]

2–8 Version 1.3

ADSMFullBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

[–a LogFile=<adsm logfile>]

[–a Compress=Y|N]

[–a Mountwait=Y|N]

[–a Buffers=<buffernumber>]

[–a Quiet=Y|N]

[–a NotifyTEC=Y|N]

[–a TECServer=<servername>]

[–a ReportToFile=Y|N]

[–a ReportFileName=<filename>]

[–a SaveReportFileOn=MonitoredHost | SpecifiedHost]

[–a ReportHostName=<hostname>]

Arguments are as follows:

SqlUser <sqlusername> designates the name the SQL Agent uses to logon to the database server. The default is sa.

GUI Name: SQL User

SqlPwd <sqluserpassword> designates the password the SQL Agent uses to logon to the database server. The default is blank.

GUI Name: SQL Password

SQLSecure Y uses Windows NT to authenticate user. When you use this argument, the SqlUser and SqlPwd arguments are ignored.

N uses SqlUser and SqlPwd values to authenticate user and is the default.

GUI Name: SQLSecure.

Truncate Y truncates the transaction log. N does not truncate it and is the default.

GUI Name: Truncate Log After Backup


ADSMFullBackup

AdsmNode <nodename> designates the name the SQL Agent uses to logon to the ADSM server. The default nodename is client.

GUI Name: ADSM Node

AdsmPwd <node password> designates the password the SQL Agent uses to logon to the ADSM server. The default is blank.

GUI Name: ADSM Password

AsdmOptFile <options file>.opt designates the options file the SQL Agent uses. Enter only the filename with the .opt extension.

GUI Name: ADSM Options File

LogFile <adsm logfile> designates the name of the activity log.

GUI Name: ADSM Activity Log File

Compress Y compresses data before storing it. N does not compress data and is the default.

GUI Name: Compress

Mountwait Y tells the SQL Agent to wait for the ADSM server to complete mount requests. N tells the SQL Agent not to wait and is the default.

GUI Name: Mountwait

Buffers <buffernumber> designates the number of buffers the SQL Agent uses to improve asynchronous communications.

GUI Name: Number of Buffers

Quiet Y does not display status information. N displays status information and is the default.

GUI Name: Quiet

NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If Y, specify the TEC server with

2–10 Version 1.3

ADSMFullBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

TECServer.If you specify Y, specify a valid TECServer argument or no message is sent.


ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the default. If Y, specify the file with ReportFileName and optionally the host with SaveReportFileOn.


SaveReportFileOn

MonitoredHost puts the output file on the host the task was run against. SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName.

ReportHostName

<hostname> is the name of the host on which to save the file created when you use the SpecifiedHost argument.

CLI EXAMPLE

wruntask -t ADSMFullBackup -l "MSSQLManagerTasks"-h @MSSQLDatabase:adsm_db@hbergin@hbergin -a SqlUser=sa -a SqlPwd=’’ -a Truncate=Y -a AdsmNode=client -a AdsmPwd=client -a Compress=Y -a MountWait=Y-a Buffers=8 -a NotifyTEC=Y -a TECServer=EventServer#hbergin-region


ADSMFullBackup

OUTPUT

The following window shows example output for this task.

USAGE NOTES

ADSM stands for ADSTAR Distributed Storage Manager.

ADSMFullBackup makes online backups of one or more databases to ADSM storage.

2–12 Version 1.3

ADSMFullBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

Before you can use ADSMFullBackup, the following conditions must be met:

■ The database server installed on the managed node must be registered by Tivoli Manager for Microsoft SQL Server.

■ The SQL Agent must be installed and configured to back up the database server on the managed node.

ADSMFullBackup connects to the SQL Agent to perform database backups. The agent provides a connection between a database server and an ADSM server. This enables ADSM to protect and manage Microsoft SQL Server data. The agent communicates with ADSM using the ADSM Application Programming Interface (API) and with a database server using the SQL DB-LIBRARY.

The following steps occur when you run the ADSMFullBackup:

1. ADSMFullBackup connects and prompts the SQL Agent to perform a backup with the arguments provided.

2. The SQL Agent starts a session with the database server using DB-LIBRARY.

3. The SQL Agent starts a session with an ADSM server using the ADSM API and the information contained in a client options file.

4. The SQL Agent instructs the database server to begin a dump of the selected database objects.


ADSMFullBackup

M on

1.

n

red

to

5. The SQL Agent receives data from the SQL Agent and forwards it to the ADSM server.

6. The SQL Agent ends the ADSM and database server sessions.

When the ADSM server receives database objects, it stores the objects’ attributes in its own database and writes the database objects’ data to its storage hierarchy. ADSM policies control all aspects of how and where the data is actually stored on the ADSserver. A backup creates a copy of a database or transaction logstorage media. The ADSM server is effectively the dump device when backing up data. The ADSM server hides the details of theactual dump devices.

Microsoft SQL Server Version 6.5 is supported by SQL Agent Versions 1.1 and 1.1.1 and ADSM Server Version 2.0, 3.0 and 3.Microsoft SQL Server Version 7.0 is supported by SQL Agent Version 1.1.1 and ADSM Server Version 3.1. The SQL Agent cacommunicate with an ADSM server running on any supported operating system. This communication must be correctly configuand working in order for this task to succeed.

For more information on the SQL Agent and ADSM server, refer the ADSTAR Distributed Storage Manager Administrators Reference Manual.

SEE ALSO

Tasks: ADSMIncBackup, Dump Database, Dump Transaction Log

2–14 Version 1.3

ADSMIncBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

ADSMIncBackup

DESCRIPTION

Performs a backup of only transaction logs. Incremental backups reduce network usage, server storage, and the time required for backups. You can back up a transaction log only when it is on a separate device than the database. You can choose not to truncate the log.

AUTHORIZATION ROLE

mssqlserver_dba

TARGET ENDPOINT

Database


ADSMIncBackup


The following shows the ADSMIncBackup dialog; a description of each field follows.

Do Not Truncate After Backup

Does not clear the log after an incremental backup when this box is checked. By default, an incremental backup clears out the inactive part of the transaction log. Use this option when rebuilding a corrupt database. It writes all transaction log entries from the time of the last transaction log backup up to the point of a database corruption.

SQL Secure Tells the SQL Agent to use Windows NT to authenticate the user. When you select SQL Secure, the task ignores SQL User and SQL Password.

2–16 Version 1.3

ADSMIncBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

is f

to

M re

Compress Compresses data prior to sending it to ADSM storage. This option can lower network bandwidth utilization, but it increases CPU utilization.

Mountwait SQL Agent should wait for the ADSM server to complete mount requests.

Quiet Prevents status information from displaying.

SQL User Name the SQL Agent uses to logon to the database server. If you do not specify the SQL User, the task uses sa, the default value. If you specify SQL User, specify the corresponding SQL Password value. If the value for SQL Password does not match the password assigned to SQL User, the task fails. If you select SQL Secure, the system ignores this value.

SQL Password

Password the SQL Agent uses to logon to the database server. If you specify Sql User, you must specify what that user’s password is at SQL Password. If the value for SQL Password does not match the password for the user specified with SQL User, the task fails. If you select SQL Secure, the task ignores this value.

ADSM Node Name the SQL Agent uses to logon to the ADSM server. If you do not specify a value for ADSM Node, the task uses the default value, which is client. You can store a password in the options file, but thparameter overrides the value in the options file. Iyou enter a value at ADSM Node you also must enter a value at ADSM Password. If the value for ADSM Password does not match the password assigned ADSM Node, the task fails.

ADSM Password

Password the SQL Agent uses to log onto the ADSserver. The default password is blank. You can stoa password in the options file, but this parameter overrides it.


ADSMIncBackup

ADSM Options File

Name of the ADSM options file the SQL Agent uses. Enter only the filename with the .opt extension. The file must already exist in the install path of the SQL Agent. If you enter a full path name, the task fails.

ADSM Activity Log File

Name of the activity log. Statistics about backed up and restored database objects are written to the specified log file. This option requires only the filename. If you do not specify a path, ADSM stores the file in a default location in its install path. You can force the file to be saved to a specific directory with forward slashes (/). The task ignores a back slash (\) and cannot interpret double (escape) back slashes (\\).

If you specify only the filename without a path name, ADSM stores the file in a default location in its install path.

Number of Buffers

Number of buffers the SQL Agent uses to improve asynchronous communications with the ADSM and database servers.

Report to File



2–18 Version 1.3

ADSMIncBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

CLI SYNTAX

This task can be run with no arguments; it uses default values.

ADSMIncBackup

[–a SqlUser=<sqlusername> –a SqlPwd=<sqluserpassword>]

[–a SQLSecure=Y|N]

[–a NoTruncate=Y|N]

[–a AdsmNode=<nodename>]

[–a AdsmPwd=<node password>]

[–a AsdmOptFile=<options file>.opt]

[–a LogFile=<adsm logfile>]

[–a Compress=Y|N]

[–a Mountwait=Y|N]

[–a Quiet=Y|N]

[–a Buffers=<buffernumber>]








SqlUser <sqlusername> designates the name the SQL Agent uses to logon. The default is sa.

GUI Name: SQL User

SqlPwd <sqluserpassword> designates the password the SQL Agent uses to logon. The default is blank.

GUI Name: SQL Password


ADSMIncBackup

SQLSecure Y uses Windows NT to authenticate user. If you use this argument, do not use the SqlUser and SqlPwd arguments. N is the default.

N uses SqlUser and SqlPwd values to authenticate user.

GUI Name: SQLSecure

NoTruncate Y indicates that you do not want to truncate the transaction log and is the default. N truncates it.

GUI Name: Do not truncate log after backup

AdsmNode <nodename> designates the name the SQL Agent uses to logon to the ADSM server. The default node name is client.

GUI Name: ADSM Node

AdsmPwd <nodepassword> designates the password the SQL Agent uses to logon to the ADSM server. The default is blank.

GUI Name: ADSM Password

AsdmOptFile <options file>.opt designates the options file the SQL Agent uses. Enter only the filename with the .opt extension.

GUI Name: ADSM Options File

LogFile <adsm logfile> designates the name of the activity log.

GUI Name: ADSM Activity Log File

Compress Y compresses data before storing it. N does not compress data and is the default.

GUI Name: Compress

Mountwait Y tells the SQL Agent to wait for the ADSM server to complete mount requests. N tells the SQL Agent not to wait and is the default.

GUI Name: Mountwait

2–20 Version 1.3

ADSMIncBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

Buffers <buffernumber> designates the number of buffers the SQL Agent uses to improve asynchronous communications.

GUI Name: Number of Buffers

Quiet Y does not display status information. N displays status information and is the default.

GUI Name: Quiet

NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC. The default is N. If you specify Y, specify a valid TECServer argument or no message is sent.




SaveReportFileOn



CLI EXAMPLE

wruntask -t ADSMIncBackup -l "MSSQLManagerTasks"-h @MSSQLDatabase:adsm_db@hbergin@hbergin -a SqlSecure=Y -a NoTruncate=Y -a NotifyTEC=Y -a TECServer=EventServer#hbergin-region


ADSMIncBackup

OUTPUT


USAGE NOTES

ADSM stands for ADSTAR Distributed Storage Manager.

ADSMIncBackup makes online backups of one or more transaction logs to ADSM storage.

Before you can use ADSMIncBackup, the following conditions must be met:

■ The database server installed on the managed node must be registered by Tivoli Manager for Microsoft SQL Server.

■ The SQL Agent (identified as SQL Agent in the diagram below) must be installed and configured to backup the database server on the managed node.

ADSMIncBackup connects to the SQL Agent to perform transaction log backups. The agent provides a connection between a database server and an ADSM server. This enables ADSM to protect and

2–22 Version 1.3

ADSMIncBackup

Th

e MS

SQ

LM

anag

erTasks L

ibrary

M e

manage SQL data. The agent communicates with ADSM using the ADSM Application Programming Interface (API) and with a database server using the SQL DB-LIBRARY.

The following occurs when you run ADSMIncBackup:

1. ADSMIncBackup connects and prompts the SQL Agent to perform a backup with the arguments provided.

2. The SQL Agent starts a session with the database server using DB-LIBRARY.

3. The SQL Agent starts a session with an ADSM server using the ADSM API and the information contained in a client options file.

4. The SQL Agent instructs the database server to begin a dump of the selected database transaction log.

5. The SQL Agent receives data from the database server and forwards it to the ADSM server.

6. The SQL Agent ends the ADSM and database server sessions.

When the ADSM server receives database objects, it stores the objects’ attributes in its own database and writes the database objects’ data to its storage hierarchy. ADSM policies control all aspects of how and where the data is actually stored on the ADSserver. A backup creates a copy of the transaction log on storagmedia. The ADSM server is effectively the dump device when


ADSMIncBackup

backing up data using this task. The ADSM server hides the details of the actual dump devices.

Microsoft SQL Server Version 6.5 is supported by SQL Agent Versions 1.1 and 1.1.1 and ADSM Server Version 2.0, 3.0 and 3.1. Microsoft SQL Server Version 7.0 is supported by SQL Agent Version 1.1.1 and ADSM Server Version 3.1. The SQL Agent can communicate with an ADSM server running on any supported operating system. This communication must be correctly configured and working in order for this task to succeed.

For more information on the SQL Agent and ADSM server, refer to the ADSTAR Distributed Storage Manager Administrators Reference Manual.

SEE ALSO

Tasks: ADSMFullBackup, Dump Database, Dump Transaction Log

2–24 Version 1.3

ConfigureTECMSSQL

Th

e MS

SQ

LM

anag

erTasks L

ibrary

ConfigureTECMSSQL

DESCRIPTION

Provides TEC configuration options. You can configure TEC to receive events from the following:

■ Distributed Monitors (MSSQLServer and MSSQLDatabase monitors)

■ Tasks (MSSQLManagerTask tasks)

■ TEC NT Event Adapter

■ GEM Instrumentation (if installed)

The task adds the class and rule set definitions of the selected configuration option to a valid rule base, if the class and rule set definitions are not already defined in the specified rule base. Chapter 4, “Setting Up Tivoli Manager for Microsoft SQL Server,” in the Tivoli Manager for Microsoft SQL Server User’s Guide provides a procedure for this task.

Before you run this task, the following software must be installed:

■ TEC Event Server

■ The Tivoli Manager for Microsoft SQL Server on the TMR server of the TMR on which to run this task.

ConfigureTECMSSQL does the following, depending on the options you choose:

1. Creates a rule base in the directory where TEC is installed.

2. Provides TEC configuration for the specified options. It adds class and rule set definitions to a valid rule base for the options, if they are not already defined in the specified rule base.

3. Copies a specified rule base into the newly created rule base.

4. Creates the event group(s).

5. Adds filters to an event group for the TEC configuration options specified.

6. Loads the rule base.

7. Restarts the event server.


ConfigureTECMSSQL

AUTHORIZATION ROLE

super, senior, admin, user, and mssqlserver_dba (must have all roles)

TARGET ENDPOINT

Managed node (where the event server is installed)


The following shows the ConfigureTECMSSQL dialog; a description of each field follows.

Rule Base Name

Name of the rule base to configure. This can be the new name for a rule base that you want to create or the name of an existing rule base. If you specify an existing rule base, ConfigureTECMSSQL checks to make sure both its class and rule set files are

2–26 Version 1.3

ConfigureTECMSSQL

Th

e MS

SQ

LM

anag

erTasks L

ibrary

ll

defined correctly. Enter only the name; a full path is ignored.

Copy Rule Base

Uses an existing rule base as the basis for the rule base you are setting up for this configuration option.

Rule Base to Copy

Name of the rule base to copy. If you leave this field blank after selecting the Copy Rule Base check box, the task uses the Default rule base. If you use a rule base other than Default, it must be a valid rule base.

The Default rule base contains correctly defined default classes. Although Tivoli Manager for Microsoft SQL Server does not need these classes, other applications (such as adapters) may require them.

Create Event Group

Creates an event group for this configuration option.

Event Group Name

Name of the event group that you create. If you select the Create Event Group check box and do not enter an event group name, the task creates and configures an event group called MSSQLEventBase. If you specify an existing event group, the task configures the event group that you named.

Event Server option to configure

TEC filters to add to the event group. The options include the following:

Configure Event Server for Distributed Monitoring — enables the event server to receive aevents sent from the MSSQLServer and MSSQLDatabase monitors.


ConfigureTECMSSQL

e

t is

he ke

If

nt

Configure Event Server for Tasks — enables the event server to receive all events sent from MSSQLManagerTasks tasks.

Configure Event Server for TEC NT Event Adapter — enables the event server to receive allevents reported from the Windows NT event log. Threporting of those events is configured using the Customize TEC NT Event Adapter MSSQL task.

Configure Event Server for GEM — enables the event server to receive all events sent from GEM. This option appears only if the GEM integration package for Tivoli Manager for Microsoft SQL Server is installed.

Restart Event Server

Loads the rule base and starts the event server, if inot already running. When you create a new rule base or modify an existing one, you must restart tevent server for any rule base configurations to taeffect.

If the event server is not running, this task starts it.the event server is running, this task stops and restarts it. If you do not have the task restart the eveserver, you must load the rule base and restart theevent server manually. (See the TME 10 Enterprise Console User’s Guide for information on how to do this.)

Report to File



2–28 Version 1.3

ConfigureTECMSSQL

Th

e MS

SQ

LM

anag

erTasks L

ibrary

CLI SYNTAX

ConfigureTECMSSQL

–a RuleBaseName=<rulebasename>

[–a CreateEventGroup=Y|N [–a EventGroupName=<eventgroupname>]]

[–a CopyBase=Y|N [–a CopyBaseName=<rulebasetocopy>]]

–a ConfigureForDM=Y|N

–a ConfigureForTask=Y|N

–a ConfigureForTECAdapter=Y|N

–a ConfigureForGEM=Y|N

[–a RestartServer=Y|N]








RuleBaseName

<rulebasename> is the name to give to the rule base.

GUI Name: Rule Base Name

CreateEventGroup

Y creates an event group and is the default. N does not create an event group.

GUI Name: Create Event Group

EventGroupName

<eventgroupname> is the name to give to the event group that you are creating.

GUI Name: Event Group Name


ConfigureTECMSSQL

CopyBase Y uses an existing rule base as the basis for the rule base you are setting up. N does not use the existing rule base.

GUI Name: Copy Rule Base

CopyBaseName

<rulebasetocopy> is the name of the rule base to copy.

GUI Name: Rule Base Name

ConfigureForDM

Y enables the event server to receive all events sent from the MSSQLServer and MSSQLDatabase monitors. N does not set this option.

GUI Name: Configure the TEC for Distributed Monitoring

ConfigureForTask

Y enables the event server to receive all events sent from MSSQLManagerTasks tasks. N does not set this option.

GUI Name: Configure Event Server for Tasks

ConfigureForTECAdapter

Y enables the event server to receive all events reported from the Windows NT event log. The reporting of those events is configured using Customize TEC NT Event Adapter MSSQL. N does not set this option.

GUI Name: Configure Event Server for TEC NT Event Adaptor

ConfigureForGEM

Y enables the event server to receive all events sent from GEM. N does not set this option. Prerequisite: GEM and the GEM integration package for Tivoli

2–30 Version 1.3

ConfigureTECMSSQL

Th

e MS

SQ

LM

anag

erTasks L

ibrary

Manager for Microsoft SQL Server must be installed.

GUI Name: Configure Event Server for GEM

RestartServer Y restarts the server. N does not restart the server.

GUI Name: Restart Event Server





SaveReportFileOn



CLI EXAMPLE

wruntask -t ConfigureTECMSSQL -l "MSSQLManagerTasks" -h @ManagedNode:nemuchay -a RuleBaseName=MSSQLBase1 -a CopyBase=Y -a CopyBaseName=Default-a CreateEventGroup=Y -a EventGroupName=MSSQLEventBase1 -a ConfigureForDM=Y -a ConfigureForTask=Y -a ConfigureForTECAdapter=Y


ConfigureTECMSSQL

OUTPUT


USAGE NOTES

The $root_user virtual login name is mapped to tmersrvd across TMR boundaries by default in Windows NT environments. Administrators with a login of $root_user do not have sufficient operating system privileges to create the files and directories for a new rule base in another TMR. You can edit administrator properties to change this: see the Tivoli Enterprise Console User’s Guide.

You must restart the event server after defining new classes so that TEC can recognize and display instances of them. Because each command defines new classes, you must stop and restart the event server for each instance of these defined classes.

SEE ALSO

Tasks: Customize TEC NT Event Adapter MSSQL

2–32 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

d

.


DESCRIPTION

Customizes the TEC NT Event Adapter to detect and forward Microsoft SQL Server events from the Windows NT event log to the TEC server. You can define classes for different types of events and write rules for actions.

Customize TEC NT Event Adapter MSSQL does the following:

1. Checks if the NT Event Adapter is already customized for Microsoft SQL Server Events.

2. Checks if the TEC NT Event Adapter is configured to accept customization.

3. Makes a backup of the existing TEC NT Event configuration. See the “Usage Notes” for additional information on how anwhy this is done.

4. Customizes the Adapter to receive different types of events

AUTHORIZATION ROLE

senior and mssqlserver_dba

TARGET ENDPOINT

Managed node


The following shows the CustomizeTECNTEventAdapter dialog; a description of each field follows.



You select the filters to screen out events, not to include them. If you do not select any of the filter check boxes, this task does not filter out any events. This means that all events in the following event classes are sent to the TEC.

NT_MSSQLError

Does not send any error events when checked. Fatal errors are always reported to the Windows NT event log when event logging is enabled. See the NT Event Logging task for information on configuring what SQL Server events are written to the Windows NT event log.

NT_MSSQLMessage

Does not send any message events when checked. Messages can include warnings that a backup record could not be written. Microsoft defines which types of events are considered messages. This task uses the Microsoft classification.

2–34 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

NT_MSSQLInformation

Does not send any information events when checked. Information events can include information on backups being performed and the server being stopped and started. Microsoft defines which types of events are considered information. This task uses the Microsoft classification.

NT_SQLExecutiveBase

Does not send any events associated with the SQLExecutive service when checked. SQLExecutive events include information on tasks and replication. The SQLExecutive service is unique to Microsoft SQL Server Version 6.5; it is called SQLServerAgent in 7.0.

NT_SQLServerAgentBase

Does not send any events associated with the SQLServerAgent service when checked. SQLServerAgent events include information on jobs and replication. The SQLServerAgent service is unique to Microsoft SQL Server Version 7.0; it is called SQLExecutive in 6.5.

NT_MSDTCBase

Does not send any events associated with the MSDTC service when checked. MSDTC information relates to Distributed Transaction Coordination.

Overwrite any previous MSSQL customization

Overwrites any previous Microsoft SQL Server customization to the TEC NT Event Adapter when the check box is selected. When you run this task for the first time, you do not need to select this option to customize the Adapter. To make subsequent changes to the customization, make sure that you select this option each time you rerun the task. When you rerun this task and do not select Overwrite any previous



MSSQL customization, you receive a message that the Adapter is already customized for Microsoft SQL Server Events.

Report to File



CLI SYNTAX

CustomizeTECNTEventAdapter

[–a OverwritePrevious=Y|N]

[–a FilterErrors=Y|N]

[–a FilterMessages=Y|N]

[–a FilterInformation=Y|N]

[–a FilterSQLExecutive=Y|N]

[–a FilterSQLServerAgent=Y|N]

[–a FilterMSDTC=Y|N]








OverwritePrevious

Y overwrites any previous Microsoft SQL Server customization to the TEC NT Event Adapter. N does not overwrite previous adaptations.

GUI Name: Overwrite any previous MSSQL customization

2–36 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

FilterErrors

Y filters out error events associated with Microsoft SQL Server. N does not filter.

GUI Name: NT_MSSQLError

FilterMessages

Y filters out message events associated with Microsoft SQL Server. N does not filter.

GUI Name: NT_MSSQLMessage

FilterInformation

Y filters out information events associated with Microsoft SQL Server. N does not filter.

GUI Name: NT_MSSQLInformation

FilterSQLExecutive

Y filters out events associated with the SQLExecutive service. N does not filter.

GUI Name: NT_SQLExecutiveBase

Note: The SQLExecutive service in Version 6.5 is called the SQLServerAgent service in Microsoft SQL Server Version 7.0.

FilterSQLServerAgent

Y filters out events associated with the SQLServerAgent service. N does not filter.

GUI Name: NT_SQLServerAgentBase

Note: The SQLExecutive service in Version 6.5 is called the SQLServerAgent service in Microsoft SQL Server Version 7.0.

FilterMSDTC

Y filters out events associated with the MSDTC service. N does not filter.

GUI Name: NT_MSDTCBase







SaveReportFileOn



CLI EXAMPLE

wruntask -t CustomizeTECNTEventAdapter -l "MSSQLManagerTasks" -h @ManagedNode:nemuchay -a OverwritePrevious=Y -a FilterInformation=Y -a FilterSQLExecutive=Y -a FilterMSDTC=Y

2–38 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

OUTPUT


USAGE NOTES

This task backs up the tecad_nt.conf and tecad_nt.fmt files before customizing them.

The naming convention for the backup files is:

<filename>.before.mssql.<timestamp>

The <timestamp> convention is year.month.day.hour.minute, using a 24-hour clock (4pm is represented as hour 16). For example, the following filenames show that backups were done at 10:16 a.m. on July 9, 1999 before the adapter customization.

tecad_nt.conf.before.mssql.1999.07.09.10.16

tecad_nt.fmt.before.mssql.1999.07.09.10.16

Only one set of backup files is maintained at a time. When you run the Restore TEC NT Event Adapter MSSQL task with the



RestoreFromBackup argument, it uses these files to restore the adapter.

SEE ALSO

Tasks: ConfigureTECMSSQL, NT Event Logging, Restore TEC NT Event Adapter MSSQL

2–40 Version 1.3

Database Check-up and Tune-up

Th

e MS

SQ

LM

anag

erTasks L

ibrary

st

t

” for

e


DESCRIPTION

Performs a series of regular maintenance tasks that correct many inconsistencies in the database and tune the performance of the system.

Database Check-up and Tune-up does the following:

1. Runs DBCC CHECKDB, DBCC NEWALLOC, DBCC CHECKCATALOG, and DBCC CHECKIDENT.

• DBCC CHECKDB checks each table to ensure that:

- Index and data pages are correctly linked

- Indexes are in proper sorted order

- All pointers are consistent

- Data information on each page is reasonable

- Page offsets are reasonable

• DBCC NEWALLOC checks data and index pages againcorresponding extent structures. (Version 6.5 only; this function is performed as part of DBCC CHECKDB in Version 7.0.)

• DBCC CHECKCATALOG identifies inconsistencies between system tables and checks the validity of the lascheckpoint.

• DBCC CHECKIDENT corrects disrupted identity columnvalues that can result from unclean shutdowns or non-logged operations.

2. Rebuilds fragmented indexes and runs UPDATE STATISTICS to ensure that the query optimizer is using the most recent information.

3. Drops and reloads stored procedures. See the “Usage Notesadditional information.

4. Runs DBCC UPDATEUSAGE to ensure more accurate spacusage statistics.



5. Runs DBCC FIX_AL when DBCC NEWALLOC returns errors 2540 or 2541 and DBCC CHECKDB returns no errors. (Version 6.5 only.)

AUTHORIZATION ROLE

mssqlserver_dba

Microsoft SQL Server Permissions:

■ Microsoft SQL Server 6.5: SA or DBO

■ Microsoft SQL Server 7.0: sysadmin or db_owner

TARGET ENDPOINT

Database


The following shows the DBCheckup dialog; a description of each field follows.

2–42 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Rebuild if fragmentation % is greater than

Index fragmentation limit. When the actual index fragmentation percentage is greater than the number entered, this task rebuilds the index. (This is optional.)

Stored Procedure Archive

Provides a record of the stored procedures that were dropped and recreated. The creation script is a snapshot of all user-defined stored procedures in the database at the time the task was run. The utilities provided with Tivoli software enable you to decompress and untar this file. A compressed tar file reduces the size of large files for storage and transfer across the network.

Path and name is the directory in which to place the tar file of the SQL script used to drop and recreate all user-defined stored procedures.

There are several default variables for this entry. For a description of these variables, see “Using the Create a Report File Dialog” on page 8-7 in the Tivoli Manager for Microsoft SQL Server User’s Guide.

On monitored host creates the output file on each of the monitored hosts the task was run against. (Mutually exclusive with On specified host.)

On specified host creates the output file on a specific host; you cannot save output files on multiple hosts. You specify the host name with Host name. (Mutually exclusive with On monitored host.)

Host Name displays a scrolling list of host names from which you can select a host. The host is used to store the output file. Use with On specified host.

Report to File





CLI SYNTAX

This task can be run with no arguments. In that case, default values are used for the arguments.

DBCheckup

[–a FragLimit =<percentage>]

[–a ArchiveFileName=<filename>]

[–a SaveArchiveFileOn=MonitoredHost | SpecifiedHost]

[–a ArchiveHostName=<hostname>]








FragLimit <percentage> is the value for an index fragmentation limit. The default limit is 30.

GUI Name: Rebuild if fragmentation % is greater than

ArchiveFileName

<filename> is the path and filename for the stored procedure syntax archive file.

If you do not specify this argument, the task does not drop and recreate the user-defined stored procedures on the endpoint database.

The SaveArchiveFileOn and ArchiveHostName arguments are valid only when ArchiveFileName is specified. If you specify either of those arguments

2–44 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

without specifying ArchiveFileName, the task ignores them.

GUI Name: Path and filename

SaveArchiveFileOn

Choose one of the following:

MonitoredHost creates the output file on the monitored host against which the task was run. This is the default.

GUI Name: On monitored host

SpecifiedHost creates the output file on a specified host. Specify the host with ArchiveHostName.

GUI Name: On specified host

ArchiveHostName

<hostname> is the name of the host computer. If you use the SaveArchiveFileOn=SpecifiedHost argument, but do not specify a host name here, the task defaults to SaveArchiveFileOn=MonitoredHost.

GUI Name: Host name







SaveReportFileOn



CLI EXAMPLEwruntask -t DBCheckup -l "MSSQLManagerTasks" -h @MSSQLDatabase:pubs@hbergin@hbergin -a FragLimit=0-a ArchiveFileName=’${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.taz’-a SaveArchiveFileOn=SpecifiedHost -a ArchiveHostName=hbergin -a ReportToFile=Y-a ReportFileName=’${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.rpt’-a SaveReportFileOn=SpecifiedHost -a ReportHostName=hbergin

2–46 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

d

oes e

OUTPUT


Output information includes:

■ Errors found while running DBCC statements

■ Statistics on the procedures run, as follows:

• Index fragmentation checked on: reports the number of tables with indexes defined, plus the number of clustereand non-clustered indexes checked.

• Index rebuilt on: reports the number tables where the fragmentation limit was exceeded, plus the number of clustered indexes and non-clustered indexes that were rebuilt.

• Statistics updated on: reports the number of tables and indexes on which statistics were updated. This number dnot included the number of tables and indexes where th



n all

s

the

’

they

is to

ch ure fter up.

indexes were rebuilt, because statistics are updated automatically when indexes are rebuilt.

• Space usage update on: reports the total number of tablesand indexes in the database. Space usage is updated otables and indexes in the database.

■ Location of the tar file

USAGE NOTES

You should put the server in single user mode before running thitask. If it is not in single user mode, the task will run but you mayencounter error messages and problems. Putting the database insingle user mode ensures the cleanest execution of this task for following reasons:

■ The database must be in single user mode in order for the information on the syslogs table to be updated.

■ The DBCC NEWALLOC statement may find spurious allocation problems (such as error 2558) due to other userstransactions in progress.

■ The DBCC FIX_AL statement can run only in single user mode. It normally fixes error 2540 regarding allocation discrepancy.

■ Stored procedures cannot be dropped and recreated when are in use.

For Microsoft SQL Server Version 6.5: The task drops and reloadsstored procedures. Each time a query tree is rebuilt, sysprocedures appends it to the old one. The only way to start a new query tree drop and recreate the stored procedure, which this task does automatically when you specify the archive filename and path. Easp_recompile call rebuilds the query tree, so a large stored procedcan easily reach its query tree size limit of 64Kb. If errors persist aDBCC FIX_AL runs, then restore the database from a good back

For Microsoft SQL Server Version 7.0: DBCC FIX_AL no longer exists. DBCC CHECKDB is called with the REPAIR_REBUILD option, if the database is in single user mode.

2–48 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

To extract and check the contents of the taz file that is created, use the following:

uncompress filename.taz > filename.tartar –xvf filename.tar

The uncompress command shown uncompresses the tar archive. The tar command shown extracts the contents of the archive and places them in the current directory. See the online help for the tar command for more options.

You may also use a commercial compression utility to extract the files, such as WinZip (available at http://www.winzip.com). However, Tivoli Systems provides technical support only for the use of the Tivoli utilities.

SEE ALSO

Tasks: Rebuild Fragmented Indexes, Refresh Query Optimizer Statistics, Update Space Usage Information




DESCRIPTION

Changes the configuration so that the physical and logical disk counters used in performance monitoring are deactivated. These counters are disabled by default for performance reasons. Use this command only when you have enabled the counters with the Enable NT Disk Performance Counters task.

AUTHORIZATION ROLE

mssqlserver_dba and NT Administrator

TARGET ENDPOINT

Managed node


The following shows the DisableDiskCounters dialog; a description of each field follows.

Reboot NT Server

Reboots Windows NT. The task changes the disk performance counters configuration; but the configuration change does not take effect until the computer is restarted. If you do not use this check box, you can restart the server at a later time.

2–50 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Report to File



CLI SYNTAX


DisableDiskCounters

[–a RebootNTServer=Y | N]








RebootNTServer

Y restarts the NT Server. N does not restart it.

GUI Name: Reboot NT Server







SaveReportFileOn



CLI EXAMPLE

wruntask -t DisableDiskCounters -l "MSSQLManagerTasks" -h @ManagedNode:hbergin -a RebootNTServer=No

2–52 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

OUTPUT


USAGE NOTES

You must restart the NT Server (either by specifying it with this task or by using the SHUT DOWN command on the Windows NT Start menu) before changes can take effect.

You must be logged on to an account belonging to the Windows NT Administrators group to do this.

SEE ALSO

Tasks: Enable NT Disk Performance Counters


Discover MS SQL Servers

nd er


DESCRIPTION

Finds a database server installation on a managed node and registers it on the Tivoli desktop. Tivoli recommends running this task serially when run against multiple nodes. There may be contention issues on the TMR server when it is run in parallel.

For additional information, see “Registering a Database Server aDiscovering Its Databases” in Chapter 4, “Setting Up Tivoli Managfor Microsoft SQL Server,” of the Tivoli Manager for Microsoft SQL Server User’s Guide.

AUTHORIZATION ROLE


TARGET ENDPOINT

Managed node

2–54 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary


The following shows the DiscoverSQLSRVR dialog; a description of each field follows.

Register MS SQL Server Icon on Tivoli Desktop

This area includes the following fields:

Policy Region designates the region in which to register the database server icon. You must specify a policy region in this field. You can specify a different policy region than the one from where you are running this task. If this tasks fails to register the database server, it removes the policy region it created.

Parent Policy Region designates the parent policy region for a new policy region specified with Policy Region. The task does not register the server in the parent policy region. Use this field when you create a new policy region to specify where to locate the new policy region in the policy region hierarchy.



The following table shows how entries in the Policy Region and Parent Policy Region fields determine where the server is registered.

Ignore server state when registering

Ignores the database server state when during registration. Unless you use this option, you cannot successfully register the database server when the

Policy Region

Parent Policy Region

Policy Region Creation and Server Icon Registration

Entered/ Does not exist

Entered/ Exists

Creates the new policy region as a sub-region of the parent policy region and registers the server icon in the new policy region.



Error. Does not know where to create this policy region.


Blank Creates the new policy region at the top level and registers the server icon in the new policy region.

Entered/ Exists

Entered/ Exists

Registers the server icon in the specified policy region.

Entered/ Exists


Registers the server icon in the specified policy region.

Entered/ Exists

Blank Registers the server icon in the specified policy region.

Blank Entered/ Exists

Error. Does not know where to register the server icon.

Blank Entered/ Does not exist

Error. Does not know where to register the server icon.

Blank Blank Error. Does not know where to register the server icon.

2–56 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

database server is not running. Some administrators may not want to use this option: when you use it and the server is not running, the databases associated with the database server are not available until you refresh the server’s collection of objects with the Refresh Databases task while the server is running.

MS SQL Server Logon (for standard security only)

This section has two fields:

User Name designates the logon name that has access to the database server and its databases.

If this field is left blank (recommended), Tivoli Manager for Microsoft SQL Server logs on through a trusted connection. See “Using Trusted Connections” in Chapter 4, “Setting Up Tivoli Manager for Microsoft SQL Server” in the Tivoli Manager for Microsoft SQL Server User’s Guide for more information about trusted connections.

Password designates the password associated with User Name field. If you leave the User Name field blank, leave this field blank, too.

Report to File



CLI SYNTAX

The only required argument for this task is PolicyRegion.

DiscoverSQLSRVR

–a PolicyRegion=<policyregionname>

[–a ParentPolicyRegion=<parentpolicyregionname>]

[–a IgnoreSRVRState=Y | N]

[–a UserName=<name>]



g

se

[–a Password =<password>]








PolicyRegion <policyregionname> is the name of the region in which to register the database server.

GUI Name: Policy Region

ParentPolicyRegion

<parentpolicyregionname> is the parent policy region in which to create the PolicyRegion. See Parent Policy Region in the “GUI Data Entry Fields” section for complete information about thisargument.

GUI Name: Parent Policy Region

IgnoreSRVRState

Y — register the server whether or not it is runninand whether or not Tivoli Manager for Microsoft SQL Server can log on to it.

N — do not register the server when it cannot connect to it. This is the default.

GUI Name: Ignore server state when registering

Username <name> is the logon name for access to the databaserver and its databases. You can specify a Username, but Tivoli does not recommend it.

GUI Name: User Name

2–58 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Password <password> is the password for Username. If you did not use the Username argument, do not use this argument.

GUI Name: Password




ReportFileName

<filename> is the path to and the name of the file to create as the task output.

SaveReportFileOn



CLI EXAMPLE

wruntask -t DiscoverSQLSRVR -l "MSSQLManagerTasks" -h @ManagedNode:hbergin -a PolicyRegion="hbergin-region"-a ParentPolicyRegion="parent-region"-a IgnoreSRVRState=Y -a UserName="sa" -a Password=" "



OUTPUT


USAGE NOTES

Although Microsoft SQL Server Versions 6.5 and 7.0 can reside on the same Windows NT installation (for upgrade purposes), only one can be active at any time.

SEE ALSO

None

2–60 Version 1.3

Dump Database

Th

e MS

SQ

LM

anag

erTasks L

ibrary

Dump Database

DESCRIPTION

Performs a full database backup.

Dump Database does the following:

1. Provides the option for checking the database integrity before backing up to ensure the backup is viable.

2. Allows you to designate an existing backup device, a temporary backup device, or the previous backup device when possible.

3. Allows you to specify a list of backup options, for example, whether to append to a previous backup or to overwrite it. You may also specify what type of backup to perform. The backup options available vary by version of Microsoft SQL Server (6.5 or 7.0).

4. Checks the backup’s readability after the backup is complete. Verification consists of reading header information and verifying that the backup set is complete and all volumes are readable. Data structure in the backup volume is not verified.

5. Reports some statistics on the backup procedure along with the header information on the backup device.

AUTHORIZATION ROLE

mssqlserver_dba


■ Microsoft SQL Server 6.5: SA, DBO, or Dump DB

■ Microsoft SQL Server 7.0: sysadmin, db_owner, or db_backupoperator

TARGET ENDPOINT

Database


Dump Database


The following shows the DumpDatabase dialog; a description of each field follows.

Validate database integrity

Runs DBCC CHECKDB, NEWALLOC, CHECKCATALOG, and CHECKIDENT to determine if the database is corrupted. If the database fails the integrity checks, the backup is not performed.

Backup Device

Uses one of two options:

Use same device as last backup uses the same backup device that you used the last time you backed

2–62 Version 1.3

Dump Database

Th

e MS

SQ

LM

anag

erTasks L

ibrary

or

up the database. If the task cannot determine the last backup device, it fails.

Specify backup device (logical name or temporary device) is the logical name for an existing backup device or a temporary device. When you specify a temporary device, the system creates it, if it does not exist.

For striped disk backups, enter a comma-separated list of logical names, temporary devices, or a mixture of both. The list entered can be a mix of logical and temporary filenames (or variables). The device types, however, must be the same.

Dump devices used in a stripe set must always be used in a striped set (unless you reinitialize it at some point). Once a device is defined as part of a striped set, you cannot use it for a single device dump, unless you overwrite it. You cannot use a device that contains non-striped dumps in a striped set, unless you overwrite it. Tivoli does not recommend dumping to diskette; see the “Usage Notes” for additional information.

The following shows how logical and temporary device names are entered: Logical Device:<logical_name>

Temporary Device: <DISK|TAPE|FLOPPY|DISKETTE=<physical path and filename>

Backup options

Enter a comma-separated list of options. For all options that take a parameter, a Microsoft SQL Server variable can be used as well as literal text. Fmore information on these options, see the description of BACKUP in Microsoft SQL Server Book On-line.


Dump Database

Choose from the following options:

BLOCKSIZE=numberSets the block size to use when writing the backup. When writing to DISK or TAPE, the size is set automatically unless overridden. When writing to PIPE, the default size is 65,536 unless overridden.

DESCRIPTION=textSpecifies a description for the backup set. The maximum length is 255 characters. Default: blank.

DIFFERENTIAL Use with Microsoft SQL Server Version 7.0 only: Specifies a differential backup rather than a full backup. Default: full backup.

EXPIREDATE=date or RETAINDAYS=numberSpecifies when the backup file may be overwritten. Only one of these options may be used. EXPIREDATE specifies the expiration date. RETAINDAYS specifies how many days to retain the backup.

FORMAT or NOFORMATWrites the media header on all volumes used for this backup and rewrites the backup device. Any existing media header is overwritten. All media contents are invalidated, ignoring any existing password. Use only on complete backup sets. Using it on a single tape belonging to an existing striped backup set renders the entire backup set useless. Using FORMAT implicitly sets INIT and SKIP. They do not have to be specified separately.

INIT or NOINITINIT means the backup overwrites any previous backup on the backup device. The media header is preserved. NOINIT means the backup is appended to the previous backup, if any. Default: NOINIT. The backup does not overwrite if it encounters any of the following conditions:

2–64 Version 1.3

Dump Database

Th

e MS

SQ

LM

anag

erTasks L

ibrary

m

IP

pt

The media contains unexpired backup sets. You can override this condition by specifying SKIP.

An explicitly given backup set name does not match the name on the backup media. You can override this condition by specifying SKIP.

The backup media is password-protected.

The backup media is encrypted.

MEDIADESCRIPTION= textSpecifies a description for the media set. The maximum length is 128 characters. Default: blank.

MEDIANAME=text Specifies the media name for the backup. When specified, if the existing MEDIANAME on the backup media doesn’t match, the backup fails.

NAME=text Specifies the name of the backup set. The maximulength is 128 characters. Default: blank.

RESTART Use when restarting a backup operation that was interrupted. SQL Server attempts to restart the backup where it was interrupted, possibly saving time.

SKIP or NOSKIPSKIP disables the checking for name match and expiration date of all backup sets on the media. SKcan be used with INIT (see description). NOSKIP can be used with FORMAT to override its default behavior (see description). Default: NOSKIP excewhere otherwise noted.

STATS=percentSpecifies how often to write a progress message, expressed in percent complete. Default: 10.

UNLOAD or NOUNLOADUsed only for tape devices. UNLOAD specifies that


Dump Database

the media be rewound and unloaded (ejected) when the backup is complete. Default: NOUNLOAD.

Report to File



CLI SYNTAX

There are two ways to specify the syntax for this task. You must specify either the DumpDevice= Last argument or the DumpTo =<devicename> argument to run this task.

DumpDatabase

[–a ValidateDB=Y | N]

–a DumpDevice=Last

[–a WithOptions “ options” ]

[–a NotifyTEC ]

[–a ReportToFile]

—OR—

DumpDatabase

[–a ValidateDB=Y | N]

[–a DumpDevice=Specified]

–a DumpTo=<devicename1>, [<devicename2>, <devicename3>, <devicename...>]


[–a NotifyTEC ]

[–a ReportToFile]


ValidateDB

Y runs DBCC CHECKDB , NEWALLOC (Version 6.5 only), CHECKCATALOG , and

2–66 Version 1.3

Dump Database

Th

e MS

SQ

LM

anag

erTasks L

ibrary

CHECKIDENT to determine if the database is corrupted. N does not validate the integrity of the database. This is the default.

GUI Name: Validate database integrity

DumpDevice This is optional when you specify DumpTo.

Last uses the same backup device that you used the last time you backed up the database. If the task cannot determine the last device, it fails.

GUI Name: Use same device as last backup

Specified uses a backup device that you specify with DumpTo.

GUI Name: Specify backup device (logical name or temporary device)

DumpTo Logical name for an existing backup device or a temporary device. This argument is ignored when you specify DumpDevice=Last.

GUI Name: Specify backup device (logical name or temporary device)

WithOptions Specifies the backup options to use. Options must be a comma-separated list and enclosed in double quotes. The options are specified the same way as in the Backup Options GUI field.

GUI Name: Backup Options





Dump Database


SaveReportFileOn



CLI EXAMPLE

wruntask -t DumpDatabase -l "MSSQLManagerTasks"-h @MSSQLDatabase:msdb@hbergin@hbergin -a ValidateDB=N -a DumpDevice=Specified -a DumpTo=DumpA -a WithOptions="INIT,UNLOAD"

OUTPUT

The following shows sample output for this task.

More information is available if you use the Report to File argument. Among other information, output sent to the report file includes the following:

2–68 Version 1.3

Dump Database

Th

e MS

SQ

LM

anag

erTasks L

ibrary

■ Detail of errors found running DBCC checks

■ Database name, device name and types, number of pages backed up, start time of backup, finish time of backup

■ Output from the LOAD HEADERONLY command

USAGE NOTES

Backups of individual files and file groups are not supported through this task.

For backups to remote machines, Microsoft SQL Server service must have rights on the remote machine and cannot be running under the local system account.

Do not make master backups to striped devices. Doing so causes the task to fail and return a warning.

Dumping to diskette is not supported in Microsoft SQL Server Version 7.0. Tivoli does not recommend dumping to diskette. You should back up to a disk device and copy (or use the file backup command) to a diskette instead.

To make a backup to a floppy disk, CONSOLE.EXE must be running in a MS-DOS window, and you must manually load and remove diskettes. A series of prompts guides you through the back up. If CONSOLE.EXE is not running, the dump cannot continue. If it is running and you do not answer its questions, the dump cannot continue. See the Windows NT Help or the Microsoft SQL Server Books On-line system for additional information on the CONSOLE command.

Before backing up a database, it is common practice to back up a transaction log using the TRUNCATE_ONLY option to clear out the log and decrease the total time required to back up the database. However, if the database backup is not done immediately or for some reason fails, all the logged transactions could be lost. This task does not truncate the log before backing up the database.

A special device, named DISKDUMP, is created when Microsoft SQL Server is installed. Backing up to DISKDUMP sends the data to the NULL device, which dumps data without saving it. You can use the DISKDUMP device name as a bit bucket in conjunction with


Dump Database

database or transaction log backups. You cannot retrieve dumps sent to the NULL (DISKDUMP) device.

SEE ALSO

Tasks: ADSMFullBackup, ADSMIncBackup, Dump Transaction Log, MS SQL Server Warnings and Indicators

2–70 Version 1.3

Dump Transaction Log

Th

e MS

SQ

LM

anag

erTasks L

ibrary

g og ing me

ry e.

ou

pe he

e.

e

the


DESCRIPTION

Backs up, truncates, or backs up and truncates a database’s transaction log.

In a production environment, many DBAs schedule transaction lodumps to manage normal server activity so that the transaction lnever fills up. Full database backups do not truncate the log; durexceptionally high database usage, the transaction log may becofull. To alleviate this problem, you should configure the Log Space Used monitor to run this task to perform an interim dump.

This task does the following:

1. Allows you designate an existing backup device, a temporabackup device, or the previous backup device when possibl

2. Allows you to specify a list of backup options. For example, ycan choose to append a backup to a previous backup or overwrite the previous backup. You may also specify what tyof backup to perform. The backup options available vary by tversion of Microsoft SQL Server (6.5 or 7.0).

3. Checks the backup's readability after the backup is completVerification consists of reading header information and verifying that the backup set is complete and all volumes arreadable. Data structure in the backup volume is not verified.

4. Reports some statistics on the backup procedure along withheader information on the backup device.

AUTHORIZATION ROLE

mssqlserver_dba


■ Microsoft SQL Server 6.5: SA, DBO, or Dump Trans

■ Microsoft SQL Server 7.0: sysadmin, db_owner, or db_backupoperator



TARGET ENDPOINT

Database


The following shows the DumpTransactionLog dialog; a description of each field follows.

Dump Options Specify how to backup and or truncate a transaction log. Your choices are the following:

Backup and truncate backs up the transaction log and truncates it. Truncating the log clears it of all non-active transactions. You may only use this

2–72 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

option when the transaction log is on a separate device fragment than the data.

Backup backs up the transaction log, but does not truncate it. The SYSBACKUPHISTORY table in Version 6.5 does not record this operation. In Version 7.0, this type of backup is recorded as normal.

Truncate truncates the transaction log, but does not back it up. This operation is logged.

Truncate (use this option when log is full) truncates the transaction log, but does not back it up. It is the only choice when the log is full. This operation is not logged.

Backup Device

Uses one of two options:

Use same device as last backup uses the same backup device that you used the last time you backed up the transaction log. If the task cannot determine the last backup device, it fails.

Microsoft SQL Server, Version 6.5, keeps backup history in system tables. Note that system tables are different in Version 7.0 than in Version 6.5.

Specify backup device (logical name or temporary device) is the logical name for an existing backup device or a temporary device. When you specify a temporary device, the system creates it, if it does not exist.

For striped disk backups, enter a comma-separated list of either logical names or temporary devices or a mixture of both. The list entered can be a mix of logical and temporary filenames (or variables). The device types, however, must be the same.

Dump devices used in a stripe set must always be used in a striped set (unless you reinitialize it at some point). Once a device is defined as part of a striped set, you cannot use it for a single device dump, unless



or

.

.

m

.

you overwrite it. You cannot use a device that contains non-striped dumps in a striped set, unless you overwrite it. Tivoli does not recommend dumping to diskette; see the “Usage Notes” for additional information.

The following shows how logical and temporary device names are entered: Logical Device:<logical_name>Temporary Device: <DISK|TAPE|FLOPPY|DISKETTE=<physical path and filename>

Backup options

Enter a comma-separated list of options. For all options that take a parameter, a Microsoft SQL Server variable can be used as well as literal text. Fmore information on these options, see the description of Backup in Microsoft SQL Server Book On-line.

Choose from the following options:

BLOCKSIZE=numberSets the block size to use when writing the backupWhen writing to DISK or TAPE, the size is set automatically unless overridden. When writing to PIPE, the default size is 65,536 unless overridden

DESCRIPTION=textSpecifies a description for the backup set, maximulength 255 characters. Default: blank.

DIFFERENTIAL Use with Microsoft SQL ServerVersion 7.0 only: Specifies a differential backup rather than a full backup. Default: full backup.

EXPIREDATE=date or RETAINDAYS=numberSpecifies when the backup file may be overwrittenOnly one of these options may be used. EXPIREDATE specifies the expiration date.

2–74 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

RETAINDAYS specifies how many days to retain the backup.

FORMAT or NOFORMATWrites the media header on all volumes used for this backup and rewrites the backup device. Any existing media header is overwritten. All media contents are invalidated, ignoring any existing password. Use only on complete backup sets. Using it on a single tape belonging to an existing striped backup set renders the entire backup set useless. Using FORMAT implicitly sets INIT and SKIP. They do not have to be specified separately.

INIT or NOINITINIT means the backup overwrites any previous backups on the backup device. The media header is preserved. NOINIT means the backup is appended to the previous backup, if any. Default: NOINIT. The backup does not overwrite if it encounters any of the following conditions:

The media contains unexpired backup sets. You can override this condition by specifying SKIP.

An explicitly given backup set name does not match the name on the backup media. You can override this condition by specifying SKIP.

The backup media is password-protected.

The backup media is encrypted.

MEDIADESCRIPTION= textSpecifies a description for the media set. The maximum length is 128 characters. Default: blank.

MEDIANAME=text Specifies the media name for the backup. When specified, if the existing medianame on the backup media doesn’t match, the backup fails.



NAME=text Specifies the name of the backup set. The maximum length is 128 characters. Default: blank.

NO_TRUNCATE Backs up the log without truncating it. Otherwise, the log is truncated as per the setting in the Dump Options. It also backs up the log if the database becomes damaged, if the database has been marked suspect, or if the database has not been recovered.

RESTART Use when restarting a backup operation that was interrupted. SQL Server will attempt to restart the backup where it was interrupted, possibly saving time.

SKIP or NOSKIPSKIP disables the checking for name match and expiration date of all backup sets on the media. SKIP can be used with INIT (see description). NOSKIP can be used with FORMAT to override its default behavior (see description). Default: NOSKIP except where otherwise noted.

STATS=percentSpecifies how often to write a progress message, expressed in percent done. Default: 10.

UNLOAD or NOUNLOADUsed only for tape devices. UNLOAD specifies that the media be rewound and unloaded (ejected) when the backup is complete. Default: NOUNLOAD.

Report to File



2–76 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

CLI SYNTAX

There are three ways to specify the syntax for this task.

DumpTransactionLog

[–a DumpOption=Default | NoTruncate]

[–a DumpDevice=Last]


[–a NotifyTEC ]

[–a ReportToFile]

—OR—

DumpTransactionLog

[–a DumpOption=Default | NoTruncate]

[–a DumpDevice=Specified]

–a DumpTo=<devicename1>, [<devicename2>, <devicename3>, <devicename...>]


[–a NotifyTEC ]

[–a ReportToFile]


DumpOptions Choose one of the following:

Default backs up the transaction log and truncates it. This is the default.

GUI Name: Backup and truncate

NoTruncate backs up the transaction log, but does not truncate it.

GUI Name: Backup

TruncateOnly truncates the transaction log, but does not back it up.

GUI Name: Truncate



NoLog truncates the transaction log, but does not back it up. It is the only choice you have when the transaction log is full.

GUI Name: Truncate (use this option when log is full)

DumpDevice This is optional when you specify DumpTo.

Last use the same backup device that you used the last time you backed up the database.

GUI Name: Use same device as last backup

Specified uses a backup device that you specify with DumpTo.

GUI Name: Specify backup device (logical name or temporary device

DumpTo Logical name for an existing backup device or a temporary device. This argument is ignored when you specify DumpDevice=Last.

GUI Name: Specify backup device (logical name or temporary device

WithOptions Specifies the backup options to use. Options must be a comma-separated list and enclosed in double quotes. The options are specified the same way as in the Backup Options GUI field.

GUI Name: Backup Options




2–78 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary


SaveReportFileOn



CLI EXAMPLE

wruntask -t DumpTransactionLog -l "MSSQLManagerTasks" -h @MSSQLDatabase:msdb@hbergin@hbergin -a DumpOption=Default -a DumpDevice=Specified -a DumpTo=DumpA -a WithOptions="INIT,UNLOAD"

OUTPUT


More information is available if you use the Report to File argument. Among other information, output sent to the report file includes the following:



■ Database name, device name and types, number of MB backed up, start time of backup, finish time of backup

■ Output from the LOAD HEADERONLY command

USAGE NOTES

Use NoTruncate when media fails. This makes it possible to dump a transaction log even when the database is inaccessible; it uses a pointer to the transaction log in the master database. NoTruncate provides up-to-the-minute media recovery when the master database and the log portion of the user database reside on undamaged database devices and when only the data portion of the user database is damaged. In Version 6.5, this backup is not recorded in the SYSBACKUPHISTORY table. The only way to tell if it was successful is to read the header information on the backup device (LOAD HEADERONLY). In Version 7.0, this backup is recorded in the appropriate system tables.

You can backup the master database log on its own if you use the NoTruncate option.

The DUMP DATABASE command backs up both the data and the log. The DUMP TRANSACTION command backs up only the transaction log and not the data.

In Version 6.5, the transaction log and data can share a device fragment. If they are sharing the same storage area, then the transaction log cannot be backed up independently of the data. In Version 7.0, the transaction log and data are always stored in separate files, so the transaction log can always be backed up independently of the data.

When you dump a database, it always means you are backing it up. When you dump a transaction log, it could mean you are backing it up, truncating it, or both.

2–80 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Note: The restrictions in these notes are Microsoft product restrictions. It is physically impossible, for example, to dump a transaction log when the database has never been dumpedYou should back up the transaction log when it is 50 to 75 percent full.

See the Dump Database task for additional information.

SEE ALSO

MSSQLDatabase monitors: Log Space Used, Log Space Percent Used (Database)

Tasks: ADSMFullBackup, ADSMIncBackup, Dump Database, Log Space Percent Used (Server), MS SQL Server Warnings and Indicators


Enable NT Disk Performance Counters


DESCRIPTION

Changes the configuration so that the physical and logical disk counters used in performance monitoring are activated. Windows NT disables these counters by default for performance reasons.

AUTHORIZATION ROLE

mssqlserver_dba and NT Administrator

TARGET ENDPOINT

Managed node


The following shows the EnableDiskCounters dialog; a description of each field follows.

Disk Type Designates the type of disk on which to enable performance counters. Choose one of the following:

Standard enables the disk performance counters for a standard single disk.

Striped disk set enables the disk performance counters for a striped disk set.

2–82 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Reboot NT Server

Reboot Windows NT. This task changes the disk performance counters configuration; the configuration change does not take effect until the computer is restarted. If you do not use this check box, you can restart the server at a later time.

Report to File



CLI SYNTAX


EnableDiskCounters

[–a DiskType=Striped | Standard]

[–a RebootNTServer=Y | N]








DiskType Use one of the following qualifiers:

Striped enables the disk performance counters for a striped disk set.

GUI Name: Striped disk set

Standard enables the disk performance counters for a standard disk. It is the default.



GUI Name: Standard

RebootNTServer

Y reboots the NT Server, which must be done before the counters can be disabled. N does not reboot the NT, which means that you must do it manually. This is the default.

GUI Name: Reboot NT Server





SaveReportFileOn



CLI EXAMPLE

wruntask -t EnableDiskCounters -l "MSSQLManagerTasks" -h @ManagedNode:hbergin -a DiskType=Standard -a RebootNTServer=No

2–84 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

OUTPUT


USAGE NOTES

You must restart the NT Server (either with this task or separately on the machine) before the counters can be enabled.

You must be logged on to an account that is a member of the Windows NT Administrators group to do this.

SEE ALSO

Tasks: Disable NT Disk Performance Counters


Execute SQL

Execute SQL

DESCRIPTION

Runs a user-defined TSQL statement on a database. You can specify that the task use the resulting set to create a file using the BCP default format on the monitored host or on a nominated host.

Note: Some actions resulting from this task may have far-reaching repercussions on data and database availability.

AUTHORIZATION ROLE

mssqlserver_dba


■ Microsoft SQL Server 6.5: depends on SQL statement

■ Microsoft SQL Server 7.0: depends on SQL statement

TARGET ENDPOINT

Database

2–86 Version 1.3

Execute SQL

Th

e MS

SQ

LM

anag

erTasks L

ibrary


The following shows the ExecuteSQL dialog; a description of each field follows.

TSQL Command

TSQL string to execute. Type the exact string in the space provided; you do not need to enclose the string in quotes. When calling a stored procedure, always precede the name of the stored procedure with execute or exec: For example:

exec xp_cmdshell "dir"

Report to File




Execute SQL

CLI SYNTAX

ExecuteSQL

–a TSQL="<sql command>"








TSQL " <sql command>" is the TSQL string to execute. Type the exact string and enclose the string in quotes. When calling a stored procedure, always precede the name of the stored procedure with execute or exec: For example:

" exec xp_cmdshell ’dir’"

GUI Name: TSQL Command





SaveReportFileOn

MonitoredHost puts the output file on the host the task was run against. SpecifiedHost puts the output

2–88 Version 1.3

Execute SQL

Th

e MS

SQ

LM

anag

erTasks L

ibrary

file on a specified host. Specify the host with ReportHostName.


CLI EXAMPLEwruntask -t ExecuteSQL -l "MSSQLManagerTasks" -h @MSSQLDatabase:master@hbergin@hbergin -a TSQL="select count(*) from pubs.dbo.authors" -a ReportToFile=Y-a ReportFileName=’${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.rpt’ -a SaveReportFileOn=MonitoredHost -a ReportHostName=hbergin

OUTPUT

The standard output file includes any errors reported by the TSQL command, such as insufficient permissions or non-existent objects. The report contains the resulting set produced by the TSQL command. The columns of data are separated by \t’ (tab); the rows are separated by \n (new line); this is the default in BCP.


Execute SQL

USAGE NOTES

Make sure that the TSQL statement is valid on all targeted versions of Microsoft SQL Server.

The code is executed in a single batch. The task automatically puts a USE DATABASE statement at the beginning of the batch. Note that Microsoft requires that the following statements must be the first statement in a batch: CREATE DEFAULT, CREATE PROCEDURE, CREATE RULE, CREATE TRIGGER, and CREATE VIEW. They cannot be used normally in this task but may be executed in an EXECUTE command. Example:

EXECUTE (’CREATE VIEW view_name AS SELECT * FROM pubs.dbo.authors’)

Exercise caution when using this task to run DDL (Data Definition Language) or DML (Data Manipulation Language) commands, such as DROP TABLE, DROP DATABASE, DELETE FROM TABLE, or DELETE FROM DATABASE. It could have far-reaching consequences.

Resource-intensive queries can hamper the availability of the server to other users.

SEE ALSO

None

2–90 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary


DESCRIPTION

Reports on several important issues and enables you to flag exceptional situations that may require investigation.

This task reports on the following:

■ TEMPDB left in RAM

■ Number of hours since the server started

■ If the logs and data are on the same device file (excluding the master database)

■ Data and procedure cache configuration

■ Space used per database

■ Disk space available on the host

■ Microsoft SQL Server version and service pack; for example, 201 Retail, 213 SP1, 240 SP2, 258 SP3

■ The percentage of system memory configured for the database server

■ Date of the last database and transaction log dump

■ Average chain length

■ Windows NT event logging

AUTHORIZATION ROLE

mssqlserver_user or mssqlserver_dba


■ Microsoft SQL Server 6.5: SA

■ Microsoft SQL Server 7.0: sysadmin

TARGET ENDPOINT

Database server




The following shows the SQLWarnings dialog; a description of each field follows.

Return Warnings only

Shows only the warnings that are checked. Otherwise information is returned for each item in the list.

Warning options

You can choose any or all of the following warnings:

MSSQLServer has not been restarted in (##.#) days warns when the database server has not been

2–92 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

restarted for the number of days that you specify. If this field is blank, you do not receive this warning.

MS SQL Server Service Pack is less than (#) warns when the version number of the service pack is less than the value that you specify. If the field is blank, you do not receive this warning.

For Microsoft SQL Server, Version 6.5, the service pack to version mapping is:

None = 6.50.201

SP1 = 6.50.213

SP2 = 6.50.240

SP3 = 6.50.258

SP4 = 6.50.281

SP5 = 6.50.415

SP5a = 6.50.416

For Microsoft SQL Server, Version 7.0, the service pack to version mapping is:

None = 7.00.623

SP1 = 7.00.699

NT disk space used is greater than (#) % warns when the disk space used on the NT server is greater than the value specified. If the field is blank, you do not receive this warning.

NT event logging is disabled warns when events are not being forwarded by the database server to the Windows NT event log.

TempDB is in RAM (Version 6.5 only) warns when the temporary database is in RAM.

Procedure cache ratio is greater than (##) % Version 6.5 only: warns when the procedure cache ratio is greater than the value specified. If the field is blank, you do not receive this warning.



is k,

e

e

s

e

NT system memory configured for MSSQL Server is greater than (##) % warns when the percentage of Windows NT System memory that is configured for the database server is greater than the value specified. If the field is blank, you do not receive this warning. For Version 7.0, if dynamic memory allocation is in effect, this option returns “No maximum set.”

Average Chain length is greater than (##) warns when the average chain length is greater than thevalue specified. If the field is blank, you do not receive this warning.

Database space used is greater than (##) % warns when the percentage of the database space usedgreater than the value specified. If the field is blanyou do not receive this warning.

Log and data are sharing a device (Version 6.5 only) warns when the logs and data are on the samdevice file (excluding the master database). The master database is the only database that cannot have its log and data on separate devices. Other system installed databases (MSDB, MODEL, TEMPDB and pubs) can have their logs on separatdevices. Although data and log for MODEL, TEMPDB and PUBS share a device at install time,you can alter this later.

Last database dump was greater than (##) day(s) ago warns when the last time the database was backed up was more than the number of days specified. If the field is blank, you do not receive thiwarning.

Last transaction log dump was greater than (##) hours ago warns when the last time the transactionlog was backed up was more than the number of hours specified. If the field is blank, you do not receive this warning. No warning is returned for thmaster database.

2–94 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Report to File



CLI SYNTAX


SQLWarnings

[–a WarnOnly=Y | N]

[–a RestartSRVR=Y | N [–a RestartSRVRMax=<days>]]

[–a ServicePack=Y | N [–a ServicePackMin=<version number>]]

[–a NTDiskSpaceUsed=Y | N [–a NTDiskSpaceUsedMax=<percentage>]]

[–a NTEventLogging=Y | N]

[–a TempDBInRam=Y | N]

[–a ProcCache=Y | N [–a ProcCacheMax=<percentage>]]

[–a Memory=Y | N [– a MemoryMax =<percentage>]]

[–a AvgChainLen=Y | N [–a AvgChainLenMax=<number>]]

[–a DBSpaceUsed=Y | N [–a DBSpaceUsedMax =<percentage>]]

[–a LogAndData=Y | N]

[–a LastDBDump=Y | N [–a LastDBDumpMax =<days>]]

[–a LastTransLogDump=Y | N [–a LastTransLogDumpMax =<hours>]]










WarnOnly Y shows only specified warning arguments in the output file. N shows both warnings and the current values in the output file. If WarnOnly = N , then the task returns information on all arguments. The task issues warnings only for those arguments that = Y when they breach the specified threshold. The task ignores any thresholds if the corresponding argument is =N. Consider the following example:

SQLWarnings -a WarnOnly=Y -a RestartSRVR=N -a RestartSRVRMax=4

The task ignores the threshold of RestartSRVRMax=4, because RestartSRVR=N.

GUI Name: Return warnings only

RestartSRVR Y warns when the database server has not been restarted for the number of days that you specify with RestartSRVRMAX . N means you do not want a warning.

RestartSRVRMAX

<days> is the number of days since the database server has been restarted. The default is 47.5.

GUI Name: MSSQLServer has not been started in ## day(s)

ServicePack Y warns when the service pack version number is below a certain level specified by ServicePackMin. N means you do not want a warning.

ServicePackMin

<version number> is the version number of the service pack. The default is 5.

GUI Name: MS SQL Server Service Pack is less than ##

2–96 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

NTDiskSpaceUsed

Y warns when the percentage of disk space used for the database server on local disk drives is greater than the value specified with NTDiskSpaceUsedMax. The disk space used is determined by counting the disk space used by disk drives that are referenced in the sysdevices (Version 6.5) or sysfiles (Version 7.0) system tables. N means you do not want a warning.

NTDiskSpaceUsedMax

<percentage> is the percentage of used disk space. The default is 70 percent.

GUI Name: NT disk space used is greater than %

NTEventLogging

Y warns when NT Event Logging is disabled. N means you do not want a warning.

GUI Name: NT event logging is disabled

TempDBInRam

Version 6.5 only: Y warns when the temporary database is in RAM. N means you do not want a warning.

GUI Name: TempDB in RAM

ProcCache Version 6.5 only: Y warns when the procedure cache ratio is greater than the percentage value specified with ProcCacheMax. N means you do not want a warning.

ProcCacheMax

<percentage> is the procedure cache ratio.

GUI Name: Procedure cache is greater than ## %

Memory Y warns when the percentage of the NT System memory configured for the database server is greater



than the value specified with MemoryMax. N means you do not want a warning.

MemoryMax <percentage> is the maximum percentage of the NT System memory to be configured for the database server.

GUI Name: NT system memory configured for MS SQL Server is greater than ## %

AvgChainLen Y warns when the average chain length is greater than the value that you specify with AvgChainLenMax. N means you do not want a warning.

AvgChainLenMax

<number> is the average chain length.

GUI Name: Average chain length is greater than ##

DBSpaceUsed Y warns when the percentage of configured database space used is greater than the value that you specify with DBSpaceUsedMax. N means you do not want a warning.

DBSpaceUsedMax

<percentage> is the percentage of database space used.

GUI Name: Database space used is greater than ## %

LogAndData (Version 6.5 only) Y warns when the log and data are on the same device fragment, except in the case of the master database. N means you do not want a warning.

GUI Name: Log and data are sharing a device

LastDBDump Y warns when the last time the database was backed up was more than the number of days specified with LastDBDumpMax. N means you do not want a warning.

2–98 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

LastDBDumpMax

<days> is the number of days since the database was last backed up.

GUI Name: Last database dump was greater than ## day(s) ago

LastTransLogDump

Y warns when more than LastTransLogDumpMax hours have passed since the last transaction log backup. N means you do not want a warning.

GUI Name: Last transaction log dump was greater than ## hour(s) ago

LastTransLogDumpMax

<hours> is the number of hours since the transaction log was last backed up.

GUI Name: Last transaction log dump was greater than ## hour(s) ago





SaveReportFileOn





CLI EXAMPLEwruntask -t SQLWarnings -l "MSSQLManagerTasks" -h @MSSQLServer:hbergin@hbergin -a WarnOnly=Y -a RestartSRVR=N -a RestartSRVRMax=1 -a ReportToFile=Y-a ReportFileName=’${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.rpt’-a SaveReportFileOn=SpecifiedHost -a ReportHostName=hbergin

OUTPUT


More information is available if you use the Report to File argument. The additional information appears in the report file. If a threshold is reached, the word WARNING! appears before the text, as shown in the following example. If the user has selected to be warned when a

2–100 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

database has its log and data on the same device fragment, no warning is issued for the master database. This is because the master database always has its log and data on the same device fragment.



The following table identifies the information returned for each choice.

USAGE NOTES

None

SEE ALSO

None

Warnings Only

Checked

Individual Option Checked

Warning Threshold

Broken Output

Y Blank Blank No output

Y Y Blank No output

Y Y Y Warning and Information

Blank Y Blank Information

Blank Y Y Warning and Information

Blank Blank Y Information

Blank Blank Blank Information

2–102 Version 1.3

NT Event Logging

Th

e MS

SQ

LM

anag

erTasks L

ibrary

NT Event Logging

DESCRIPTION

This task specifies which non-fatal errors and user-defined errors are logged to the Windows NT event log. This error logging is performed in addition to logging performed by the database server to the SQL Server error log. The specified SQL Server errors get logged to the Application log section of the event log.

This task operates only on non-fatal and user-defined errors. All fatal errors are logged to both the Windows NT event log and the SQL Server error log.

AUTHORIZATION ROLE

mssqlserver_dba

TARGET ENDPOINT

Database servers


NT Event Logging


The following shows the NTEventLogging dialog; a description of each field follows.

Change current settings

Choose one of the following:

Add: adds the specified errors to the list of errors that are sent to the Windows NT event log. The task changes only the logging status for the errors. It does not affect any other existing error configurations. If you specify a number that is already included, the system ignores it.

Remove: removes the specified errors from the list of errors that are sent to the Windows NT event log. It changes only the logging status for the specified errors. It does not affect any other existing error configurations. If you specify a number that is not part of the list, the system ignores it.

2–104 Version 1.3

NT Event Logging

Th

e MS

SQ

LM

anag

erTasks L

ibrary

Overwrite: changes the list of errors to be logged to include only the errors specified.

To stop logging any non-fatal or user-defined errors, select Overwrite and leave the Non-fatal error numbers field blank.

Non-fatal error numbers

Identifies the errors to add, delete, or overwrite. Enter the errors by number and separate them with commas.

Report to File



CLI SYNTAX

NTEventLogging

–a EditMode=Add | Remove | Overwrite

–a ErrorNumbers=<number>









NT Event Logging

EditMode You can specify one of the three mutually exclusive arguments.

Add adds the error numbers that you designate with ErrorNumbers to the current list of errors logged.

GUI Name: Add

Remove removes the errors that you designate with ErrorNumbers from the list of errors logged.

GUI Name: Remove

Overwrite logs only the error numbers that you designate with ErrorNumbers.

GUI Name: Overwrite

ErrorNumbers

<number> identifies the Microsoft SQL Server error numbers to include in the Windows NT event log; separate error numbers with commas.

GUI Name: Non-fatal error numbers





SaveReportFileOn


2–106 Version 1.3

NT Event Logging

Th

e MS

SQ

LM

anag

erTasks L

ibrary


CLI EXAMPLE

wruntask -t NTEventLogging -l "MSSQLManagerTasks" -h @MSSQLServer:hbergin@hbergin -a EditMode=Add -a ErrorNumbers=208,170

OUTPUT


USAGE NOTES

This task uses the Microsoft SQL Server sp_altermessage stored procedure. For more information, see the Microsoft SQL Server Books On-line.


NT Event Logging

Fatal errors (severity 19 and above) are automatically logged to the Windows NT event log, even though they are not marked to do so in the sysmessages table. You cannot change this.

SEE ALSO

MSSQLServer monitors: NT Application Log, NT Application Log Age, NT Application Log Percent Full

2–108 Version 1.3

Rebuild Fragmented Indexes

Th

e MS

SQ

LM

anag

erTasks L

ibrary


DESCRIPTION

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

AUTHORIZATION ROLE

mssqlserver_dba




TARGET ENDPOINT

Database


The following shows the RebuildIndex dialog; a description of each field follows.

Table name Updates the indexes for a specific table or for all tables.



Index name Updates indexes of a particular name, which you specify in this field, or all indexes.

The following chart shows how entries in the Table name and Index name fields determine which indexes and tables are updated:

Rebuild if fragmentation % greater than

Rebuilds the index when the index reaches this percentage of fragmentation. If the actual index fragmentation percentage is greater than the number you enter here, the task rebuilds the index. To rebuild the indexes under all circumstances use zero (0). The default value is 30 percent.

Rebuild if disconnected overflow pages found

Version 6.5 only: Re-indexes and fixes any disconnected overflow pages. In some cases, overflow pages may become disconnected. If the overflow page is disconnected, records on that page may not be accessible.

Fill factor Specifies how full you want the new page to be. Enter a value that is the percentage of the page to be

Table Name

TableExists

IndexName

IndexExists

Outcome

Entered Y Entered Y Updates the specified index on the specified table.

Entered Y Entered N Error. Specified index does not exist.

Entered Y Blank - Updates all indexes on the specified table.

Entered N Entered Y Error. Specified table does not exist.

Entered N Entered N Error. Specified table does not exist.

Entered N Blank - Error. Specified table does not exist.

Blank - Entered Y Updates all indexes that share the specified name.

Blank - Entered N Error. Specified index does not exist.

Blank - Blank - Updates all indexes.

2–110 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

filled; for example, entering 20 means fill one fifth of the page, leaving 80 percent free. To rebuild with the same FILLFACTOR used in the previous rebuild, specify zero (0). If the actual fill factor is greater than the number you enter here, this tasks rebuilds the index using the specified fill factor. Leaving some space on a page may improve the performance on clustered indexes. If you specify a low fill factor, remember that the database takes up more disk space. The default for this field is 0 percent (no fill factor).

See DBCC DBREINDEX in the Microsoft SQL Server Books On-line for more details on specifying the FILLFACTOR for an index.

Report to File



CLI SYNTAX


RebuildIndex

[–a TableName= <tablename>]

[–a IndexName=<indexname>]

[–a FragLimit= <percentage>]

[–a DisconnectedOverflow=Y | N]

[–a Fillfactor=<number>]







u

ult

. EC.




Note: See the discussion of and chart for Table name and Index name in the “GUI Data Entry Fields” section to see how yocan use combinations of table and index names.

TableName <tablename> rebuilds the indexes on the specifiedtable. If you do not specify <tablename>, the task rebuilds indexes for all tables.

GUI Name: Table name

IndexName <indexname> rebuilds the specified index. If you donot specify <indexname>, the task updates all indexes.

GUI Name: Index name

FragLimit <percentage> rebuilds the index when the index reaches this percentage of fragmentation. The defapercentage is 30.

GUI Name: Rebuild if fragmentation % is greater than

DisconnectedOverflow

Y reindexes and fixes any disconnected overflow pages. N does not reindex or fix disconnected overflow pages and is the default.

GUI Name: Rebuild if disconnected overflow pages found

FillFactor <number> specifies how full, in percent, you want the page to be when it rebuilds the index.

GUI Name: Fill factor

NotifyTEC Y sends the success or failure message to the TECN does not send the success or failure message to TThe default is N. If you specify Y, specify a valid TECServer argument or no message is sent.

2–112 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary




SaveReportFileOn



CLI EXAMPLE

wruntask -t RebuildIndex -l "MSSQLManagerTasks"-h @MSSQLDatabase:pubs@hbergin@hbergin-a TableName=’authors’ -a IndexName=’aunmind’ -a FragLevel=0 -a Fillfactor=0



OUTPUT


USAGE NOTES

You can improve table fragmentation only if the table has a clustered index that can be rebuilt. Table data is directly related to the clustered index because it is the leaf level of the index. The task first checks the clustered index (INDID = 1). Rebuilding the clustered index reorders the data pages and causes all other indexes to be rebuilt.

If a table has no clustered index or the clustered index is not fragmented (called non-clustered index fragmentation), you may still want to run this task. It checks the non-clustered indexes for fragmentation, which the task automatically rebuilds on an individual basis if necessary. Non-clustered indexes have an INDID > 1.

SEE ALSO

Tasks: Database Check-up and Tune-up

MSSQLServer monitors: Fragmentation

2–114 Version 1.3

Recovery Preparation

Th

e MS

SQ

LM

anag

erTasks L

ibrary

ices

t


DESCRIPTION

Prepares scripts and saves essential information that is required for recovering the database server and its associated databases when a fatal condition occurs on a database server.

Recovery Preparation does the following:

1. Optimizes the device configuration information by merging contiguous fragments (Version 6.5 only).

2. Saves information about where devices have been created and what their sizes are.

3. Produces an SQL script that enables you to recreate each database, except the master database, with its device fragments in the correct order and size.

For Verion 6.5: Appends a LOAD DATABASE command for each database, leaving the backup device to be specified by the DBA. The master database is not included in this script because it requires a unique restore procedure. This statement is not necessary with Version 7.0

4. Produces an SQL script so you can rebuild each database’sstored procedures, triggers, security options, tables, and indexes. This script provides only the schema and does notinclude data. The task prepares an SQL script for server dev(Version 6.5 only) and server logins.

5. Saves vital system table contents into separate ASCII files.

ASCII files for the master database include the following:

Note: The * indicates the minimum recommended by Microsoft.

■ syscharsets contains one row for each character set and sororder defined for use by Microsoft SQL Server.

■ *sysconfigures contains one row for each user-defined configuration option.

■ *sysdatabases contains one row for each database.



■ *sysdevices contains one row for each disk dump device, diskette dump device, tape dump device, and database device.

■ syslanguages contains one row for each language known the the database server. Although US English is omitted, it is always available.

■ *syslogins contains one row for each valid user account.

■ sysmessages contains one row for each user-defined system error or warning that can be returned by the database server.

■ sysremotelogins contains one row for each remote user who is allowed to call remote stored procedures on this database server.

■ sysservers contains one row for each remote database server on which this database server can call remote stored procedures.

■ *sysusages contains one row for each disk-allocation piece assigned to a database (Version 6.5 only).

ASCII files for the MSDB database include the following:

■ sysalerts contains one row for each alert.

■ sysjobs contains information for each scheduled job to be executed by SQLServerAgent (Version 7.0 only).

■ sysjobsteps contains information for each step in a job to be executed by SQLServer Agent (Version 7.0 only).

■ sysjobservers contains information on the association or relationship of a particular job with one or more target servers (Version 7.0 only).

■ sysjobschedules contains schedule information for jobs to be executed by SQLServerAgent (Version 7.0 only).

■ sysnotifications contains one row for each notification.

■ sysoperators contains one row for each operator.

■ systasks contains one row for every scheduled task (Version 6.5 only).

2–116 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

AUTHORIZATION ROLE

mssqlserver_dba




TARGET ENDPOINT

Database server


The following shows the RecoveryPrep dialog; a description of each field follows.



Include object drop in schema scripts

Ensures that an existing object is dropped before the creation statement is run. Microsoft SQL Server returns an error when you try to create an object that already exists. This option also ensures that the script version of the object is the latest version.

BCP the following system table contents to file

Displays a list of system tables in the master and MSDB databases so you can copy them to a file. This option is an extra precaution in case backups are unreadable or unavailable.

Recovery Archive File

Path and filename is the directory in which to place the compressed tar file of all the created BCP files and SQL scripts. Tivoli ships the tar utility; this provides a reference for the actions carried out by this task. The output file uses the filename specified in this field and appends the host name to it.

There are several default variables for this field. For a description of these variables, see “Using the Create a Report File Dialog” on page 8-7 in the Tivoli Manager for Microsoft SQL Server User’s Guide.

On monitored host creates the output file on the monitored host the task was run against. (Mutually exclusive with On specified host.)

On specified host creates the output file on a specific host; you cannot save output files on multiple hosts. (You specify the host name with Host name.)

Host name displays a scrolling list of host names so you can select the host computer on which to create the output file. Use with On specified host.

2–118 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Report to File



CLI SYNTAX

This task can be run with no arguments. In that case, default values are used for the arguments. There are two ways to specify the syntax for this task.

RecoveryPrep

[–a ObjectDrop=Y | N]

[–a BCPList=<tablename1>, <tablename2>, . . .]

[–a ArchiveFileName=<filename>]

[–a SaveArchiveFileOn=MonitoredHost | SpecifiedHost]








ObjectDrop Y drops an existing object before the creation statement. N does not drop an existing object and is the default.

GUI Name: Include object drop in schema scripts



BCPList Copies the contents of the specified tables to a file. Valid <tablename#> choices are syscharsets, sysconfigures, sysdatabase, sysdevices, syslanguages, syslogins, sysmessages, sysremotelogins, sysservers, sysusages, sysalerts, sysjobs, sysjobsteps, sysjobservers, sysjobschedules, sysnotifications, sysoperators, or systasks. You may include none, one, many, or all the choices.

GUI Name: BCP the following system table contents to file

ArchiveFileName

<filename> is the directory and filename for the compressed tar file of all the created BCP files and SQL scripts.

GUI Name: Path and filename

SaveArchiveFileOn

You have two choices for this argument.

MonitoredHost creates the output file on the monitored host the task was run against. This is the default.

GUI Name: On monitored host

SpecifiedHost creates the output file on a specific host, which you specify with the ArchiveHostName=<hostname> argument.

GUI Name: On specified host

ArchiveHostName

<hostname> designates the name of the host on which to save the file. This argument is ignored when SaveArchiveFileOn=MonitoredHost.

GUI Name: Host name

NotifyTEC Y sends the success or failure message to the TEC. N does not send the success or failure message to TEC.

2–120 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

The default is N. If you specify Y, specify a valid TECServer argument or no message is sent.




SaveReportFileOn



CLI EXAMPLEwruntask -t RecoveryPrep -l "MSSQLManagerTasks" -h @MSSQLServer:hbergin@hbergin -a ObjectDrop=Y -a BCPList="syscharsets,sysconfigures"-a ArchiveFileName=’${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.taz’-a SaveArchiveFileOn=SpecifiedHost -a ArchiveHostName=hbergin -a ReportToFile=Y-a ReportFileName=’${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.rpt’ -a SaveReportFileOn=SpecifiedHost -a ReportHostName=hbergin



OUTPUT


Output shows the names of all files created. Output filenames should follow these rules:

<server_name>_devices.sql (information and create syntax for devices)

<server_name>_logins.sql

<server_name>_<db_name>.sql (file for each database)

<server_name>_<table_name>.bcp (for each BCP system table)

<server_name>_restore.sql (CREATE and LOAD DUMP skeleton script)

2–122 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

If you use the defaults, the scripts are placed in ${WTEMP}/${TASK}_${NODE}_${ENDPOINT}_${DATE}_${TIME}.taz.

USAGE NOTES

None

SEE ALSO

None


Refresh Databases

Refresh Databases

DESCRIPTION

Synchronizes the existing databases on a database server with the list of database objects known to the TMR. The Tivoli desktop does not automatically update itself when the underlying databases on an endpoint change.

AUTHORIZATION ROLE

mssqlserver_user or mssqlserver_dba

TARGET ENDPOINT

Database server


The following shows the RefreshDB dialog; a description of each field follows.

Report to File



2–124 Version 1.3

Refresh Databases

Th

e MS

SQ

LM

anag

erTasks L

ibrary

CLI SYNTAX


RefreshDB












SaveReportFileOn




Refresh Databases

CLI EXAMPLE

wruntask -t RefreshDB -l "MSSQLManagerTasks" -h @MSSQLServer:hbergin@hbergin -a NotifyTEC=Y-a TECServer=hbergin

OUTPUT


USAGE NOTES

None

SEE ALSO

None

2–126 Version 1.3

Refresh Query Optimizer Statistics

Th

e MS

SQ

LM

anag

erTasks L

ibrary


DESCRIPTION

Refreshes the optimizer statistics for either all indexes on a table or a specific index. This task forces every affected stored procedure to recompile before it is next run.

AUTHORIZATION ROLE

mssqlserver_dba


■ Microsoft SQL Server 6.5: SA or table owner

■ Microsoft SQL Server 7.0: sysadmin or table owner

TARGET ENDPOINT

Database


The following shows the RefreshStats dialog; a description of each field follows.

Table name Updates the indexes for a specified table. If blank updates indexes for all tables.

Index name Updates the specified indexes. If blank, updates all indexes.



The following table shows how entries in the Table name and Index name fields determine which indexes and tables are updated.


Report to File


CLI SYNTAX


RefreshStats

[–a TableName=<tablename>]





Table Name

TableExists

IndexName

IndexExists

Outcome

Entered Y Entered Y Updates the specified index on the specified table.

Entered Y Entered N Error. Specified index does not exist.

Entered Y Blank - Updates all indexes on the specified table.

Entered N Entered Y Error. Specified table does not exist.

Entered N Entered N Error. Specified table does not exist.

Entered N Blank - Error. Specified table does not exist.

Blank - Entered Y Updates all indexes that share the specified name.

Blank - Entered N Error. Specified index does not exist.

Blank - Blank - Updates all indexes.

2–128 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

u

it

. EC.

lt.






TableName <tablename> refreshes statistics for indexes for a specific table. If you do not specify a table name, refreshes indexes for all tables.


IndexName <indexname> refreshes statistics for the specified index. If you do not specify an <indexname>, it refreshes all indexes.



TECServer <servername> the name of the TEC server to sendthe message to.

ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the defauIf Y, specify the file with ReportFileName and optionally the host with SaveReportFileOn.

ReportFileName <filename> is the path to and the name of the fileto create as the task output.

SaveReportFileOn

MonitoredHost puts the output file on the host thetask was run against. SpecifiedHost puts the output file on a specified host. Specify the host with ReportHostName.




CLI EXAMPLE

wruntask -t RefreshStats -l "MSSQLManagerTasks"-h @MSSQLDatabase:pubs@hbergin@hbergin-a TableName=’authors’ -a IndexName=’aunmind’

OUTPUT


USAGE NOTES

This task is subject to the limitations of the sp_recompile stored procedure. For example, you cannot use sp_recompile with system tables. If you must have stored procedures based solely on system tables dropped and recreated, use the Database Check-up and Tune-up task on page 2-41.

2–130 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

If you update a single index on a table, then all stored procedures based on that table are recompiled.

SEE ALSO


MSSQLDatabase monitors: Optimizer Statistics Age




DESCRIPTION

Restores the TEC NT Event Adapter to its state before the last Microsoft SQL Server customization, or it completely removes any Microsoft SQL Server Adapter customization.

Note: When you run this task before you customize the Adapter (with the CustomizeTECNTEventAdapter task and the RestoreFromBackup option), it reports that it cannot find the required files to restore from.

AUTHORIZATION ROLE


TARGET ENDPOINT

Managed node


The following shows the RestoreTECNTEventAdapterMSSQL dialog; a description of each field follows.

Remove any previous MSSQL customization

Removes any previous customization that was performed on the event adapter using Customize TEC NT Event Adapter MSSQL.

2–132 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Restore configuration prior to last MSSQL customization

Restores the TEC NT Event Adapter configuration to the way it was before the last Tivoli Manager for Microsoft SQL Server customization.

Report to File



CLI SYNTAX

RestoreTECNTEventAdapterMSSQL

–a RestoreOption=RemoveCustomization| RestoreFromBackup








RemoveCustomization

Removes any customization. This is the default.

GUI Name: Remove any previous MSSQL customization

RestoreFromBackup

Restores the TEC NT Event Adapter to what it was before the last customization.

GUI Name: Restore configuration prior to last MSSQL customization







SaveReportFileOn



CLI EXAMPLE

wruntask -t RestoreTECNTEventAdapterMSSQL-l MSSQLManagerTasks -h @ManagedNode:nemuchay-a RestoreOption=RemoveCustomization

This example restores the TEC NT Event Adapter on the host called nemuchay to a configuration prior to the Tivoli Manager for Microsoft SQL Server customization. After RestoreTECNTEventAdapterMSSQL runs with the RemoveCustomization option, events previously sent to the TEC as a result of the Adapter customization from host nemuchay are no longer sent as instances of the customized classes: NT_SQLExecutiveBase, NT_MSDTCBase, NT_MSSQLError, NT_MSSQLMessage, and NT_MSSQLInformation.

2–134 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

set

OUTPUT


USAGE NOTES

The RestoreTECNTEventAdapterMSSQL task defaults to the RemoveCustomization option. It removes entries in the tecad_nt.fmt and tecad_nt.conf files made as a result of the Adapter customization.

The RestoreFromBackup option restores the event adapter to its prior configuration before the last Tivoli Manager for Microsoft SQL Server customization, using the files created by the CustomizeTECNTEventAdapter task.

CustomizeTECNTEventAdapter backs up the tecad_nt.conf and tecad_nt.fmt files before customizing the event adapter. The backup files are located in the event adapter’s install directory. Only one of backup files is maintained. The naming convention for backupfiles is:



filename.before.mssql.timestamp

The timestamp convention is year.month.day.hour.minute, using a 24-hour clock (4pm is represented as hour 16). For example, the following files show backups were done at 10:16 a.m. on July 9, 1999 prior to Adapter customization.

tecad_nt.conf.before.mssql.1999.07.09.10.16 tecad_nt.fmt.before.mssql.1999.07.09.10.16

When RestoreTECNTEventAdapterMSSQL runs with the RestoreFromBackup option, it uses these backup files to restore the Adapter. Warning: any customization performed on the event adapter after the last Tivoli Manager for Microsoft SQL Server customization is lost.

RemoveCustomization removes any Tivoli Manager for Microsoft SQL Server customization. It preserves any customizations performed after the Tivoli Manager for Microsoft SQL Server customization. The customization can later be done again with CustomizeTECNTEventAdapter.

After restoring the event adapter, events sent to the TEC as a result of the event adapter customization by Tivoli Manager for Microsoft SQL Server may no longer be received as instances of the customized classes. You may need to re-evaluate event filters after restoring the Event Adapter. Refer to the CustomizeTECNTEventAdapter task for notes on customizing the Adapter.

If the task is run on a TEC server where no customization has been performed, the task reports as follows, depending on which option was specified:

■ RemoveCustomization: reports that nothing needs to be done.

■ RestoreFromBackup: reports that it cannot find the required backup files from which to restore.

SEE ALSO

Tasks: Customize TEC NT Event Adapter MSSQL

2–136 Version 1.3

Set and Retrieve Database Options

Th

e MS

SQ

LM

anag

erTasks L

ibrary


DESCRIPTION

Changes the configuration of the database or reports on its current configuration.

You can run the task with each database option set to one of three values: True, False, or No Change. Using True and False sets the database option to True or False, respectively. Using No Change leaves the database configuration as it is currently.

To get the current configuration settings, run the task with No Change set for all options.

Example: if the READONLY option is currently set to False at the database, running the task has the following effect, depending on how you set the READONLY task argument:

■ No Change: leaves READONLY set to False.

■ True: sets READONLY to True.

■ False: sets READONLY to False (effectively no change).

AUTHORIZATION ROLE

mssqlserver_dba


■ Microsoft SQL Server 6.5: SA or DBO to set

■ Microsoft SQL Server 7.0: sysadmin or db_owner to set

TARGET ENDPOINT

Database




The following shows the DBOption dialog; a description of each field follows.

ANSI null default

When true, the default attribute of new columns in a database is nullable: new columns are created to accept null values on input. If set to False, they are set not to accept null values on input (non-nullable). This option does not change the attributes of existing columns. Default: false.

ANSI nulls 7.0 only. When true, comparisons return NULL if either side of a comparison operation (=, <>) contains a null value. Otherwise a true comparison is made, returning TRUE or FALSE. Default: false.

2–138 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

ANSI warnings

7.0 only. When true, specifies ANSI-92 standard behavior for several error conditions. A message is generated if null values appear in aggregate functions. In addition, when true, the statement is rolled back if divide-by-zero or arithmetic overflow errors are encountered. When false, no message is generated for null values in aggregate functions and null values are returned when divide-by-zero and arithmetic overlflow errors are encountered. Default: false.

auto create statistics

7.0 only. When true, statistical information about the distribution of values in a column is automatically created and stored. The query processor and query optimizer make use of these statistics. Default: true.

auto update statistics

7.0 only. When true, statistics are updated automatically when changes to the table make them obsolete. (based on a statistical sampling algorithm). When off, no statistics are updated. You must update the statistics manually when desired. Default: true.

autoclose 7.0 only. When true, the database is closed and its resources are freed when no user connection accesses the database. When false, the server maintains the database in an open and ready state at all times. Default: false (except for Desktop Edition for Windows 95/98).

autoshrink 7.0 only. When true, database and log files are candidates for automatic shrinking. The files are shrunk if they contain more than 25% unused space. Default: false (except for Desktop Edition).

concat null yields null

7.0 only. When true, concatenating a null value to any string causes the string to be set to NULL. When



s om

e.

false, concatenating a NULL to a string does not change the string. Default: false.

cursor close on commit

7.0 only. When true, open cursors (if any) are closed when a transaction is committed. Default: false.

dbo use only When true, only the database owner (DBO) or logins aliased to the DBO can access the database. Default: false.

default to local cursor

7.0 only. When true, cursor scope is local unless specified global when created. Default: false.

merge publish

7.0 only. When true, the database can be used for merge replication publications. Default: false.

NoChkpt on recovery

6.5 only. When true, a checkpoint record is not added to the database whenever it is recovered during a database server startup. Default: false.

If False, the default, a checkpoint record is added. This option is useful when an up-to-date copy of a database is kept. In these situations, there is a “primary” and a “secondary” database. Initially, theprimary database is dumped and loaded into the secondary database. Then, at intervals, the transaction log of the primary database is dumpedand loaded into the secondary database.

If this option is True in the secondary database, nocheckpoint record is added to a database after it irecovered, so subsequent transaction log dumps frthe primary database are loaded into it.

For information on checkpoint records, refer to theMicrosoft SQL Server Books On-line.

offline When true, take the database offline. Default: fals

2–140 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

published When true, make the database available for replication publications. Default: false.

quoted identifier

7.0 only. When true, identifiers can be delimited by double quotes and literals must be delimited by single quotes. When false, identifiers cannot be in quotes and must follow all Transact-SQL rules for identifiers. Default: false.

read only When true, make the database read-only. If it is read-only, users can read from the database, but they cannot make changes to it. Default: false.

recursive triggers

7.0 only. When true, allows triggers to fire recursively. Note that there is a risk of causing a race condition in table updates that are initiated by triggers. Default: false.

select into/bulk copy

When true, allows users to use the SELECT INTO statement and BCP command. Default: false.

single user When true, puts the database in single-user mode. You can set this option only if there are no other users currently on the database. Default: false.

subscribed When true, make the database available to be subscribed for publication. Default: false.

torn page detection

7.0 only. When true, allows Microsoft SQL Server to detect incorrectly incomplete I/O operations. Detection normally occurs during recovery. Detection of a torn page results in the database being marked suspect, an I/O error, and termination of the connection. Default: false.



Th

e MS

SQ

LM

anag

erTasks L

ibrary

[–a ReadOnly=NoChange | True | False]

[–a RecursiveTriggers=NoChange | True | False]

[–a SelectIntoBulkCopy=NoChange | True | False]

[–a SingleUser=NoChange | True | False]

[–a Subscribed=NoChange | True | False]

[–a TornPageDetection=NoChange | True | False]

[– a TruncLogOnChkpt=NoChange | True | False]








ANSINullDefault

When true, the default attribute of new columns in a database is nullable: new columns are created to accept null values on input. If set to False, they are set not to accept null values on input (non-nullable). This option does not change the attributes of existing columns. Default: false.

GUI Name: ANSI null default

ANSINulls 7.0 only. When on, comparisons return NULL if either side of a comparison operation (=, <>) contains a null value. Otherwise a true comparison is made, returning TRUE or FALSE.

GUI Name: ANSI nulls

ANSI Warnings

7.0 only. When true, a message is generated if null values appear in aggregate functions. In addition, when true, the statement is rolled back if



divide-by-zero or arithmetic overflow errors are encountered. When false, no message is generated for null values in aggregate functions and null values are returned when divide-by-zero and arithmetic overlflow errors are encountered.

GUI Name: ANSI warnings

AutoCreateStatistics

7.0 only. When true, statistical information about the distribution of values in a column is automatically created and stored. The query processor and query optimizer make use of these statistics.

GUI Name: auto create statistics

AutoUpdateStatistics

7.0 only. When true, statistics are updated automatically when changes to the table make them obsolete. (based on a statistical sampling algorithm). When off, no statistics are updated. You must update the statistics manually when desired.

GUI Name: auto update statistics

Autoclose 7.0 only. When true, the database is closed and shut down cleanly when the last user of the database exits and all processes complete.

GUI Name: autoclose

Autoshrink 7.0 only. When true, database and log files are candidates for automatic shrinking. The files are shrunk if they contain more than 25% unused space.

GUI Name: autoshrink

ConcatNullYieldsNull

7.0 only. When true, concatenating a null value to any string causes the string to be set to NULL. When false, concatenating a NULL to a string does not change the string.

GUI Name: concat null yields null

2–144 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

CursorCloseOnCommit

7.0 only. When true, open cursors (if any) are closed when a transaction is committed.

GUI Name: cursor close on commit

DboUseOnly Limits access to the database owner (DBO) or logins aliased to the DBO.

GUI Name: dbo use only

DefaultToLocalCursor

7.0 only. When true, cursor scope is local unless specified global when created.

GUI Name: default to local cursor

MergePublish

7.0 only. When true, the database can be used for merge replication publications.

GUI Name: merge publish

NoChkptOnRecovery

6.5 only. When true, a checkpoint record is not added to the database whenever it is recovered during a database server startup.

GUI Name: NoChkpt on recovery

Offline When true, take the database is offline.

GUI Name: offline

Published When true, make the database available for merge replication publications.

GUI Name: published

QuotedIdentifier

7.0 only. When true, identifiers can be delimited by double quotes and literals must be delimited by single quotes. When false, identifiers cannot be in



quotes and must follow all Transact-SQL rules for identifiers.

GUI Name: quoted identifier

ReadOnly When true, make the database read-only. If it is read-only, users can read from the database, but they cannot make changes to it.

GUI Name: read only

RecursiveTriggers

7.0 only. When true, allows triggers to fire recursively. Note that there is a risk of causing a race condition in table updates that are initiated by triggers.

GUI Name: recursive triggers

SelectIntoBulkCopy

When true, allows users to use the SELECT INTO statement and BCP command.

GUI Name: select into/bulk copy

SingleUser When true, puts the database in single-user mode. You can set this option only if there are no other users currently on the database.

GUI Name: single user

Subscribed When true, make the database available to be subscribed for publication.

GUI Name: subscribed

TornPageDetection

7.0 only. When true, allows Microsoft SQL Server to detect incomplete I/O operations. Detection normally occurs during recovery. Detection of a torn page results in the database being marked suspect, an I/O error, and termination of the connection.

GUI Name: torn page detection

2–146 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

TruncLogOnChkpt

When true, the transaction log is truncated each time a checkpoint is issued.

GUI Name: trunc. log on chkpt





SaveReportFileOn



CLI EXAMPLE

wruntask -t DBOption -l "MSSQLManagerTasks"-h @MSSQLDatabase:pubs@hbergin@hbergin-a SelectIntoBulkCopy=True



OUTPUT


The output records which options you have chosen to set and whether or not the setting needed to be changed. It then lists the current settings for all the database options.

USAGE NOTES

Setting single user mode does not disconnect current user connections. It simply prevents any new connections to the database.

SEE ALSO

None

2–148 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary


DESCRIPTION

Starts any or all of the Microsoft SQL Server services and enables monitors on a specified endpoint. You can start services and monitors independently.

AUTHORIZATION ROLE

mssqlserver_dba

TARGET ENDPOINT

Database server


The following shows the StartServMon dialog; a description of each field follows.

MSSQLServer Service

Displays a scrolling list of options for starting the MSSQLServer service in different modes. It also



e

t

er

o

o

the

provides the option not to start the service. Choose one of the following:

None means do not use any of these actions.

Continue continues the service, if it is paused.

Start in normal mode starts the database server in multi-user mode with full access.

Start in single user mode and connect — starts the database server, restricting database access to onconnection, and Tivoli Manager for Microsoft SQLServer takes the connection. Since only one connection is allowed in single user mode; the SQLExecutive service not started, even if you selecthis option. The MSDTC service does not require aconnection, so it can be started in parallel with thisoption. If you successfully start the server in singleuser mode, you should receive the following message in the Windows NT event log or SQL Serverror log:

Msg 17658: SQL Server booted single user mode - updates allowed to system catalog

Start in single user mode but do not connect — starts the database server, restricting the access tone connection, but Tivoli Manager for Microsoft SQL Server does not take the connection.

If you select either Start in single user mode and connect or Start in single user mode but do not connect, the task does not start the SQLExecutive service, even if you select the check box. Doing swould take the only available connection. Since single user mode is used for server maintenance, SQLExecutive service would prevent maintenanceif it had the connection.

2–150 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Additional Services

Provides two options. You can choose both.

Start MSDTC starts the service required for distributed transaction control.

Start SQLExecutive/SQLServerAgent starts the SQLExecutive service (6.5) or SQLServerAgent service (7.0). This service is required for running Microsoft SQL Server tasks and replication.

Note: In Microsoft SQL Server Version 7.0, the SQL Executive has been renamed to SQLServerAgent, and tasks are referred to as jobs.

TME MS SQL Monitors

Offers one option, Start Server and Database Monitors, which starts any Tivoli Manager for Microsoft SQL Server monitors already set up on the target endpoint. This starts the monitors only when the MSSQLServer service is already running.

Report to File



CLI SYNTAX

Although all the arguments are optional, you must specify at least one. If you use only one argument, it cannot be StartMode= None.

StartServMon

[–a StartMode=None | Continue | Normal | Single | SingleConnect]

[–a SQLExecutive=Y | N]

[–a SQLServerAgent=Y | N]

[–a MSDTC=Y | N]



[–a Monitors=Y | N]








StartMode Sets the start-up mode for the server. Your choices are: None, Continue, Normal (Start in Normal Mode), Single (Start in single user mode), SingleConnect (Start in single user mode and connect). The default is None.

GUI Name: MSSQLServer ServiceSQLExecutive Y starts the service required for running Microsoft SQL Server tasks and replication. N does not start the service and is the default.

GUI Name: Start SQLExecutive/SQLServerAgent


SQLServerAgent

Y starts the service required for running Microsoft SQL Server tasks and replication. N does not start the service and is the default.

GUI Name: Start SQLExecutive/SQLServerAgent


2–152 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

MSDTC Y starts the service required for distributed transaction control. N does not start the service and is the default.

GUI Name: Start MSDTC

Monitors Y starts any Tivoli Manager for Microsoft SQL Server monitors set up on the target endpoint. N does not start them and is the default.

GUI Name: Start Server and Database Monitors





SaveReportFileOn



CLI EXAMPLE

wruntask -t StartServMon -l "MSSQLManagerTasks" -h @MSSQLServer:hbergin@hbergin -a StartMode=Normal --a SQLExecutive=Y



-a MSDTC=Y -a Monitors=Y

OUTPUT


USAGE NOTES

The options for starting the SQLExecutive (6.5) and SQLServerAgent (7.0) are equivalent and work with either version of Microsoft SQL Server. That is, using the SQLServerAgent option in Version 6.5 starts the SQLExecutive service, and vice versa. The alternate naming is provided for convenience.

SEE ALSO

Tasks: Stop MS SQL Server Services and TME Monitors

2–154 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary


DESCRIPTION

Stops any or all of the Microsoft SQL Server services and disables monitors on a specified endpoint. You can stop services and monitors independently.

If you choose both to stop services and stop monitors, all monitors are stopped before the services are shut down. The task may take more time than expected to complete if there is a delay in stopping the monitors.

AUTHORIZATION ROLE

mssqlserver_dba


■ Microsoft SQL Server 6.5: SA for shutdown options

■ Microsoft SQL Server 7.0: sysadmin for shutdown options

TARGET ENDPOINT

Database server




The following shows the StopServMon dialog; a description of each field follows.

MSSQLServer Service

Displays a scrolling list of options for stopping the Microsoft SQL Server service in different modes. It also provides the option not to stop the service.

None means do not use any of these actions.

Shutdown disables all logins but the Microsoft SQL Server sa, waits for executing statements to finish, checkpoints each database, and then stops the database server service. Shutdown tries to shut down the database server in an orderly fashion by: 1) disabling logins (except for the system

2–156 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

administrator); 2) waiting for currently executing TRANSACT-SQL statements or stored procedures to finish; and 3) performing a checkpoint in every database.

Shutdown with no wait stops the database server immediately with no preparation. This can lead to recovery problems. It shuts down the database server immediately without performing checkpoints in every database. The database server exits after attempting to terminate all user processes and rolls back any active transactions.

Pause stops any new users from logging onto the server.

Pause followed by shutdown stops any new users logging onto the server; waits for the specified time out; and then performs the same actions as Shutdown.

Pause followed by shutdown with no wait stops any new users logging onto server. Waits for the specified time-out and then performs the same actions as Shutdown with no wait.

Stop stops server without waiting for transactions to finish.

Pause timeout How long to wait (in hh:mm:ss format) before taking action. Valid only with the Pause followed by shutdown and Pause followed by shutdown with no wait options. For all other options it is ignored.

Shutdown Message

Displays a box for you to enter a message to send to all users logged onto the system where the database server is running. Valid only with the Pause followed by shutdown and Pause followed by shutdown with no wait options. For all other options it is ignored.



Additional Services

Provides two options. You can choose both. Note that stopping the MSSQLServer service in Version 7.0 automatically stops SQLServerAgent and MSDTC as well.

Stop SQLExecutive/SQLServerAgent stops the SQLExecutive service (6.5) or the SQLServerAgent service (7.0). The service is required for running Microsoft SQL Server tasks and replication.

Stop MSDTC stops the service required for distributed transaction control.

Note: In Microsoft SQL Server Version 7.0, the SQL Executive service has been renamed to SQLServerAgent.

TME MS SQL Monitors

Offers one option: Stop Server and Database Monitors, which disables any Tivoli Manager for Microsoft SQL Server monitors already set up on the target endpoint. You can stop the monitors without stopping the MSSQLServer service.

Report to File



CLI SYNTAX

Although all the arguments are optional, you must specify at least one argument. It cannot be StopMode= None.

StopServMon

[–a StopMode=None | Shutdown | NoWait | Pause | PauseShutdown | PauseNoWait | Stop]

[–a Timeout=<hh:mm:ss>]

2–158 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

[–a Message="<message text>" ]

[–a SQLExecutive=Y | N]

[–a SQLServerAgent=Y | N]

[–a MSDTC=Y | N]

[–a Monitors=Y | N]








StopMode Sets the shutdown mode for the server. Your choices are: None (None), Shutdown (Shutdown), NoWait (Shutdown with no wait), Pause (Pause), PauseShutdown (Pause followed by shutdown), PauseNoWait (Pause followed by shutdown with no wait), and Stop (stop). The default is None.

GUI Name: MSSQLServer Service

Timeout <hh:mm:ss> is the amount of time to wait before stopping the server. Valid only with the Pause followed by shutdown and Pause followed by shutdown with no wait options. For all other options it is ignored.

GUI Name: Pause timeout (hh:mm:ss)

Message " <message text>" is the text of the message the task sends to users. This option is valid only if PauseShutdown or PauseNoWait is also specified.

GUI Name: Shutdown Message

SQLExecutive Y stops the SQLExecutive service. N does not stop the service and is the default.



s

. EC.

lt.

GUI Name: Stop SQLExecutive/SQLServerAgent

Note: In Microsoft SQL Server Version 7.0, the SQL Executive has been renamed to SQLServerAgent.

SQLServerAgent

Y — stop the SQLServerAgent service. N does not stop the service and is the default.

GUI Name: Stop SQLExecutive/SQLServerAgent

Note: In Microsoft SQL Server Version 7.0, the SQL Executive has been renamed to SQLServerAgent.

MSDTC Y — stop the service required for distributed transaction control. N does not stop the service and ithe default.

GUI Name: Stop MSDTC

Monitors Y — disables any Tivoli Manager for Microsoft SQLServer monitors set up on the target endpoint. N does not stop the monitors and is the default.

GUI Name: Stop Server and Database Monitors


TECServer <servername> the name of the TEC server to sendthe message to.

ReportToFile Y saves the output of this task to a file. N does not save the output of this task to a file and is the defauIf Y, specify the file with ReportFileName and optionally the host with SaveReportFileOn.

ReportFileName <filename> is the path to and the name of the fileto create as the task output.

2–160 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

SaveReportFileOn



CLI EXAMPLE.

wruntask -t StopServMon -l "MSSQLManagerTasks" -h @MSSQLServer:hbergin@hbergin -a StopMode=PauseShutdown -a Timeout="00:02:00" -a Message="Server shutting down in two minutes"-a SQLExecutive=Y -a MSDTC=Y -a Monitors=Y



OUTPUT


USAGE NOTES

The options for stopping the SQLExecutive (6.5) and SQLServerAgent (7.0) services are equivalent and work with either version of Microsoft SQL Server. That is, using the SQLServerAgent option in Version 6.5 starts the SQLExecutive service, and vice versa. The alternate naming is provided for convenience.

In Version 7.0, the SQLServerAgent service is dependent upon the MSSQLServer service: if both are running and MSSQLServer is stopped, SQLServerAgent is stopped as well. If SQLServerAgent is started, MSSQLServer also starts, if it is not running.

In Version 6.5, the SQLExecutive service is not dependent upon the MSSQLServer service. The services can be stopped and started independently.

2–162 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

SEE ALSO

Tasks: Start MS SQL Server Services and TME Monitors


Update Space Usage Information


DESCRIPTION

Corrects inaccuracies in the sysindexes table that can result in incorrect space usage reports by the sp_spaceused stored procedure. The database must be in single user mode for the information on the syslogs table to be updated.

AUTHORIZATION ROLE

mssqlserver_dba




TARGET ENDPOINT

Database


The following shows the UpdateUsage dialog; a description of each field follows.

Table name Updates the space usage information for a specific table or for all tables.

2–164 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

Index name Updates the space usage information for indexes with a particular name, which you specify in this field, or all indexes.

The following chart shows how entries in the Table name and Index name fields determine which indexes and tables are updated:

Table Name

Index Name

Outcome

Exists Exists Updates only the specified index on the specified table.

Exists Does not exist

Error. Specified index does not exist.

Exists Blank Updates all indexes on the specified table.

Does not exist

Exists Error. Specified table does not exist.

Does not exist

Does not exist

Error. Specified table does not exist.

Does not exist

Blank Error. Specified table does not exist.

Blank Exists Updates all indexes that share the specified name. The syslogs table is excluded when the Exclude Syslogs option is checked. If the database is not in single user mode, then the syslogs table is not updated. This does not cause the task to fail.

Blank Does not exist

Error. Specified index does not exist.

Blank Blank Updates all indexes. The syslogs table is excluded when the Exclude Syslogs option is checked. If the database is not in single user mode, then the syslogs table is not updated. This does not cause the task to fail.



u

Exclude syslogs table

(Version 6.5 only) Attempts to put the database in single user mode while updating the syslogs table. If the database cannot be put into single user mode (because other users are on the database), the output alerts you of this.

Report to File



CLI SYNTAX


UpdateUsage

[–a TableName=<tablename>]


[–a ExcludeSyslogsTable=Y | N]









TableName <tablename> updates information for indexes in a specific table; if you do not specify <tablename>, it updates all tables.

2–166 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary


IndexName <indexname> updates the indexes with a particular name, which you specify in this field, or all indexes.


ExcludeSyslogsTable

(Version 6.5 only) Y does not attempt to put the database in single user mode; it does not update the syslogs table. N tries to put the database in single user mode while updating the syslogs table. This is the default.

GUI Name: Exclude syslogs table


TECServer <servername> is the name of the TEC server to send the message to.



SaveReportFileOn





CLI EXAMPLE

wruntask -t UpdateUsage -l "MSSQLManagerTasks"-h @MSSQLDatabase:pubs@hbergin@hbergin-a TableName=’authors’ -a IndexName=’aunmind’ -a ExcludeSyslogsTable=Y

OUTPUT


USAGE NOTES

This task creates no report to show whether any corrections to the sysindexes table needed to be made.

This task is based on the DBCC UPDATEUSAGE statement and corrects the USED, RESERVED, and DPAGES columns of the sysindexes table for any clustered indexes on U (user-defined table) or S (system table) object types. It does not maintain size information for nonclustered indexes. You can use this task to synchronize space

2–168 Version 1.3


Th

e MS

SQ

LM

anag

erTasks L

ibrary

usage counters in sysindexes, which results in accurate usage information.

The DBCC UPDATEUSAGE statement acquires a shared table lock on the table it is processing. It can perform updates to the SYSINDEXES row for syslogs only when the database is in single user mode and you specify the syslogs table. This prevents any logging during the update and ensures accurate changes. All other changes to the SYSINDEXES row are fully logged.

The single user mode database option restricts database access to a single user. You can set this option only when there are no other users currently accessing the database. A new user is allowed into this database only when all other users have disconnected or changed to another database. When this option is set, the trunc. log on chkpt. option is not supported. Truncate the log after single user operations are completed.

SEE ALSO




2–170 Version 1.3

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

3The MSSQLServer Monitoring Collection


■ A table that lists all monitors by GUI name and CLI name

■ Reference entries for each monitor in the MSSQLServer monitoring collection, sorted alphabetically by GUI name

The MSSQLServer monitoring collection provides a range of monitors to allow you to manage distributed Microsoft SQL Server resources. Each monitor manages a different aspect of a database server, such as availability, locks, I/O, and space usage.

■ To monitor database servers, distribute a profile containing MSSQLServer monitors to database server or managed node endpoints, as specified in the reference entry. Those monitors are described in this chapter.

■ To create customized monitors, use the Freeform SQL numeric and Freeform SQL string monitors in the MSSQLServer monitoring collection. You provide SQL statements that determine the monitors behavior. Those monitors are described in this chapter.

■ To monitor individual databases, distribute a profile containing MSSQLDatabase monitors to database endpoints. Database monitors are described in Chapter 4, “MSSQLDatabase Monitoring Collection.”

3


List of MSSQLServer Monitoring Sources by GUI and CLI Names

For more information about distributed monitoring, see Chapter 6, “Setting Up Monitoring,” in Tivoli Manager for Microsoft SQL Server User’s Guide.


The following table lists the monitoring sources in this collection by their GUI and their CLI names.

GUI Name CLI Name

Cache Average Free Page Scan

CacheAverageFreePageScan

Cache Configured Free Buffers Percent Used

CacheConfiguredFreeBuffersPercentUsed

Cache Hit Ratio CacheHitRatio

Cache Maximum Free Page Scan

CacheMaximumFreePageScan

Cache Number of Free Buffers

CacheNumberFreeBuffers

Client Count ClientCount

Client Count Percent Used ClientCountPercentUsed

CPU Percent Busy CPUPercentBusy

CPU Percent Busy Doing I/O CPUPercentBusyDoingIO

CPU Percent Idle CPUPercentIdle

Database Status (Server) DatabaseStatusSRVR

Data Space Percent Used (Server)

DataSpacePercentUsedSRVR

Delivered Latency DeliveryLatency

Delivered Transaction Rate DeliveredTransactionRate

3–2 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

Delivered Transactions DeliveredTransactions

Extent Locks Exclusive ExtentLocksExclusive

Extent Locks Total ExtentLocksTotal

Extent Locks Update ExtentLocksUpdate

Freeform SQL Numeric FreeFormSQLNumeric

Freeform SQL String FreeFormSQLString

I/O Batch Average Size IOBatchAverageSize

I/O Batch Maximum Size IOBatchMaximumSize

I/O Batch Write Rate IOBatchWriteRate

I/O Disk Errors IODiskErrors

I/O Disk Reads IODiskReads

I/O Disk Writes IODiskWrites

I/O Log Write Rate IOLogWriteRate

I/O Outstanding Reads IOOutstandingReads

I/O Outstanding Writes IOOutstandingWrites

I/O Page Read Rate IOPageReadRate

I/O Single Page Write Rate IOSinglePageWriteRate

I/O Transaction Rate IOTransactionRate

I/O Transactions Per Log Record

IOTransactionsPerLogRecord

Intent Locks Exclusive IntentLocksExclusive

Intent Locks Shared IntentLocksShared

Intent Locks Total IntentLocksTotal

GUI Name CLI Name



Log Space Percent Used (Server)

LogSpacePercentUsedSRVR

Network Read Rate NetworkReadRate

Network Write Rate NetworkWriteRate

NT Application Log NTApplicationLog

NT Application Log Age NTApplicationLogAge

NT Application Log Percent Full

NTApplicationLogPercentFull

Number of Blocked Processes NumberOfBlockedProcesses

Number of Deadlocks NumberOfDeadlocks

Oldest Open Transaction (Server)

OldestOpenTransactionSRVR

Page Locks Exclusive PageLocksExclusive

Page Locks Shared PageLocksShared

Page Locks Total PageLocksTotal

Page Locks Update PageLocksUpdate

Procedure Buffers Active ProcedureBuffersActive

Procedure Buffers Total ProcedureBuffersTotal

Procedure Buffers Used ProcedureBuffersUsed

Procedure Cache Active ProcedureCacheActive

Procedure Cache Size ProcedureCacheSize

Procedure Cache Used ProcedureCacheUsed

RA Effectiveness RAEffectiveness

RA Pages Fetched into Cache Per Second

RAPagesFetchedIntoCachePerSecond

GUI Name CLI Name

3–4 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

RA Pages Found in Cache Per Second

RAPagesFoundInCachePerSecond

RA Physical Read Rate RAPhysicalReadRate

RA Slots Used RASlotsUsed

Service State ServiceState

SQL Server State SQLServerState

SQLServerAgent Failed Jobs SQLServerAgentFailedJobs

Table Locks Exclusive TableLocksExclusive

Table Locks Shared TableLocksShared

Table Locks Total TableLocksTotal

Total Blocking Locks TotalBlockingLocks

Total Exclusive Locks TotalExclusiveLocks

Total Locks TotalLocks

Total Locks Percent Used TotalLocksPercentUsed

Total Locks Remaining TotalLocksRemaining

Total Shared Locks TotalSharedLocks

Undelivered Transactions UndeliveredTransactions

User Connections UserConnections

User Connections Percent Used

UserConnectionsPercentUsed

User Connections Remaining UserConnectionsRemaining

GUI Name CLI Name




DESCRIPTION

Reports the average number of buffers scanned by the LazyWriter when the LazyWriter searches the data cache for an unused buffer to replenish the free buffer pool. If Microsoft SQL Server must read a large number of buffers to find a free one, server performance may degrade. A low value indicates optimal performance.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CacheAverageFreePageScan

CLI EXAMPLE

waddmon ’MSSQLServer’ ’CacheAverageFreePageScan’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CacheAverageFreePageScan_1.log’ "<profilename>"

3–6 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a 100-page buffer.

Suggested monitoring schedule: ten minutes

OUTPUT

The following shows example output from this monitor:

USAGE NOTES

If the returned value is high, you can do one of the following:

■ Increase cache size

■ Check the disk I/O to ensure buffers are flushing efficiently

Severity Trigger When Default Actions

Critical Greater than 15 Send MSSQL Sentry notice

Severe Greater than 10 Send MSSQL Sentry notice

Warning Greater than 5 Send MSSQL Sentry notice

Normal N/A None

Always N/A None



■ Increase the number in the Microsoft SQL Server free buffers configuration option (Microsoft SQL Server Version 6.5 only)

SEE ALSO

MSSQLServer monitors: Cache Hit Ratio, Cache Maximum Free Page Scan, Cache Number of Free Buffers, Cache Configured Free Buffers Percent Used

3–8 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

This monitor is available only for Microsoft SQL Server Version 6.5. Version 7.0 does not support the free buffers server configuration option.

Returns a percentage value of the number of actual free buffers compared to the minimum number of buffers configured with the Microsoft SQL Server free buffers configuration option. If the percentage falls below 100 percent, the minimum number of buffers are not being maintained. If Microsoft SQL Server must read a large number of buffers to find a free one, server performance may degrade. A value of 100% or higher indicates optimal performance.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CacheConfiguredFreeBuffersPercentUsed

CLI EXAMPLEwaddmon ’MSSQLServer’’CacheConfiguredFreeBuffersPercentUsed’-t ’2 minutes’ -c ’critical’-c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CacheConfiguredFreeBuffersPercentUsed.log’ "<profilename>"




The following table shows suggested threshold values for severity levels.


OUTPUT

The following shows an example output from this monitor:


Critical Less than 70% Send MSSQL Sentry notice

Severe Less than 80% Send MSSQL Sentry notice

Warning Less than 90% Send MSSQL Sentry notice

Normal N/A None

Always N/A None

3–10 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
You can configure a minimum number of free buffers with the Microsoft SQL Server free buffers configuration option. This tells the LazyWriter to try to maintain at least the specified amount of free buffers. Use this monitor to see if the specified number is free.

If the returned value is low, you can do one of the following:

■ Increase cache size

■ Check the disk I/O to ensure buffers are flushing efficiently

■ Increase the number in the free buffers configuration option

SEE ALSO

MSSQLServer monitors: Cache Average Free Page Scan, Cache Hit Ratio, Cache Maximum Free Page Scan, Cache Configured Free Buffers Percent Used


Cache Hit Ratio

Cache Hit Ratio

DESCRIPTION

Reports the current ratio of data cache hits to total requests. Use this monitor to check the effectiveness of the data cache. For optimal performance, the returned value should be approximately 95% or greater.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CacheHitRatio

CLI EXAMPLE

waddmon ’MSSQLServer’ ’CacheHitRatio’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CacheHitRatio_2.log’ "<profilename>"

3–12 Version 1.3

Cache Hit Ratio

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


Cache Hit Ratio

rge

USAGE NOTES

A correctly tuned data cache can significantly improve overall performance. Tuning consists of sizing the memory available to the database server. Memory strategies are different for Microsoft SQL Server 6.5 and 7.0, because Microsoft SQL Server 7.0 can be configured to manage its own memory dynamically.

Microsoft SQL Server 6.5

You can increase the cache hit ratio by increasing the amount of memory reserved for the data cache using the memory configuration option. Increasing memory also increases the procedure cache.

Note: When using the memory configuration option, make sure you do not allocate so much memory to the database server that you inhibit the performance of the operating system.

Microsoft SQL Server 7.0

You can use dynamic memory allocation to allow Microsoft SQL Server to tune itself. The preferred scenario is for the database server to run on a dedicated machine with dynamic memory allocation in effect. Microsoft SQL Server 7.0 increases its allocation if (a) it needs it and (b) there is more than 5 megabytes of unallocated memory available. It concedes memory if unallocated memory available falls below 5 megabytes.

If other critical processes are running on the same machine, it may be better to use the max server memory and min server memory server configuration options to define the database server’s memoryterritory. This is particularly true if the other processes consume laamounts of memory or have widely varying needs for memory.

SEE ALSO

MSSQLServer monitors: Cache Average Free Page Scan, Cache Maximum Free Page Scan, Cache Number of Free Buffers, Cache Configured Free Buffers Percent Used

3–14 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the maximum value for the number of buffers scanned by the LazyWriter when the LazyWriter searches the data cache for an unused buffer to replenish the free buffer pool. Use this monitor to check the effectiveness of the data cache.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CacheMaximumFreePageScan

CLI EXAMPLE

waddmon ’MSSQLServer’ ’CacheMaximumFreePageScan’ -t ’2 minutes’ -c ’critical’ -c ’severe’-c ’warning’-c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CacheMaximumFreePageScan_3.log’ "<profilename>"




The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a 100-page buffer.


OUTPUT



Critical More than 15 Send MSSQL Sentry notice

Severe More than 10 Send MSSQL Sentry notice

Warning More than 5 Send MSSQL Sentry notice

Normal N/A None

Always N/A None

3–16 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
If you run this monitor every half hour for two hours, the following table shows an example of time increments, the actual buffers scanned, and the value returned by the monitor:

SEE ALSO

MSSQLServer monitors: Cache Average Free Page Scan, Cache Hit Ratio, Cache Number of Free Buffers, Cache Configured Free Buffers Percent Used

Time IncrementsBuffers Scanned

Value Returned by Monitor

30 minutes 30 30

60 minutes 40 40

90 minutes 20 40

120 minutes 10 40




DESCRIPTION

Reports the current number of cache buffers in the free buffer pool. Use this monitor as an alert when the number of buffers is getting low. A low number of free buffers may degrade server performance.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CacheNumberFreeBuffers

CLI EXAMPLE

waddmon ’MSSQLServer’ ’CacheNumberFreeBuffers’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CacheNumberFreeBuffers_4.log’ "<profilename>"

3–18 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a buffer count of 2000.


OUTPUT



Critical Less than 60 Send MSSQL Sentry notice

Severe Less than 80 Send MSSQL Sentry notice

Warning Less than 100 Send MSSQL Sentry notice

Normal N/A None

Always N/A None



USAGE NOTES

The value should not fall below the number specified by the free buffers configuration option. If it does fall below the threshold, you may need to increase the maximum async io and maximum lazywrite io configuration options, although the LazyWriter normally ensures that the value does not fall below the threshold.

SEE ALSO

MSSQLServer monitors: Cache Average Free Page Scan, Cache Hit Ratio, Cache Maximum Free Page Scan, Cache Configured Free Buffers Percent Used

3–20 Version 1.3

Client Count

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Client Count
DESCRIPTION

Monitors the number of client workstations currently connected to the database server. Use this monitor as an alert when you are running out of client connections, which may result in server access problems. This monitor is also useful for tracking client access patterns.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

ClientCount

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ClientCount’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQL\Server\ClientCount_6.log’ "<profilename>"


Client Count


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a client count limit of 100.


OUTPUT


USAGE NOTES

None

SEE ALSO

MSSQLServer monitors: Client Count Percent Used





Normal N/A None

Always N/A None

3–22 Version 1.3

Client Count Percent Used

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Monitors the number of client workstations currently connected to the database server and returns the ratio percentage of the number of possible connections. For example, if you have 10 client connections and eight are currently in use, this monitor returns a value of 80%. Running out of client connections may result in server access problems.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

ClientCountPercentUsed

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ClientCountPercentUsed’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ClientCountPercentUsed_7.log’ "<profilename>"






OUTPUT


USAGE NOTES

None

SEE ALSO

MSSQLServer monitors: Client Count


Critical Greater than 90% Send MSSQL Sentry notice

Severe Greater than 80% Send MSSQL Sentry notice

Warning Greater than 70% Send MSSQL Sentry notice

Normal N/A None

Always N/A None

3–24 Version 1.3

CPU Percent Busy

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
CPU Percent Busy
DESCRIPTION

Reports the percentage of time that the CPU is used for database server work during the current monitoring interval. Use this monitor to gauge how much of the CPU resource the database server uses so you can allocate resources more efficiently. You can also use this monitor to determine how resource-intensive certain operations are.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CPUPercentBusy

CLI EXAMPLE

waddmon ’MSSQLServer’ ’CPUPercentBusy’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CPUPercentBusy_9.log’ "<profilename>"


CPU Percent Busy




OUTPUT


USAGE NOTES

If you use CPU Percent Idle, you do not need to use this monitor.

SEE ALSO

MSSQLServer monitors: CPU Percent Busy Doing I/O, CPU Percent Idle.





Normal N/A None

Always N/A None

3–26 Version 1.3

CPU Percent Busy Doing I/O

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the percentage of time used for I/O operations during the current monitoring interval. Use this monitor to gauge how much of the CPU resource the database server uses for I/O so you can allocate resources more efficiently. You also can use this monitor to determine how I/O resource-intensive certain operations are.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CPUPercentBusyDoingIO

CLI EXAMPLEwaddmon ’MSSQLServer’ ’CPUPercentBusyDoingIO’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CPUPercentBusyDoingIO_10.log’ "<profilename>"





Suggested monitoring schedule: 10 minutes

OUTPUT


USAGE NOTES

None

SEE ALSO

CPU Percent Busy, CPU Percent Idle





Normal N/A None

Always N/A None

3–28 Version 1.3

CPU Percent Idle

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
CPU Percent Idle
DESCRIPTION

Reports the percentage of time that a database server has been idle during the current monitoring interval. Use this monitor to gauge how much of the CPU resource the database server uses so you can allocate resources more efficiently. You also can use this monitor to determine how resource-intensive certain operations are.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

CPUPercentIdle

CLI EXAMPLE

waddmon ’MSSQLServer’ ’CPUPercentIdle’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\CPUPercentIdle_11.log’ "<profilename>"


CPU Percent Idle




OUTPUT


USAGE NOTES

If you use the CPU Percent Busy monitor, you do not need to use this monitor.

SEE ALSO

MSSQLServer monitors: CPU Percent Busy, CPU Percent Busy Doing I/O





Normal N/A None

Always N/A None

3–30 Version 1.3

Database Status (Server)

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports when a database has become unavailable. A database is considered unavailable when it has been marked offline, suspect, or is in recovery. This monitor checks the status of each database and reports the first one it finds unavailable. Use this monitor to obtain an overview of database availability on the server. If you are interested in the status of one particular database, use the database version of this monitor.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

DatabaseStatusSRVR

CLI EXAMPLE

waddmon ’MSSQLServer’ ’DatabaseStatusSRVR’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\DatabaseStatus_12.log’ "<profilename>"





Suggested monitoring schedule: five minutes

OUTPUT



Critical Is unavailable Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–32 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
Database availability may affect replication, if the database that is unavailable is a subscriber or a distribution database.

If a database is in one of the following states, it is Available:

■ ’read only’ =1024

■ ’single user’, connection in use =4096

■ ’dbo use only’ =2048

■ ’is being checkpointed’ = 8192

If a database is in one of the following states, it is Unavailable:

■ ‘in transition’ = 2 (Microsoft SQL Server Version 6.5 only)

■ ‘loading’ = 32

■ ‘pre recovery’ = 64

■ ‘recovering’ = 128

■ ‘not recovered’ = 256

■ ‘offline’ = 512

■ ‘emergency mode’ = 32768

SEE ALSO

MSSQLServer monitors: Service State, SQL Server State

MSSQLDatabase monitors: Database Status (Database)



then of its to

e


DESCRIPTION

Examines the percentage of each database’s allocated space. Itreports which database on the server uses the largest percentageallocated disk space and supplies the percentage value. Use thismonitor to determine when to extend the size of a database and track database growth on the server.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


The following window shows the fields for this monitor shown on th Add Monitor to TME 10 Distributed Monitoring Profile dialog. A description of each field follows.

3–34 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

Run Update Usage

Yes runs DBCC UPDATEUSAGE against the database before the monitor value is set. This ensures that the data returned is up-to-date. This procedure can take some time on large tables, so it may make the monitor unusable or too resource-intensive.

No does not run DBCC UPDATEUSAGE.



CLI SYNTAX

DataSpacePercentUsedSRVR

–a <Update Usage>


<Update Usage>

YES runs the SQL command DBCC UPDATEUSAGE against the database before the monitor value is set. NO does not run DBCC UPDATEUSAGE. (Yes, yes, No, and no are also acceptable forms.)

CLI EXAMPLE

waddmon ’MSSQLServer’ ’DataSpacePercentUsedSRVR’ -a ’No’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’ -f ’hbergin:C:\MSSQLServer\DataSpacePercentUsed.log’ "<profilename>"



Suggested monitoring schedule: thirty minutes





Normal N/A None

Always N/A None

3–36 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
OUTPUT

USAGE NOTES

In Microsoft SQL Server Version 6.5, the data and log may or may not be on the same device fragment. If they are, then the space reported is for both the data and log. If they are not, then the space reported is for the data only.

In Microsoft SQL Server Version 7.0, the value reported is always for the data only.

When the database runs out of space, it is not extended automatically in Microsoft SQL Server Version 6.5. It can be configured to extend itself automatically in Microsoft SQL Server 7.0. You may also want to use the NT Logical Disk: Percent Free Space monitor if the database is set to grow itself indefinitely.

If you have a particularly volatile database, you may want to use the MSSQLDatabase version of this monitor. The MSSQLDatabase monitors are also useful if you have a static database that has used a high percentage of its allocated space.

SEE ALSO

MSSQLDatabase monitors: Data Space Used, Data Space Percent Used (Database), Space Used (Table)

Tasks: MS SQL Server Warnings and Indicators


Delivered Latency

Delivered Latency

DESCRIPTION

Reports the number of seconds a replicated transaction remains in the distribution database before it is delivered to the subscription server. This is the time between a job being inserted in the distribution database and being executed against the destination database. Use this monitor to discover if there are any bottlenecks in the replication process. Bottlenecks cause delays in the published transactions reaching the subscriber.

Version 7.0: Microsoft no longer officially supports the sp_distcounters stored procedure, which this monitor uses. However, in testing the procedure appears to return valid data. Be aware that this monitor currently works on Version 7.0 but may be vulnerable to Microsoft updates or changes.

AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


The following window shows the fields for this monitor shown on the Add Monitor to TME 10 Distributed Monitoring Profile dialog. A description of each field follows.

3–38 Version 1.3

Delivered Latency

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

Subscriber Name

Specifies the server name set up to subscribe to a publication. For example, Server A has a publication on the table called ‘current_rates’ . This table is constantly updated. Server B has a similar table and should reflect any updates made to the ‘current rates’ table on Server A. Therefore, Server B is the subscriber name.


Delivered Latency

CLI SYNTAX

DeliveryLatency

–a <subscriber>


<subscriber> Specifies the server name set up to subscribe to a publication.

CLI EXAMPLE

waddmon ’MSSQLServer’ ’DeliveryLatency’-a ’hbergin’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\DeliveryLatency_16.log’ "<profilename>"


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 30 transactions per minute, assuming the distribution schedule is set to run every minute.






Normal N/A None

Always N/A None

3–40 Version 1.3

Delivered Latency

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
OUTPUT

USAGE NOTES

The distribution schedule can affect the transaction rate, which determines the interval between transactions being distributed to the subscriber. It can also be affected by the amount of transactions that you configure to be sent in a batch.

The subscription server is the server with the subscriber database on it; the distribution server is the server that has the distribution database on it.

There are several monitors that check the flow of replication transactions from the distribution to the subscriber database. These are Delivered Latency, Delivered Transaction Rate, Delivered Transactions, and Undelivered Transactions.

There also are several monitors that check the flow of replication transactions from the publisher to the distribution database. These are Replicated Transaction Rate, Replicated Transactions, and Replication Latency.


Delivered Latency

If delays are reported, you can do the following:

■ Check the network between the distribution database and subscriber database, if they are on different servers. Use the Network Read Rate and Network Write Rate monitors.

■ Check the workload on one or both servers to determine when it is overloaded. Use the CPU Percent Busy monitor.

■ Check to see if the subscriber database is unavailable. Use the Database Status (Database) monitor to check this.

SEE ALSO

MSSQLServer monitors: CPU Percent Busy, Delivered Transaction Rate, Delivered Transactions, Network Read Rate, Network Write Rate, Undelivered Transactions

MSSQLDatabase monitors: Database Status (Database), Replication Latency, Replicated Transactions, Replicated Transaction Rate

3–42 Version 1.3

Delivered Transaction Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the replication transaction delivery rate, which is the number of jobs per second that were executed in the last batch sent to the subscription server from the distribution server.

Use this monitor to see if there are bottlenecks in the replication process; bottlenecks cause delays in the published transactions reaching the subscriber. You also can use this monitor to find out if the transaction rate is slower than anticipated.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers





Subscriber Name


3–44 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
CLI SYNTAX
DeliveredTransactionRate

–a <subscriber>



CLI EXAMPLE

waddmon ’MSSQLServer’ ’DeliveredTransactionRate’ -a ’hbergin’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\DeliveredTransactionRatelog’ "<profilename>"


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 30 transactions per minute, assuming the distribution schedule is set to run every minute.



Critical Less than 0.0 Send MSSQL Sentry notice

Severe Less than 0.25 Send MSSQL Sentry notice

Warning Less than 0.5 Send MSSQL Sentry notice

Normal N/A None

Always N/A None



OUTPUT


USAGE NOTES

The distribution schedule can affect the transaction rate, which determines the interval between transactions being distributed to the subscriber. The amount of transactions that you configure to be sent in a batch also can affect it.


There are several monitors that check the flow of replication transactions from the distribution to the subscriber database. These are Delivered Latency, Delivered Transactions, and Undelivered Transactions.


3–46 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
■ Check the network between the distribution database and subscriber database if they are on different servers. Use the Network Read Rate and Network Write Rate monitors to do this.

■ Check the workload on one or both servers to determine if it is overloaded. Use the CPU Percent Busy monitor to check this.


SEE ALSO

MSSQLServer monitors: CPU Percent Busy, Delivered Latency, Delivered Transactions, Network Read Rate, Network Write Rate, Undelivered Transactions

MSSQLDatabase monitors: Database Status (Database), Replication Latency, Replicated Transaction Rate, Replicated Transactions


Delivered Transactions


DESCRIPTION

Reports the number of delivered transactions in the distribution database. A delivered transaction is one that has already been executed against the destination database, but it still resides in the distribution database. Use this to check the number of transactions that have been successfully executed against the destination database during a specified period.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers



3–48 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

Subscriber Name




get ery

CLI SYNTAX

DeliveredTransactions

–a <subscriber>


<subscriber> Specifies the server name set up to subscribe to apublication.

CLI EXAMPLE

waddmon ’MSSQLServer’ ’DeliveredTransactions’ -a ’hbergin’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\DeliveredTransactions_15.log’ "<profilename>"


The following table shows suggested threshold values for severitylevels. The response levels are based on the assumption of a tarrate of 30 transactions per minute, assuming the monitor is run evfive minutes, and distributed transactions are set to remain in thedistribution database for one minute.






Normal N/A None

Always N/A None

3–50 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
OUTPUT

USAGE NOTES


The transaction rate can be affected by the distribution schedule, which determines the interval between transactions being distributed to the subscriber. It can also be affected by the number of transactions that you configure to be sent in a batch.

The period that delivered transactions remain in the distribution database is configurable. You can tell how many transactions have successfully executed during this period of time. If the value is lower than anticipated, this could point to a bottleneck in the replicated transaction process. If the value is high, it indicates you are getting good throughput, but you may be unnecessarily filling up the distribution database.

If the value is high, you can do the following:

■ Check whether the period that delivered transactions remain in the distribution database is too long. If it is, the database can fill up. Reduce the value for the period.



If the value is low, you can do the following:




There are several monitors that check the flow of replication transactions from the distribution to the subscriber database. These are Delivered Latency, Delivered Transaction Rate, and Undelivered Transactions.


SEE ALSO

MSSQLServer monitors: CPU Percent Busy, Delivered Latency, Delivered Transaction Rate, Network Read Rate, Network Write Rate, Undelivered Transactions

MSSQLDatabase monitors: Database Status (Database), Replicated Transaction Rate, Replicated Transactions, Replication Latency

3–52 Version 1.3

Extent Locks Exclusive

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the current number of exclusive extent locks. An extent is an allocation unit; these locks are taken out when space needs to be allocated. (For more information on exclusive extent locks, see the Microsoft SQL Server Books On-line.) SQL statements based on CREATE, DROP, and INSERT require this type of lock to be taken out. Use this monitor to show the number of these locks during normal server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

ExtentLocksExclusive

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ExtentLocksExclusive’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ExtentLocksExclusive_17.log’ "<profilename>"




The following table shows suggested threshold values for severity levels. The response levels are based a total of 5000 total locks.


OUTPUT






Normal N/A None

Always N/A None

3–54 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
The reported value indicates the type of activity occurring on the server. If you run out of locks frequently, the sp_lock stored procedure can provide a greater level of detail about lock activity.

SEE ALSO

MSSQLServer monitors: Extent Locks Total, Extent Locks Update.


Extent Locks Total

Extent Locks Total

DESCRIPTION

Reports the current number of all extent locks. An extent is an allocation unit; these locks are taken out when space needs to be allocated. (For more information on extent locks, see the Microsoft SQL Server Books On-line.) SQL statements based on CREATE, DROP, and INSERT require this type of lock to be taken out. Use this monitor to show the number of these locks during normal server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

ExtentLocksTotal

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ExtentLocksTotal’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ExtentLocksTotal_21.log’ "<profilename>"

3–56 Version 1.3

Extent Locks Total

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a total of 5000 locks for the server.


OUTPUT






Normal N/A None

Always N/A None


Extent Locks Total

USAGE NOTES

The reported value indicates the type of activity occurring on the server. If you run out of locks frequently, the sp_lock stored procedure can provide a greater level of detail about lock activity.

SEE ALSO

MSSQLServer monitors: Extent Locks Exclusive, Extent Locks Update

3–58 Version 1.3

Extent Locks Update

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Extent Locks Update
DESCRIPTION

Reports the current number of update extent locks. An extent is an allocation unit; these locks are taken out when space needs to be allocated. (For more information on update extent locks, see the Microsoft SQL Server Books On-line.) SQL statements based on CREATE, DROP, and INSERT require this type of lock to be taken out. Use this monitor to show the number of these locks during normal server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

ExtentLocksUpdate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ExtentLocksUpdate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ExtentLocksUpdate_21.log’ "<profilename>"


Extent Locks Update




OUTPUT






Normal N/A None

Always N/A None

3–60 Version 1.3

Extent Locks Update

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
The reported value indicates the type of activity occurring on the server. If you are running out of locks, the sp_lock stored procedure can provide a greater level of detail about lock activity.

SEE ALSO

MSSQLServer monitors: Extent Locks Exclusive, Extent Locks Total


Freeform SQL Numeric

s

e


DESCRIPTION

Runs a user-defined TRANSACT-SQL (TSQL) SELECT statement that returns a numeric value. Use this monitor to define a monitor that meets your site’s specific needs. You can define multiple monitorand run them concurrently. The only limitation to the number of monitors you can create and run is your system resources.

AUTHORIZATION ROLE

mssqlserver_monitor


■ Microsoft SQL Server 6.5: SELECT


TARGET ENDPOINT

database servers



3–62 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

SQL Statement

Transact-SQL statement to be used in the monitor.

Column number of return value

Column number within the first row returned that contains the monitor value. This is zero-based, that is, the first column is number 0.

Default value (if no rows found)

Default value to be returned when no rows are returned from the SQL Statement.



CLI SYNTAX

FreeFormSQLNumeric

–a <SQL_select_statement >

–a <index >

–a <value>


<SQL_select_statement>

Transact-SQL statement to be used in the monitor.

<index> Column number within the first row returned that contains the monitor value. This is zero-based, that is, the first column is number 0.

<value> Default value to be returned when no rows are returned from the SQL_select_statement.

CLI EXAMPLE

The following example creates a monitor that checks the number of databases in a server.

waddmon MSSQLServer FreeFormSQLNumeric -a ’select count(*) from master.dbo.sysdatabases’ -a ’0’ -a ’-1’ -t ’15 minutes’ -c ’critical’ -R ’==’ ’-1’ -p ’steven,Root_sunos414-region’-n ’Microsoft SQLServer Sentry’ -c ’severe’-c ’warning’ -R ’<’ ’5’ -p ’steven,Root_sunos414-region’-n ’Microsoft SQLServer Sentry’ -c ’normal’-c ’always’ "mssqlserver"

In the example, the first column on the first row returned is the monitor value. The monitor is set to run every 15 minutes.

When the number returned is five or greater, there are no problems; the number is returned as the monitor value.

3–64 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
When the number is less than five, it triggers a warning response level and sends a pop-up window to the user steven and the root administrators group; it also sends a notice to the Microsoft SQLServer Sentry notice group.
If no value is returned by the SQL query, then the value is defaulted to –1. This triggers a critical response level and sends a pop-up window to the user steven and the root administrators group; it also sends a notice to the Microsoft SQLServer Sentry notice group.

No severe response level is set. The monitor is set to always return a value.

The profile name is mssqlserver.


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of an SQL query “SELECT @@LANGID” , where us_english is the server language.

Suggested monitoring schedule: Once a day


Critical Not equal to 0 Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None



OUTPUT


USAGE NOTES

Using the TRANSACT-SQL syntax, the Freeform SQL numeric monitor defines an SQL SELECT statement as the basis of a monitor. Do not terminate the SQL statement with a semi-colon (;) or forward slash (/). The select statement may return multiple columns and multiple rows.

The monitor value (the value against which the monitoring criteria is evaluated) must be one of the columns in the first row returned by the statement and must be a numeric value.

The index parameter defines which column in the first row contains the monitor value (zero-based).

A SQL select statement may return no rows. By default, Tivoli Manager for Microsoft SQL Server treats this as an error. You can override the default behavior with the –a value option, in which case the monitor returns the value specified.

The ability to define a freeform SQL SELECT statement allows integration of existing performance monitoring tools (particularly those reporting monitored values to system tables within the subscribing database).

Note: There are no default actions for this monitor.

3–66 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

or

Monitors defined with this monitoring source use numeric operators to evaluate data. You can select the trigger when: pop-up menu of the Edit Monitor dialog to display a list of the available operators. For information about these operators, see Appendix C, “OperatGroups,” of the Tivoli Manager for Microsoft SQL Server User’s Guide.

SEE ALSO

MSSQLServer monitors: Freeform SQL String


Freeform SQL String

s

e

Freeform SQL String

DESCRIPTION

Runs a user-defined TRANSACT-SQL (TSQL) SELECT statement that returns a string value. Use this monitor to define a monitor that meets your site’s specific needs. You can define multiple monitorand run them concurrently. The only limitation to the number of monitors you can create and run is your system resources.

AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers



3–68 Version 1.3

Freeform SQL String

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

SQL Statement

TRANSACT-SQL statement to use in the monitor.

Column number of return value

Column number in the first row returned that contains the monitor value. This is zero-based, that is, the first column is number 0.

Default value (if no rows found)

Default value to be returned if no rows are returned from the SQL Statement.


Freeform SQL String

CLI SYNTAX

FreeFormSQLString

–a <SQL_select_statement >

–a <index >

–a <value>


<SQL_select_statement>

TRANSACT-SQL statement to use in the monitor.

<index> Column number in the first row returned that contains the monitor value. This is zero-based, that is, the first column is number 0.

<value> Default value to be returned if no rows are returned from the SQL_select_statement.

CLI EXAMPLE

The following example creates a monitor that checks that the master database has dbid of 1.

waddmon MSSQLServer FreeFormSQLString -a ’select name, dbid from master.dbo.sysdatabase where dbid = 1’ -a ’0’ -a ’FATAL’ -t ’15 minutes’ -c ’critical’-R ’==’ ’FATAL’ -p ’steven, Root_sunos414-region’ -n ’Microsoft SQLServer Sentry’ -c ’severe’ -R ’!=’ ’master’ -p ’steven, Root_sunos414-region’-n ’Microsoft SQLServer Sentry’ -c ’warning’ -c ’normal’ -c ’always’ "mssqlserver"

The value in the first column is the monitor value. The monitor is set to run every 15 minutes. It takes the value from the first column of the first row returned by the SQL query.

In this example, the monitor returns the name of the database with the ID of 1.

3–70 Version 1.3

Freeform SQL String

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
If the name equals master, there is no problem, and the name is returned as the monitor value.
If the database name is not master, it triggers a severe response level and sends a pop-up window to the user steven and the root administrators group; it also sends a notice to the Microsoft SQLServer Sentry notice group.

If no value is returned by the SQL query, the value defaulted to FATAL. This triggers a critical response level and sends a pop-up window to the user steven and the root administrators group; it also sends a notice to the Microsoft SQLServer Sentry notice group.

No warning response level is set. The monitor is set to always return a value.

The profile name is mssqlserver.


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a SQL query “SELECT @@LANGUAGE” , where us_english is the server language.

Suggested monitoring schedule: Once a day


Critical Not equal to “us_english”

Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None


Freeform SQL String

OUTPUT


USAGE NOTES

Using the TRANSACT-SQL syntax, the Freeform SQL string monitor allows you to define a SQL SELECT statement as the basis of a monitor. Do not terminate the SQL statement with a semi-colon (;) or forward slash (/.) The SELECT statement can return multiple columns and multiple rows. The trigger value (the value against which the monitoring criteria is evaluated) must be one of the columns in the first row returned by the statement and must be a string value.

The index parameter defines which column in the first row contains the trigger value (zero-based).

A SQL SELECT statement can return no rows. By default, Tivoli Manager for Microsoft SQL Server treats this as an error. You may override the default behavior with the –a value option, in which case the monitor returns the value specified by the argument value.

The ability to define a freeform SQL SELECT statement allows for the integration of existing performance monitoring tools, particularly those reporting monitored values to internal system tables in the subscribing database.

Note: There are no default actions for this monitor.

3–72 Version 1.3

Freeform SQL String

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Monitors that are defined with this monitoring source use string operators to evaluate data. You can select the trigger when: pop-up menu of the Edit Sentry Monitor dialog to display a list of the available operators. For information about these operators, see Appendix C, “Operator Groups,” of the Tivoli Manager for Microsoft SQL Server User’s Guide.
SEE ALSO

MSSQLServer monitors: Freeform SQL Numeric


I/O Batch Average Size


DESCRIPTION

Version 6.5 only. Reports the average number of pages written to disk during a batch I/O operation. The checkpoint thread is the primary use of batch I/O. Use this monitor to check that the maximum async io configuration option is set correctly.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOBatchAverageSize

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOBatchAverageSize’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’ -f "<profilename>"

3–74 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target batch size of eight.


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

The maximum number of pages written during a batch I/O operation can be configured. The default is eight in Microsoft SQL Server 6.5 and 32 in Microsoft SQL Server 7.0. If the I/O subsystem handles queued I/O efficiently, you can increase the maximum limit with the maximum async io configuration option. This in turn raises the values for I/O Batch Maximum Size and I/O Batch Write Rate. Setting the maximum async io configuration option too high can overload the disk subsystem with writes.

SEE ALSO

MSSQLServer monitors: I/O Batch Maximum Size, I/O Batch Write Rate, I/O Disk Reads, I/O Disk Writes, , I/O Outstanding Writes

3–76 Version 1.3

I/O Batch Maximum Size

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Version 6.5 only. Reports the maximum number of pages written to disk during a batch I/O operation. The checkpoint thread is the primary use of batch I/O. Use this monitor to check that the maximum async io configuration option is set correctly.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOBatchMaximumSize

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOBatchMaximumSize’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOBatchMaximumSize_28.log’ "<profilename>"




The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target batch size of eight.


OUTPUT


USAGE NOTES

The maximum number of pages written during a batch I/O operation can be configured. The default is eight in Microsoft SQL Server 6.5 and 32 in Microsoft SQL Server 7.0.If the I/O subsystem handles queued I/O efficiently, you can increase the maximum limit with the



Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–78 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
maximum async io configuration option. This in turn raises the values for I/O Batch Average Size, I/O Batch Maximum Size, and I/O Log Write Rate. Setting the maximum async io configuration option too high can overload the disk subsystem with writes.
If you run this monitor every half hour for two hours, the following table shows an example of time increments, the actual pages written, and the value returned by the monitor:

SEE ALSO

MSSQLServer monitors: I/O Batch Average Size, I/O Batch Write Rate, I/O Disk Reads, I/O Disk Writes, , I/O Outstanding Writes

Time Increments Pages WrittenValue Returned by

Monitor

30 minutes 6 6

60 minutes 8 8

90 minutes 4 8

120 minutes 2 8


I/O Batch Write Rate


DESCRIPTION

Version 6.5 only. Reports the rate per second at which pages are written to disk using batch I/O. The checkpoint thread is the primary use of batch I/O. Use this monitor to check that the maximum async io configuration option is set correctly.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOBatchWriteRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOBatchWriteRate’-t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOBatchWriteRate.log’ "<profilename>"

3–80 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 50 pages per second.


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

The maximum number of pages written during a batch I/O operation can be configured. The default is eight in Microsoft SQL Server 6.5 and 32 in Microsoft SQL Server 7.0. If the I/O subsystem handles queued I/O efficiently, you can increase the maximum limit with the maximum async io configuration option. This in turn raises the values for I/O Batch Average Size, I/O Batch Maximum Size, and I/O Log Write Rate. Setting the maximum async io configuration option too high can overload the disk subsystem with writes.

SEE ALSO

MSSQLServer monitors: I/O Batch Average Size, I/O Batch Maximum Size, I/O Disk Reads, I/O Disk Writes, , I/O Outstanding Writes

3–82 Version 1.3

I/O Disk Errors

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
I/O Disk Errors
DESCRIPTION

Reports the number of database server read/write disk errors in a monitoring session. Use this monitor to find out if problems occur in the low level disk I/O, which may indicate disk corruption.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IODiskErrors

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IODiskErrors’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IODiskErrors_30.log’ "<profilename>"


I/O Disk Errors




OUTPUT


USAGE NOTES

None

SEE ALSO

None



Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–84 Version 1.3

I/O Disk Reads

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
I/O Disk Reads
DESCRIPTION

Reports the number of disk reads by the database server during the current monitoring interval. It includes disk reads only, not cache reads. Use this monitor to assess how much disk access is taking place during a normal session.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IODiskReads

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IODiskReads’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IODiskReads_31.log’ "<profilename>"


I/O Disk Reads




OUTPUT






Normal N/A None

Always N/A None

3–86 Version 1.3

I/O Disk Reads

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
The maximum number of pages written during a batch I/O operation can be configured. The default is eight in Microsoft SQL Server 6.5 and 32 in Microsoft SQL Server 7.0. If the I/O subsystem handles queued I/O efficiently, you can increase the maximum limit with the maximum async io configuration option. This in turn raises the values for I/O Batch Average Size, I/O Batch Maximum Size, and I/O Log Write Rate. Setting the maximum async io configuration option too high can overload the disk subsystem with writes.

If the returned value is high, you may have an opportunity to increase performance by improving disk access speeds. You may also want to review the queries to ensure they are not reading more information than required. For example, you may need to add an index to a table, which would prevent table scans.

SEE ALSO

MSSQLServer monitors: I/O Batch Average Size, I/O Batch Maximum Size, I/O Batch Write Rate, I/O Disk Writes, , I/O Outstanding Writes


I/O Disk Writes

I/O Disk Writes

DESCRIPTION

Reports the number of disk writes by the database server during the current monitoring interval. Use this monitor to assess UPDATE, INSERT, and DELETE activities on the server and to assess the load on and the throughput of the server.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IODiskWrites

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IODiskWrites’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IODiskWrites_32.log’ "<profilename>"

3–88 Version 1.3

I/O Disk Writes

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT


USAGE NOTES

The maximum number of pages written during a batch I/O operation can be configured. The default is eight in Microsoft SQL Server 6.5 and 32 in Microsoft SQL Server 7.0. If the I/O subsystem handles queued I/O efficiently, you can increase the maximum limit with the





Normal N/A None

Always N/A None


I/O Disk Writes

maximum async io configuration option. This in turn raises the values for I/O Batch Average Size, I/O Batch Maximum Size, and I/O Log Write Rate. Setting the maximum async io configuration option too high can overload the disk subsystem with writes.

If performance is adequate and the value returned is high, this is an indication of good throughput.

If performance is inadequate and the value returned is high, you may want to stagger UPDATE and INSERT activities to better balance the load.

SEE ALSO

MSSQLServer monitors: I/O Batch Average Size, I/O Batch Maximum Size, I/O Batch Write Rate, I/O Disk Reads, , I/O Outstanding Writes

3–90 Version 1.3

I/O Log Write Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
I/O Log Write Rate
DESCRIPTION

Version 6.5 only. Monitors the rate per second at which log pages are physically written to disk. Use this monitor to ensure changes made in cache are being written to disk promptly.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOLogWriteRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOLogWriteRate’ -t ’2 minutes’-c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOLogWriteRate_33.log’ "<profilename>"


I/O Log Write Rate




OUTPUT






Normal N/A None

Always N/A None

3–92 Version 1.3

I/O Log Write Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
For a transaction to be marked as complete, all changes must be physically logged to disk. If transactions are not completed, this means that overall transaction throughput can be limited by the disk drive on which the log is located. If the log is unable to write its entries out to disk, they remain in cache, which contributes to general performance degradation.

SEE ALSO

MSSQLServer monitors: I/O Outstanding Writes


I/O Outstanding Reads


DESCRIPTION

Version 6.5 only. Reports the number of physical reads pending. Use this statistic to evaluate how the I/O subsystem is performing.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOOutstandingReads

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOOutstandingReads’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOOutstandingReads_34.log’ "<profilename>"

3–94 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None



USAGE NOTES

A large number of outstanding reads over an extended time period can indicate that the I/O subsystem is a bottleneck and that changing to faster disks or a disk array would help performance. It also indicates degraded transaction throughput that may overload system resources, such as locks and cache.

SEE ALSO

MSSQLServer monitors: I/O Batch Average Size, I/O Batch Maximum Size, I/O Batch Write Rate, I/O Disk Writes, I/O Disk Reads, I/O Outstanding Writes

3–96 Version 1.3

I/O Outstanding Writes

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Version 6.5 only. Reports the number of physical writes pending. Use this statistic to evaluate how the I/O subsystem is performing.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOOutstandingWrites

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOOutstandingWrites’-t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f hbergin:C:\MSSQLServer\IOOutstandingWrites_35.log’ "<profilename>"






OUTPUT




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–98 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
A large number of outstanding writes over an extended time period can indicate that the I/O subsystem is a bottleneck; changing to faster disks or a disk array may help performance.

SEE ALSO

MSSQLServer monitors: I/O Batch Average Size, I/O Batch Maximum Size, I/O Batch Write Rate, I/O Disk Reads, I/O Disk Writes


I/O Page Read Rate

I/O Page Read Rate

DESCRIPTION

Version 6.5 only. Monitors the physical page read rate per second across all databases. Use this monitor to assess the performance on standard queries.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOPageReadRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOPageReadRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOPageReadRate_36.log’ "<profilename>"

3–100 Version 1.3

I/O Page Read Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


I/O Page Read Rate

USAGE NOTES

Page reads are slower than cache hits, so they reduce overall performance. When this monitor returns high values, you should attempt to reduce excessive page reads by one or more of the following strategies:

■ Increase data cache size.

■ Use intelligent indexes.

■ Rewrite queries to be more efficient.

■ Revisit the database schema and check for efficiency.

Low values may be a sign of a bottleneck in I/O throughput.

SEE ALSO

None

3–102 Version 1.3

I/O Single Page Write Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Version 6.5 only. Monitors the rate per second at which single page writes are performed by logging and cache flushes as opposed to batch writes that are carried out during checkpoints. Use this monitor to check the efficiency of I/O writes and the LazyWriter.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOSinglePageWriteRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOSinglePageWriteRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOSinglePageWriteRate_37.log’ "<profilename>"



, not

wide

ol




OUTPUT


USAGE NOTES

This monitor’s page read rates refer to logging and cache flushesto LazyWrite and checkpoint operations, which use batch I/O.

Single-page writes are generally expensive, as opposed to batch-I/O writes. Reducing single-page-write activity is important for optimal tuning. One way to do this is to ensure the free buffer po



Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–104 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
does not run out of free buffers. If it does, single-page writes occur when waiting for an unused cache buffer to flush. See the monitors.
Note: For an overall picture of system performance, you may need to look at a number of monitors, such as the network, I/O, and cache monitors.

The following are common solutions to a large number of single page reads or writes:

■ Increase the cache

■ Improve the indexes

■ Make queries more efficient

■ Change the database design

SEE ALSO

MSSQLServer monitors: Cache Average Free Page Scan, Cache Configured Free Buffers Percent Used, Cache Maximum Free Page Scan, Cache Number of Free Buffers


I/O Transaction Rate


DESCRIPTION

Version 6.5 only. Monitors the execution rate per second of Transact-SQL command batches. Use this monitor to check if the database server is completing its list of transactions efficiently.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOTransactionRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IOTransactionRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOTransactionRate_39.log’ "<profilename>"

3–106 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 50 transactions per second and an average of 10 transactions per log record.


OUTPUT




Severe Less than 4 None

Warning Less then 5 None

Normal N/A None

Always N/A None



USAGE NOTES

This returned value is affected by general system performance and resource constraints, such as I/O, number of users, cache size, and complexity of requests. A high transaction rate indicates good throughput.

Note: For an overall picture of system performance, you may need to look at a number of monitors, such as the network, I/O, and cache monitors.

It is important to note that this rate is expressed as command batches per second, not transactions per second. Look at the I/O Transactions Per Log Record to get an idea of the average number of transactions per batch.

SEE ALSO

MSSQLServer monitors: I/O Transactions Per Log Record

3–108 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Version 6.5 only. Reports the number of transactions packed into a log record before the log record was written to disk. Use this monitor to see if the log write sleep configuration option is set correctly.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IOTransactionsPerLogRecord

CLI EXAMPLEwaddmon ’MSSQLServer’ ’IOTransactionsPerLogRecord’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IOTransactionsPerLogRecord_38.log’ "<profilename>"




The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target of 100 transactions per minute, assuming 10 transactions per log record and 10 log records being written to disk per minute.


OUTPUT




Severe Less than 5 None

Warning Less than 10 None

Normal N/A None

Always N/A None

3–110 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
Because log records must be physically written to disk before a transaction is considered complete, the rate at which log writes are completed is the ultimate limit on system throughput. If the log writes from many transactions are packed into a single physical write, throughput can be improved. It may be possible to increase the number of transactions per log record by adjusting the LOGWRITE SLEEP configuration option.

If the I/O Transaction Rate monitor is high, you may want to ensure that the optimal amount of transactions are being grouped into a single log record.

SEE ALSO

MSSQLServer monitors: I/O Transaction Rate


Intent Locks Exclusive


DESCRIPTION

Reports the current number of exclusive intent locks. Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IntentLocksExclusive

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IntentLocksExclusive’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IntentLocksExclusive_24.log’ "<profilename>"

3–112 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

An intent lock indicates the intention to acquire a shared or exclusive lock on a data page. Intent locks are used to let high-level lock granules, such as table locks, know that other locks, such as page locks, intend to place locks at a lower level in the lock hierarchy.

It may be more efficient to replace a large number of page locks on a single table with a single table lock. You can use the LE threshold maximum, LE threshold minimum, or LE threshold % configuration options to control the point at which a large number of page locks are upgraded to a table lock. Efficiency is a tradeoff with concurrency, however. If LE threshold values are set too low, transaction throughput could fall due to waits on table locks. If LE thresholds are correctly configured, they may be overridden in queries that use the HOLDLOCK feature.

If you are looking particularly at LE (lock escalation) options, look at the Intent, Page, and Table Lock monitors. To understand how many intent locks there are in relation to total locks, use the Total Locks monitors.

For more information on exclusive intent locks, see the Microsoft SQL Server Books On-line.

Note: Lock escalation configuration options are not available in Microsoft SQL Server Version 7.0.

SEE ALSO

MSSQLServer monitors: Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining

3–114 Version 1.3

Intent Locks Shared

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Intent Locks Shared
DESCRIPTION

Reports the current number of shared intent locks. (For more information on intent locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IntentLocksShared

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IntentLocksShared’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’-c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IntentLocksShared_25.log’ "<profilename>"


Intent Locks Shared




OUTPUT






Normal N/A None

Always N/A None

3–116 Version 1.3

Intent Locks Shared

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES

It may be more efficient to replace a large number of page locks on a single table with a single table lock. You can use the LE threshold maximum, LE threshold minimum, or LE threshold % configuration options to control the point at which a large number of page locks are upgraded to a table lock. Efficiency is a tradeoff with concurrency, however. If LE threshold values are set too low, transaction throughput could fall due to waits on table locks. If these are correctly configured, they may be overridden in queries that use the HOLDLOCK feature.


SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Total, Page Locks Exclusive, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining


Intent Locks Total

Intent Locks Total

DESCRIPTION

Reports the current number of all intent locks. (For more information on exclusive intent locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

IntentLocksTotal

CLI EXAMPLE

waddmon ’MSSQLServer’ ’IntentLocksTotal’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\IntentLocksTotal_26.log’ "<profilename>"

3–118 Version 1.3

Intent Locks Total

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


Intent Locks Total

USAGE NOTES


It may be more efficient to replace a large number of page locks on a single table with a single table lock. You can use the LE threshold maximum, LE threshold minimum, or LE threshold % configuration options to control the point at which a large number of page locks are upgraded to a table lock. Efficiency is a tradeoff with concurrency, however. If LE threshold values are set too low, transaction throughput could fall due to waits on table locks. If these are correctly configured, they may be overridden in queries that use the HOLDLOCK feature.


SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Page Locks Exclusive, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining

3–120 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Examines the percentage of log space used by each database on the database server. Use this monitor to find out which database on the server has used the largest percentage of its allocated log space and what that percentage value is. You also can use this monitor as an alert for when you need to extend the size of or truncate a log.

When used with Microsoft SQL Server Version 6.5, this monitor may return a value higher than 100%. The value is based on the size of the syslogs table compared to the configured log size. The Microsoft SQL Server tools never return a value for the log space used percentage that is higher than 100%. Microsoft SQL Server allows the syslogs table to grow beyond the configured log size. To be safe, you should set a response action to truncate the log before this monitor reaches 100%.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

LogSpacePercentUsedSRVR

CLI EXAMPLE

waddmon ’MSSQLServer’ ’LogSpacePercentUsedSRVR’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\LogSpacePercentUsed_40.log’ "<profilename>"






OUTPUT


USAGE NOTES

If the log runs out of space, you can no longer use the database. You can use the database versions of this monitor to further refine which databases have a significant amount of log activity. Although the database identified with this monitor may have the highest value, if it is a static database it may not be the one that needs attention. A





Normal N/A None

Always N/A None

3–122 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

t, this g

me ack CLI

volatile database with a smaller percentage of used log space may fill up more rapidly.

When a database’s log and data share the same device fragmenmonitor returns a value of 0. To correct the problem of the log fillinup on such a database, use the NT Event Logging task to configure the following error to be forwarded to the Application log in the Windows NT event log:

ERROR 1105Can’t allocate space for object ’%.*s’ in database ’%.*s’ because the ’%.*s’ segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.

Once you do this, use the NT Application Log monitor to search the log for this particular error and set the response action in the Run Program field to the following:

wruntask -t DumpTransactionLog-l "MSSQLManagerTasks"-h @MSSQLDatabase:msdb@hbergin@hbergin-a DumpOption=NoLog

For databases that do not have the logs and data sharing the sadevice fragment, configure the response action to truncate or to bup and truncate the log when it reaches a specified level; use thesyntax for the Dump Transaction Log task in the Run Program field.

SEE ALSO

MSSQLServer monitors: NT Application Log

MSSQLDatabase monitors: Log Space Used, Log Space Percent Used (Database)

Tasks: Dump Transaction Log, NT Event Logging


Network Read Rate

Network Read Rate

DESCRIPTION

Monitors the rate at which tabular data stream (TDS) packets are read from the network, in packets per second. This statistic is an indicator of network throughput. When this statistic is high, it indicates heavy network traffic.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

NetworkReadRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’NetworkReadRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\NetworkReadRate_41.log’ "<profilename>"

3–124 Version 1.3

Network Read Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. Assumptions: 10 Mbps network and a packet size of 4096.


OUTPUT






Normal N/A None

Always N/A None


Network Read Rate

USAGE NOTES

This statistic is best used in conjunction with the other network statistics. See “NT Performance Monitors” in Appendix A, “Monitoring Collection Information,” of the Tivoli Manager for Microsoft SQL Server User’s Guide.

SEE ALSO

MSSQLServer monitors: Network Write Rate

3–126 Version 1.3

Network Write Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Network Write Rate
DESCRIPTION

Monitors the rate at which tabular data stream (TDS) packets are written to the network, in packets per second. This statistic is an indicator of network throughput. When this statistic is high, it indicates heavy network traffic.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

NetworkWriteRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’NetworkWriteRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\NetworkWriteRate_42.log’ "<profilename>"


Network Write Rate


The following table shows suggested threshold values for severity levels. The following values are based on a 10 Mbps network and a packet size of 4096.


OUTPUT






Normal N/A None

Always N/A None

3–128 Version 1.3

Network Write Rate

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

USAGE NOTES

This statistic is best used with other network statistics. See “NT Performance Monitors” in Appendix A, “Monitoring Collection Information,” of the Tivoli Manager for Microsoft SQL Server User’sGuide.

SEE ALSO

MSSQLServer monitors: Network Read Rate


NT Application Log

NT Application Log

DESCRIPTION

Searches the Application log in the Windows NT event log for Microsoft SQL Server errors only; it does not search for messages. It returns the number of entries matching any combination of the following criteria:

■ Error number

■ Error severity

■ Error text matching string

Use this monitor to check on errors that are specific to your application or site.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers



3–130 Version 1.3

NT Application Log

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

Error Number

The error number to search for.

Min. Severity Level

The lower bound of the range of error severities to search for. It must be less than or equal to Max. Severity Level

Max. Severity Level

The upper bound of the range of error severities to search for. It must be greater than or equal to Min. Severity Level.

Error Text A string to search for in the error text of the log.


NT Application Log

CLI SYNTAX

NTApplicationLog

–a <Error_number >

–a <Min_severity_level >

–a <Max_severity_level >

–a <Error_text>


<Error_number >

The error number to search for.

<Min_severity_level >

The lower bound of the range of error severities to search for. It must be less than or equal to <Max_severity_level>.

<Max_severity_level>

The upper bound of the range of error severities to search for. It must be greater than or equal to <Min_severity_level>.

<Error_text> The string to search for in the error text of the log.

CLI EXAMPLE

waddmon ’MSSQLServer’ ’NTApplicationLog’ -a ’50000’ -a ’10’ -a ’1000’ -a ’Error’ -t ’1 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\NTApplicationLog_43.log’ "<profilename>"

3–132 Version 1.3

NT Application Log

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of flagging errors with a severity level of 19 and above (FATAL).


OUTPUT




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None


NT Application Log

USAGE NOTES

This monitor returns errors from Microsoft SQL Server, not other applications. It returns only errors that have occurred since the last time this monitor was run.

SEE ALSO

MSSQLServer monitors: NT Application Log Age, NT Application Log Percent Full

3–134 Version 1.3

NT Application Log Age

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Looks at the date of the oldest entry in the Application log in the Windows NT event log, which indicates the period for which information is being held. Use this monitor to determine if this period matches the configurations for the Application log.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

NTApplicationLogAge

CLI EXAMPLE

waddmon ’MSSQLServer’ ’NTApplicationLogAge’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin: C:\MSSQLServer\NTApplicationLogAge.log’ "< profilename>"




The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target history being kept in the Applications log of the Windows NT event log for at least one week (7 * 24 * 60 minutes).


OUTPUT




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–136 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
If the log is circular, then the oldest events are overwritten to make room for new events. In this situation, it is good to know what events are being cleared.

If the log is not circular, then it is helpful to know if its size is correctly configured. If the log keeps events that are too old to be of interest, you could reduce the log size and free resources. If the history of events is not adequate, you can increase the log size.

Tracking the size and age of the log can help in determining its most efficient configuration.

SEE ALSO

MSSQLServer monitors: NT Application Log Percent Full, NT Application Log




DESCRIPTION

Returns the percentage of space used in the Application log in the Windows NT event log. Use this monitor to alert you that you are running out of log space. This enables you to clear out and archive the log.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

NTApplicationLogPercentFull

CLI EXAMPLE

waddmon ’MSSQLServer’ ’NTApplicationLogPercentFull’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’bergin: C:\MSSQLServer\NTApplicationLogPercentFull.log’ "< profilename>"

3–138 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

If the log is circular, then the oldest events are overwritten to make room for new events. In this situation, it is good to know that events are about to be cleared. This will give you time to archive the log.

If the log is not circular, it is helpful to know if its size is correctly configured. If the log keeps events that are too old to be of interest, you could reduce the log size and free resources. If the history of events is not adequate, you can increase the log size. This monitor can help in establishing how often you need to archive the log, if you do not want it to take up too many resources, but do not want to lose events either.

Tracking the size and age of the log can help in determining its most efficient configuration.

SEE ALSO

MSSQLServer monitors: NT Application Log Age, NT Application Log

3–140 Version 1.3

Number of Blocked Processes

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the total number of processes that have requested a lock but are waiting for a competing lock to be released by another process. Use this monitor to check which processes are being held up through lock contention rather than hardware performance issues.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

NumberOfBlockedProcesses

CLI EXAMPLEwaddmon ’MSSQLServer’ ’NumberOfBlockedProcesses’-t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\Server\NumberOfBlockedProcesses.log’ "<profilename>"




The following table shows suggested thresholds for severity levels.


OUTPUT


USAGE NOTES

Lock contention can seriously affect transaction throughput. You can minimize lock contention by keeping transactions as small as possible. You may also want to stagger competing transactions or alter the order in which they run.

SEE ALSO

MSSQLServer monitors: Number of Deadlocks





Normal N/A None

Always N/A None

3–142 Version 1.3

Number of Deadlocks

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Number of Deadlocks
DESCRIPTION

Reports the number of deadlocks that have occurred during the current monitoring interval. Use this monitor to alert you to deadlocks occurring; this ensures that you do not lose any transactions.

Note: In order for this monitor to work, Microsoft SQL Server Error 1205 must be logged to the Windows NT event log. See the NT Event Logging task.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

NumberOfDeadlocks

CLI EXAMPLE

waddmon ’MSSQLServer’ ’NumberOfDeadlocks’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\NumberOfDeadlocks_46.log’ "<profilename>"


Number of Deadlocks


The following table shows suggested thresholds for severity levels.


OUTPUT




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–144 Version 1.3

Number of Deadlocks

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
A deadlock occurs when two processes both wait on locks that have been taken out by the other process. This creates a stalemate; one process is designated as the victim, and the system kills it. You can minimize the number of deadlocks by staggering competing transactions or by altering the order in which they run. You may want to rewrite the queries that cause the deadlocks.

You may also want to make certain that you code applications to resubmit transactions that are killed as a result of a deadlock.

SEE ALSO

MSSQLServer monitors: Number of Blocked Processes

Tasks: NT Event Logging



you ase


DESCRIPTION

Reports the age of the oldest open transaction at a database server. The monitor examines each database’s transaction log to determinethe oldest transaction. Use this monitor to determine up to whichpoint in time a transaction log can be truncated and backed up. If want the information for a particular database, then use the databversion of this monitor

AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


None

CLI SYNTAX

OldestOpenTransactionSRVR

CLI EXAMPLE

waddmon ’MSSQLServer’ ’OldestOpenTransactionSRVR’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\OldestOpenTransaction_48.log’ "<profilename>"

3–146 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The following response levels are based on a 15-minute data loss window.


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

If you are unable to back up the transaction log to the current point in time and you rely on the transaction log for a RESTORE, you may lose any transactions that occurred after the timestamp on the oldest open transaction.

SEE ALSO

MSSQLDatabase monitors: Oldest Open Transaction (Database)

3–148 Version 1.3

Page Locks Exclusive

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the current number of exclusive page locks. (For more information on exclusive page locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

PageLocksExclusive

CLI EXAMPLE

waddmon ’MSSQLServer’ ’PageLocksExclusive’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’-c ’always’-f ’hbergin:C:\MSSQLServer\PageLocksExclusive_49.log’ "<profilename>"






OUTPUT






Normal N/A None

Always N/A None

3–150 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
It may be more efficient to replace a large number of page locks on a single table with a single table lock. A large number of page locks may indicate that the LE threshold maximum, LE threshold minimum, or LE threshold % configuration options are not optimal. If these are correctly configured, they may be overridden in queries that use the HOLDLOCK feature.

If you are looking particularly at LE (lock escalation) options, look at the Intent, Page, and Table Lock monitors. To understand how many page locks there are in relation to total locks, use the Total Locks monitors.

SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining


Page Locks Shared

Page Locks Shared

DESCRIPTION

Reports the current number of shared page locks. (For more information on shared page locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

PageLocksShared

CLI EXAMPLE

waddmon ’MSSQLServer’ ’PageLocksShared’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\PageLocksShared_50.log’ "<profilename>"

3–152 Version 1.3

Page Locks Shared

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


Page Locks Shared

USAGE NOTES


If you are looking particularly at LE (lock escalation) options, look at the Intent, Page, and Table Lock monitors. To understand how many page locks there are in relation to total locks, use the Total Locks monitors

SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared,Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining

3–154 Version 1.3

Page Locks Total

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Page Locks Total
DESCRIPTION

Reports the current number of all page locks. (For more information on total page locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks that are active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

PageLocksTotal

CLI EXAMPLE

waddmon ’MSSQLServer’ ’PageLocksTotal’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\PageLocksTotal_51.log’ "<profilename>"


Page Locks Total




OUTPUT






Normal N/A None

Always N/A None

3–156 Version 1.3

Page Locks Total

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES


SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining


Page Locks Update

Page Locks Update

DESCRIPTION

Reports the number of current update page locks. Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

PageLocksUpdate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’PageLocksUpdate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\PageLocksUpdate_52.log’ "<profilename>"

3–158 Version 1.3

Page Locks Update

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


Page Locks Update

USAGE NOTES



SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining

3–160 Version 1.3

Procedure Buffers Active

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the percentage of slots with a procedure that is currently executing. Use this monitor to see how much of the cache these procedures use in relation to the cache size as a whole. This allows you to determine if the procedure cache configuration option is optimal or if you need to amend the memory configuration option.

Note: In Microsoft SQL Server Version 7.0, you can no longer configure the procedure cache size. It is sized automatically.

AUTHORIZATION ROLE

mssqlserver_monitor


■ Microsoft SQL Server 6.5: any


TARGET ENDPOINT

database servers


None

CLI SYNTAX

ProcedureBuffersActive

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ProcedureBuffersActive’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ProcedureBuffersActive_53.log’ "<profilename>"






OUTPUT






Normal N/A None

Always N/A None

3–162 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
To make a complete assessment of whether or not the procedure cache configuration option is optimal, you may want to run the other Procedure monitors. You can compare the result of this monitor to the Procedure Buffers Used monitor to show the amount of cache being taken up by compiled and stored procedures as opposed to executing stored procedures.

When you use the Procedure monitors, keep the following in mind:

Procedure Buffers Used is the percentage of slots that have a procedure in them.

Procedure Buffers Active is the percentage of slots that have a procedure in them which is currently executing.

Procedure Buffers Total is the total number of slots.

Procedure Cache Size is the total size of the procedure cache.

Procedure Cache Used is the percentage of the procedure cache which has procedures in it.

Procedure Cache Active is the percentage of the procedure cache that has currently executing procedures in it.

SEE ALSO

MSSQLServer monitors: Procedure Buffers Total, Procedure Buffers Used, Procedure Cache Active, , Procedure Cache Used


Procedure Buffers Total


DESCRIPTION

Reports the number of procedure buffers that are in the procedure cache. This number is a fixed number based on the procedure cache that is allocated. Use this monitor to see how much of the cache currently executing procedures use in relation to the cache size as a whole. This allows you to determine if the procedure cache configuration option is optimal or if you need to amend the memory configuration option.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


None

CLI SYNTAX

ProcedureBuffersTotal

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ProcedureBuffersTotal’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ProcedureBuffersTotal_54.log’ "<profilename>"

3–164 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target total of 2000 procedure buffers for the server.


OUTPUT




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None



USAGE NOTES

To make a complete assessment of whether or not the procedure cache configuration option is optimal, you may want to run the other Procedure monitors. You can compare the result of this monitor to the Procedure Buffers Used monitor to show the amount of cache being taken up by compiled, and stored procedures as opposed to executing stored procedures.








SEE ALSO

MSSQLServer monitors: Procedure Buffers Active, Procedure Buffers Used, Procedure Cache Active, , Procedure Cache Used

3–166 Version 1.3

Procedure Buffers Used

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the percentage of slots that have a procedure in them. A procedure buffer is considered used when it is associated with a procedure cache entry. A used procedure buffer may or may not be active.

Use this monitor to see how much of the cache is being used by currently compiled procedures in relation to the cache size as a whole; this helps to determine if the procedure cache and the memory configuration options are optimal.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


None

CLI SYNTAX

ProcedureBuffersUsed



CLI EXAMPLE

waddmon ’MSSQLServer’ ’ProcedureBuffersUsed’ -t ’2 minutes’ -c ’critical’ -c ’severe’-c ’warning’-c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ProcedureBuffersUsed_55.log’ "<profilename>"




OUTPUT






Normal N/A None

Always N/A None

3–168 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
To make a complete assessment of whether or not the procedure cache configuration option is optimal, you may want to run the other Procedure monitors. You can compare the result of this monitor to the Procedure Buffers Active monitor to show the amount of cache being taken up by compiled, and stored procedures as opposed to executing stored procedures.






Procedure Cache Used is the percentage of the procedure cache that has procedures in it.


SEE ALSO

MSSQLServer monitors: Procedure Buffers Active, Procedure Buffers Total, Procedure Cache Active, , Procedure Cache Used


Procedure Cache Active


DESCRIPTION

Reports the percentage of the procedure cache that has currently executing procedures in it. Use this monitor to see how much of the cache these procedures use in relation to the cache size as a whole. This allows you to evaluate if the procedure cache and the memory configuration options are optimal.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


None

CLI SYNTAX

ProcedureCacheActive

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ProcedureCacheActive’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLServer\ProcedureCacheActive_56.log’ "<profilename>"

3–170 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

To make a complete assessment of the procedure cache configuration option, you may want to run the other Procedure monitors; you can compare this monitor to the Procedure Cache Used monitor to show the amount of cache used by compiled, and stored procedures as opposed to executing stored procedures.








SEE ALSO

MSSQLServer monitors: Procedure Buffers Active, Procedure Buffers Total, Procedure Buffers Used, , Procedure Cache Used

3–172 Version 1.3

Procedure Cache Size

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Monitors the total size of the procedure cache in pages. The size of the procedure cache can fluctuate depending on the activity of other database server processes that may require procedure cache slots, such as query plans.

Use the monitor to see the current size of the procedure cache. Use it to evaluate the procedure cache and the memory configuration options.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


None

CLI SYNTAX

ProcedureCacheSize



CLI EXAMPLE

waddmon ’MSSQLServer’ ’ProcedureCacheSize’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\Server\ProcedureCacheSize.log’ "< profilename>"


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target total of 2000 pages for the server.




Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–174 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
OUTPUT

USAGE NOTES

To assess whether your procedure cache configuration is optimal, you may want to run the other Procedure monitors; you can compare this monitor to the Procedure Buffers Total monitor to compare the number of buffers with the size of the cache.






Procedure Cache Used is the percentage of the procedure cache that has procedures in it.


SEE ALSO

MSSQLServer monitors: Procedure Buffers Active, Procedure Buffers Total, Procedure Buffers Used, Procedure Cache Active, Procedure Cache Used


Procedure Cache Used


DESCRIPTION

Reports the percentage of the procedure cache that has procedures in it. Use this monitor to see how much of the cache currently executing procedures use in relation to the cache size as a whole. This allows you to evaluate the procedure cache and the memory configuration options.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers


None

CLI SYNTAX

ProcedureCacheUsed

None

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ProcedureCacheUsed’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\ProcedureCacheUsed_57.log’ "< profilename>"

3–176 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

To make a complete assessment of if the procedure cache configuration option is optimal, you may want to run the other Procedure monitors; you can compare this monitor to the Procedure Cache Active monitor to show the amount of cache being taken up by compiled and stored procedures as opposed to executing stored procedures.








SEE ALSO

MSSQLServer monitors: Procedure Buffers Active, Procedure Buffers Total, Procedure Buffers Used, Procedure Cache Active,

3–178 Version 1.3

RA Effectiveness

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
RA Effectiveness
DESCRIPTION

Version 6.5 only. Returns the ratio of pages fetched into cache to pages found in cache as a percentage. For example, if 60 pages are fetched and 100 pages are found, then the percentage returned by this monitor will be 60. The lower the percentage returned by this monitor, the less effective RA is. For RA to be considered effective, more pages should be read into cache than are found in cache, so monitor values of 100% or less show RA to be ineffective.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

RAEffectiveness

CLI EXAMPLE

waddmon ’MSSQLServer’ ’RAEffectiveness’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\Server\RAEffectiveness_58.log’ "< profilename>"


RA Effectiveness




OUTPUT






Normal N/A None

Always N/A None

3–180 Version 1.3

RA Effectiveness

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
If RA Pages Fetched into Cache Per Second is high and RA Pages Found in Cache Per Second is low, then read-ahead is effective. The less effective read-ahead is, the closer the two counters become. If RA Pages Fetched into Cache Per Second is less than RA Pages Found in Cache Per Second then read-ahead is simply overhead and is not helping scan times.

Read-ahead configuration options control parallel data scan capabilities, which enable asynchronous read-ahead of data when Microsoft SQL Server determines that pages are being retrieved in sequential order. With read-ahead, separate background threads are used to pre-fetch pages for a given result set. Read-ahead pre-fetches are configured based on extents.

SEE ALSO

MSSQLServer monitors: RA Pages Fetched into Cache Per Second, RA Pages Found in Cache Per Second




DESCRIPTION

Version 6.5 only. Reports the rate at which pages are being pre-fetched into the cache by the Read Ahead Manager. If you use this source in conjunction with RA Pages Found in Cache Per Second, you can determine the effectiveness of the Read Ahead Manager.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

RAPagesFetchedIntoCachePerSecond

CLI EXAMPLEwaddmon ’MSSQLServer’ ’RAPagesFetchedIntoCachePerSecond’-t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’bergin: C:\MSSQLServer\RAPagesFetchedIntoCachePerSecondlog"< profilename>"

3–182 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 50 pages per second. This value is most useful when compared to the RA Pages Found in Cache Per Second monitor. This value should be higher for optimal performance.


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES



SEE ALSO

MSSQLServer monitors: RA Effectiveness, RA Pages Found in Cache Per Second

3–184 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Version 6.5 only. Reports the rate at which pages being pre-fetched into the cache by the Read Ahead Manager were already found to be there. This value should be low in comparison to RA PAGES FETCHED INTO CACHE PER SECOND. Use this monitor to determine the effectiveness of the Read Ahead Manager.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

RAPagesFoundInCachePerSecond

CLI EXAMPLE

waddmon ’MSSQLServer’ ’RAPagesFoundInCachePerSecond’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’ber1: C:\MSSQLServer\RAPagesFoundInCachePerSecond.log’ "< profilename>"




The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 50 pages per second. This value is most useful when compared to the RA Pages Fetched into Cache Per Second monitor. This value should be lower for optimal performance.


OUTPUT






Normal N/A None

Always N/A None

3–186 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES


SEE ALSO

MSSQLServer monitors: RA Effectiveness, RA Pages Fetched into Cache Per Second


RA Physical Read Rate

d er

see


DESCRIPTION

Version 6.5 only. Reports the Read Ahead Manager’s physical rearate per second. The Read Ahead Manager reads eight pages prequest. This source provides a general indication of how busy read-ahead is in terms of actual physical I/O. Use this monitor to if the Read Ahead Manager is operating efficiently, or if I/O operations affect its performance.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

RAPhysicalReadRate

CLI EXAMPLE

waddmon ’MSSQLServer’ ’RAPhysicalReadRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\RAPhysicalReadRate_61.log’ "< profilename>"

3–188 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 50 pages per second. The RA Manager needs to issue 6.25 physical reads per second.


OUTPUT



Critical Greater than 8.75 Send MSSQL Sentry notice

Severe Greater than 7.5 Send MSSQL Sentry notice

Warning Greater than 6.25 Send MSSQL Sentry notice

Normal N/A None

Always N/A None



USAGE NOTES

If the returned value is high, you may have an opportunity to increase performance by improving disk access speeds. You may also want to review queries to ensure they are not reading more information than required. For example, you may need to rebuild an index to reduce fragmentation, which improves table scans.

You also may want to use the monitor to see if the read-ahead rate is affected by I/O bottlenecks.

SEE ALSO

MSSQLServer monitors: , RA Pages Fetched into Cache Per Second, RA Pages Found in Cache Per Second, RA Slots Used

3–190 Version 1.3

RA Slots Used

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
RA Slots Used
DESCRIPTION

Version 6.5 only. Reports the total number of slots in use for read-ahead. This can help you determine how close the number of slots in use is getting to the number of slots configured. It also indicates the number of queries using read-ahead at any given time. If this counter hits the maximum slots ceiling, you may need to increase the number of RA slots per thread configuration option (Microsoft SQL Server Version 6.5 only).

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

RASlotsUsed

CLI EXAMPLE

waddmon ’MSSQLServer’ ’RASlotsUsed’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\RASlotsUsed_62.log’ "< profilename>"


RA Slots Used


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target total of 15 slots for the server: five RA slots per thread on three RA worker threads.


OUTPUT


USAGE NOTES

None

SEE ALSO

None


Critical More than 13.5 Send MSSQL Sentry notice


Warning More than 10.5 Send MSSQL Sentry notice

Normal N/A None

Always N/A None

3–192 Version 1.3

Service State

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Service State
DESCRIPTION

Reports the state of the following services: MSSQLServer, MSDTC, and SQLExecutive (renamed SQLServerAgent in Version 7.0). The MSSQLServer service may have three states: STOPPED, PAUSED, STARTED. The other two services have two states: STOPPED or STARTED. Use this monitor to ensure server availability and that the replication process and scheduled SQL tasks (jobs in 7.0) are running. This monitor does not need a connection to the SQL Server; it reports accurately even if no connection can be established.

The monitor only returns one TRUE or FALSE value that relates to the state of all specified services.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

Managed Node


Service State



Monitor SQLServer Service

Yes means check if this service is running. No means do not check if it is running.

Monitor SQLExecutive/SQLServerAgent Service

Yes means check if this service is running. No means do not check if it is running. With Microsoft SQL

3–194 Version 1.3

Service State

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Server Version 7.0, this option checks the SQLServerAgent service.
Monitor MSDTC Service

Yes means check if this service is running. No means do not check if it is running.

CLI SYNTAX

ServiceState

–a <MSSQLServer >

–a <SQLExecutive/SQLServerAgent>

–a <MSDTC>


<MSSQLServer>

YES means check if this service is running. NO means do not check if it is running. (Yes, yes, No, and no are also acceptable forms.)

<SQLExecutive/SQLServerAgent>

YES means check if this service is running. NO means do not check if it is running. (Yes, yes, No, and no are also acceptable forms.) With Microsoft SQL Server Version 6.5, this options checks the SQLExecutive service. With Microsoft SQL Server Version 7.0, this option checks the SQLServerAgent service.

<MSDTC> YES means check if this service is running. NO means do not check if it is running. (Yes, yes, No, and no are also acceptable forms.)


Service State

CLI EXAMPLE

waddmon ’MSSQLServer’ ’ServiceState’ -a ’Yes’ -a ’Yes’ -a ’Yes’-t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\ServiceState_63.log’ "< profilename>"





Critical False Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–196 Version 1.3

Service State

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
OUTPUT

USAGE NOTES

The MSSQLServer service must be running for any operations to be carried out on the server or its databases. The server may have stopped due to a user request or an internal error. It may also have stopped if the NT computer was rebooted and the service is not automatically set to restart at boot time. This monitor helps identify the problem by alerting the DBA. You also can configure an automatic response to try to start the service again. This reduces the amount of time the server is unavailable to users and applications. If the server is paused, then it cannot accept new logons, which causes an availability issue.

SQLExecutive (SQLServerAgent in Version 7.0) must be running for SQL scheduled tasks (jobs in 7.0) and replication to operate. This monitor helps to identify a replication bottleneck quickly and to avoid a backlog of replicated transactions or an unacceptable delay in subscribers getting published information. It also alerts you when scheduled tasks are unable to run.

MSDTC must be running in order for distributed transactions to be coordinated correctly.


Service State

SEE ALSO

MSSQLServer monitors: Database Status (Server), SQLServerAgent Failed Jobs, SQL Server State

Tasks: Database Status (Database)

3–198 Version 1.3

SQL Server State

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
SQL Server State
DESCRIPTION

Checks that the database server is available and that Tivoli Manager for Microsoft SQL Server can connect to it. This monitor lets you know if Tivoli Manager for Microsoft SQL Server cannot access the database server even though other applications can.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

SQLServerState

CLI EXAMPLE

waddmon ’MSSQLServer’ ’SQLServerState’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\SQLServerState_65.log’ "< profilename>"


SQL Server State




OUTPUT



Critical UNAVAILABLE Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

3–200 Version 1.3

SQL Server State

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
If Tivoli tasks or monitors are failing, Tivoli Manager for Microsoft SQL Server may be unable to access the database server, even though other applications can. This situation may be temporary; the next time you run this monitor, it could return a successful connection value with no intervention on your part.

Things to check:

■ Are all user connections in use?

■ Is the server in single user mode?

■ Is the server paused?

■ Are login attempts timing out? (network, SQL Server busy)

■ Is the Tivoli login correct?

SEE ALSO

MSSQLServer monitors: Database Status (Server), Service State



SQLServerAgent Failed Jobs


DESCRIPTION

Reports any jobs run by the SQLServerAgent service (or SQLExecutive service in Version 6.5) that have failed in the last monitoring interval. The first time you run this monitor, it returns 0. The next time you run it, it returns the total number of SQLServerAgent failed jobs found in the system history tables since the first run. These jobs include replication and user-defined jobs, such as maintenance or backup tasks. Use this monitor to alert you when scheduled tasks have failed.

Note: The SQLExecutive service in Version 6.5 was renamed SQLServerAgent in Version 7.0, and tasks were renamed jobs.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

SQLServerAgentFailedJobs

CLI EXAMPLE

waddmon ’MSSQLServer’ ’SQLServerAgentFailedJobs’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\SQLServerAgentFailedJobs.log’ "< profilename>"

3–202 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n



Critical Greater then 0 Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None



OUTPUT


USAGE NOTES

This monitor helps ensure that the replication processes are functioning. You may also want to be alerted to failed backups to minimize data loss.

SEE ALSO

MSSQLServer monitors: SQLServerAgent Failed Jobs

3–204 Version 1.3

Table Locks Exclusive

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the number of current exclusive table locks. (For more information on table locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TableLocksExclusive

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TableLocksExclusive’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TableLocksExclusive_66.log’ "< profilename>"






OUTPUT






Normal N/A None

Always N/A None

3–206 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES
A large number of page locks may indicate that the lock escalation configuration option is not optimal. It may be more efficient to replace a large number of page locks on a single table with a single table lock.

Note: Lock escalation can be manually adjusted only in Microsoft SQL Server Version 6.5.

If you are looking at lock escalation, use the Page Locks and Table Locks monitors. To understand how many table locks there are in relation to total locks, use the Total Locks monitors.

SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining


Table Locks Shared

Table Locks Shared

DESCRIPTION

Reports the number of current shared table locks. (For more information on table locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TableLocksShared

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TableLocksShared’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TableLocksShared_67.log’ "< profilename>"

3–208 Version 1.3

Table Locks Shared

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


Table Locks Shared

USAGE NOTES




SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining

3–210 Version 1.3

Table Locks Total

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
Table Locks Total
DESCRIPTION

Reports the total number of current table locks. (For more information on table locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TableLocksTotal

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TableLocksTotal’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TableLocksTotal_68.log’ "< profilename>"


Table Locks Total




OUTPUT






Normal N/A None

Always N/A None

3–212 Version 1.3

Table Locks Total

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES



SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining


Total Blocking Locks


DESCRIPTION

Reports the total number of current locks blocking other processes. A blocking lock must be released before other processes requesting competing locks can progress. (For more information on locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of blocking locks active during server activity. Use this monitor in conjunction with the Number of Blocked Processes monitor to determine when a small number of locks is blocking a large number of processes or vice versa. This monitor also can indicate that processes are being held up through lock contention rather than hardware performance issues.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TotalBlockingLocks

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TotalBlockingLocks’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TotalBlockingLocks_69.log’ "< profilename>"

3–214 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

Lock contention can seriously affect transaction throughput. You can minimize lock contention by keeping transactions as small as possible. You may want to stagger competing transactions or alter the order in which they are run.

SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used, Total Locks Remaining

3–216 Version 1.3

Total Exclusive Locks

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the total number of current exclusive locks. (For more information on locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TotalExclusiveLocks

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TotalExclusiveLocks’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’-c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TotalExclusiveLocks_70.log’ "< profilename>"






OUTPUT






Normal N/A None

Always N/A None

3–218 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
USAGE NOTES

SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Locks, Total Locks Percent Used, Total Locks Remaining


Total Locks

Total Locks

DESCRIPTION

Reports the total number of locks currently used by the database server. (For more information on locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TotalLocks

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TotalLocks’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’ -f ’nemuchay: C:\MSSQLServer\TotalLocks_71.log’ "< profilename>"

3–220 Version 1.3

Total Locks

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT


USAGE NOTES

The total number of locks available defaults to 5000. You can increase or decrease this number using the locks server configuration option. In setting the number of locks, you should consider that each lock requires space (32 bytes in Version 6.5, 96 bytes in Version 7.0)





Normal N/A None

Always N/A None


Total Locks

t

and determine the amount of resources you want to allocate solely to locks.

Microsoft SQL Server Version 7.0

You can set the locks configuration option to 0 to allow dynamic lock management. In this case, two percent of the memory allocated to Microsoft SQL Server is allocated initially. The memory allocated to locks grows and shrinks with the demand for locks, but is not allowed to exceed 40 percent.


For Microsoft SQL Server Version 6.5, the calculation of total locks includes undocumented lock types. Because of this, the Total Locks monitor provides values that are slightly larger than the sum of all documented lock types. Due to the transient nature of locks, it is unlikely that this implementation detail is noticeable, even when comparing the monitor return values with Microsoft SQL Server’sPerformance Monitor.

Two other monitors use Total Locks in their calculations: Total Locks Percentage Used and Total Locks Remaining. These monitors accordingly return slightly smaller values due to Total Locks being bigger.

The undocumented lock types should be considered as Microsofinternals. They are not available for monitoring through Tivoli Manager for Microsoft SQL Server. They are:

■ 10 ShTab_ExIntent

■ 13 Insert_page

■ 14 Link_page

■ 266 ShTab_ExIntent-blk

■ 269 Insert_page-blk

■ 270 Link_page-blk

3–222 Version 1.3

Total Locks

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
SEE ALSO
MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks Percent Used, Total Locks Remaining


Total Locks Percent Used


DESCRIPTION

Reports the percentage of locks available that are currently in use. (For more information on locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of locks active during server activity and to determine whether you should configure more or fewer locks. In Microsoft SQL Server 7.0 you can have the lock allocation configured automatically.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TotalLocksPercentUsed

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TotalLocksPercentUsed’ -t ’2 minutes’ -c ’critical’-c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TotalLocksPercentUsed_72.log’ "< profilename>"

3–224 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT


USAGE NOTES

The total number of locks available defaults to 5000. You can increase or decrease this number using the locks server configuration option. In setting the number of locks, you should consider that each lock requires 32 bytes and determine the amount of resource you want to allocate to locks.





Normal N/A None

Always N/A None



t


You can set the locks configuration option to 0 to allow dynamic lock management. In this case, two percent of the memory allocated to Microsoft SQL Server is allocated initially. The memory allocated to locks grows and shrinks with the demand for locks, but is not allowed to exceed 40 percent.






■ 13 Insert_page

■ 14 Link_page




SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Remaining

3–226 Version 1.3

Total Locks Remaining

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the total number of locks that can still be taken out. The maximum number of locks is configurable. In Microsoft SQL Server Version 7.0, you can have the number of locks configured automatically. Use this monitor to show the number of locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TotalLocksRemaining

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TotalLocksRemaining’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TotalLocksRemaining_73.log’ "< profilename>"






OUTPUT






Normal N/A None

Always N/A None

3–228 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

t

USAGE NOTES

The total number of locks available defaults to 5000. You can increase or decrease this number using the locks server configuration option. In setting the number of locks, you should consider that each lock requires space (32 bytes in Version 6.5, 96 bytes in Version 7.0) and determine the amount of resource you want to allocate to locks.






■ 13 Insert_page

■ 14 Link_page




SEE ALSO

MSSQLServer monitors: Intent Locks Exclusive, Intent Locks Shared, Intent Locks Total, Page Locks Exclusive, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used


Total Shared Locks

Total Shared Locks

DESCRIPTION

Reports the total number of current shared locks. (For more information on locks, see the Microsoft SQL Server Books On-line.) Use this monitor to show the number of these locks active during server activity.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

TotalSharedLocks

CLI EXAMPLE

waddmon ’MSSQLServer’ ’TotalSharedLocks’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\TotalSharedLocks_74.log’ "< profilename>"

3–230 Version 1.3

Total Shared Locks

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None


Total Shared Locks

USAGE NOTES

If you are looking at lock escalation, use the Page Locks and Table Locks monitors. To understand how many shared locks there are in relation to total locks, use the Total Locks monitors.

SEE ALSO

MSSQLServer monitors: Page Locks Exclusive, Page Locks Shared, Page Locks Total, Page Locks Update, Table Locks Exclusive, Table Locks Shared, Table Locks Total, Total Exclusive Locks, Total Locks, Total Locks Percent Used

3–232 Version 1.3

Undelivered Transactions

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the number of transactions that have been delivered from the publisher to the distribution database, but have not been executed against the subscriber database(s). Use this monitor to check the success of the replication process in delivering transactions to the subscribers in a timely manner; you also can find out if bottlenecks are occurring.


AUTHORIZATION ROLE

mssqlserver_monitor




TARGET ENDPOINT

database servers





Subscriber Name


3–234 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
CLI SYNTAX
UndeliveredTransactions

–a <subscriber>



CLI EXAMPLE

waddmon ’MSSQLServer’ ’UndeliveredTransactions’ -a ’nemuchay’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\UndeliveredTransactions.log’ "< profilename>"


The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a target rate of 30 transactions a minute. It is assumed that the monitor is run every five minutes and the distribution schedule runs every minute.






Normal N/A None

Always N/A None



OUTPUT


USAGE NOTES

When the returned value is higher than anticipated, it could indicate a bottleneck in the replicated transaction process. When the returned value is lower than anticipated it indicates good throughput.

When the value is high, you can do the following:

■ Check the network between the distribution database and subscriber database if they are on different servers. (Use the Network Read Rate and Network Write Rate monitors.)

■ Check the workload on one or both servers to determine if it is overloaded. (Use the CPU Percent Busy monitor.)

■ Check to see if the subscriber database is unavailable. (Use the Database Status (Database) monitor.)



3–236 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
SEE ALSO
MSSQLServer monitors: Delivered Latency, Delivered Transaction Rate, and Delivered Transactions

MSSQLDatabase monitors: Replicated Transaction Rate, Replicated Transactions, Replication Latency


User Connections

User Connections

DESCRIPTION

Reports the current number of user connections. Since each user connection consumes some memory, configuring a high number of user connections could impact throughput. Set user connections to the maximum expected number of concurrent users. In Microsoft SQL Server Version 7.0 it is possible to have the number of user connections configured automatically.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

UserConnections

CLI EXAMPLE

waddmon ’MSSQLServer’ ’UserConnections’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLServer\UserConnections_76.log’ "< profilename>"

3–238 Version 1.3

User Connections

Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
The following table shows suggested threshold values for severity levels. The response levels are based on the assumption of a USER CONNECTION limit of 20.


OUTPUT






Normal N/A None

Always N/A None


User Connections

USAGE NOTES

If a performance slow-down coincides with an increased number of user connections, use the user connections configuration option to restrict user connections or increase the number of worker threads. The number of worker threads should always be greater than or equal to the number of user connections to avoid thread pooling. As an alternative, you may want to increase the available memory.

SEE ALSO

MSSQLServer monitors: User Connections Percent Used, User Connections Remaining

3–240 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n
DESCRIPTION

Reports the current number of user connections as a percentage of the available number of user connections for the database server. Use this monitor to gain an overview of high and low access periods and to warn you of impending availability problems. In Microsoft SQL Server Version 7.0 it is possible to have the number of user connections configured automatically.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

UserConnectionsPercentUsed

CLI EXAMPLE

waddmon ’MSSQLServer’ ’UserConnectionsPercentUsed’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin: C:\MSSQLServer\UserConnectionsPercentUsed.log’ "< profilename>"






OUTPUT






Normal N/A None

Always N/A None

3–242 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n

USAGE NOTES

If you run out of user connections, then the server rejects login requests causing an availability issue. You can increase connections with the user connections configuration option. When setting this option, take into account that each connection has a 40 KB overhead.

To reduce the number of user connections requested, you can ensure the applications are not using multiple connections when a single one would do. You could also try to stagger access requirements.

Version 7.0: If the user connections variable has been set to 0 (meaning “no limit”), then this monitor calculates its information using the global @@MAX_CONNECTIONS value. Microsoft SQLServer maintains @@MAX_CONNECTIONS automatically. The value it chooses reflects the resources of the current computing environment.

SEE ALSO

MSSQLServer monitors: User Connections, User Connections Remaining


User Connections Remaining


DESCRIPTION

Reports the number of user connections remaining out of the total allocated. Use this monitor to gain an overview of high and low access periods and to warn you of impending availability problems. In Microsoft SQL Server Version 7.0 it is possible to have the number of user connections configured automatically.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

database servers


None

CLI SYNTAX

UserConnectionsRemaining

CLI EXAMPLE

waddmon ’MSSQLServer’ ’UserConnectionsRemaining’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin: C:\MSSQLServer\UserConnectionsRemaining.log’ "< profilename>"

3–244 Version 1.3


Th

e MS

SQ

LS

erver M

on

itorin

g C

ollectio

n


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

If you run out of user connections, then the server rejects login requests causing an availability issue. You can increase connections with the user connections server configuration option. When setting this option, take into account that each connection has a 40 KB overhead.

To reduce the number of user connections requested, you can ensure the applications are not using multiple connections when a single one would do. You could also try to stagger access requirements.

Version 7.0: If the user connections variable has been set to 0 (meaning “no limit”), then this monitor calculates its information using the global @@MAX_CONNECTIONS value. Microsoft SQLServer maintains @@MAX_CONNECTIONS automatically. The value it chooses reflects the resources of the current computing environment.

SEE ALSO

MSSQLServer monitors: User Connections, User Connections Percent Used

3–246 Version 1.3

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

4MSSQLDatabase Monitoring Collection


■ A table that lists all monitors by GUI name and CLI name

■ Reference entries for each monitor in the MSSQLServer monitoring collection, sorted alphabetically by GUI name

The MSSQLDatabase monitoring collection provides a range of monitors to allow you to manage Microsoft SQL Server databases. Each manages a different aspect of a database, such as database status, replication latency, and transaction log size.

■ To monitor individual databases, distribute a profile containing MSSQLDatabase monitors to database endpoints. Those monitors are described in this chapter.

■ To monitor database servers, distribute a profile containing MSSQLServer monitors to database server or managed node endpoints, as specified in the reference entry. Those monitors are described in Chapter 3, “The MSSQLServer Monitoring Collection.”

■ To create customized monitors, use the Freeform SQL numeric and Freeform SQL string monitors in the MSSQLServer monitoring collection. You provide SQL statements that determine the monitors’ behavior. Those

4


List of MSSQLDatabase Monitoring Sources by GUI and CLI Names

,

monitors are described in Chapter 3, “The MSSQLServer Monitoring Collection.”

For more information about distributed monitoring, see Chapter 6“Setting Up Monitoring,” in Tivoli Manager for Microsoft SQL Server User’s Guide.

List of MSSQLDatabase Monitoring Sources by GUI and CLI Names

The following table lists the MSSQLDatabase monitoring sources by both their GUI and CLI names.

GUI Name CLI Name

Data Space Percent Used (Database) DataSpacePercentUsedDB

Data Space Used DataSpaceUsed

Database Status (Database) DatabaseStatusDB

Fragmentation Fragmentation

Log Space Percent Used (Database) LogSpacePercentUsedDB

Log Space Used LogSpaceUsed

Oldest Open Transaction (Database) OldestOpenTransactionDB

Optimizer Statistics Age OptimizerStatisticsAge

PeopleSoft Fragmentation PeopleSoftFragmentation

PeopleSoft Optimizer Statistics Age PeopleSoftOptimizerStatisticsAge

PeopleSoft Space Used Table PeopleSoftDataSpaceUsed

Replicated Transaction Rate ReplicatedTransactionRate

Replicated Transactions ReplicatedTransactions

Replication Latency ReplicationLatency

Space Used (Table) SpaceUsedTable

Suspect Database SuspectDatabase

4–2 Version 1.3

Data Space Percent Used (Database)

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


DESCRIPTION

Monitors the amount of space (in megabytes) used in the database as a percentage of total space allowed. Use this monitor to warn you when you need to extend the database. If you run out of space, you can no longer use the database. In Microsoft SQL Server Version 7.0 the amount of space allocated can be configured to grow automatically.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases





Run Update Usage

Yes runs the DBCC UPDATEUSAGE against the database before the monitor value is set. This ensures that the data returned is up-to-date. This procedure can take some time on large tables, so it may make the monitor unusable or too resource-intensive.


4–4 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

CLI SYNTAX

DataSpacePercentUsedDB

–a <UpdateUsage>


<UpdateUsage>

Y runs DBCC UPDATEUSAGE against the database before the monitor value is set. This may take some time on larger tables, which may cause the monitor to time out. N does not run DBCC UPDATEUSAGE.

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’DataSpacePercentUsedDB’ -a ’No’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin: C:\MSSQLDatabase\DataSpacePercentUsed_3.log’ "<profilename>"


The following chart shows suggested threshold values for severity levels.


Severity Trigger When Default Action




Normal N/A None

Always N/A None



OUTPUT


USAGE NOTES

You may also want to use this monitor to track database growth and to help forecast disk space and backup requirements.

In Microsoft SQL Server Version 6.5, the data and log may or may not be on the same device fragment. If they are, then the space reported is for both the data and log. If they are not, then the space reported is for the data only.

In Microsoft SQL Server Version 7.0, the value reported is always for the data only.

When the database runs out of space, it is not extended automatically in Microsoft SQL Server Version 6.5. It can be configured to extend itself automatically in Microsoft SQL Server 7.0. You may also want to use the NT Logical Disk: Percent Free Space monitor if the database is set to grow itself indefinitely.

SEE ALSO

MSSQLDatabase monitors: Data Space Used, Log Space Used, Log Space Percent Used (Database), Space Used (Table)

MSSQLServer monitors: Data Space Percent Used (Server)


Windows NT Monitors: DISK SPACE USED

4–6 Version 1.3

Data Space Used

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

Data Space Used

DESCRIPTION

Monitors the amount of space (in megabytes) taken up by the indexes and data in a specified database. Use this monitor to keep track of the actual size of (as opposed to the disk space allocated to) the database. Use this monitor to plan for backups and to track database growth, so you can forecast disk space needs.

Note: The amount of space returned does not include space occupied by the syslogs table.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


Data Space Used



Run Update Usage



4–8 Version 1.3

Data Space Used

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

CLI SYNTAX

DataSpaceUsed

–a <UpdateUsage>


<UpdateUsage>


CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’DataSpaceUsed’ -a ’No’ -t ’1 minutes’ -c ’critical’ -c ’severe’ -c ’warning’-c ’normal’ -c ’always’ -f ’C:\MSSQL\Database\DataSpaceUsed_2.log’ "<profilename>"


The following chart shows suggested threshold values for severity levels. The response levels are based on the assumption of 500 MB database space available.






Normal N/A None

Always N/A None


Data Space Used

OUTPUT


USAGE NOTES

If the database runs out of space, you cannot use it. You must extend it. Use this monitor in conjunction with the MS SQL Server Warnings and Indicators task to ensure that when you need to extend or backup the database you have adequate space.

SEE ALSO

MSSQLDatabase monitors: Database Status (Database), Log Space Used, Log Space Percent Used (Database), Space Used (Table)

MSSQLServer monitors: Data Space Percent Used (Server)


4–10 Version 1.3

Database Status (Database)

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


DESCRIPTION

Reports when the database is unavailable. If a database is offline, for example, you cannot access it. Use this monitor to warn that the database has become unavailable.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

None

CLI SYNTAX

DatabaseStatusDB

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’DatabaseStatusDB’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’nemuchay: C:\MSSQLDatabase\DatabaseStatusDB_1.log’ "< profilename>"






OUTPUT



Critical Is unavailable Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

4–12 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

USAGE NOTES

If a subscriber database becomes unavailable, then transactions will back up in the distribution database.

If the database is in one of the following states, it is Available:

■ ’read only’ =1024

■ ’single user’, connection in use =4096

■ ’dbo use only’ =2048

■ ’is being checkpointed’ = 8192

If the database is in one of the following states, it is Unavailable:

■ ‘in transition’ = 2 (Microsoft SQL Server Version 6.5 only)

■ ‘loading’ = 32

■ ‘pre recovery’ = 64

■ ‘recovering’ = 128

■ ‘not recovered’ = 256

■ ‘offline’ = 512

■ ‘emergency mode’ = 32768

SEE ALSO

MSSQLServer monitors: Data Space Percent Used (Server), Database Status (Server), Service State, SQL Server State


Fragmentation

Fragmentation

DESCRIPTION

Reports the degree of fragmentation for a specified index or table. Use this monitor to determine if fragmentation is reaching a level that causes performance degradation. Performance degradation is due to non-contiguous table reads that require additional extent switches.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases



4–14 Version 1.3

Fragmentation

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

Table Name Specifies the table to monitor.

Index Name Specifies the index to monitor. This field is optional; the monitor reports fragmentation at the data page level when the argument is left blank.

For more information see “Usage Notes.”


Fragmentation

CLI SYNTAX

Fragmentation

–a <Table Name >

[–a <Index Name>]


<Table Name > Specifies the table to monitor.

<Index Name> Specifies the index to monitor. <Index Name> is optional; the monitor reports fragmentation at the data page level when you leave the argument blank.

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’Fragmentation’ -a ’authors’ -a ’aunmind’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’ -f ’hbergin: C:\MSSQLDatabase\Fragmentation_4.log’ "<profilename>"








Normal N/A None

Always N/A None

4–16 Version 1.3

Fragmentation

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

OUTPUT


USAGE NOTES

If the table has a clustered index, then the fragmentation level is the same whether you specify the table name alone or specify the table name with the clustered index name. Non-clustered indexes are stored separately to the table data, so they may have a different level of fragmentation.

When rebuilding a fragmented index, you may want to consider specifying a fill factor that leaves some free space on each page for inserts and updates. This can reduce page splitting and help performance. Rebuilding the clustered index automatically rebuilds all non-clustered indexes.

SEE ALSO

MSSQLServer monitors: I/O Page Read Rate

Tasks: Database Check-up and Tune-up, Rebuild Fragmented Indexes


Log Space Percent Used (Database)

ame


DESCRIPTION

Reports the percentage of the transaction log that is full. When the log has filled up all of its allocated space, transactions that require logging are rejected. Use this monitor to set an alert based on a percent full threshold and then spawn a task to dump and/or truncate the transaction log.

When used with Microsoft SQL Server Version 6.5, this monitor may return a value higher than 100%. The value is based on the size of the syslogs table compared to the configured log size. The Microsoft SQL Server tools never return a value for the log space used percentage that is higher than 100%. Microsoft SQL Server allows the syslogs table to grow beyond the configured log size. To be safe, you should set a response action to truncate the log before this monitor reaches 100%. See the “Response Levels” section.

This monitor returns 0 if the log and database space are on the sdevice fragment.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

LogSpacePercentUsedDB

4–18 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’LogSpacePercentUsedDB’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\LogSpacePercentUsed_6.log’"<profilename>"




OUTPUT






Normal N/A None

Always N/A None



, then or

the

USAGE NOTES

If the transaction log fills up, you must truncate it before you can continue working; but, you cannot backup the transaction log before you truncate it. After truncating the log, back up the entire database immediately to ensure that you do not lose data.

When a database’s log and data share the same device fragmentthis monitor returns a value of 0. If you want a corrective action fthe log filling up on such a database, use the NT Event Logging task to configure the following error to be forwarded to the Applicationlog in the Windows NT event log:




For databases with logs and data not sharing the same device, configure the response action to truncate or back up and truncatelog when it reaches a specified level; use the CLI syntax for the Dump Transaction Log task in the Run Program field.

SEE ALSO

MSSQLServer monitors: Data Space Percent Used (Server), Log Space Percent Used (Server), NT Application Log

MSSQLDatabase monitors: Data Space Used, Data Space Percent Used (Database), Log Space Used, Space Used (Table)


4–20 Version 1.3

Log Space Used

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

the r cast mps.

ay l size

Log Space Used

DESCRIPTION

Monitors the amount of allocated space (in megabytes) in the database’s transaction log that has been used. Use this monitor to keep track of the actual size (as opposed to the defined size) of log. Use this monitor to plan for the amount of space required fobackups. You also can use it to track log growth, so you can foredisk space needs or increase the frequency of transaction log du

When used with Microsoft SQL Server Version 6.5, this monitor mreturn a value higher than 100%. The value is based on the actuaof the syslogs table. Microsoft SQL Server allows the syslogs table to grow beyond the configured log size.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

LogSpaceUsed

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’LogSpaceUsed’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\LogSpaceUsed_5.log’ "<profilename>"


Log Space Used


The following chart shows suggested threshold values for severity levels. The response levels are based on the assumption of 500 MB log space available.


OUTPUT






Normal N/A None

Always N/A None

4–22 Version 1.3

Log Space Used

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

USAGE NOTES

You should determine a window for acceptable data loss, then set the log to be automatically dumped at this interval. The log space must be an adequate size for the specified time period. If you increase the frequency of the dumps, you should be able to decrease the log size.

If you want a corrective action for the log filling up on such a database, use the NT Event Logging task to configure the following error to be forwarded to the Windows NT event log (it gets put in the Application log).




For databases with logs and data not sharing the same device fragment, configure the response action of this monitor to truncate or back up and truncate the log when it reaches a specified level; use the CLI syntax for the Dump Transaction Log task in the Run Program field.

SEE ALSO

MSSQLServer monitors: NT Application Log

MSSQLDatabase monitors: Data Space Used, Data Space Percent Used (Database), Log Space Percent Used (Database), Space Used (Table)



Oldest Open Transaction (Database)

ich .


DESCRIPTION

Reports the age (in minutes) of the oldest open transaction in the database’s transaction log. Use this monitor to determine up to whpoint in time the transaction log can be truncated and backed up

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

OldestOpenTransactionDB

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’OldestOpenTransactionDB’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\OldestOpenTransaction_7.log’ "<profilename>"

4–24 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


The following chart shows suggested threshold values for severity levels. The following response levels are based on a 15-minute data-loss window.


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES

If you are unable to back up the transaction log to the current point in time and you rely on it for a RESTORE, you may lose any transactions that occurred after the timestamp on the oldest open transaction.

SEE ALSO

MSSQLServer monitors: I/O Transactions Per Log Record, I/O Transaction Rate

4–26 Version 1.3

Optimizer Statistics Age

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


DESCRIPTION

Reports the time (in minutes) since statistics were updated for the specified index. Use this monitor to ensure that queries base their query plans on up-to-date information. If query plans are based on old information, they may be inefficient.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases






Index Name Specifies the index to monitor. Index name is optional.

4–28 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

CLI SYNTAX

OptimizerStatisticsAge

–a <Table Name>

[–a <Index Name>]


<Table Name > Specifies the table to monitor.

<Index Name> Specifies the index to monitor. <Index Name > is optional.

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’OptimizerStatisticsAge’ -a ’authors’ -a ’aunmind’ -t ’2 minutes’ -c ’critical’-c ’severe’ -c ’warning’ -c ’normal’-c ’always’-f ’hbergin:C:\MSSQLDatabase\OptimizerStatisticsAge.log’ "<profilename>"


The following chart shows suggested threshold values for severity levels. It assumes significant updates are made within a three-hour period. The appropriate time values vary widely from application to application.






Normal N/A None

Always N/A None



OUTPUT


USAGE NOTES

The efficiency of query plans is integral to overall server performance. The repercussions of query plans based on out-of-date statistics show up as problems elsewhere in the system, such as queries doing unnecessary reads, the incorrect use of indexes, and blocking locks.

SEE ALSO

None

4–30 Version 1.3

PeopleSoft Fragmentation

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


DESCRIPTION

Reports the 10 PeopleSoft tables with the highest degree of fragmentation from a specified group of PeopleSoft tables: Base Benefits, Human Resource, Payroll, or All. Use this monitor to determine if fragmentation is reaching a level that causes performance degradation. Performance degradation is due to non-contiguous table reads that require additional extent switches.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases





PeopleSoft Table Category

Specifies the group of tables to monitor. Click the Categories button to choose one of these groups: BaseBenefits, HumanResources, Payroll, or All.

4–32 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

CLI SYNTAX

PeopleSoftFragmentation

–a <TableGroup>


<TableGroup> Specifies the group of tables to monitor. Specify one of these groups: BaseBenefits, HumanResources, Payroll, or All .

CLI EXAMPLEwaddmon ’MSSQLDatabase’ ’PeopleSoftFragmentation’ -a ’All’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’ -f ’hbergin: C:\MSSQLDatabase\PeopleSoftFragmentation_4.log’ "<profilename>"








Normal Less than 30% None

Always N/A None



OUTPUT


USAGE NOTES

Indexes are checked by this monitor. Only table data pages are checked.

When rebuilding a fragmented index, you may want to consider specifying a fill factor that leaves some free space on each page for inserts and updates. This can reduce page splitting and help performance. Rebuilding the clustered index automatically rebuilds all non-clustered indexes.

SEE ALSO

MSSQLDatabase monitors: Fragmentation

MSSQLManagerTasks: Database Check-up and Tune-up, Rebuild Fragmented Indexes

4–34 Version 1.3

PeopleSoft Optimizer Statistics Age

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


DESCRIPTION

Reports the 10 indexes with the oldest statistics from a specified group of PeopleSoft tables: Base Benefits, Human Resources, Payroll, or All. A return of 999999999 indicates that the index has never been updated or has not been updated within one year.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases







4–36 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

CLI SYNTAX

PeopleSoftOptimizerStatisticsAge

–a <TableGroup>



CLI EXAMPLEwaddmon ’MSSQLDatabase’ ’PeopleSoftOptimizerStatisticsAge’ -a ’All’ -t ’2 minutes’ -c ’critical’-c ’severe’ -c ’warning’ -c ’normal’-c ’always’-f ’hbergin:C:\MSSQLDatabase\PeopleSoftOptimizerStatisticsAge.log’ "<profilename>"


The following chart shows suggested threshold values for severity levels. It assumes significant updates are made within a three-hour period. The appropriate time values vary widely from application to application.






Normal Less than 180 None

Always N/A None



OUTPUT


USAGE NOTES

The efficiency of query plans is integral to overall server performance. The repercussions of query plans based on out-of-date statistics show up as problems elsewhere in the system, such as queries doing unnecessary reads, the incorrect use of indexes, and blocking locks.

SEE ALSO

None

4–38 Version 1.3

PeopleSoft Space Used Table

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


DESCRIPTION

Monitors the amount of space (in megabytes) taken up by the tables in a specified group of PeopleSoft tables: Base Benefits, Human Resource, Payroll, or All. Use this monitor to keep track of the actual size of (as opposed to the disk space allocated to) the database. Use this monitor to plan for backups and to track database growth, so you can forecast disk space needs.

Note: The amount of space returned does not include space occupied by the syslogs table.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases





Run Update Usage



4–40 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection



CLI SYNTAX

PeopleSoftSpaceUsedTable

–a <UpdateUsage>

–a <TableGroup>


<UpdateUsage>



CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’PeopleSoftSpaceUsedTable’ -a ’No’ -a ’All’ -t ’1 minutes’ -c ’critical’ -c ’severe’ -c ’warning’-c ’normal’ -c ’always’ -f ’C:\MSSQL\Database\PeopleSoftSpaceUsedTable_2.log’ "<profilename>"




The following chart shows suggested threshold values for severity levels. The response levels are based on the assumption of 500 MB database space available.


OUTPUT






Normal N/A None

Always N/A None

4–42 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

USAGE NOTES

If the database runs out of space, you cannot use it. You must extend it. Use this monitor in conjunction with the MS SQL Server Warnings and Indicators task to ensure that when you need to extend or backup the database you have adequate space.

SEE ALSO

MSSQLDatabase monitors: Data Space Used, Data Space Percent Used (Database), Log Space Used, Log Space Percent Used (Database)

MSSQLServer monitors: Data Space Percent Used (Server), Log Space Percent Used (Server)



Replicated Transaction Rate

y the


DESCRIPTION

Monitors the rate per second at which transactions have been read out of the publication database’s transaction log and delivered to the distribution database. Use this monitor to discover if there are anbottlenecks in the replication process; bottlenecks cause delays inpublished transactions reaching the subscriber database.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

ReplicatedTransactionRate

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’ReplicatedTransactionRate’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’berg1:C:\MSSQLDatabase\ReplicatedTransactionRate.log’ "<profilename>"

4–44 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


The following chart shows suggested threshold values for severity levels. The response levels are based on the following assumptions: a target rate of 30 transactions a minute and the log reader set to run every minute.


OUTPUT



Critical Less than 0.0 Send MSSQL Sentry notice

Severe Less than 0.25 Send MSSQL Sentry notice

Warning Less than 0.5 Send MSSQL Sentry notice

Normal N/A None

Always N/A None



USAGE NOTES


The transaction rate can be affected by the distribution schedule, which determines the interval between transactions being distributed to the subscriber. It can also be affected by the number of transactions that you configure to be sent in a batch.

The period that delivered transactions remain in the distribution database is configurable. You can tell how many transactions have successfully executed during this period of time. If the value is lower than anticipated, this could point to a bottleneck in the replicated transaction process. If the value is high, it indicates you are getting good throughput, but you may be unnecessarily filling up the distribution database.

If the value is high, you can do the following:

■ Check whether the period that delivered transactions remain in the distribution database is too long. If it is, the database can fill up. Reduce the value for the period.

If the value is low, you can do the following:





There also are several monitors that check the flow of replication transactions from the publication to the distribution database. These

4–46 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

are Replicated Transaction Rate, Replicated Transactions, and Replication Latency.


■ Check the network between the publication database and distribution database if they are on different servers. (Use the Network Read Rate and Network Write Rate monitors.)


■ Determine if the distribution database is unavailable. (Use the Database Status (Database) monitor.)

SEE ALSO

MSSQLDatabase monitors: Database Status (Database), Replication Latency, Replicated Transactions

MSSQLServer monitors: CPU Percent Busy, Delivered Latency, Delivered Transaction Rate, Delivered Transactions, Network Read Rate, Network Write Rate, Undelivered Transactions


Replicated Transactions

een r if ause


DESCRIPTION

Reports the number of transactions in the publication database’s transaction log that are marked for replication but have not yet bdelivered to the distribution database. Use this monitor to discovethere are any bottlenecks in the replication process; bottlenecks cdelays in the published transactions reaching the subscriber database.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

ReplicatedTransactions

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’ReplicatedTransactions’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\ReplicatedTransactions.log’ "<profilename>"\

4–48 Version 1.3


MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


The following chart shows suggested threshold values for severity levels. The response levels are based on the following assumptions: a target rate of 30 transactions a minute, the monitor running every five minutes, and the log reader set to run every minute.


OUTPUT






Normal N/A None

Always N/A None



USAGE NOTES


There also are several monitors that check the flow of replication transactions from the publication to the distribution database. These are Replicated Transaction Rate, Replicated Transactions, and Replication Latency.



■ Check the workload on one or both servers to determine when it is overloaded. (Use the CPU Percent Busy monitor.)


SEE ALSO

MSSQLDatabase monitors: Database Status (Database), Replication Latency, Replicated Transaction Rate

MSSQLServer monitors: CPU Percent Busy, Delivered Transaction Rate, Delivered Latency, Delivered Transactions, Network Read Rate, Network Write Rate, Undelivered Transactions

4–50 Version 1.3

Replication Latency

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

to any the

Replication Latency

DESCRIPTION

Reports the number of milliseconds between the time a transaction marked for replication is entered into the publication database’s transaction log and the time it is read out of the log and deliveredthe distribution database. Use this monitor to discover if there are bottlenecks in the replication process; bottlenecks cause delays inpublished transactions reaching the subscriber database.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

ReplicationLatency

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’ReplicationLatency’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\ReplicationLatency_11.log’ "<profilename>"


Replication Latency


The following chart shows suggested threshold values in milliseconds for severity levels. The response levels are based on the following assumptions: a target rate of 30 transactions a minute and the log reader set to run every minute.


OUTPUT



Critical Greater than 900,000 Send MSSQL Sentry notice

Severe Greater than 300,000 Send MSSQL Sentry notice

Warning Greater than 120,000 Send MSSQL Sentry notice

Normal N/A None

Always N/A None

4–52 Version 1.3

Replication Latency

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

USAGE NOTES


There also are several monitors that check the flow of replication transactions from the publication to the distribution database. These are Replicated Transaction Rate, Replicated Transactions, and Replication Latency.





SEE ALSO

MSSQLDatabase monitors: Database Status (Database), Replicated Transaction Rate, Replicated Transactions

MSSQLServer monitors: CPU Percent Busy, Delivered Latency, Delivered Transaction Rate, Delivered Transactions, Network Read Rate, Network Write Rate, Undelivered Transactions


Space Used (Table)

Space Used (Table)

DESCRIPTION

Reports the amount of space (in megabytes) used by the specified table. Use this monitor to determine how much of the database space is used by a specified table. You can monitor the growth of individual tables and compare the actual growth to the expected growth.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases



4–54 Version 1.3

Space Used (Table)

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


Run Update Usage




Space Used (Table)

CLI SYNTAX

SpaceUsedTable

–a <Table Name>

–a <UpdateUsage>


<Table Name>

Specifies the table to monitor.

<UpdateUsage>


CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’SpaceUsedTable’ -a ’sysobjects’ -a ’Yes’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\SpaceUsedTable_12.log’ "<profilename>"

4–56 Version 1.3

Space Used (Table)

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection


The following chart shows suggested threshold values for severity levels. The response levels are based on the assumption 100 MB table space available.


OUTPUT


USAGE NOTES

None





Normal N/A None

Always N/A None


Space Used (Table)

SEE ALSO

MSSQLDatabase monitors: Data Space Used, Data Space Percent Used (Database), Log Space Used, Log Space Percent Used (Database)

MSSQLServer monitors: Data Space Percent Used (Server), Log Space Percent Used (Server)

4–58 Version 1.3

Suspect Database

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

Suspect Database

DESCRIPTION

Reports whether a database is marked as suspect. Use this monitor to warn you that a database cannot be loaded.

AUTHORIZATION ROLE

mssqlserver_monitor

TARGET ENDPOINT

databases


None

CLI SYNTAX

SuspectDatabase

CLI EXAMPLE

waddmon ’MSSQLDatabase’ ’SuspectDatabase’ -t ’2 minutes’ -c ’critical’ -c ’severe’ -c ’warning’ -c ’normal’ -c ’always’-f ’hbergin:C:\MSSQLDatabase\SuspectDatabase_13.log’ "<profilename>"


Suspect Database




OUTPUT



Critical True Send MSSQL Sentry notice

Severe N/A None

Warning N/A None

Normal N/A None

Always N/A None

4–60 Version 1.3

Suspect Database

MS

SQ

LD

atabase

Mo

nito

ring

Co

llection

USAGE NOTES

Microsoft SQL Server marks a database as SUSPECT and fails recovery when problems occur while attempting to recover the database during STARTUP. If you can determine the reason why the database was marked as SUSPECT, it may be safe to reset it. Before doing so, check the Microsoft SQL Server Books On-line. If you cannot determine if it is safe to reset the database, restore it from a known-good backup.

SEE ALSO


MSSQLServer monitors: Database Status (Server), Service State, SQL Server State


Suspect Database

4–62 Version 1.3

Index

Symbols$root_user virtual login name, mapped to

tmersrvd 2-32

Aactive procedure cache 3-170activity log

ADSM 2-8, 2-18Add argument 2-106Add field 2-104Additional Services field 2-151, 2-158addmon command 1-6Administrators group

membership required 2-53membership required in 2-85

ADSMactivity log 2-8, 2-18backing up databases 2-5backing up transaction log 2-5options file 2-7, 2-18server 2-13, 2-15, 2-17, 2-22SQL Agent 2-13, 2-22versions supported 2-14

ADSM Activity Log File field 2-8, 2-18ADSM Node field 2-7, 2-17ADSM Options File field 2-7, 2-18ADSM Password field 2-7, 2-17ADSMFullBackup task 2-5ADSMFullBackup task CLI syntax 2-8ADSMIncBackup task 2-15ADSMIncBackup task CLI syntax 2-19AdsmNode argument 2-10, 2-20

AdsmPwd argument 2-10, 2-20ADSTAR Distributed Storage Manager, see

ADSMAll table group, PeopleSoft 4-31, 4-35,

4-39ANSI

null columns 2-138null return on compares 2-138specifying compliant warnings 2-139

ANSI null default field 2-138ANSI nulls field 2-138ANSI warnings field 2-139ANSINullDefault argument 2-143ANSINulls argument 2-143ANSIWarnings argument 2-143Application log

age 3-130, 3-135forwarding SQL Server errors to

2-103, 4-20percent full 3-138

ArchiveFileName argument 2-44, 2-45, 2-120

ArchiveHostName argument 2-45, 2-120arguments

Add 2-106AdsmNode 2-10, 2-20AdsmOptFile 2-10AdsmOptfile 2-20AdsmPwd 2-10, 2-20ANSINullDefault 2-143ANSINulls 2-143ANSIWarnings 2-143ArchiveFileName 2-44, 2-45,

2-120ArchiveHostName 2-45, 2-120Autoclose 2-144AutoCreateStatistics 2-144Autoshrink 2-144AutoUpdateStatistics 2-144AvgChainLen 2-98AvgChainLenMax 2-98

Tivoli Manager for Microsoft SQL Server Reference Guide Index–1

BCPList 2-120Buffers 2-10, 2-21Compress 2-10, 2-20ConcatNullYieldsNull 2-144ConfigureForDM 2-30ConfigureForGEM 2-30ConfigureForTask 2-30ConfigureForTECAdapter 2-30CopyBase 2-30CopyBaseName 2-30CreateEventGroup 2-29CursorCloseOnCommit 2-145DboUseOnly 2-145DBSpaceUsed 2-98DBSpaceUsedMax 2-98Default 2-77DefaultToLocalCursor 2-145DisconnectedOverlow 2-112DiskType 2-83DumpDevice 2-67, 2-78DumpOptions 2-77DumpTo 2-67, 2-78EditMode 2-106Error_number 3-132Error_text 3-132ErrorNumbers 2-106EventGroupName 2-29ExcludeSyslogsTable 2-167FillFactor 2-112FilterErrors 2-37FilterInformation 2-37FilterMessages 2-37FilterMSDTC 2-37FilterSQLExecutive 2-37FilterSQLServerAgent 2-37FragLimit 2-44, 2-112IgnoreSRVRState 2-58index 3-64, 3-70Index Name 4-16, 4-29IndexName 2-112, 2-129, 2-167Last 2-67LastDBDump 2-98

LastDBDumpMax 2-99LastTransLogDump 2-99LastTransLogDumpMax 2-99LogAndData 2-98LogFile 2-10, 2-20Max_severity_level 3-132Memory 2-97MemoryMax 2-98MergePublish 2-145Message 2-159Min_severity_level 3-132MonitoredHost 2-45, 2-120Monitors 2-153, 2-160Mountwait 2-10, 2-20MSDTC 2-153, 2-160, 3-195MSSQLServer 3-195NoChkptOnRecovery 2-145NoLog 2-78NotifyTEC 2-2NoTruncate 2-20, 2-77NTDiskSpaceUsed 2-97NTDiskSpaceUsedMax 2-97NTEventLogging 2-97ObjectDrop 2-119Offline 2-145Overwrite 2-106OverwritePrevious 2-36ParentPolicyRegion 2-58Password 2-59PolicyRegion 2-58ProCache 2-97ProCacheMax 2-97Published 2-145Quiet 2-10, 2-21ReadOnly 2-146RebootNTServer 2-51RebootServer 2-84RecursiveTriggers 2-146Remove 2-106RemoveCustomization 2-133ReportFileName 2-2ReportHostName 2-2

Index–2 Version 1.3

ReportToFile 2-2RestartServer 2-31RestartSRVR 2-96RestartSRVRMAX 2-96RestoreFromBackup 2-133RuleBaseName 2-29SaveArchiveFileOn 2-45, 2-120SaveReportFileOn 2-2SelectIntoBulkCopy 2-146servername 2-2ServicePack 2-96ServicePackMin 2-96SingleUser 2-146Specified 2-67SpecifiedHost 2-45, 2-120SQL_select_statement 3-70SQLExecutive 2-152, 2-159SQLExecutive/SQLServerAgent

3-195SqlPwd 2-9, 2-19SQLSecure 2-9SqlSecure 2-20SQLServerAgent 2-152, 2-160SqlUser 2-9, 2-19Standard 2-83StartMode 2-152StopMode 2-159Striped 2-83Subscribed 2-146subscriber 3-40, 3-45, 3-50, 3-235Table Name 4-16, 4-29, 4-56TableGroup 4-33, 4-37, 4-41TableName 2-112, 2-129, 2-166TECServer 2-2TempDBINRam 2-97Timeout 2-159TornPageDetection 2-146Truncate 2-9TruncateOnly 2-77TruncLogOnChkpt 2-147TSQL 2-88UpdateUsage 4-5, 4-9, 4-41, 4-56

Username 2-58ValidateDB 2-66value 3-64, 3-70WarnOnly 2-96

AsdmOptFile argument 2-10, 2-20asynchronous read-ahead of data 3-181,

3-184, 3-187authorization role

shown in each reference entry 1-2auto create statistics field 2-139auto update statistics 2-139Autoclose argument 2-144autoclose field 2-139AutoCreateStatistics argument 2-144Autoshrink argument 2-144autoshrink field 2-139AutoUpdateStatistics argument 2-144availability codes 3-33availability of database server 3-199availability states for databases 4-13Average Chain length is greater than (##)

field 2-94AvgChainLen argument 2-98AvgChainLenMax argument 2-98

Bbacking up

avoiding diskettes 2-63, 2-74avoiding striped devices for master

2-69backup readability 2-61checking readability 2-71database incrementally using ADSM

2-15database, using ADSM 2-5databases 2-61date since last backup 2-91frequency versus space usage 4-23


history 2-73master database 2-80remote machines 2-69statistics 2-61, 2-71striped disks 2-63, 2-73to NULL device 2-69transaction log 2-71transaction log using ADSM 2-5transaction log when database

unavailable 2-80Backup and truncate field 2-72Backup Device field 2-62, 2-73Backup device options field 2-63Backup field 2-73Backup options field 2-74Base Benefits table group, PeopleSoft

4-31, 4-35, 4-39batch I/O

max writes 3-77pages per write 3-74write rate 3-80writes per batch 3-87

BCP commandallowing use of 2-141

BCP the following system table contents to file field 2-118

BCPList argument 2-120blocked processes

number 3-141blocking locks 3-214bottlenecks

I/O 3-96, 3-99, 3-102, 3-190replication process 3-38, 3-43,

3-51, 3-197, 3-233, 4-44, 4-48, 4-51

buffersfree, number 3-18free, percent used 3-9max scanned for unused 3-15minimum number maintained 3-11minimum to maintain 3-9

searching for unused 3-6SQL Agent uses 2-18used by SQL Agent in ADSM backup

2-8Buffers argument 2-10, 2-21

Ccache

changes written to disk 3-91data 3-6, 3-12, 3-14, 3-15, 3-104getting configuration of 2-91overloaded 3-96procedure 3-161, 3-164, 3-167,

3-170, 3-173, 3-176procedure, see procedure cacheread-ahead effectiveness 3-179

Cache Average Free Page Scan monitor 3-6Cache Configured Free Buffers Percent Used

monitor 3-9Cache Hit Ratio monitor 3-12Cache Maximum Free Page Scan monitor

3-15Cache Number of Free Buffers monitor

3-18CacheAverageFreePageScan monitor CLI

syntax 3-6CacheConfiguredFreeBuffersPercentUsed

monitor CLI syntax 3-9CacheHitRatio monitor CLI syntax 3-12CacheMaximumFreePageScan monitor CLI

syntax 3-15CacheNumberFreeBuffers monitor CLI

syntax 3-18chain length

average 2-91Change current setting field 2-104CHECKCATALOG 2-62CHECKIDENT 2-62


checkpointnone upon recovery 2-140

checkpoint record 2-140checkpoint thread

batch I/O 3-74, 3-77, 3-80checkpointing

auto-truncating transaction log 2-142CLI

adding monitors 1-6creating a job 1-6getting help 1-6running a job 1-6running tasks 1-6scheduling a job 1-6syntax shown in each reference entry

1-3using 1-5

CLI namesMSSQLDatabase monitors 4-2MSSQLServer monitors 3-2tasks, list of 2-3

CLI syntaxADSMFullBackup task 2-8ADSMIncBackup task 2-19CacheAverageFreePageScan monitor

3-6CacheConfiguredFreeBuffersPercentUse

d monitor 3-9CacheHitRatio monitor 3-12CacheMaximumFreePageScan monitor

3-15CacheNumberFreeBuffers monitor

3-18ClientCount monitor 3-21ClientCountPercentUsed monitor 3-23ConfigureTECMSSQL task 2-29CPUPercentBusy monitor 3-25CPUPercentBusyDoingIO monitor

3-27CPUPercentIdle monitor 3-29CustomizeTECNTEventAdapterMSSQL

task 2-36

DatabaseStatusDB monitor 4-11DatabaseStatusSRVR monitor 3-31DataSpacePercentUsedDB monitor 4-5DataSpacePercentUsedSRVR monitor

3-36DataSpaceUsed monitor 4-9DBCheckup task 2-44DBOption task 2-142DeliveredTransactionRate monitor

3-45DeliveredTransactions monitor 3-50DeliveryLatency monitor 3-40DisableDiskCounters task 2-51DiscoverSQLSRVR task 2-57DumpDatabase task 2-66DumpTransactionLog task 2-77EnableDiskCounters task 2-83ExecuteSQL task 2-88ExtentLocksExclusive monitor 3-53ExtentLocksTotal monitor 3-56ExtentLocksUpdate monitor 3-59Freeform SQL Numeric monitor 3-62,

3-64FreeFormSQLString monitor 3-70IntentLocksExclusive monitor 3-112IntentLocksShared monitor 3-115IntentLocksTotal monitor 3-118IOBatchAverageSize monitor 3-74IOBatchMaximumSize monitor 3-77IOBatchWriteRate monitor 3-80IODiskErrors monitor 3-83IODiskReads monitor 3-85IODiskWrites monitor 3-88IOLogWriteRate monitor 3-91IOOutstandingReads monitor 3-94IOOutstandingWrites monitor 3-97IOPageReadRate monitor 3-100IOSinglePageWriteRate monitor 3-103IOTransactionRate monitor 3-106IOTransactionsPerLogRecord monitor

3-109LogSpacePercentUsedDB monitor


4-18LogSpacePercentUsedSRVR monitor

3-121LogSpaceUsed monitor 4-21NetworkReadRate monitor 3-124NetworkWriteRate monitor 3-127NTApplicationLog monitor 3-132NTApplicationLogAge monitor 3-135NTApplicationLogPercentFull monitor

3-138NTEventLogging task 2-105NumberOfBlockedProcesses monitor

3-141NumberOfDeadlocks monitor 3-143OldestOpenTransactionDB monitor

4-24OldestOpenTransactionSRVR monitor

3-146OptimizerStatisticsAge monitor 4-29,

4-37PageLocksExclusive monitor 3-149PageLocksShared 3-152PageLocksTotal monitor 3-155PageLocksUpdate monitor 3-158PagesFetchedIntoCachePerSecond

monitor 3-182PeopleSoftDataSpaceUsed monitor

4-41PeopleSoftFragmentation monitor 4-33ProcedureBuffersActive monitor 3-161ProcedureBuffersTotal monitor 3-164ProcedureBuffersUsed monitor 3-167ProcedureCacheActive monitor 3-170ProcedureCacheSize monitor 3-173ProcedureCacheUsed monitor 3-176RAEffectiveness monitor 3-179RAPagesFoundInCachePerSecond

monitor 3-185RAPhysicalReadRate monitor 3-188RASlotsUsed monitor 3-191Rebuild Index task 2-111RecoveryPrep task 2-119

RefreshDB task 2-125RefreshStats task 2-128ReplicatedTransactionRate monitor

4-44ReplicatedTransactions monitor 4-48ReplicationLatency monitor 4-51RestoreTECNTEventAdapterMSSQL

task 2-133ServiceState monitor 3-195SpaceUsedTable monitor 4-56SQLServerAgentFailedJobs monitor

3-202SQLServerState monitor 3-199SQLWarnings task 2-95StartServMon task 2-151StopServMon task 2-158SuspectDatabase monitor 4-59TableLocksExclusive monitor 3-205TableLocksShared monitor 3-208TableLocksTotal monitor 3-211TotalBlockingLocks monitor 3-214TotalExclusiveLocks monitor 3-217TotalLocks monitor 3-220TotalLocksPercentUsed monitor 3-224TotalLocksRemaining monitor 3-227TotalSharedLocks monitor 3-230UndeliveredTransactions 3-235UpdateUsage task 2-166UserConnections monitor 3-238UserConnectionsPercentUsed monitor

3-241UserConnectionsRemaining monitor

3-244Client Count monitor 3-21Client Count Percent Used monitor 3-23ClientCount monitor CLI syntax 3-21ClientCountPercentUsed monitor CLI

syntax 3-23clients

see also user connectionsuser connections 3-238


user connections percent used 3-241user connections remaining 3-244workstations, current count 3-21workstations, percent of allowed 3-23

clustered indexes 2-114fragmentation 4-17

Column number of return value field 3-63, 3-69

columnsmaking nullable 2-138statistics 2-139

commandsaddmon 1-6Tivoli, for this product 1-5wcrtjob 1-6wexectask 1-6wgettaskhelp 1-6wrunjob 1-6wruntask 1-6wschedjob 1-6

committed transactionsclosing cursors 2-140

Compress argument 2-10, 2-20Compress field 2-6, 2-17concat null yields null field 2-139ConcatNullYieldsNull argument 2-144configuration options

free buffers 3-8, 3-9, 3-11, 3-20LE THRESHOLD % 3-114, 3-117,

3-120, 3-151, 3-154, 3-157, 3-160

LE THRESHOLD MAXIMUM 3-114, 3-117, 3-120, 3-151, 3-154, 3-157, 3-160

LE THRESHOLD MINIMUM 3-114, 3-117, 3-120, 3-151, 3-154, 3-157, 3-160

LOCK ESCALATION 3-207, 3-210, 3-213, 3-232

LOCKS 3-221, 3-222, 3-225,

3-229LOG WRITE SLEEP 3-109MAX_SERVER_MEMORY 3-14MAXIMUM ASYNC IO 3-20, 3-74,

3-77, 3-80, 3-87, 3-90MAXIMUM LAZYWRITE IO 3-20MEMORY 3-14, 3-161, 3-173,

3-176MIN_SERVER_MEMORY 3-14PROCEDURE CACHE 3-161,

3-164, 3-167, 3-170, 3-173, 3-176

RA SLOTS PER THREAD 3-191USER CONNECTIONS 3-240,

3-243, 3-246Configure Event Server for Distributed

Monitoring field 2-27Configure Event Server for GEM field 2-28Configure Event Server for Tasks field 2-28Configure Event Server for TEC NT Event

Adapter field 2-28ConfigureForDM argument 2-30ConfigureForGEM argument 2-30ConfigureForTask argument 2-30ConfigureForTECAdapter argument 2-30ConfigureTECMSSQL task 2-25ConfigureTECMSSQL task CLI syntax

2-29connections

database server 3-199user 3-238, 3-241, 3-244workstations 3-21

contentionlock 3-214

Continue field 2-150Copy Rule Base field 2-27CopyBase argument 2-30CopyBaseName argument 2-30CPU

I/O usage 3-27


idle 3-29percent busy 3-25

CPU Percent Busy Doing I/O monitor 3-27CPU Percent Busy monitor 3-25CPU Percent Idle monitor 3-29CPUPercentBusy monitor CLI syntax 3-25CPUPercentBusyDoingIO monitor CLI

syntax 3-27CPUPercentIdle monitor CLI syntax 3-29Create a Report File dialog called from tasks

2-2Create Event Group field 2-27CreateEventGroup argument 2-29cursor close on commit field 2-140CursorCloseOnCommit argument 2-145cursors

closing on commit 2-140limiting scope 2-140

Customize TEC NT Event Adapter MSSQL task 2-33

CustomizeTECNTEventAdapterMSSQL task CLI syntax 2-36

Ddata

acceptable loss 4-23ADSM management of 2-13backing up 2-80compressing prior to ADSM storage

2-17sharing device file with log 2-91sharing same device file with logs 2-94space used in databases 4-7

data cachebuffers, max search for unused 3-15buffers, search for unused 3-6effectiveness of 3-12, 3-15flushes 3-104minimizing I/O overhead 3-102

ratio of hits to requests 3-12tuning 3-14

data pageschecking index links 2-41

Data Space Percent Used (Database) monitor 4-3

Data Space Percent Used (Server) monitor 3-34

Data Space Used monitor 4-7Database Check-up and Tune-up task 2-41database servers

availability 3-199buffers, unused and 3-6buffers, unused and performance 3-9cache hit ratio 3-12client count 3-21clients 3-23CPU usage 3-25, 3-27databases unavailable 3-31discovering 2-54disk space available 2-93hours since started 2-91idle 3-29locks remaining 3-227locks, percent used 3-224locks, total 3-220locks, total shared 3-230login 2-57memory for 2-91monitors for, table of 3-2recovering 2-115registering 2-54registering, state of server 2-56starting 2-149state of services 3-193stopping 2-155torn page detection 2-141transaction logs, oldest transaction in

3-146version 2-91

Database space used is greater than (##) %


field 2-94Database Status (Database) monitor 4-11Database Status (Server) monitor 3-31databases

access by dbo only 2-140actual size 4-7actual size, PeopleSoft 4-39availability 4-11, 4-59availability states 4-13available, codes for 3-33backing up 2-61backing up incrementally using ADSM

2-15backing up transaction log when database

unavailable 2-80backing up using ADSM 2-5backup readability 2-61backup requirements 4-6checking integrity before backup 2-61checkpointing during shutdown 2-157checkpoints 2-140cursor scope 2-140design and single page I/O 3-105disk space requirements, forecasting

4-6growth 3-34log space used by 3-121maintenance 2-41making read-only 2-141master 2-91, 2-101master, backing up 2-80master, recovering 2-115merge replication eligibility 2-140monitors for, table of 4-2MSDB, tables 2-116options, current settings 2-148PeopleSoft 4-31, 4-35, 4-39quote usage 2-141read-only 2-141recovery 2-115refreshing after database server

registration 2-57refreshing on the TMR 2-124replication publications 2-141restoring, and losing transactions 3-148running TSQL statement on 2-86setting options 2-137sharing device fragment with transaction

log 2-80, 3-123shrinking automatically 2-139single user mode 2-48, 2-148single-user mode, specifying 2-141space used 4-3space used per 2-91space used, percentage 3-34specifying autoclose 2-139status of all on a database server 3-31stored procedures in 2-43suspect 4-59taking offline 2-140tracking growth 4-6, 4-7transactions remaining in too long 3-51transactions, oldest in transaction log

3-146triggers, recursive 2-141unavailable 3-31unavailable, codes for 3-33warnings, log and data on same device

fragment 2-101DatabaseStatusDB monitor CLI syntax

4-11DatabaseStatusSRVR monitor CLI syntax

3-31DataSpacePercentUsedDB monitor CLI

syntax 4-5DataSpacePercentUsedSRVR monitor CLI

syntax 3-36DataSpaceUsed monitor CLI syntax 4-9DBCC CHECKCATALOG statement 2-41DBCC CHECKDB statement 2-41, 2-62DBCC CHECKIDENT statement 2-41DBCC DBREINDEX statement 2-111


DBCC FIX_AL statement 2-42, 2-48DBCC NEWALLOC statement 2-41,

2-48DBCC UPDATEUSAGE statement 2-41,

2-168, 2-169, 3-35, 4-4, 4-8, 4-40, 4-55

DBCheckup task CLI syntax 2-44dbo use only field 2-140DBOption task CLI syntax 2-142DboUseOnly argument 2-145DBSpaceUsed argument 2-98DBSpaceUsedMax argument 2-98DDL commands 2-90deadlocks

number of 3-143Default argument 2-77Default rule base for TEC 2-27default to local cursor field 2-140Default value (if no rows found) field 3-63,

3-69DefaultToLocalCursor argument 2-145Delivered Latency monitor 3-38Delivered Transaction Rate monitor 3-43Delivered Transactions monitor 3-48DeliveredTransactionRate monitor CLI

syntax 3-45DeliveredTransactions monitor CLI syntax

3-50DeliveryLatency monitor CLI syntax 3-40description

shown in each reference entry 1-2desktop

using 1-5device fragment

database and transaction log sharing 2-80, 3-123

dialogsCreate a Report File, called from tasks

2-2data entry, shown in each reference

entry 1-3monitor output 1-3task output 1-3TEC, called from task 2-2

Disable NT Disk Performance Counters task 2-50

DisableDiskCounters task CLI syntax 2-51disconnected overflow pages 2-110DisconnectedOverflow argument 2-112Discover MS SQL Servers task 2-54discovering database servers 2-54DiscoverSQLSRVR task CLI syntax 2-57disk

access speeds 3-87I/O errors 3-83physical writes pending 3-97reads 3-85reads, pending 3-94space available 2-91, 2-93space used by database 3-34space used by databases 4-3space used by PeopleSoft tables 4-39space used by transaction logs 4-21space, forecasting requirements 4-6writes 3-88writes, single page 3-103

disk counters 2-50enabling 2-82

Disk Type field 2-82DISKDUMP device

as NULL device 2-69diskettes

avoiding backups on 2-63avoiding for backups 2-74using CONSOLE.EXE 2-69

DiskType argument 2-83Distributed Transaction Coordination, see

MSDTC servicedistribution databases

definition 3-41filling up unnecessarily 3-51


number of delivered transactions in 3-48

pending transactions 4-48publication databases unavailability

4-13time transactions remain in 3-50transaction delivery rate 3-38transaction flow 3-52, 3-236transaction latency 4-51transaction rate 4-44unavailable 3-33undelivered transactions in 3-233

DML commands 2-90Do Not Truncate After Backup field 2-16double quotes

use of 2-141DUMP DATABASE command 2-80Dump Options field 2-72DUMP TRANSACTION command 2-80Dump Transaction Log task 2-71dump, see backing upDumpDatabase task CLI syntax 2-66DumpDevice argument 2-67, 2-78DumpOptions argument 2-77DumpTo argument 2-67, 2-78DumpTransactionLog task CLI syntax 2-77

EEditMode argument 2-106Enable NT Disk Performance Counters task

2-82EnableDiskCounters task CLI syntax 2-83endpoint

shown in each reference entry 1-3error logs

percent full 3-138Error Number field 3-131Error Text field 3-131

Error_number argument 3-132Error_textargument 3-132ErrorNumbers argument 2-106errors

1205, logged to Windows NT event log 3-143

2540, allocation discrepancy 2-482540, response to 2-422541, response to 2-422558, during maintenance 2-48after DBCC FIX_ALL statement 2-48age in Applications 3-135forwarding SQL Server errors to

Application log 2-103, 3-123, 4-20

I/O, during disk operations 3-83in backups, reported in report file 2-69monitoring Windows NT event log for

SQL Server 3-130reported during database checkup 2-47SQL Server error log 2-103, 2-150SQL Server, reported to Windows NT

event log 2-34TSQL command, reporting 2-89Windows NT event log 2-91, 2-97Windows NT, sending to TEC 2-34

Event Group Name field 2-27event log

forwarding SQL Server errors to 2-34, 3-123

forwarding Windows NT events to TEC 2-33

logging SQL error 1205 3-143monitoring for SQL Server errors

3-130oldest Application entry 3-135percent full of Application log 3-138warnings about 2-91

event loggingWindows NT 2-91

Event Server option to configure field 2-27


event server, see TECEventGroupName argument 2-29Exclude syslogs table field 2-166ExcludeSyslogsTable argument 2-167exclusive extent locks 3-53exclusive intent locks 3-112exclusive locks 3-217exclusive page locks 3-149exclusive table locks 3-205Execute SQL task 2-86ExecuteSQL task CLI syntax 2-88extent locks

exclusive 3-53total 3-56update 3-59

Extent Locks Exclusive monitor 3-53Extent Locks Total monitor 3-56Extent Locks Update monitor 3-59ExtentLocksExclusive monitor CLI syntax

3-53ExtentLocksTotal monitor CLI syntax 3-56ExtentLocksUpdate monitor CLI syntax

3-59

Ffailed SQLExecutive tasks 3-202failed SQLServerAgent jobs 3-202fetch rate of Read Ahead Manager 3-182fill factor

indexes 2-110, 4-17, 4-34Fill factor field 2-110FillFactor argument 2-112FilterErrors argument 2-37FilterInformation argument 2-37FilterMessages argument 2-37FilterMSDTC argument 2-37FilterSQLExecutive argument 2-37

FilterSQLServerAgent argument 2-37found-pages rate of Read Ahead Manager

3-185FragLimit argument 2-44, 2-112fragmentation

indexes 4-14PeopleSoft tables 4-31rebuilding fragmented indexes 2-41,

2-109reducing to improve I/O 3-190tables 4-14tables with clustered indexes 4-17

Fragmentation monitor 4-14free buffer pool 3-18free buffers 3-18free buffers configuration option 3-8, 3-9,

3-11, 3-20Freeform SQL Numeric monitor CLI syntax

3-62, 3-64Freeform SQL String monitor 3-68FreeFormSQLString monitor CLI syntax

3-70

Ggrowth

databases 3-34GUI

using 1-5GUI names

MSSQLDatabase monitors 4-2MSSQLServer monitors 3-2tasks, list of 2-3

Hhelp

for monitors 1-5for tasks 1-5


getting from the CLI 1-6history

of backups 2-73HOLDLOCK feature

in queries 3-114, 3-117, 3-120queries 3-151, 3-154, 3-157,

3-160Host Name field 2-43Host name field 2-118Human Resources table group,PeopleSoft

4-31, 4-35, 4-39

II/O

batch write rate 3-80bottlenecks 3-96, 3-99, 3-102,

3-190CPU usage 3-27detecting incomplete 2-141disk errors 3-83disk reads 3-85disk writes 3-88log writes 3-91max writes per batch 3-77network 3-124, 3-127pagers written per batch 3-74pending reads 3-94physical read rate 3-100physical writes pending 3-97single page writes 3-103transaction rate 3-106transactions per log record 3-109

I/O Batch Average Size monitor 3-74I/O Batch Maximum Size monitor 3-77I/O Batch Write Rate monitor 3-80I/O Disk Errors monitor 3-83I/O Disk Reads monitor 3-85I/O Disk Writes monitor 3-88I/O Log Write Rate monitor 3-91

I/O Outstanding Reads monitor 3-94Read Ahead Manager, assessing I/O rate

3-190I/O Outstanding Writes monitor 3-97I/O Page Read Rate monitor 3-100I/O Single Page Write Rate monitor 3-103I/O Transaction Rate monitor 3-106I/O Transactions Per Log Record monitor

3-109Ignore server state when registering field

2-56IgnoreSRVRState argument 2-58Include object drop in schema scripts field

2-118incomplete I/O

detecting 2-141incremental backups, see transaction log,

backing up 2-15index argument 3-64, 3-70Index Name argument 4-16, 4-29Index Name field 4-15, 4-28Index name field 2-110, 2-127, 2-165indexes

and read efficiency 3-87checking page links 2-41clustered 2-114disconnected overflow pages 2-110fill factor 2-110, 4-17, 4-34fragmentation 4-14fragmented, rebuilding 2-109I/O performance, role in 3-102improving table scans 3-190maintenance 2-41non-clustered 2-114PeopleSoft, age statistics 4-35rebuilding during recovery 2-115rebuilding fragmented 2-41statistics, refreshing 2-127time since statistics updated 4-27

IndexName argument 2-112, 2-129,


2-167Insert_page lock type 3-222Insert_page-blk lock type 3-222intent locks

exclusive 3-112shared 3-115total 3-118

Intent Locks Exclusive monitor 3-112Intent Locks Shared monitor 3-115Intent Locks Total monitor 3-118IntentLocksExclusive monitor CLI syntax

3-112IntentLocksShared monitor CLI syntax

3-115IntentLocksTotal monitor CLI syntax 3-118IOBatchAverageSize monitor CLI syntax

3-74IOBatchMaximumSize monitor CLI syntax

3-77IOBatchWriteRate monitor CLI syntax

3-80IODiskErrors monitor CLI syntax 3-83IODiskReads monitor CLI syntax 3-85IODiskWrites monitor CLI syntax 3-88IOLogWriteRate monitor CLI syntax 3-91IOOutstandingReads monitor CLI syntax

3-94IOOutstandingWrites monitor CLI syntax

3-97IOPageReadRate monitor CLI syntax 3-100IOSinglePageWriteRate monitor CLI syntax

3-103IOTransactionRate monitor CLI syntax

3-106IOTransactionsPerLogRecord monitor CLI

syntax 3-109

Jjob

creating from the CLI 1-6running from the CLI 1-6scheduling from the CLI 1-6

jobsSQLServerAgent, failed 3-202

LLast argument 2-67Last database dump was greater than (##)

day(s) ago field 2-94Last transaction log dump was greater than

(##) hours ago field 2-94LastDBDump argument 2-98LastDBDumpMax argument 2-99LastTransLogDump argument 2-99LastTransLogDumpMax argument 2-99latency

replication transacitons 4-51LazyWriter

efficiency 3-103free buffers, maintaining minimum

number 3-11, 3-20max buffers scanned for unused 3-15searching for unused buffers 3-6

LE THRESHOLD % configuration option 3-114, 3-117, 3-120, 3-151, 3-154, 3-157, 3-160

LE THRESHOLD MAXIMUM configuration option 3-114, 3-117, 3-120, 3-151, 3-154, 3-157, 3-160

LE THRESHOLD MINIMUM configuration option 3-114, 3-117, 3-120, 3-151, 3-154, 3-157, 3-160

Link_page lock type 3-222Link_page-blk lock type 3-222LOAD DATABASE


used during recovery 2-115LOAD HEADERONLY 2-69, 2-80LOCK ESCALATION configuration option

3-207, 3-210, 3-213, 3-232locks

blocking processes 3-214contention 3-214contention and blocked processes

3-141deadlocks 3-143dynamic management in Version 7.0

3-222exclusive locks 3-217extent locks 3-53, 3-56, 3-59intent locks 3-112, 3-115, 3-118overloaded 3-96page locks 3-149, 3-152, 3-155,

3-158resources allocated to 3-222, 3-225,

3-229table locks 3-205, 3-208, 3-211total locks 3-220total remaining 3-227total shared locks 3-230undocumented types 3-226, 3-229undocumented, counted in total (Version

6.5) 3-222used, percent of total 3-224

LOCKS configuration option 3-221, 3-222, 3-225, 3-229

Log Space Percent Used (Database) monitor 4-18

Log Space Percent Used (Server) monitor 3-121

Log Space Used monitor 4-21LOG WRITE SLEEP configuration option

3-109LogAndData argument 2-98LogFile argument 2-10, 2-20logins

database servers 2-57

trusted connection 2-57logs

page write rate 3-91transactions per log record 3-109

LogSpacePercentUsedDB monitor CLI syntax 4-18

LogSpacePercentUsedSRVR monitor CLI syntax 3-121

LogSpaceUsed monitor CLI syntax 4-21losing data, acceptable amount 4-23losing transactions during restore 3-148

Mmaintenance

databases 2-41indexing 2-41procedure statistics 2-47rebuilding query tree 2-48single user mode 2-48

manualorganization 1-2reference entry information 1-2using online 1-4

master backupsavoiding striped devices 2-69

master database 2-91, 2-101, 2-115backing up 2-80databases 2-115example of freeform SQL monitor for

3-70recovering 2-115

Max. Severity Level field 3-131MAX_SERVER_MEMORY configuration

option 3-14Max_severity_level argument 3-132MAXIMUM ASYNC IO configuration

option 3-20, 3-74, 3-77, 3-80, 3-87, 3-90

MAXIMUM LAZYWRITE IO configuration


option 3-20memory

configured for database server 2-91Memory argument 2-97MEMORY configuration option 3-14,

3-161, 3-173, 3-176MemoryMax argument 2-98merge publish field 2-140MergePublish argument 2-145Message argument 2-159Microsoft SQL Server

host, running other critical processes on 3-14

Microsoft SQL Server version 2-91Microsoft SQL Server Version 6.5

ADSM versions supported 2-14backup history in system tables 2-73cache hit ratio and MEMORY

configuration option 3-14data and log on same device fragment

2-94device fragment usage 2-80I/O monitors 3-74, 3-77, 3-80,

3-91, 3-94, 3-97, 3-100, 3-103, 3-106, 3-109

read-ahead monitors 3-179, 3-182, 3-185, 3-188, 3-191

recovery, merging contiguous fragments 2-115

SQL Executive service 2-151total locks calculation 3-222transaction log size calculation 3-121

Microsoft SQL Server Version 7.0ADSM versions supported 2-14automatic space extension 3-37database options unique to 2-138differing system tables 2-73dynamic lock management 3-222dynamic memory allocation 3-14dynamic user connections configuration

3-238, 3-241, 3-244

procedure cache sizing 3-161replication monitor limitations 3-38,

3-43, 3-48SQLServerAgent service 2-151user connections calculations 3-243

Min. Severity Level field 3-131MIN_SERVER_MEMORY configuration

option 3-14Min_severity_level argument 3-132Monitor MSDTC Service field 3-195monitor output

shown in each reference entry 1-3Monitor SQLExecutive/SQLServerAgent

Service field 3-194Monitor SQLServer Service field 3-194MonitoredHost argument 2-45, 2-120monitoring schedule, suggested

in each reference entry 1-3monitors

adding at the CLI 1-6getting help 1-5list of, MSSQLDatabase collection 4-2MSSQLServer collection, list of 3-2NT Application Log monitor, searching

for errors 3-123starting 2-149stopping 2-155suggested monitoring schedule in each

reference entry 1-3suggested response levels in each

reference entry 1-3user-defined 3-62, 3-68

Monitors argument 2-153, 2-160monitors, by GUI name

Cache Average Free Page Scan 3-6Cache Configured Free Buffers Percent

Used 3-9Cache Hit Ratio 3-12Cache Maximum Free Page Scan 3-15Cache Number of Free Buffers 3-18Client Count 3-21


Client Count Percent Used 3-23CPU Percent Busy 3-25CPU Percent Busy Doing I/O 3-27CPU Percent Idle 3-29Data Space Percent Used (Database)

4-3Data Space Percent Used (Server) 3-34Data Space Used 4-7Database Status (Database) 4-11Database Status (Server) 3-31Delivered Latency 3-38Delivered Transaction Rate 3-43Delivered Transactions 3-48Extent Locks Exclusive 3-53Extent Locks Total 3-56Extent Locks Update 3-59Fragmentation 4-14Freeform SQL String 3-68I/O Batch Average Size 3-74I/O Batch Maximum Size 3-77I/O Batch Write Rate 3-80I/O Disk Errors 3-83I/O Disk Reads 3-85I/O Disk Writes 3-88I/O Log Write Rate 3-91I/O Outstanding Reads 3-94I/O Outstanding Writes 3-97I/O Page Read Rate 3-100I/O Single Page Write Rate 3-103I/O Transaction Rate 3-106I/O Transactions Per Log Record 3-109Intent Locks Exclusive 3-112Intent Locks Shared 3-115Intent Locks Total 3-118Log Space Percent Used (Database)

4-18Log Space Percent Used (Server) 3-121Log Space Used 4-21Network Read Rate 3-124Network Write Rate 3-127NT Application Log 3-130NT Application Log Age 3-135

NT Application Log Percent Full 3-138Number of Blocked Processes 3-141Number of Deadlocks 3-143Oldest Open Transaction (Database)

4-24Oldest Open Transaction (Server)

3-146Optimizer Statistics Age 4-27Page Locks Exclusive 3-149Page Locks Shared 3-152Page Locks Total 3-155Page Locks Update 3-158PeopleSoft Data Space Used 4-39PeopleSoft Fragmentation 4-31PeopleSoft Optimizer Statistics Age

4-35Procedure Buffers Active 3-161Procedure Buffers Total 3-164Procedure Buffers Used 3-167Procedure Cache Active 3-170Procedure Cache Size 3-173Procedure Cache Used 3-176RA Effectiveness 3-179RA Pages Fetched into Cache Per

Second 3-182RA Pages Found in Cache Per Second

3-185RA Physical Read Rate 3-188RA Slots Used 3-191Replicated Transaction Rate 4-44ReplicatedTransactions 4-48Replication Latency 4-51Service State 3-193Space Used (Table) 4-54SQL Server State 3-199SQLServerAgent Failed Jobs 3-202Suspect Database 4-59Table Locks Exclusive 3-205Table Locks Shared monitor 3-208Table Locks Total 3-211Total Blocking Locks 3-214Total Exclusive Locks 3-217


Total Locks 3-220Total Locks Percent Used 3-224Total Locks Remaining 3-227Total Locks Shared 3-230Undelivered Transactions 3-233User Connections 3-238User Connections Percent Used 3-241User Connections Remaining 3-244

Mountwait argument 2-10, 2-20Mountwait field 2-6, 2-17MS SQL Server Logon (for standard security

only) field 2-57MS SQL Server Service Pack is less than (#)

field 2-93MS SQL Server Warnings and Indicators

task 2-91MSDB database

recovering 2-116MSDTC argument 2-153, 2-160, 3-195MSDTC service 2-151

single user mode, using in 2-150starting 2-151stopping 2-158TEC events 2-35

MSDTC services 3-193MSSQLDatabase monitoring collection

list of monitors 4-2MSSQLDatabase monitoring collection, see

monitors, MSSQLDatabaseMSSQLManagerTasks library

list of tasks 2-3MSSQLServer argument 3-195MSSQLServer has not been restarted for

(##.#) days field 2-92MSSQLServer monitoring collection

list of monitors 3-2MSSQLServer service

single user mode 3-201starting 2-149stopping 2-156

MSSQLServer Service field 2-149, 2-156

MSSQLServer services 3-193

Nnetwork

bandwidth utilization (ADSM) 2-17heavy traffic 3-127read throughput 3-124throughput 3-127usage with backups 2-15write throughput 3-127

Network Read Rate monitor 3-124Network Write Rate monitor 3-127NetworkReadRate monitor CLI syntax

3-124NetworkWriteRate monitor CLI syntax

3-127NEWALLOC 2-62NoChkpt on recovery field 2-140NoChkptOnRecovery argument 2-145NoLog argument 2-78non-clustered indexes 2-114None field 2-150, 2-156Non-fatal error numbers field 2-105Notify TEC button 2-2NotifyTEC argument 2-2NoTruncate argument 2-20, 2-77NT Application Log Age monitor 3-135NT Application Log monitor 3-130NT Application Log Percent Full monitor

3-138NT disk space used is greater than (70) %

field 2-93NT Event Adapter

undoing customization 2-132NT Event configuration

backing up 2-33NT event logging is disabled field 2-93NT Event Logging task 2-103


used to monitor transaction log growth 3-123

using to monitor transaction log growth 4-20

NT Logical Disk monitors, by GUI namePercent Free Space 3-37

NT_MSDTCBase field 2-35NT_MSSQLError field 2-34NT_MSSQLInformation field 2-35NT_MSSQLMessage field 2-34NT_SQLExecutiveBase field 2-35NT_SQLServerAgentBase field 2-35NTApplicationLog monitor CLI syntax

3-132NTApplicationLogAge monitor CLI syntax

3-135NTApplicationLogPercentFull monitor CLI

syntax 3-138NTDiskSpaceUsed argument 2-97NTDiskSpaceUsedMax argument 2-97NTEventLogging argument 2-97NTEventLogging task CLI syntax 2-105null

columns accepting 2-138concatenation to resulting in null 2-139return on compares 2-138

NULL deviceand DISKDUMP device 2-69backing up to 2-69

null returns on compares 2-138nullable columns 2-138Number of Blocked Processes monitor

3-141Number of Buffers field 2-8, 2-18Number of Deadlocks monitor 3-143NumberOfBlockedProcesses monitor CLI

syntax 3-141NumberOfDeadlocks monitor CLI syntax

3-143numeric operators 3-67

OObjectDrop argument 2-119Offline argument 2-145offline databases 2-140, 3-31offline field 2-140oldest open transaction 3-146, 4-24Oldest Open Transaction (Database) monitor

4-24Oldest Open Transaction (Server) monitor

3-146OldestOpenTransactionDB monitor CLI

syntax 4-24OldestOpenTransactionSRVR monitor CLI

syntax 3-146On monitored host field 2-43, 2-118On specified host field 2-43, 2-118online help, see helpoperators

numeric 3-67return on NULL 2-138string 3-73

Optimizer Statistics Age monitor 4-27OptimizerStatisticsAge monitor CLI syntax

4-29options file

ADSM 2-7, 2-18overflow pages

disconnected 2-110Overwrite any previous MSSQL

customization field 2-35Overwrite argument 2-106Overwrite field 2-105OverwritePrevious argument 2-36

Ppage locks

exclusive 3-149shared 3-152


total 3-155update 3-158

Page Locks Exclusive monitor 3-149Page Locks Shared monitor 3-152Page Locks Total monitor 3-155Page Locks Update monitor 3-158PageLocksExclusive monitor CLI syntax

3-149PageLocksShared monitor CLI syntax

3-152PageLocksTotal monitor CLI syntax 3-155PageLocksUpdate monitor CLI syntax

3-158PARALLEL DATA SCAN capability

3-181, 3-187parallel data scan capability 3-184Parent Policy Region field 2-55ParentPolicyRegion argument 2-58Password argument 2-59Password field 2-57Path and file name field 2-118Path and name field 2-43path names

format in UNIX vs. Window NT 1-5Pause field 2-157Pause followed by shutdown field 2-157Pause followed by shutdown with no wait

field 2-157Pause timeout field 2-157Payroll table group, PeopleSoft 4-31,

4-35, 4-39PDF files

of manual 1-4PeopleSoft Data Space Used monitor 4-39PeopleSoft Fragmentation monitor 4-31PeopleSoft Optimizer Statistics Age monitor

4-35PeopleSoft Table Category field 4-32,

4-36, 4-41

PeopleSoft table groups 4-31, 4-35, 4-39PeopleSoftDataSpaceUsed monitor CLI

syntax 4-41PeopleSoftFragmentation monitor CLI

syntax 4-33PeopleSoftOptimizerStatisticsAge monitor

CLI syntax 4-37performance

buffers unused and 3-9data cache and 3-15data cache hit ratio 3-12disk counters and 2-50, 2-82fragmentation and 4-14free buffers and 3-18log write throughput 3-93pending reads 3-96tuning the data cache 3-14unused buffers and 3-6

physical I/Oread rate 3-100writes pending 3-97

physical readsrate 3-100

physical writespending 3-97

Policy Region field 2-55PolicyRegion argument 2-58ProcCache argument 2-97ProcCacheMax argument 2-97Procedure Buffers Active monitor 3-161Procedure Buffers Total monitor 3-164Procedure Buffers Used monitor 3-167procedure cache

active 3-170percent usage 3-161ratio warning 2-93size 3-164, 3-173used 3-167, 3-176

Procedure Cache Active monitor 3-170PROCEDURE CACHE configuration option

3-161, 3-164, 3-167, 3-170,


3-173, 3-176Procedure cache ratio is greater than (##) %

field 2-93Procedure Cache Size monitor 3-173Procedure Cache Used monitor 3-176ProcedureBuffersActive monitor CLI syntax

3-161ProcedureBuffersTotal monitor CLI syntax

3-164ProcedureBuffersUsed monitor CLI syntax

3-167ProcedureCacheActive monitor CLI syntax

3-170ProcedureCacheSize monitor CLI syntax

3-173ProcedureCacheUsed monitor CLI syntax

3-176processes

number of blocked 3-141publication databases

pending transactions 4-48subscription availability 2-141transaction latency 4-51transaction rate 4-44

publicationsmerge replication 2-140subscribing to 3-40

Published argument 2-145published field 2-141

Qqueries 3-100

deadlocks caused by 3-145efficiency 3-102HOLDLOCK feature 3-114, 3-117,

3-120, 3-151, 3-154, 3-157, 3-160

index statistics and 4-27

Read Ahead Manager, using 3-191reading more information than needed

3-190reducing unnecessary reads 3-87

query optimizerrefreshing statistics 2-127updating statistics 2-41

query plans 4-27, 4-38query tree

rebuilding 2-48Quiet argument 2-10, 2-21Quiet field 2-6, 2-17quoted identifier field 2-141QuotedIdentifier argument

argumentsQuotedIdentifier 2-145

quotesspecifying use of 2-141

RRA

see also READ-AHEAD MANAGERRA Effectiveness monitor 3-179RA Pages Fetched into Cache Per Second

monitor 3-182RA Pages Found in Cache Per Second

monitor 3-185RA Physical Read Rate monitor 3-188RA SLOTS PER THREAD configuration

option 3-191RA Slots Used monitor 3-191RAEffectiveness monitor CLI syntax 3-179RAPagesFetchedIntoCachePerSecond

monitor CLI syntax 3-182RAPagesFoundInCachePerSecond monitor

CLI syntax 3-185RAPhysicalReadRate monitor CLI syntax

3-188


RASlotsUsed monitor CLI syntax 3-191Read Ahead Manager

effectiveness 3-179fetch rate 3-182found rate 3-185read rate, physical 3-188

read only field 2-141ReadOnly argument 2-146read-only databases 2-141reads

disk 3-85, 3-94network 3-124physical 3-100rate, Read Ahead Manager 3-188

Reboot NT Server field 2-50, 2-83rebooting Windows NT 2-50, 2-83RebootNT Server argument 2-51RebootNTServer argument 2-84Rebuild Fragmented Indexes task 2-109Rebuild if disconnected overflow pages found

field 2-110Rebuild if fragmentation % is greater than

field 2-43Rebuild if fragmentation% greater than field

2-110RebuildIndex task CLI syntax 2-111rebuilding tables 2-115recovery

database servers 2-115databases 2-115databases in 3-31failing when database is suspect 4-61no checkpoint on 2-140rebuilding tables 2-115

Recovery Archive File field 2-118Recovery Preparation task 2-115RecoveryPrep task CLI syntax 2-119recursive triggers field 2-141RecursiveTriggers argument 2-146reference entries

authorization role 1-2CLI syntax 1-3description section 1-2endpoint information 1-3GUI data entry dialog 1-3monitor output 1-3suggested monitor response levels 1-3suggested monitoring schedule 1-3task output 1-3usage notes 1-4

reference entrystandard information in 1-2

Refresh Databases task 2-124Refresh Query Optimizer Statistics task

2-127RefreshDB task CLI syntax 2-125refreshing databases shown on the TMR

2-124RefreshStats task CLI syntax 2-128Register MS SQL Server Icon on Tivoli

Desktop field 2-55registering database servers 2-54remote machines

backing up 2-69Remove any previous MSSQL customization

field 2-132Remove argument 2-106Remove field 2-104RemoveCustomization argument 2-133Replicated Transaction Rate monitor 4-44ReplicatedTransactionRate monitor CLI

syntax 4-44ReplicatedTransactions monitor 4-48ReplicatedTransactions monitor CLI syntax

4-48Replication

Latency monitor 4-51replication

bottlenecks 3-38, 3-43, 3-51, 3-197, 3-233, 4-44, 4-48,


4-51database availability and 3-33failed jobs/tasks 3-204latency in updates 3-38merge replication publications, making

database available for 2-140publications 2-141specifying subscription availability

2-141SQLExecutive/SQLServerAgent

services 3-197transaction delivery rate 3-43transactions pending 4-48undelivered transactions 3-233update latency 3-41

ReplicationLatency monitor CLI syntax 4-51

report filebackup errors reported in 2-69transaction log backup information in

2-79warnings and indicators information

2-100Report to File button 2-2ReportFileName argument 2-2ReportHostName argument 2-2ReportToFile argument 2-2response levels, suggested

shown in each reference entry 1-3Restart Event Server field 2-28RestartServer argument 2-31RestartSRVR argument 2-96RestartSRVRMAX argument 2-96Restore configuration prior to last MSSQL

customization field 2-133Restore TEC NT Event Adapter MSSQL

task 2-132RestoreFromBackup argument 2-133RestoreTECNTEventAdapterMSSQL task

CLI syntax 2-133

Return Warnings only field 2-92rule base

default 2-27Rule Base Name field 2-26Rule Base to Copy field 2-27RuleBaseName argument 2-29Run Update Usage field 4-4, 4-8, 4-40,

4-55

SSaveArchiveFileOn argument 2-45,

2-120SaveReportFileOn argument 2-2SELECT INTO statement

allowing use of 2-141select into/bulk copy field 2-141SELECT statement

in monitors 3-62, 3-68SelectIntoBulkCopy argument 2-146server

Microsoft SQL, see Microsoft SQL Server

server, see database serverservername argument 2-2servers

ADSM 2-13, 2-15, 2-17, 2-22rebooting Windows NT 2-50SQL Agent server in ADSM 2-13TEC, configuring 2-25TEC, customizing 2-33TEC, restarting 2-28, 2-32TMR 2-32TMR, contention problems 2-54TMR, product on 2-25

Service Pack version 2-91Service State monitor 3-193ServicePack argument 2-96ServicePackMin argument 2-96


servicesMSDTC 2-150, 3-193MSDTC, starting 2-151MSDTC, stopping 2-158MSSQLServer 3-193MSSQLServer, starting 2-149MSSQLServer, stopping 2-156SQLExecutive 3-193, 3-202SQLExecutive, starting 2-151SQLServerAgent 3-193, 3-202SQLServerAgent, starting 2-151starting on database server 2-149

ServiceState monitor CLI syntax 3-195Set and Retrieve Database Options task

2-137shared intent locks 3-115shared locks, total 3-230shared page locks 3-152shared table locks 3-208shrinking databases and logs automatically

2-139ShTab_ExIntent lock type 3-222ShTab_ExIntent-blk lock type 3-222SHUT DOWN 2-53Shutdown field 2-156Shutdown Message field 2-157Shutdown with no wait field 2-157single page writes 3-103single quotes

use of 2-141single user field 2-141single user mode 3-201

current users 2-148databases, for maintenance 2-48during maintenance 2-48SQLExecutive not started in 2-150updating space usage info 2-164

SingleUser argument 2-146single-user mode for databases 2-141size

procedure cache 3-173sp_altermessage stored procedure 2-107sp_distcounters stored procedure 3-38,

3-43, 3-48, 3-233sp_lock stored procedure 3-55, 3-58,

3-61sp_recompile stored procedure 2-48,

2-130sp_spaceused stored procedure 2-164space usage

databases 3-34NT Logical Disk monitors 3-37

space usage statistics 2-41Space Used (Table) monitor 4-54SpaceUsedTable monitor CLI syntax 4-56Specified argument 2-67SpecifiedHost argument 2-45, 2-120Specify backup device (logical name or

temporary device) field 2-63, 2-73

SQL Agent 2-17SQL Agent server in ADSM 2-13SQL DB-LIBRARY, used in ADSM 2-13SQL Password field 2-7, 2-17SQL Secure field 2-16SQL Server error log 2-103, 2-150

forwarding errors to Windows NT event log 3-123

SQL Server State monitor 3-199SQL Statement field 3-63, 3-69SQL statements

DBCC CHECKCATALOG 2-41DBCC CHECKDB 2-41, 2-62DBCC CHECKIDENT 2-41DBCC DBREINDEX 2-111DBCC FIX_AL 2-42, 2-48DBCC NEWALLOC 2-41DBCC UPDATEUSAGE 2-41,

2-168, 2-169, 3-35, 4-4, 4-8, 4-40, 4-55


SELECT INTO 2-141UPDATE STATISTICS 2-41using to define monitors 3-62, 3-68

SQL User field 2-7, 2-17SQL_select_statement argument 3-70SQLExecutive

TEC events 2-35SQLExecutive argument 2-152, 2-159SQLExecutive service 2-150, 2-151,

2-158, 3-202single user mode 2-150starting 2-151tasks, failed 3-202

SQLExecutive services 3-193SQLExecutive/SQLServerAgent argument

3-195SqlPwd argument 2-9, 2-19SQLSecure argument 2-9, 2-20SQLSecure field 2-6SQLServerAgent

TEC events 2-35SQLServerAgent argument 2-152, 2-160SQLServerAgent Failed Jobs monitor

3-202SQLServerAgent service 3-193, 3-202

jobs, failed 3-202starting 2-151

SQLServerAgentFailedJobs monitor CLI syntax 3-202

SQLServerState monitor CLI syntax 3-199SqlUser argument 2-9, 2-19SQLWarnings task CLI syntax 2-95Standard argument 2-83Standard field 2-82Start in normal mode field 2-150Start in single user mode and connect field

2-150Start in single user mode but do not connect

field 2-150Start MS SQL Server Services and TME

Monitors task 2-149starting

database servers 2-149monitors 2-149

StartMode argument 2-152StartServMon task CLI syntax 2-151statements

DBCC NEWALLOC 2-48statistics

backing up 2-71database objects 2-18for backups 2-61index, time since update 4-27network throughput 3-127on values in columns, auto-updating

2-139on values in columns, specifying 2-139query optimizer 2-127space usage 2-41

Stop field 2-157Stop MS SQL Server Services and TME

Monitors task 2-155Stop MSDTC field 2-158Stop Server and Database Monitors field

2-158Stop SQLExecutive/SQLServerAgent field

2-158StopMode argument 2-159stopping

database servers 2-155monitors 2-155

StopServMon task CLI syntax 2-158Stored Procedure Archive field 2-43stored procedures

archive 2-43cache taken by 3-163, 3-166,

3-169, 3-172, 3-178run during maintenance 2-47sp_altermessage 2-107sp_distcounters 3-38, 3-43, 3-48,

3-233


sp_lock 3-55, 3-58, 3-61sp_recompile 2-48, 2-130sp_spaceused 2-164

string operators 3-73Striped argument 2-83Striped disk set field 2-82striped disks

avoiding for master backup 2-69backing up 2-63, 2-73performance counters 2-82

Subscribed argument 2-146subscribed field 2-141subscriber argument 3-40, 3-45, 3-50,

3-235subscriber databases

definition 3-41latency in updating 3-41transaction delays 4-44transactions not delivered to 3-233unavailability effect on distribution

databases 4-13unavailable 3-33, 3-42

Subscriber Name field 3-39, 3-44, 3-49, 3-234

subscriptionsallowing 2-141

suspect database 3-31Suspect Database monitor 4-59suspect databases 4-59SuspectDatabase monitor CLI syntax 4-59sysalerts table 2-116SYSBACKUPHISTORY system table

system tablesSYSBACKUPHISTORY 2-80

SYSBACKUPHISTORY table 2-73syscharsets table 2-115sysconfigures table 2-115sysdatabases table 2-115sysdevices table 2-116sysindexes system table 2-164

sysindexes table 2-168syslanguages table 2-116syslogins table 2-116syslogs table 2-48, 2-164, 2-166,

2-167, 2-169, 3-121, 4-7, 4-18, 4-21, 4-39

sysmessages table 2-108, 2-116sysnotifications table 2-116sysoperators table 2-116sysprocedures system tables 2-48sysremotelogins table 2-116sysservers table 2-116systasks table 2-116system tables

checking inconsistencies 2-41saving during recovery 2-115sysindexes 2-164, 2-168syslogs 2-48, 2-164, 2-166,

2-167, 2-169, 3-121, 4-7, 4-18, 4-21, 4-39

sysmessages 2-108sysprocedures 2-48

Ttable locks

exclusive 3-205shared 3-208total 3-211

Table Locks Exclusive monitor 3-205Table Locks Shared monitor 3-208Table Locks Total monitor 3-211Table Name argument 4-16, 4-29, 4-56Table Name field 4-15, 4-28, 4-55Table name field 2-109, 2-127, 2-164TableGroup argument 4-33, 4-37, 4-41TableLocksExclusive monitor CLI syntax

3-205TableLocksShared monitor CLI syntax


3-208TableLocksTotal monitor CLI syntax 3-211TableName argument 2-112, 2-129,

2-166tables

checking with DBCC statements 2-41fragmentation 4-14locks 3-205, 3-208, 3-211non-contiguous reads and performance

4-14PeopleSoft 4-31, 4-35, 4-39read efficiency 3-87rebuilding 2-115rebuilding indexes 2-109scans, improving 3-190statistics, refreshing 2-127system, see also system tables 3-121user-defined 2-168

tabular data stream, see TDStar file

location, after database maintenance 2-48

task outputshown in each reference entry 1-3

tasksgetting help 1-5list of 2-3MS SQL Server Warnings and Indicators,

used with Data Space Used monitor 4-10

Notify TEC button 2-2output, sending to a file 2-2Report to File button 2-2running from the CLI 1-6TEC, sending messages to 2-2

tasks, by GUI nameADSMFullBackup 2-5ADSMIncBackup 2-15ConfigureTECMSSQL 2-25Customize TEC NT Event Adapter

MSSQL 2-33

Database Check-up and Tune-up 2-41Disable NT Disk Performance Counters

2-50Discover MS SQL Servers 2-54Dump Transaction Log 2-71Enable NT Disk Performance Counters

2-82Execute SQL 2-86MS SQL Server Warnings and

Indicators 2-91NT Event Logging 2-103Rebuild Fragmented Indexes 2-109Recovery Preparation 2-115Refresh Databases 2-124Refresh Query Optimizer Statistics

2-127Restore TEC NT Event Adapter

MSSQL 2-132Set and Retrieve Database Options

2-137Start MS SQL Server Services and TME

Monitors 2-149Stop MS SQL Server Services and TME

Monitors 2-155Update Space Usage Information

2-164TDS

read rate 3-124write rate 3-127

TECdefault rule base 2-27NT Event Adapter, undoing

customization 2-132NT Event configuration 2-33server, configuring 2-25server, customizing 2-33server, restarting 2-28, 2-32TEC dialog called from tasks 2-2

TEC dialog called from tasks 2-2tecad_nt.conf file

backing up 2-39updating 2-135


tecad_nt.fmt filebacking up 2-39updating 2-135

TECServer argument 2-2TempDB is in RAM field 2-93TempDBInRam argument 2-97The MS SQL Monitors field 2-151threads

worker 3-240Timeout argument 2-159Tivoli commands

for this product 1-5Tivoli Managed Region, see TMRTivoli Manager for SQLServer

connecting to database server 3-199TME MS SQL Monitors field 2-158tmersrvd

login across TMR boundaries 2-32TMR

desktop, discovering database servers 2-54

login names 2-32policy region, database server in 2-55refreshing databases shown 2-124server 2-25, 2-32server, contention 2-54

torn page detection 2-141torn page detection field 2-141TornPageDetection argument 2-146total blocking locks 3-214Total Blocking Locks monitor 3-214total exclusive locks 3-217Total Exclusive Locks monitor 3-217total extent locks 3-56total intent locks 3-118total locks 3-220

undocumented lock types counted 3-222

Total Locks monitor 3-220Total Locks Percent Used monitor 3-224

total locks remaining 3-227Total Locks Remaining monitor 3-227total locks, percent used 3-224total page locks 3-155Total Shared Locks monitor 3-230total table locks 3-211TotalBlockingLocks monitor CLI syntax

3-214TotalExclusiveLocks monitor CLI syntax

3-217TotalLocks monitor CLI syntax 3-220TotalLocksPercentUsed monitor CLI syntax

3-224TotalLocksRemaining monitor CLI syntax

3-227TotalSharedLocks monitor CLI syntax

3-230transaction logs

backing up 2-15, 2-23, 2-71backing up using ADSM 2-5backing up when database unavailable

2-80backup 2-80date of last dump 2-91growth and NT Event Logging task

3-123inactive part 2-16last backup time warning 2-94sharing device file with data 2-91sharing device fragment with database

2-80, 3-123shrinking automatically 2-139space used 4-21space used by 3-121space used versus dump frequency

4-23space used, percent 4-18transaction, oldest open 3-146, 4-24truncating 2-71truncating upon checkpointimg 2-142


when to back up 2-81transactions

batch, number configured for 3-46delays in reaching subscriber database

3-38delivered, number of 3-48lock contention and throughput 3-142logged to disk 3-93losing 3-148losing to deadlocks 3-143not completed 3-93oldest open 3-146per log record 3-109rate 3-106remaining in database too long 3-51replicated, avoiding backlog 3-197replication latency 4-51replication rate 4-44replication, monitoring 3-41replication, pending 4-48replication, rate of 3-43sizing to minimize lock contention

3-216target rate 3-50throughput 3-93undelivered 3-233when subscriber databases unavailable

4-13TRANSACT-SQL see TSQLtriggers

recursive, enabling 2-141trunc. log on chkpt field 2-142Truncate (use this option when log is full)

field 2-73Truncate argument 2-9Truncate field 2-73Truncate Log After Backup field 2-6TruncateOnly argument 2-77TruncLogOnChkpt argument 2-147trusted connection

database server logins 2-57

TSQLSELECT statement, in monitors 3-62,

3-68TSQL argument 2-88TSQL Command field 2-87TSQL statement 2-86

version dependency 2-90tuning the data cache 3-14, 3-104

Uundelivered transactions 3-233Undelivered Transactions monitor 3-233UndeliveredTransactions monitor CLI

syntax 3-235undocumented lock types 3-222, 3-226,

3-229update latency in replication 3-41update page locks 3-158Update Space Usage Information task

2-164UPDATE STATISTICS statement 2-41update, extent locks 3-59UpdateUsage argument 4-5, 4-9, 4-41,

4-56UpdateUsage task CLI syntax 2-166usage notes

shown in each reference entry 1-4Use same device as last backup field 2-62,

2-73used procedure cache 3-167, 3-176user connections

number 3-238percent used 3-241remaining 3-244see also clients

USER CONNECTIONS configuration option 3-240, 3-243, 3-246

User Connections monitor 3-238


User Connections Percent Used monitor 3-241

User Connections Remaining monitor 3-244

User Name field 2-57UserConnections monitor CLI syntax 3-238UserConnectionsPercentUsed monitor CLI

syntax 3-241UserConnectionsRemaining monitor CLI

syntax 3-244Username argument 2-58

VValidate database integrity field 2-62ValidateDB argument 2-66value argument 3-64, 3-70Version 6.5, see Microsoft SQL Server

Version 6.5Version 7.0, see Microsoft SQL Server

Version 7.0 2-14versions

database server 2-93Microsoft SQL Server 2-73, 2-91Service pack 2-91

WWarning options field 2-92warnings

log and data on same device fragment 2-101

logging disabled 2-97specifying ANSI-92 standard 2-139transaction log last backup 2-94

WarnOnly argument 2-96wcrtjob command 1-6wexectask command 1-6

wgettaskhelp command 1-6Window NT

event log, SQL Server errors in 2-34Windows NT

Administrators group 2-53, 2-85event logging 2-91rebooting 2-50, 2-83

Windows NT event log 3-143error forwarding from SQL Server error

log 3-123forwarding events to TEC 2-33monitoring Application log for SQL

Server errors 3-130oldest entry in Applications 3-135percent full of Application log 3-138specifying errors to log 2-103SQL Server error forwarding to

Application log 4-20warning when logging disabled 2-97

worker threads 3-240writes

disk 3-88, 3-103network 3-127

wrunjob command 1-6wruntask command 1-6wschedjob command 1-6
