Microsoft SQL Server 7.

0 and SQL Server 2000 Management Pack Guide
Microsoft SQL Server 7.0 and SQL Server 2000 Management Pack
Refresh for Microsoft Operations Manager 1.0 SP1
Published: November 2003 Acknowledgements
Program Managers: Tom Keane, Steve Wilson Writer: Brenda Carter Technical Reviewer: James Hedrick Editor: Scott Kendall

Recommended Knowledge and Skills

2

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. ©2003 Microsoft Corporation. All rights reserved. Active Directory, Microsoft, SQL Server, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Contents

iii

Contents

Recommended Knowledge and Skills.....................................................1 Overview of the Microsoft SQL Server Management Pack Refresh.........1 Deploying the Microsoft SQL Server Management Pack Refresh............4 Operations Tasks..................................................................................33 Recommendations for the Network Operations Desk...........................36 Troubleshooting...................................................................................36 Reference.............................................................................................37

Recommended Knowledge and Skills

1

Recommended Knowledge and Skills
To deploy and operate the Microsoft® SQL Server™ Management Pack Refresh, it is recommended that you possess the following knowledge and skills: • • A working knowledge of the Microsoft Operations Manager 2000 (MOM) monitoring features. Be familiar with the recommended process for deploying Management Packs as described in Chapter 7, “Deploying Management Packs,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide. Have an administrative and working knowledge of Microsoft SQL Server 7.0 and SQL Server 2000. Have a working knowledge of databases and Transact-SQL.

• •

Overview of the Microsoft SQL Server Management Pack Refresh
The Microsoft SQL Server Management Pack Refresh for MOM SP1 provides both proactive and reactive monitoring of Microsoft SQL Server 7.x and Microsoft SQL Server 2000. This Management Pack is provided as a Web download upgrade for existing users of the Microsoft SQL Server Management Pack and provides additional monitoring of SQL Server functionality in the following key areas: • • • • • • • Microsoft SQL Server clusters Microsoft SQL Server 2000 named instances Database and database transaction log free space monitoring Microsoft SQL Server service monitoring Local and remote connectivity monitoring Database health monitoring Support for Microsoft SQL Server named instance and clustered databases with MOM SP1 reporting

2 Recommended Knowledge and Skills • • An easy-to-understand and navigate processing rule group hierarchy Public views of key operating system and SQL Server performance metrics .

Recommended Knowledge and Skills 3 Microsoft SQL Server Management Pack Monitoring Scenarios The Microsoft SQL Server Management Pack monitors key data points to ensure the availability of SQL Server and related components as well as reliable day-to-day operation of SQL Server. SQL Server Availability and SQL Server Named Instance Availability • • • • • • • • • • SQL Server service monitoring SQL Server local connectivity monitoring Database and transaction log space monitoring Database health monitoring SQL Server remote connectivity monitoring SQL Server port bind errors Collection of SQL Server Windows® event log events SQL Server Cluster Availability SQL Server clustered SQL service availability SQL Server Agent Availability SQL Server Agent availability Monitor failed SQL Server agent jobs MSDTC • • • • • • • • • SQL Server MSDTC errors Performance Deadlocks and blocks Excessive user connections Pages writes and allocations Active transactions Average wait time DBCC logical scan bytes per second Full scans per second Memory grants pending .

. It is essential that previous versions of the Management Pack are installed prior to installing this Management Pack.4 Recommended Knowledge and Skills Reporting • • • • • • • • • • • • • • • • Replication metrics Backup device throughput Lock performance Log performance SQL Server critical errors Security Trusted and non-trusted security configurations Collection of failed SQL Server login attempts Backups Failed full database backups Failed incremental database backups Database device throughput Successful database backups Replication Snapshot replication Merge replication Transactional replication Replication components Replication agents running Deploying the Microsoft SQL Server Management Pack Refresh Upgrading the Management Pack The Microsoft SQL Server Management Pack Refresh is an upgrade of existing versions of the Management Pack.

Select the desired options for backing up the previous version of the SQL Server Management Pack. review the Purpose section of the knowledge base content. 7. 6. 3. and then click Next. and then click Import Management Pack. 5.Recommended Knowledge and Skills 5 The upgrade process replaces the existing SQL Server Management Pack. To verify that the upgraded SQL Server Management Pack appears in the MOM Administrator console 1. Click Finish. In the right pane. navigate to Rules. 2. and then click Commit Configuration Change. . Processing Rule Groups. You should also perform a full database backup prior to upgrading this Management Pack. Verify that Replace Existing Management Pack is selected. and then verify that the last sentence in this section lists a build number of 1334 or later. 4. Right-click Rules. Enter the path to the Microsoft SQL Server. All reports continue to work as is. Right-click Processing Rule Groups. if you have made customizations to existing rules in a previous version of the SQL Server Management Pack.akm file or browse to and select this file. Therefore. In the MOM Administrator console. 8. and then click Microsoft SQL Server. if required. This allows you to revert to the previous Management Pack. commit the new configuration changes manually to ensure that agents receive the new SQL Server Management Pack rules. This updated Management Pack includes significant changes to the structure of the existing Management Pack hierarchy and relocates a large number of rules. In the MOM Administrator console. 2. Verify that the Backup existing Management Pack on upgrade check box is selected. it is recommended that you copy these customized rules to a dedicated Management Pack for the upgrade process. Click Next. After upgrading the SQL Server Management Pack. The Import Management Pack wizard in MOM allows you to perform a backup of the previous version of the SQL Server Management Pack. In the MOM Administrator console. The best practice is to leave the Backup existing Management Pack on upgrade check box selected. To upgrade the SQL Server Management Pack 1. 2. Note No changes are made to existing SQL Server Management Pack reports. To commit configuration changes 1. navigate to Rules. navigate to Rules.

