Microsoft Sharepoint Products and Technologies Resource Kit eBook

Chapter 10: Performance Monitoring in Microsoft Office SharePoint Portal Server 2003 249
Table 10-6 Counters by Platform (continued)
Platform Counters
SQL Counters Memory\Pages/sec
System\Context Switches/sec
Process(sqlservr)\% Processor Time
Process(sqlservr)\Working Set
SQLServer:General Statistics\User Connections
SQLServer:Databases\Transactions/sec
SQLServer:Locks\Number of Deadlocks/sec
SQLServer:Locks\Lock Waits/sec
SQLServer:Locks\Lock Wait Time (ms)
SQLServer:SQL Statistics\Batch Requests/sec
Operation Management
Hardware redundancy is an important element for high availability, but ongoing
health monitoring is required to guarantee that this redundancy remains intact. For
example, if one of the front-end Web servers fails and this failure remains undetected,
it jeopardizes the high availability of the Web servers. Ongoing health monitoring and
failure detection are vital to meeting the high availability goals of the infrastructure.
This part of this chapter focuses on the incident and performance aspects of
managing the healthy operation of the architecture. These aspects include the following
items:
■ Incident, or fault, management. Fault detection, fault registration, fault assignment,
and fault resolution.
■ Performance management. Network and server capacity planning, availability,
response time, throughput, and utilization. Statistics collection tools,
traffic modeling techniques, and service probes are required to ensure that service
level agreements are fulfilled.
Architectural Components
SharePoint Portal Server is a distributed application framework that uses multitier
architecture. These components can be grouped as follows:
■ Hardware
■ Network infrastructure
■ Operating system
■ SharePoint Portal Server components