Database Fundamental Concepts - Series 2 Monitoring plan
=> Creating a Performance Baseline
=> Server-Side Profiler Traces
=> System Monitor to monitor SQL Server and the OS
by Dr.Subramani Paramasivam
2. About
me
Dr. SubraMANI Paramasivam
PhD., MCT, MCSE, MCITP, MCP, MCTS, MCSA
CEO, Principal Consultant & Trainer
@ DAGEOP (UK)
Email: mani@dageop.com
Blog: http://dataap.org/blog
Follow
Us
https://www.facebook.com/pages/YOUR-SQL-MAN-LTD/
http://www.youtube.com/user/YourSQLMAN
https://twitter.com/dageop
https://uk.linkedin.com/in/dageop
Proud Sponsor
• SQLBits
• SQL Saturdays
• MCT Summit
• SQL Server Geeks
Summit
• Data Awareness
Programme
• Dageop’s Data Day
®
www.DataAP.org
SPEAKER
3. Contents
FC-02: Monitoring plan
• Creating a Performance Baseline
• Server-Side Profiler Traces
• System Monitor to monitor SQL Server and the OS
www.dageop.com
Fundamental Concepts
5. Monitoring Plan
• Plenty of monitoring tools available
• Monitor the performance of the server
and database.
• Monitoring plan is mandatory.
• Automate the plan.
www.dageop.com
Fundamental Concepts
7. Creating a Performance Baseline
• To determine whether your SQL Server system is performing
optimally.
• Measurements at regular intervals, to establish a server performance
baseline.
• Compare each new set of measurements with old.
• Use Baseline Measurement to find below,
• Peak and off-peak hours of operation.
• Production-query or batch-command response times.
• Database backup and restore completion times.
www.dageop.com
Fundamental Concepts
8. Creating a Performance Baseline
• Performance baseline should be followed on below areas
• System resources (hardware)
• Network architecture
• The operating system
• Database applications
• Client applications
• After you establish a server performance baseline, compare the
baseline statistics to current server performance.
• Kick start the investigation.
www.dageop.com
Fundamental Concepts
9. Creating a Performance Baseline
• Use the SQL Server profiler to
fix the performance baseline.
• Decide which events should be
considered.
• Store the collected information
in Table or file.
www.dageop.com
Fundamental Concepts
12. Server-Side Profiler Traces
• Server side traces are much lighter as it does not need to transfer
data over the network
• There are four steps in creating server side trace.
• Defining a trace.
• Defining the events and columns to be captured.
• Defining the filter condition.
• Start the trace.
• For a server-side trace to a file, the only applicable option is where
the trace file will be located.
www.dageop.com
Fundamental Concepts
13. Server-Side Profile Traces
• Server side traces use less resources than a SQL profiler trace.
• To Configure the Server Side Traces we will use SQL Server Profiler.
www.dageop.com
Fundamental Concepts
15. System Monitor to monitor
SQL Server and the OS
How many used?
www.dageop.com
Fundamental Concepts
16. System Monitor
• It’s a graphical tool available in Windows server operating system.
• Uses Remote Procedure Calls (RPCs) to collect information from
Microsoft SQL Server.
• By using system monitor we can view SQL Server’s information about
• Objects
• Behaviour of objects
• Processors
• Memory
• Cache
• Threads
• Performance Counters
www.dageop.com
Fundamental Concepts
17. System Monitor
• Performance related issues (operating system and SQL Server).
• Areas to Monitor
• Disk Activity
• Processor(CPU) Utilization
• Memory Usage
• Performance Counter is good tool to understand how SQL Server is
behaving at micro level.
www.dageop.com
Fundamental Concepts
18. Performance Counter (Perfmon)
• Why counters?
• Counters are used to provide information as to how well the operating system or an
application, service, or driver is performing.
• Some of the Counters
• MSSQL:Access Methods
• MSSQL:Buffer Manager
• MSSQL:Broker Statistics
• MSSQL:SQL Errors
• MSSQL:SQL Statistics
• MSSQL:Locks
• MSSQL:Buffer Node
• MSSQL:Plan Cache
www.dageop.com
Fundamental Concepts