To enable reporting.0 Report Collection Rules\Event Processing Rules \SQL Server 7. Note Not all reporting processing rules are available for both SQL Server 7. Table 1 Processing Rules That Gather Data for Capacity Planning Reports Report Capacity Planning — SQL Server Backup Device Capacity Planning by Day Processing Rule Device Throughput Bytes/sec . no data is collected for reporting. Also.6 Recommended Knowledge and Skills Setting Up Reporting By default.0 Report Collection Rules\Performance Processing Rules SQL Server 7.0\SQL Server 7. Enabling Dependent Rules The processing rules that collect data for reporting are listed in the following locations. SQL Server 2000 • • • • \SQL Server 2000\SQL Server 2000 Report Collection Rules\Event Processing Rules \SQL Server 2000\SQL Server 2000 Report Collection Rules\Performance Processing Rules \SQL Server 2000\Server Performance Collection\Replication Performance Collection\Event Processing Rules \SQL Server 2000\Server Performance Collection\Replication Performance Collection\Performance Processing Rules \SQL Server 7. see the “Reports” section later in this guide. The following table lists the processing rules that must be enabled for each report.0 and SQL Server 2000.0 • • To collect the data that is used by reports. the processing rules that collect the data for reports must be enabled. you must enable the associated processing rules. This section lists the processing rules that need to be enabled and includes setup for the following reporting scenarios: • • Reporting for clustered databases Reporting for named instances on SQL Server 2000 For a list of reports that are included in the SQL Server Management Pack Refresh.0\SQL Server 7. report names in some processing rule groups are preceded by Report Collection —. This prevents unnecessary database growth.

sqlserv Analysis Total Server Memory Buffer Cache Hit Ratio Free Buffers (SQL Server 2000 only) Lazy Writes/Sec Readahead Pages/Sec Performance Analysis — SQL Server Merge Replication Performance Analysis Replication Merge-Conflicts/sec Replication Merge-Downloaded Changes/sec Replication Merge-Uploaded Changes/sec Replication Database Pending Xacts Replication Database Trans.sqlserv SQL Server Memory Performance Private Bytes . Rate Replication Snapshot:Delivered cmds/sec Replication Snapshot:Delivered Performance Analysis — SQL Server Overall Replication Performance Analysis Performance Analysis — SQL Server Snapshot Replication Performance Analysis .Recommended Knowledge and Skills 7 Capacity Planning — SQL Server User Connections by Day Capacity Planning — SQL Server User Connections by Peak Hours Operations — SQL Server Critical Events Operations — SQL Server Critical Events Trend by Day Performance Analysis — SQL Server Distribution Replication Performance Analysis Performance Analysis — SQL Server Lock Performance Analysis Performance Analysis — SQL Server Log Performance Analysis Performance Analysis — SQL Server Logreader Replication Performance Analysis User Connections User Connections SQL Server Critical Events SQL Server Critical Events Replication Dist:Delivered Cmds/sec. Replication Dist:Delivered Trans/sec Replication Dist:Delivery Latency Lock Requests/sec Lock Waits/sec Number of Deadlocks/sec Log Flushes/sec Log Flush Wait Time Log Flush Waits/sec Logreader:Delivered Cmds/sec Logreader:Delivered Trans/sec Logreader:Delivery Latency Performance Analysis — Page Faults/sec .

8 Recommended Knowledge and Skills Trans/sec .

2. As part of the service check functionality. By default. 4. To add virtual server names to the MS SQL Server 2000 computer group 1. and then enter the virtual server name. Processing Rules Service monitoring and local connectivity rules are listed in the following locations: • • \SQL Server 2000\SQL Server 2000 Health and Availability Monitoring\Event Processing Rules\SQL Server Service Availability \SQL Server 7. On a server with multiple instances of SQL Server installed. To report against clustered servers. and then click Add. Click OK. Right-click the MS SQL Server 2000 computer group. navigate to Rules. each instance is queried to ensure that all appropriate services are running and functional. the virtual server name must be added to the MS SQL Server 2000 computer group. and it does not generate an alert if a clustered node is passive (and the SQL Server services are not running).0 Health and Availability Monitoring\Event Processing Rules\SQL Server Service Availability . by default. 3. 5. Click the Included Computers tab. enable the following processing rule: • \Microsoft SQL Server\SQL Server 2000\Report Collection Rules\Event Processing Rules\Named Instance Discovery (24 hours) Service Monitoring and Local Connectivity The SQL Server Management Pack Refresh monitors the availability of critical SQL Server services such as the SQL Server service. Service monitoring and local connectivity is checked every five minutes. and then click Properties. select Equals. A list of the installed SQL Server instances on each server is collected by a script every 24 hours. To configure reporting for named instances. On the Computer menu.0\SQL Server 7. and then Apply.Recommended Knowledge and Skills 9 Reporting for Clustered Databases The SQL Server Management Pack Refresh supports reporting against clustered servers. the SQL Agent service. and optionally the Full Text Search service. the SQL Server Management Pack also monitors the availability of SQL Server for connections by querying the server for data. In the MOM Administrator console. The service check functionality is fully named instance and cluster aware. Reporting for Named Instances on SQL Server 2000 The SQL Server Management Pack Refresh supports reporting against named instances of SQL Server. Computer Groups. this script is disabled.

rather than disabling any of the remaining service availability processing rules. The best practice for modifying these service availability monitoring settings is to adjust the script parameters in the SQL Server Service Availability processing rule. descriptions.10 Recommended Knowledge and Skills The following table lists the service availability processing rules. and default states. Table 2 SQL Server Service Availability Processing Rules Processing Rule SQL Server Service Availability SQL Server Service Availability — Connection Failure SQL Server Service Availability — SQL Server Agent service not running SQL Server Service Availability — SQL Server Full Text Search not running SQL Server Service Availability — SQL Server service not running Default Value Enabled Enabled Enabled Enabled Enabled Scripts While there are five SQL Server service availability processing rules. the first of these rules (SQL Server Service Availability) stores the script and executes the script parameters for service availability monitoring. the scripts continues to run but the alerts are not generated. If you disable any of the remaining service availability processing rules without disabling the script responses associated with those rules. The following table lists the script parameters. Table 3 SQL Server Service Availability Script Parameters Script Parameter CheckSQLAgent Description Default Value Logs a warning event when the SQL Enabled Agent service is not running Enabled CheckSQLConnectio Logs an error event when n SQL Server local connectivity cannot be established CheckSQLServer CheckSearch InformationEvent Logs an error event when the SQL Server service is not running Enabled Logs a warning event when full text Disabled search is not available Logs an information event each time the script runs Disabled .

