1 chapter overview developing a performance monitoring methodology choosing among monitoring tools...
DESCRIPTION
3 Performance Bottlenecks Performance limited by excessive demand, bad design, and/or insufficient resources. Low numbers can be as meaningful as high numbers. Solving one bottleneck will often reveal another. At some point, resolving bottlenecks ceases to appreciably improve performance.TRANSCRIPT
1
Chapter Overview• Developing a Performance Monitoring
Methodology• Choosing Among Monitoring Tools• Performing Monitoring Tasks
2
Performance Goals
• User perspective—minimize response time per query.
• Server perspective—maximize the number of queries serviced.
• User perspective is subjective.• Server perspective can be objectively
measured.
3
Performance Bottlenecks
• Performance limited by excessive demand, bad design, and/or insufficient resources.
• Low numbers can be as meaningful as high numbers.
• Solving one bottleneck will often reveal another.
• At some point, resolving bottlenecks ceases to appreciably improve performance.
4
Trend Analysis
• Establish an initial performance baseline.• Update the performance baseline
periodically.• Analyze changes in the baseline to
identify trends.• Usage tends to change over time,
revealing new bottlenecks.
5
Resources and Activities to Monitor
• Inadequate hardware resources and competing server applications
• Network congestion• Cursors and ad hoc queries• Excessive blocking locks and deadlocks
6
Windows 2000 System Monitor
7
Task Manager
8
SQL Profiler
9
Current Activity Window in Enterprise Manager
10
Transact-SQL
• System stored procedures• Database Consistency Checker (DBCC)• Built-in functions• Trace flags
11
Resource Use Monitoring
• Task Manager• Processes tab• Performances tab
• Windows 2000 System Monitor• Chart view• Histogram view• Report view
12
Memory Objects and Counters
13
I/O Objects and Counters
14
Processor Objects and Counters
15
Monitoring Stored Procedures, SQL Batches, and User Activity
• Long-running query trace• Stored procedure performance trace• Cause of deadlock trace• Logins and logouts• Individual user activity
16
Current Locking and User Activity Monitoring
17
Chapter Summary• Develop a monitoring methodology, and monitor
periodically to detect developing trends.• Understand the range of monitoring tools and their
capabilities.• Use System Monitor and Task Manager to monitor
resource usage.• Use SQL Profiler to detect specific SQL Server events.• Use the Current Activity window to view current
processes and locks.