Export (0) Print
Expand All
Expand Minimize
1 out of 1 rated this helpful - Rate this topic

Samples Available

This section describes the monitoring samples that are included with Application Center. These samples include additional performance counters that you can install and configure for the Application Center performance chart and database monitoring samples that you can modify and use to monitor your database in the Monitors view and the performance chart.

Database Monitoring Samples

The database monitoring samples consist of six ASP applications and one .mof file. You can change these to reflect your database situation and use them to monitor your database.

Bb687506.caution(en-us,TechNet.10).gif Caution   To use these samples, you must be running SQL Server version 6.5 or later with Service Pack 2.

The ASP Files

The six ASP files provide five different monitoring tasks. Error checking procedures pass any error information back with the HTML page returned by the ASP application. These application check to ensure the following:

  • That the connection is functioning.

  • That the database is both connected and functioning.

  • That the database server can call stored procedures.

  • The Data Source Names (DSNs).

Bb687506.note(en-us,TechNet.10).gif Note   These samples are designed to work with Application Center Events and Performance Logging and might need modification to work with other types of databases.

  • Helloworld.asp—confirms you database functionality by calling a stored procedure on your database that returns the message "Hello, World" upon completion. It creates an ADO database connection and calls a stored procedure with a parameter.

  • Verifysp.asp—performs the same test as Hellowworld.asp, except that it uses information passed in a query string to call the stored procedure.

  • Adotest.asp—checks ADO functionality by querying an Application Center table for a known value. It creates an ADO database connection and uses a SQL query.

  • Eventclassescount.asp—performs the same test as Adotest.asp. It creates an ADO database connection and uses a SQL query.

  • Serverlist.asp—checks basic functionality by using a query against an Application Center table to form a list of the cluster members. It creates an ADO database connection and uses a SQL query.

  • Dnseventclasses.asp—checks DSN functionality by using a DSN to connect to your database and return results. It uses a SQL query.

    Bb687506.note(en-us,TechNet.10).gif Note   To use Dnseventclasses.asp, you must create a DSN.

  • Samples.mof—creates and registers classes in WMI. Samples.mof is compiled and registered during set up. These WMI classes define data groups, data collectors, thresholds, actions, and performance counters.

Additional Performance Counters

You can add the additional performance counter samples to the performance counters that are already monitored and displayed by Application Center. To use these counters, you must either run Application Center Setup, and select only the optional samples, or you can compile Samples.mof.

Additional Web Service Counters

You can use the additional performance counters listed in the following table for monitoring Web services and resources:

Object

Counter

ASP pages

Request Execution Time, Request Wait Time, Requests Executing, Sessions Total, Transaction/sec, Template cache hit rate 

Distributed Transaction Coordinator (DTC)

Transactions/sec

Global IIS

File Cache Hits %, File Cache Flushes

Process

% Processor Time, Thread Count

W3Svc Service

Not found errors/sec, Current anonymous users, Non-anonymous users/sec, Maximum connections, Post request/sec, Bytes Sent/sec for, Files Sent/sec for, ISAPI extension requests/sec

Additional System Counters

You can use the additional system counters listed in the following table to monitor the operating system and services:

Object

Counter

Memory

Page reads/sec

Physical Disk

Reads/sec, Writes/sec, % Disk Time

Processor

Interrupts/sec, % DPC time

Server

Logons/sec

System

Processor Queue Length

Additional SQL Server Counters

You can use the additional SQL Server counters listed in the following table for monitoring SQL Server performance and availability:

Object

Counter

Access Methods

Table Lock Escalations/sec

Buffer Manager

Page Reads/sec, Page Writes/sec, Buffer Cache Hit Ratio, Free Buffers 

Databases

Data File(s) Size (KB), Percent Log Used

General Statistics

User Connections

Locks

Number of Deadlocks/sec

Memory Manager

Total Server Memory, Lock Memory

SQL Statistics

SQL Compilations/sec, SQL Re-compilation/sec, Failed Auto-Params/sec 

Physical Disk

Avg. Disk Queue Length, % Disk Time, Disk write bytes/sec, Disk read bytes/sec 

Memory

Page Faults / sec 

Processor

% Privileged Time, % Processor Time, Processor Queue Length 

Additional COM+ Counters

You can use the additional COM+ counters listed in the following table primarily for monitoring COM+ applications. You must alter this file before you can compile and use it. The following counters are associated with this file:

Counter

Instance

Total Committed Transactions

application_name

Committed Transactions/sec

application_name

Total Aborted Transactions

application_name

Aborted Transactions/sec

application_name

Total Object Creations

application_name

Object Creations/sec

application_name

Total Object Activations

application_name

Object Activations/sec

application_name

Total Shutdowns

application_name

Timeout Shutdowns

application_name

Admin Shutdowns

application_name

Failure Shutdowns

application_name

State

application_name

Additional Miscellaneous Counters

You need to do some configuration of the additional counters listed in the following table before you can use them. You can make these changes in the Health Monitor snap-in. The following counters are associated with this file:

Object

Counter

Network Interface

Bytes total per second, Bytes received per second, Bytes sent per second

Processor

% Processor Time 

Process

% Processor Time, Thread count 

Monitors and Counters for BizTalk Server

Some monitors and performance counters are also included for use with Microsoft BizTalk™ Server. These can be used to monitor your BizTalk servers by using Application Center or Health Monitor and can be found in the Health Monitor data group BizTalk Server 2000 Sample Monitors under Samples.

The monitors and counters include:

  • BizTalk Messaging Service Perf Counter Monitors – monitors performance counters specific to BizTalk Server.

  • Suspended Queue Event Monitors – checks for documents in the suspended queue.

  • BizTalk Messaging Service Monitor – checks the status of the BizTalk Messaging Service.

  • Pipelines performance counters – lists total pipeline executions and errors.

  • Marketing and Catalog performance countersLRUCache: Cache size, LRUCache: Flushes/sec, LRUCache: Hits/sec, LRUCache: Misses/sec.

Some of these monitors do not have supplied thresholds. You will need to create the thresholds according to your specific environment.

Additional Monitors

You can add the additional monitor samples to those already monitored and displayed by Application Center. The .mof file that defines them is compiled during Setup when you install the samples.

Related Topics

  • For more information about using and compiling .mof files, see Installing and Using the Samples.

  • For more information about DSNs, see the Windows 2000 Help.

  • For more information about BizTalk Server monitors and counters, see the BizTalk Server Help.

Did you find this information useful? Please send your suggestions and comments about the documentation to acdocs@microsoft.com

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.