Right-click the rule. 2.0\SQL Server 7. modify the script responses by selecting a script. navigate to the SQL Server Service Availability processing rule. the default configuration effectively monitors the health of SQL Server. 5. commit the configuration changes to apply the changes to agent computers.Recommended Knowledge and Skills 11 Customization SQL Server service availability monitoring can be customized to modify the behavior to only check some services and connectivity. the best practice is to not change the default configuration.0 Health and Availability Monitoring\Event Processing Rules\SQL Server Database Space Analysis The following table lists the database space analysis processing rules. and then Apply. Select the rule. However. and then click Edit Script Parameters. 3. 4. and then click Edit. In the MOM Administrator console. click OK. To customize SQL Server service monitoring 1. Processing Rules The database space analysis processing rules are listed in the following locations: • • \SQL Server 2000\SQL Server 2000 Health and Availability Monitoring\Event Processing Rules\SQL Server Database Space Analysis \SQL Server 7. Table 4 SQL Server Service Availability Processing Rules Processing Rule SQL Server Database Space Analysis SQL Server Database Space Analysis — Database space error SQL Server Database Space Analysis — Database space warning SQL Server Database Space Analysis — Log file space Default Value Enabled Enabled Enabled Enabled . Granular thresholds can be defined based on the role of the databases. Database Space Analysis and Thresholds The SQL Server Management Pack monitors the space of all databases and transaction logs. and then click the Response tab. Therefore. In the Script parameters box. After modifying script responses. After modifying the script responses.

12 Recommended Knowledge and Skills error SQL Server Database Space Analysis — Log file space warning Enabled .

and files. and the default states. the first of these rules (SQL Server Database Space) stores the script responses for database space monitoring. Table 5 SQL Server Service Availability Script Parameters Script Parameter DBErrorLevel DBWarningLevel LogErrorLevel Database General databases General databases General Transaction logs Event Severity Error Warning Error Warning Error Warning Error Threshold Value 100 MB 200 MB 75 MB 150 MB 15 MB 30 MB 15 MB Default Value Enabled Enabled Enabled Enabled Enabled Enabled Enabled LogWarningLeve General Transaction l logs SysDBErrorLevel System Databases (MSDB and Master) SysDBWarningL evel System Databases (MSDB and Master) SysLogErrorLeve System Transaction l Logs (MSDB and Master) SysLogWarningL evel TempDBErrorLe vel TempDBWarnin gLevel TempLogErrorLe vel TempLogWarnin gLevel System Transaction Logs (MSDB and Master) TempDB TempDB Warning 30 MB Enabled Error Warning 100 MB 200 MB 75 MB 150 MB Enabled Enabled Enabled Enabled TempDB Transaction Error Logs TempDB Transaction Warning Logs Monitoring for Free Space Database and transaction log space monitoring intelligently monitors free space and takes into account database automatic growth.Recommended Knowledge and Skills 13 Scripts While there are five SQL Server database space processing rules. such as the System Databases and the TempDB databases. If the indicated database is General. The Model database is excluded from space monitoring. multiple file groups. The free space check runs . the script is applied to all databases except those specifically called out in the table. the database to which they are applied. The following table lists the script parameters. the threshold settings.

and checks each installed database on the server. Reporting for Databases That Are Configured to Automatically Grow When checking the free space. By default. modify the script responses by selecting a script. if required. see the “Excluding Databases from Monitoring” section later in this guide. For more information. and then click Edit. navigate to the SQL Server Database Space Analysis processing rule. If you are customizing thresholds. Right-click the rule. each database and transaction log file group and associated file is enumerated. Customizing Thresholds The database and transaction log space monitoring thresholds can be customized. it is recommended that you work with database administrators to determine the appropriate warning and error threshold levels. In the Script parameters box. The public views are in the following location: • Monitor\Public Views\Microsoft SQL Server\SQL Server 2000\Server Resource Utilization\Disk Capacity % Free Space Free Megabytes The following disk space views are provided: • • Both of these views assist in determining whether sufficient free space is available on the disk subsystem. Excluding Databases from Monitoring Individual databases can be excluded from monitoring. When checking the database. the space thresholds do not require any customization. In the MOM Administrator console. 3. The SQL Server Management Pack includes two public views that help monitor disk space. by default. . 5. the SQL Server Management Pack does not generate warnings or errors for these databases. and then Apply. each file is checked for the Automatically grow file option. 4. Combining Database Space Monitoring with Disk Space Monitoring It is recommended that you use database and transaction log free space monitoring in combination with disk space monitoring to ensure that databases that are set to automatically grow have sufficient disk space as they grow. After modifying script responses. If this option is configured. and then click Edit Script Parameters.14 Recommended Knowledge and Skills every hour. Select the rule. 2. To customize database space analysis monitoring 1. click OK. and then click the Response tab.

.Recommended Knowledge and Skills 15 After modifying the script responses. commit the configuration changes to apply the changes to agent computers.

To check for remote connectivity. however. the SQL Server Management Pack runs a timed user-defined Transact-SQL remote connectivity script on computers that are members of the following computer groups: • • MS SQL Server 2000 Client Side Monitoring Microsoft SQL Server 7. Specifying multiple remote client computers is useful for checking connectivity from different locations across a network.16 Recommended Knowledge and Skills Remote Connectivity Monitoring The SQL Server Management Pack provides a simple way to verify remote connectivity to SQL Server and to verify that users can successful connect to remote SQL Server databases. This feature monitors the availability of SQL Server by querying the server remotely from client computers that you designate.x Client Side Monitoring The script is run against servers listed in the SQL remote connectivity processing rule. While other monitoring tools do not verify that the network stack of a server is functioning or that other network devices between the server and the end user are functioning. If the script fails to execute successfully or takes too long to execute. alerts are generated. Remote connectivity checking requires that Structured Query Language-Distributed Management Objects (SQL-DMO) components be installed on the designated remote client. each client computer checks for connectivity on all servers that are listed in the SQL remote connectivity processing rule. the SQL Server Management Pack Refresh provides client-side monitoring of remote SQL Server databases. You can meet this requirement by either installing SQL Server or SQL Server client tools on designated remote client computers. You can designate multiple remote client computers. .

Table 6 SQL Server Client-Side Monitoring Processing Rules Processing Rule SQL Server Remote Connectivity SQL Server Remote Connectivity — Execution Failure SQL Server Remote Connectivity — Execution Time Warning Default Value Enabled Enabled Enabled .Recommended Knowledge and Skills 17 The following figure highlights the two-step process for remote connectivity checking.0\Client Side Monitoring\Event Processing Rules\SQL Server Remote Connectivity The following table lists the client-side monitoring processing rules. Figure 1 SQL Server remote connectivity check Processing Rules The client-side monitoring processing rules are listed in the following locations: • • \SQL Server 2000\Client Side Monitoring\Event Processing Rules\SQL Server Remote Connectivity \SQL Server 7.

18 Recommended Knowledge and Skills .

Enabled By default. Default Value Disabled DatabaseName The database to run the query against. Server\Instance10). the first of these rules (SQL Server Remote Connectivity) stores the script parameters for remote connectivity monitoring. Adding designated client computers to the appropriate computer group. Disabled Enabled Configuring Client Monitoring of Remote Connectivity Client monitoring of remote connectivity is configured by: • • Installing either SQL Server or SQL Server client tools on the designated client computers. the database is set to Master. Table 7 SQL Server Service Availability Script Parameters Script Parameter CheckInstances Description A comma-separated list of remote databases to connect to.Recommended Knowledge and Skills 19 Scripts While there are several SQL Server remote connectivity processing rules.01. If the query takes longer than the specified time to execute. Enabled ExecutionTimeAl The acceptable time for the specified ert query to execute. The default value is 5 seconds. according to the SQL Server version: • . InformationEven t Query Logs an information event each time the script runs. for example 0. The default query is SELECT GETDATE. Add the designated client computers to the same configuration group that you are using to monitor remote connectivity. The Transact-SQL query that is run on the designated client computer to check connectivity to SQL Server databases specified in the CheckInstances script parameter. descriptions. Installing a MOM agent on the designated client computers. and default states for the SQL Server Remote Connectivity processing rule. an alert is raised. This list might include only computer names (for a default instance) or a computer and instance name (for example. The following table lists the script parameters. This number can be a decimal number.

20 Recommended Knowledge and Skills • • MS SQL Server 2000 Client Side Monitoring MS SQL Server 7.x Client Side Monitoring .

and then click OK. 2. 5. and then click Edit. Alerts The results of the query determine the alerts that are generated: Alert – The query failed to execute. To check for connectivity to a named instance. In the Value field. After modifying script responses. and then click Properties. and then OK. After modifying the computer group membership and script responses. 4. click OK. To add computers to the MS SQL Server client-side monitoring computer groups 1. To check for connectivity to a default instance. Click the Responses tab. Adding SQL Server computers and instances to the SQL Server remote connectivity processing rule. Warning – The query executed outside the acceptable time threshold. select SQL Server Remote Connectivity. 3. enter only the server name. In the Script parameters box. and then click Event Processing Rules. commit the configuration changes to apply the changes to agent computers. Right-click the SQL Server Remote Connectivity processing rule. and then Apply. In the MOM Administrator console. Click the Included Computers tab. Click Add to add computers. and then click Properties. navigate to the Client Side Monitoring processing rule group. Click Apply. 2. enter the server name and instance name by using the following format: server_name\instance_name. select CheckInstances. add computer criteria. enter a comma-separated list of instances to connect to. .Recommended Knowledge and Skills 21 • • Ensuring that the MOM service account on the designated client computer has the appropriate permissions to connect to the SQL Server computers. 6. Computer Groups. and then click OK. and then click Edit Script Parameters. Right-click the appropriate computer group. navigate to Rules. 4. 3. 5. In the MOM Administrator console. To add computers to the SQL Server remote connectivity processing rule 1. Be sure to initiate a managed computer scan after modifying a computer group membership.

384 8. Processing Rules The service pack compliance processing rules are listed in the following locations: • • \SQL Server 2000\SQL Server 2000 Health and Availability Monitoring\Event Processing Rules\SQL Service Pack Compliance \SQL Server 7. While the processing rules that are associated with service pack compliance are enabled by default. the script responses must be configured to monitor for service pack compliance.163 7.00.00.00.194 8.00.x Service Pack 4 SQL Server 2000 RTM SQL Server 2000 Service Pack 1 SQL Server 2000 Service Pack 2 SQL Server 2000 Service Pack 3 For information about how to determine the SQL Server version. The checking can also optionally generate an informational alert for service pack compliance that can be used for auditing purposes. This checking generates an alert when a computer is running a service pack or hotfix version earlier than the specified version.x and the version strings beginning with 8 are SQL Server 2000. Version compliance is performed by using the SQL Server version string.x RTM SQL Server 7.0\SQL Server 7.699 7. The following table lists SQL Server version strings and their service pack levels.00. where the version strings beginning with 7 are SQL Server 7.842 7.534 8.00. Service pack compliance monitoring is not configured by default.x Service Pack 2 SQL Server 7.00.00.x Service Pack 1 SQL Server 7. Table 8 SQL Server Version Strings and Associated Releases Version String 7.22 Recommended Knowledge and Skills Service Pack Compliance The SQL Server Management Pack can monitor servers running SQL Server to ensure that they are running the most recent SQL Server service pack or hotfix version.0 Health and Availability Monitoring\Event Processing Rules\SQL Service Pack Compliance .00. see article 321185 in the Microsoft Knowledge Base.961 7.x Service Pack 3 SQL Server 7.1063 8.760 Service Pack Level SQL Server 7.

However. Select the rule. Default Value False (Disabled) False (Disabled) 8. Logs an information event when the script is run. service pack compliance is enabled. and then click Edit. 4. 5. Additionally.00. select AlertOnAll. the first of these rules (SQL Service Pack Compliance) stores the script parameters for service pack monitoring. The version string is the earliest version that is acceptable to meet service pack compliance. Right-click the rule. . Table 10 SQL Service Pack Compliance Script Parameters Script Parameter AlertOnAll InformationEven t VersionString Description Generates a success event if the version complies. Table 9 SQL Service Pack Compliance Processing Rules Processing Rule SQL Service Pack Compliance SQL Service Pack Compliance — Version does comply Default Value Enabled Enabled SQL Service Pack Compliance — Version does not comply Enabled Scripts While there are several SQL Server service pack compliance processing rules. The SQL Server version string that is used to evaluate service pack compliance. and default states for the SQL Service Pack Compliance processing rule. type True in the Value box. To configure service pack monitoring 1. and then click OK. If you want to receive success version compliance alerts. In the Script parameters box.Recommended Knowledge and Skills 23 The following table lists the service pack compliance processing rules. and then click the Response tab.194 Configuring Service Pack Monitoring By default. and then click Edit Script Parameters. 3. navigate to the SQL Service Pack Compliance processing rule. The following table lists the script parameters. 2. descriptions. you can optionally configure the script to generate an event for service pack compliance success. you need to configure the version string for your environment. In the MOM Administrator console.

if required. 2. and then click Apply. Click the General tab. the Management Pack does not generate an alert if a database enters an intentional states such as Offline or Read Only. After modifying the script responses.0\SQL Server 7. After modifying script responses. click OK. However. and then click Edit Script Parameters. In the Value box. select VersionString. For more information. In the Script parameters box. In the event that a database enters an unhealthy state (such as Suspect). Database Health Monitoring The SQL Server Management Pack Refresh monitors database health. select Enabled. and then click OK. the following databases are defined as high severity: • • • • • • Master TempDB Model msdb Distribution OnePoint Individual databases can be excluded from monitoring. Processing Rules The database health monitoring processing rules are listed in the following locations: • • \SQL Server 2000\SQL Server 2000 Health and Availability Monitoring\Event Processing Rules\SQL Server Database Health \SQL Server 7. 3. High-severity databases that are entering an unhealthy state generate a service unavailable alert. By default. Database health monitoring checking occurs every 15 minutes by default and requires no configuration changes to work. enter the SQL Server version number that applies to your environment. the Management Pack generates an alert. These databases are defined as high-severity databases. see the “Excluding Databases from Monitoring” section later in this guide. An unhealthy database generates a critical error alert. without which SQL Server or a particular application cannot function. The checking script allows high-impact databases to be defined. 4. commit the configuration changes to apply the changes to agent computers.0 Health and Availability Monitoring\Event Processing Rules\SQL Server Database Health .24 Recommended Knowledge and Skills 1.

and then click the Response tab. 4. . tempdb. Select the rule. and then click OK. enter the database names. click OK. select HighSevDatabases. 6. distribution. 2.Recommended Knowledge and Skills 25 The following table lists the database health monitoring processing rules. and then click Edit. and then Apply. the first of these rules (SQL Server Database Health) stores the script parameters for database health monitoring. 5. and then click Edit Script Parameters. Table 11 SQL Server Database Health Processing Rules Processing Rule SQL Service Database Health SQL Service Database Health — Database is unhealthy SQL Service Database Health — High impact database is unhealthy Default Value Enabled Enabled Enabled Scripts While there are several SQL Server database health processing rules. Table 12 SQL Server Database Health Script Parameters Script Parameter HighSevDatabas es Description A comma-separated list of databases that are of high importance and require extra health checks Generates an information event when the script is run Default Value master. The following table lists the script parameters. In the Script parameters box. msdb. In the Value box. After modifying script responses. descriptions. Right-click the rule. commit the configuration changes to apply the changes to agent computers. After modifying the script responses. In the MOM Administrator console. 3. and default states for this processing rule. navigate to the SQL Server Database Health processing rule. model. To add databases to the high-severity list 1. onepoint False (Disabled) InformationEven t Customizing Database Health Monitoring You can customize database health monitoring by adding databases to the list of high-severity databases.

and default states for this processing rule.0\SQL Server 7. By default. You must enable the processing rule associated with this monitoring feature and configure the script responses to check for the database configuration settings that apply to your environment. . this monitoring feature is disabled. The following table lists the script parameters. Processing Rules The database configuration monitoring processing rules are listed in the following locations: • • \SQL Server 2000\SQL Server 2000 Health and Availability Monitoring\Event Processing Rules\SQL Server Database Configuration Monitoring \SQL Server 7. Table 13 SQL Server Database Health Processing Rules Processing Rule SQL Server Database Configuration Monitoring SQL Server Database Configuration Monitoring — Database is not configured correctly Default Value Disabled Enabled Scripts The SQL Server Database Configuration Monitoring processing rule stores the script parameters for database configuration auditing. descriptions.0 Health and Availability Monitoring\Event Processing Rules\SQL Server Database Configuration Monitoring The following table lists the database configuration monitoring processing rules.26 Recommended Knowledge and Skills Database Configuration Monitoring Database configuration monitoring allows you to audit your environment for database configuration settings that you establish as a standard for your organization.

4. After modifying script responses. 2. commit the configuration changes to apply the changes to agent computers. In the Script parameters box. For example. and then click Edit Script Parameters. and then click the Response tab. and then click Edit. Select the rule. After modifying the script responses. . an event is generated if the AutoClose configuration setting on a database is enabled. Table 14 SQL Server Database Health Script Parameters Script Parameter AutoClose AutoCreateStati stics AutoShrink AutoUpdatesSta tistics CrossDBChainin g InformationEven t Description Default Value Checks for the state of the Auto close False configuration setting Checks for the state of the Auto create statistics configuration setting Checks for the state of the Auto shrink configuration setting Checks for the state of the Auto updates statistics configuration setting Checks for the state of the Crossdatabase ownership chaining configuration setting Logs an event when this script is run True False True False False (Disabled) True TornPageDetecti Checks for the state of the Torn page on detection configuration setting To customize SQL Server database configuration monitoring 1. Right-click the rule. 3. modify the script responses by selecting a script.Recommended Knowledge and Skills 27 Important The default state for database configuration monitoring script parameters indicates whether an event is generated for a configuration setting that is either enabled or disabled. navigate to the SQL Server Database Configuration Monitoring processing rule. click OK. In the MOM Administrator console. and then Apply. if the default state of the AutoClose parameter is set to False. 5.

By adding databases to an exclusion file. alerts are not generated for the following monitoring scenarios: • • • Database space monitoring Transaction log space monitoring Database health .28 Recommended Knowledge and Skills Excluding Databases from Monitoring The SQL Server Management Pack allows administrators to exclude individual databases from script-based monitoring.

This counter is refreshed periodically. an exclusions list places an overhead on monitoring and should not be overused. Full Scans/second – The number of unrestricted full scans per second. DBCC Logical Scan Bytes/second – The number of logical read scan bytes per second for database consistency checker (DBCC) statements. This counter represents the number of lock blocks currently in use on the server. Average Wait Time (ms) – The average amount of time (in milliseconds) for each lock request that resulted in a wait. The collected data is displayed in public views that can be used to monitor the health of SQL Server. • • . Save the file as SQLExclude. such as rows or tables. Reading continues at the next line until the end of the file is reached. Performance Counters Collected by Default The following performance counters are collected by default: • • • • • Active Transactions – A count of the current active transactions for the database. The following example shows a typical exclusion file. An invalid entry results in the reading being terminated for the invalid line. This includes internal requests for NOWAIT locks. Lock Timeouts/second – The number of lock requests per second that timed out. the database name should be preceded with the instance name. however.Recommended Knowledge and Skills 29 Exclusions are implemented by using a text file on the monitored server that lists database names. Review the monitoring rules. Northwind Master Pubs Instance1\Northwind Instance1\Pubs Instance2\Northwind SQL Server Performance Monitoring The SQL Server Management Pack collects performance data for sampling purposes. This section provides an overview of the performance monitoring that is provided in the SQL Server Management Pack Refresh. default states. that are locked by a user or process. These can be either base-table or full-index scans. All databases are assumed to be in the default instance unless an instance is specified. The exclusions file is parsed when read. Log Cache Reads/second – The count per second of reads performed through the log manager cache.txt and place it in the c:\ folder. and thresholds and configure these appropriately for your environment. An exclusion file can contain any number of databases. If databases that are to be excluded are in named instances. Lock Blocks – Individual resources.

Processing rule group All replication performance rules are located in the following processing rule group: • \SQL Server 2000\Server Performance Collection\Replication Performance Collection . All data that is collected by these counters is displayed in public views. Each performance collection rule must be enabled to collect data. SQL Replication Performance Collection Defaults This Management Pack collects counters that monitor the health of SQL Server replication. An extent is the smallest amount of space (eight contiguous pages or 16 KB) allocated for a table or index. The following default thresholds are monitored by the SQL Server Management Pack: • • • • • Access Methods – Full scans > two for 15 minutes (disabled by default) Buffer Manager – Page life expectancy < 300 second (disabled by default) Cache Hit Ratio – < 90% for 15 minutes Locks – The number of deadlocks > 1 for 15 minutes SQL Server User Connections – > 500 It might be necessary to adjust thresholds based on the acceptable performance of your servers running SQL Server. By default. all replication performance collection rules are disabled. Mixed Page Allocations/second – The count per second of pages allocated from mixed extents. Logins/second – The total number of logins started per second. One method for reducing page-write activity is to ensure that the free buffer pool does not run out of free buffers. page writes occur while waiting for an unused cache buffer to flush. If it does. Breaches in these thresholds generate an alert. Page Writes/second – The count per second of issued database page writes. Pages Allocated/second – The count per second of pages allocated to database objects that are used for storing index or data records.30 Recommended Knowledge and Skills • • • • Log Truncations – The total number of times the database's transaction log has been truncated. • • SQL Server Performance Threshold Defaults The SQL Server Management Pack samples performance counters for threshold breaches on a regular basis. Page writes are generally expensive. Memory Grants Pending – The count per second of processes waiting for a workspace memory grant.

performance collection occurs for all named instances (and not default instances) using each script. Default instance performance collection uses standard MOM rules. Default State – Disabled Named instance replication performance collection (15 minutes) Named instance reporting performance collection (15 minutes) . Default State – Disabled Location – SQL Server 2000\Server Performance Collection\Replication Performance Collection\Event Processing Rule Purpose – This rule collects all replication performance data every 15 minutes for named instances of SQL Server.Recommended Knowledge and Skills 31 Default performance counters The following replication performance counters are collected by default: • • • • • • • • • • Replication Distributor Delivered Commands/second Replication Distributor Delivered Transactions/second Replication Logreader Delivered Commands/second Replication Logreader Delivered Transactions /second Replication Merge Conflicts/second Replication Merge Downloaded Changes/second Replication Merge Uploaded Changes/second Replication Snapshot Delivered Commands/second Replication Snapshot Delivered Transactions/second Replication Total Agents Running Named Instance Performance Collection This Management Pack can collect performance data from named and clustered instances of SQL Server. The following named instance performance collection rules are included in the Management Pack. Default State – Disabled Location – SQL Server 2000\SQL Server 2000 Report Collection Rules\Event Processing Rules Purpose – This rule collects all named instance performance counters that are required for reports to work every 15 minutes. This performance collection is script based and disabled by default. Named instance base performance collection (15 minutes) • • • • • • • • • Location – SQL Server 2000\Server Performance Collection\Event Processing Rules Purpose – This rule collects all default performance data every 15 minutes for named instances of SQL Server. When enabled.

5. but all counters are enabled. Each collected performance counter can be enabled and disabled by adjusting the script parameter. To adjust the performance data that is collected 1. commit the configuration changes to apply the changes to agent computers. The name of the parameter is the name of the performance counter. navigate to the desired performance rule. and then click the Response tab. In the Script parameters box. Select the rule.32 Recommended Knowledge and Skills Each named instance performance collection script can be toggled to adjust the individual performance counters that it collects. Right-click the rule. In the MOM Administrator console. 3. After modifying the script responses. After modifying script responses. click OK. and then Apply. Administrators should compare this list with the counters that were collected by other Management Packs to ensure that there is no duplicate collection of performance counters on SQL Servers. 4. All performance counters are collected every 15 minutes. 2. which might affect SQL Server health. and then click Edit Script Parameters. all performance counters are collected. When enabling a script. The Management Pack monitors the following base operating system areas: CPU • • • • • • • Context Switches/Second Processor Queue Length Total CPU Usage CPU Usage – SQLAGENT process (threshold and collection) CPU Usage – SQLSERVR process (threshold and collection) CPU Usage – SQLMANGR process (threshold and collection) CPU Usage and Processor Queue Length (threshold) . Note By default all scripts are disabled. and then click Edit. select the desired script parameter. Base Operating System Performance Monitoring The SQL Server Management Pack monitors the underlying health of the base operating system.

Daily Tasks On a daily basis. The SQL Server Management Pack generates reports that display data over time and present patterns that indicate problems. Verify that all servers running SQL Server are communicating with the MOM Administrator console. Review warnings (optional). However. perform other tasks on a regular basis. depending on your environment. You can perform the daily. adjust the frequency of these tasks to meet the needs of your particular environment. but they still require periodic attention. and monthly tasks as specified in this guide.Recommended Knowledge and Skills 33 Disk • • • • • • • • • • • • Disk Free Space Capacity Disk Queue Length Disk Read Latency (threshold) Disk Write Latency (threshold) Page Read/Sec Page Writes/Sec Pages/Sec Page Nonpaged Bytes Pool Paged Bytes Bytes Received/Sec Bytes Sent/Sec Bytes Total/Sec Memory Network Operations Tasks The best practice is to review and prioritize all alerts on a daily basis. Many important problems do not cause alerts. Review the reports to resolve issues before they generate alerts. perform the following tasks: • • • Review all open alerts. . weekly. In addition.

review the following reports weekly: • • • • • SQL Server Critical Events SQL Server Critical Events Trend by Day SQL Server Lock Performance Analysis SQL Server Log Performance Analysis SQL Server Memory Performance Analysis For a description of the reports. 2. If the last contact time is greater than five minutes. In the MOM Administrator console.34 Recommended Knowledge and Skills Reviewing All Open Alerts Review all new alerts in the following order of priority: • • • • • Service Unavailable errors Critical errors SQL Server scripts. navigate to Monitor. navigate to Monitor. Verifying That All SQL Servers Are Communicating with the MOM Administrator Console Communication failure between the servers running SQL Server and the monitoring infrastructure prevents you from receiving alerts so that you can examine and resolve them. click the Last Contact column heading. Review all alerts that are older than 24 hours to ensure that they are addressed in a timely manner. such as the SQL Server Service Availability and SQL Server Remote Connectivity Warnings (optional) Informational messages (optional) Not all problems can be repaired in one day or less. All Open Alerts. This sorts all computers based on the last contact time. Weekly Tasks In addition to the tasks that you perform daily. To review open alerts 1. determine why the computer is not communicating with MOM. parts must be ordered or computers must be scheduled for restart. 2. Commonly. In the right pane. see the “Reports” section later in this guide. It is important that you follow up on these open alerts to ensure that they are addressed in a timely manner. In the MOM Administrator console. . All Agents. To verify that servers running SQL Server are communicating with the MOM Administrator console 1.

As Needed Tasks It is recommended that you perform the following tasks as required to ensure the availability of SQL Server: • • • • Review all open alerts.Recommended Knowledge and Skills 35 Monthly Tasks In addition to the tasks you perform daily. . Use the SQL Server Health Monitoring public views. review reports in the following categories on a monthly basis: Capacity planning and trending • • • • • • • • SQL Server Backup Device Capacity Planning by Day SQL Server User Connections by Day SQL Server User Connections by Peak Hours SQL Server Distribution Replication Performance Analysis SQL Server Log Reader Replication Performance Analysis SQL Server Merge Replication Performance Analysis SQL Server Overall Replication Performance Analysis SQL Server Snapshot Replication Performance Analysis SQL Server performance analysis (if using replication) Other reports Review other reports as appropriate for your installation. Use the SQL Server public views. Verify that all MOM agents are communicating. and the reports you review weekly.

These scenarios include: • • • • • SQL Server database and transaction log space warnings and errors. SQL Server failed agent jobs.36 Recommended Knowledge and Skills Recommendations for the Network Operations Desk It is recommended that network operations staff monitor servers running SQL Server for highimpact alert scenarios. SQL Server failed backups. SQL Server connection errors. Configuring notification groups. This collection of performance data uses Windows Management Instrumentation (WMI) and requires access to WMI performance objects. set the InformationEvent parameter to True on any scriptdetermined health check. The SQL Server Management Pack checks for this condition every 24 hours and notifies operators with an alert. Due to known issues with SQL Server 2000 and Microsoft Windows Server™ 2003. The event lists the servers or instances excluded during monitoring. To enable information events. . with steps to resolve this issue. Troubleshooting WMI Performance Collection The SQL Server Management Pack can collect performance counters from named instances of SQL Server. an information event is logged when the associated script is run. such as passive nodes. The best practice is to review public views in the SQL Server Health Monitoring group and use these views to monitor the previous scenarios. When enabled. WMI performance objects might not be available. such as Service Availability or Database Free Space Checking. Information events can be enabled for any script-determined health check in the Management Pack. Information Events Information events can be enabled to trace the behavior of the Management Pack.

Connection failure SQL Server Service Availability .SQL Server Agent service is not running SQL Server Service Availability . .SQL Server service is not running Service Unavailable Reports This section lists the reports that are included in the SQL Server Management Pack.Database space error SQL Server Database Space Analysis . These are found in the MOM Administrator console at the following locations: • • Processing Rule Groups\Microsoft SQL Server\SQL Server 2000 Processing Rule Groups\Microsoft SQL Server\SQL Server 7.Database is unhealthy SQL Server Database Health – High-impact database is unhealthy SQL Server Database Space Analysis .Log file space error Default Alert Severity Critical Error Service Unavailable Critical Error Critical Error Service Unavailable Service Unavailable SQL Server Service Availability .0 Processing Rule Group: SQL Server Health Monitoring The SQL Server Health Monitoring group contains rules that monitor the health of key SQL Server components.Recommended Knowledge and Skills 37 Reference Processing Rules That Generate Critical Events and Alerts This section lists the processing rule groups and event processing rules in the SQL Server Management Pack. Table 15 Processing Rules in the SQL Server Health Monitoring Group Rule SQL Server Database Health .

This report provides one graph for each specified server.38 Recommended Knowledge and Skills SQL Server Capacity Planning Reports SQL Server Backup Device Capacity Planning by Day This report provides a graph of the daily use of the SQL Server backup device. and average backup device capacity based on the backup device/device throughput bytes per second performance counter. . maximum. The graph indicates the minimum.

maximum. where the database instance is not Total.Recommended Knowledge and Skills 39 SQL Server User Connections by Day This report provides a graph of the daily SQL Server user connections for the specified server during the specified time period. Performance counter data is averaged by the hour. This report provides one graph for each specified server. SQL Server Operations Reports SQL Server Critical Events This report lists critical events.user connections performance counter. Performance counter data is averaged by the hour. SQL Server Lock Performance Analysis This report provides a graph of several SQL Server lock performance counters for the specified server during the specified time period. master. SQL Server Logreader Replication Performance Analysis This report provides a graph of several SQL Server logreader replication performance counters for the specified server during the specified time period. which are events with a severity of 1.user connections performance counter. Performance counter data is averaged by the hour. SQL Server Performance Analysis Reports SQL Server Distribution Replication Performance Analysis This report provides a graph of several SQL Server distribution replication performance counters for the specified server during the specified time period. Performance counter data is averaged by the hour. SQL Server Log Performance Analysis This report provides a graph of several SQL Server transaction log performance counters for the specified server during the specified time period. SQL Server Critical Events Trend by Day This report provides a daily graph of all critical events. which are events with a severity of 1. The graph indicates the minimum. This report provides one graph for each database instance. SQL Server User Connections by Peak Hours This report provides a graph of the daily SQL Server user connections for the specified server during the specified time period. and average user connections capacity based on the SQL Server/general statistics . . displayed by day or by peak hours. and average user connections capacity based on the SQL Server/general statistics . Northwind. maximum. model. The graph indicates the minimum. msdb. or pubs. This report provides one graph for each specified server. that have occurred on the specified server in the specified time period. displayed by day. that have occurred on the specified server in the specified time period. This report is sorted alphabetically by server and by event time.

Performance counter data is averaged by the hour. The following counters are plotted on a primary axis: • • • • • • • Total Server Memory (KB) (Scale = KB) Buffer Cache Hit Ratio (Scale = 1) Free Buffers (Scale = 1/10) Lazy Writes/sec (Scale = 1/10) Readahead Pages/sec (Scale = 1/10) Process-Page Faults/sec (Scale = 1/10) Process-Private Bytes (Scale = MB) The following counters are plotted on a secondary axis: SQL Server Merge Replication Performance Analysis This report provides a graph of several SQL Server merge replication performance counters for the specified server during the specified time period.40 Recommended Knowledge and Skills SQL Server Memory Performance Analysis This report provides a graph of several SQL Server memory performance counters for the specified server during the specified time period. Performance counter data is averaged by the hour. Computer Groups The following computer groups are included in the SQL Server Management Pack Refresh: • • • • MSSQL Server 2000 MSSQL Server 2000 Client Side Monitoring Microsoft SQL Server 7. Performance counter data is averaged by the hour. SQL Server Overall Replication Performance Analysis This report provides a graph of several SQL Server overall replication performance counters for the specified server during the specified time period.x Microsoft SQL Server 7.x Client Side Monitoring . Performance counter data is averaged by the hour. SQL Server Snapshot Replication Performance Analysis This report provides a graph of several SQL Server snapshot replication counters for the specified server during the specified time period.

Recommended Knowledge and Skills 41 Scripts The following scripts are included in the SQL Server Management Pack Refresh: • • • • • • • • • • • • • SQL Server 2000 Base Performance Collection (15 minutes) SQL Server 2000 Long Running Agent Jobs SQL Server 2000 Replication Performance Collection (15 minutes) SQL Server 2000 Report Performance Collection (15 minutes) SQL Server 2000 WMI Performance Object Check SQL Server 7.0 Instance Process ID SQL Server CPU Overload SQL Server Database Health Monitoring SQL Server Named Instance Detection SQL Server Remote Connectivity SQL Server Service Monitoring SQL Server Service Pack Compliance SQL Server Space Analysis Default Public Views This section lists the public views that are included in the SQL Server Management Pack Refresh. SQL Server 2000 Microsoft SQL Server 2000 • • • • • All alerts generated in the last 2 hours All alerts generated in the last 24 hours SQL Server 2000 computer groups SQL Server 2000 servers Unresolved alerts .

42 Recommended Knowledge and Skills Microsoft SQL Server 2000\Server Resource Utilization • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • CPU Usage\% CPU .SQLAGENT Process CPU Usage\% CPU .SQLMANGR Process CPU Usage\% CPU .MOM OnePoint Process CPU Usage\% CPU .SQLSERVR Process CPU Usage\Context Switches / second CPU Usage\Processor Queue Length CPU Usage\Total % CPU Usage Disk Capacity\% Free Space Disk Capacity\Free Megabytes Disk Performance\Average Disk Queue Length Disk Performance\Current Disk Queue Length Disk Performance\Disk Read and Write Latency Disk Performance\Disk Reads and Writes / second Memory Usage\Memory: Page Reads/sec Memory Usage\Memory: Page Writes/sec Memory Usage\Memory: Pages / second Memory Usage\Memory: Pool Nonpaged Bytes Memory Usage\Memory: Pool Paged Bytes Network Usage\Bytes Received/second Network Usage\Bytes Sent/second Network Usage\Bytes Total/second Microsoft SQL Server 2000\SQL Server Health Monitoring SQL Agent\Failed SQL Agent Jobs SQL Server Backups\Failed SQL Backups SQL Server Replication\Distributor\Delivered Commands/second SQL Server Replication\Distributor\Delivered Transaction/second SQL Server Replication\Log Reader\Delivered Commands/second SQL Server Replication\Log Reader\Delivered Transactions/second SQL Server Replication\Merge\Conflicts/second SQL Server Replication\Merge\Downloaded Changes/second SQL Server Replication\Merge\Uploaded Changes/second .

Recommended Knowledge and Skills 43 • • • • SQL Server Replication\Replication Agents Running SQL Server Replication\Snapshot\Delivered Commands/second SQL Server Replication\Snapshot\Delivered Transactions/second SQL Server Replication\SQL Server 2000 Replication Servers Microsoft SQL Server 2000\SQL Server Utilization and Performance • • • • • • • • • • • • • Active Transactions Average Wait Time/ms DBCC Logical Scan Bytes/second Full Scans/second Lock Blocks Lock Timeouts/second Log Cache Reads/second Log Truncations Logins/second Memory Grants Pending Mixed page allocations/second Page Writes/second Pages Allocated/second SQL Server 7.0 • • • • • • • • • All alerts generated in the last 2 hours All alerts generated in the last 24 hours SQL Server 7.x Servers Unresolved alerts Microsoft SQL Server 7.0 Microsoft SQL Server 7.0\SQL Server Utilization and Performance Active Transactions Average Wait Time/ms Full Scans/second Lock Blocks Lock Timeouts/second .

If a specific monitoring scenario is not being used. SQL Server 2000 Microsoft SQL Server SQL Server 2000 Client Side Monitoring Server Performance Collection Replication Performance Collection Server Resource Utilization CPU Performance Collection Disk Performance Collection Disk Space Usage Memory Performance Collection Network Performance Collection Server Performance Thresholds SQL Server 2000 Event Collection MSDTC OLE DB SQL Server Active Directory® Helper Service SQL Server Agent SQL Server Backup SQL Server Databases SQL Server DBCC .44 Recommended Knowledge and Skills • • • • • • • Log Cache Reads/second Log Truncations Logins/second Memory Grants Pending Mixed page allocations/second Page Writes/second Pages Allocated/second Processing Rule Groups The following processing rule group hierarchy is used by the SQL Server Management Pack Refresh. the best practice is to disable the processing rule group associated with the monitoring scenario.

x Microsoft SQL Server SQL Server 7.0 Events SQL Server 7.Recommended Knowledge and Skills 45 SQL Server Full Text Search SQL Server General SQL Server Log Shipping SQL Server Mail SQL Server Performance SQL Server Query Processor SQL Server Replication SQL Server Security SQL Server Security Audit Collection SQL Server Tables SQL Server Web Assistant SQL Server XML SQL Server 2000 Health and Availability Monitoring SQL Server 2000 Report Collection Rules SQL Server 7.0 Event Collection SQL Server 7.0 Profiler SQL Server 7.0 Security Events SQL Server 7.0 Report Collection Rules State Monitoring and Service Discovery .0 Report Collection Rules SQL Server 7.0 Health and Availability Monitoring SQL Server 7.0 Agent SQL Server 7.0 Client Side Monitoring Server Performance Collection Server Performance Thresholds SQL Server 7.

Sign up to vote on this title
UsefulNot useful