“Monitoring” SQL Server - netways

“Monitoring” SQL 

Server 

Workshop 

Open Source Monitoring Conferrence 

Presentation © Michael Medin

Disclaimer! 

These slides represent the work and opinions 

of the author and do not constitute official 

positions of any organization sponsoring the 

author’s work 

This material has not been peer reviewed and 

is presented here as-is with the permission of 

the author. 

The author assumes no liability for any 

content or opinion expressed in this 

presentation and or use of content herein.

My Background 

Developer (not system manager) 

Not working with Nagios 

Accidentally ended up in our NOC 

Hated BB 

2003: The birth of NSClient++ 

NSClient sucked (Broke Exchange) 

NRPE_NT was to hard to use 

2004: The open source of NSClient++ 

“just for fun”

Agenda 

Introduction 

Part 1: Remote access 

Part 2: Tools of the Trade 

Break 

Part 3: Monitoring 

Part 4: Scripting 

Conclusion 

5 minutes 

15 minutes 

40 minutes 

20 minutes 

20 minutes 

10 minutes 

0 minutes

Introductions… 

Who are you 

What are your experiences with monitoring 

What are your experiences with SQL Server 

What are your expectations 

…

Split into groups 

2-3 persons

Assignment 

Where do we start

Task/Question 

When you manage a SQL Server: 

What’s the most important thing to monitor

Hint 1 

It is not something I will speak about…

Hint 2 

It is not something I will speak about… 

It is not SQL Server related

(My) Answer 

If the infrastructure goes down 

so will SQL Server 

Always start by monitoring the infrastructure 

Hardware 

● 

● 

● 

● 

● 

Software 

Clusters 

Raid arrays 

Network infrastructure 

Temperature/HW Status 

…

Monitoring Infrastructure 

This depends on what environment you have 

NOT related to SQL Server 

Thus... Your on your own…

Part 1: Remote access 

Click to edit Master text styles 

Second level 

● 

Third level 

● 

Fourth level 

● 

Fifth level

Remote access 

SQL Server from perl

● 

Perl and SQL Server 

Perl 

Install perl and DBI with ODBC (and TDS 

driver) 

● 

You need (for debian): 

– perl 

– unixodbc unixodbc-dev tdsodbc 

● 

Then you need to configure a odbc driver 

(/etc/odbcinst.ini) 

– [FreeTDS] 

– Description = TDS driver (Sybase/MS SQL) 

– Driver = /usr/lib/odbc/libtdsodbc.so 

– Setup = /usr/lib/odbc/libtdsS.so 

– CPTimeout = 

– CPReuse =

Perl and SQL Server 

On Windows: 

Install ActiveState perl 

● 

Everything you need comes included 

Install a ODBC driver for SQL Server 

● 

Verify: 

http://www.microsoft.com/downloads/en/details.aspx 

familyid=78CAC895-EFC2-4F8E-A9E0-3A1AFBD5922E&displaylang=en 

● 

perl -e "use DBI 1.6;" 

● 

● 

● 

perl –e "use DBD::ODBC;" 

perl -MDBD::ODBC -e "print $DBD::ODBC::VERSION;" 

perl -MDBI -e "DBI->installed_versions;"

Add a datasource 

Unix: 

Edit: /etc/odbc.ini 

● 

● 

● 

[osmc] 

Driver = FreeTDS 

Server = 

Windows: 

Data sources -> System data source 

● 

Add -> {next, next, next} -> done 

Name: osmc 

Server:

Connecting to a database 

#!/usr/bin/perl -w 

use strict; 

use DBI; 

my $dbh = DBI->connect('dbi:ODBC:osmc','osmc','osmc') or die "Can't connect to osmc: $DBI::errstr"; 

my $sql = "SELECT 1 AS test_col"; 

my $sth = $dbh->prepare($sql) or die "Can't prepare statement: $DBI::errstr"; 

$sth->execute(); 

print "$sth->{NAME}->[0]\n"; 

while ( my @row = $sth->fetchrow_array ) { 

print "@row\n"; 

} 

$dbh->disconnect; 

$ perl test.pl 

test_col 

1

Assignment 

Setting up perl

Task/Question 

Configure perl for database connectivity 

Connect to the following database 

Database = osmc 

Ip= ...

Hint 1 

● 

● 

● 

apt-get install perl 

apt-get install unixodbc unixodbc-dev 

apt-get install tdsodbc 

● 

cat /usr/share/tdsodbc/odbcinst.ini >> /etc/odbcinst.ini 

● 

echo -e '[osmc]\nDriver = FreeTDS\nServer = ...' >> 

/etc/odbc.ini cpan –i DBI 

● 

● 

cpan –i DBI 

cpan –i DBD::ODBC

Hint 2 

$ cat > test.pl prepare(\$sql) or

(My) Answer 

Hopefully you can now connect

Remote access 

Performance counters

check_nrpe 

We will mainly use this for counters 

check_nrpe 

● 

–H -c -a 

Or if you are on windows: 

nsclient++ -noboot NRPEClient 

● 

–H -c -a 

Command: 

CheckCounter

Assignment 

Checking performance 

counters

Task/Question 

Access performance counters from 

Command is: 

CheckCounter 

Counter is: 

\Processor(_Total)\% Processor Time

Hint 1 

Command is: 

CheckCounter 

Counter is: 

\Processor(_Total)\% Processor Time 

Unix: 

● 

● 

check_nrpe 

–H -c -a 


● 

nsclient++ -noboot NRPEClient

Hint 2 

Command is: 

CheckCounter 

Counter is: 


Unix: 

● 

● 

check_nrpe 

–H -c CheckCounter -a ‘\Processor(_Total)\% Processor Time’ 


● 

nsclient++ -noboot NRPEClient

(My) Answer 

Hopefully you can now connect 

OK all counters within bounds. 

|'\Processor(_Total)\% processortid'=14.204358

Running SQL Queries 

perl run.pl 

For instance: 

perl run.pl “SELECT 1 AS test_col” 

Or 

perl test.pl "sp_monitor“ 

Or 

perl test.pl "SELECT r.session_id, r.wait_type 

AS wait_category, r.wait_type, r.wait_time 

FROM sys.dm_exec_requests AS r INNER JOIN

Part 2: The tools of the 

Trade 


Second level 

● 

Third level 

● 

Fourth level 

● 

Fifth level

Useful tools in SQL Server 

DML Triggers 

Fires T-SQL code on table events 

PerfMon/SysMon 

Listens for hundreds of Windows/SQL 

Server events 

SQL Trace and Profiler 

Monitors internal events 

Wait States 

Tracks system waits (processes waiting 

for resources)

DML Triggers 

A trigger is a custom “event” which fires when 

data changes. 

For instance: 

You want to be notified when someone does: 

● 

insert into orders (…)

Monitoring DML Triggers 

Nothing “out of the box”. 

Can be extended (via external stored 

procedures) and submit to for instance NSCA 

or what not. 

There are probably better/simpler ways unless 

you really need this…

Performance Counters 

PDH (Performance Data Helper) 

A framework with metrics for “various things” 

Format: 

\Group(Instance)\Metric 

● 

● 

● 

Group = “area” 

Instance = “instance identifier” 

Metric = “value” 


Performance Viewer 


Second level 

● 

Third level 

● 

Fourth level 

● 

Fifth level

Monitoring Performance 

Two (ish) options: 

Counters 

PDH Counters 

● 

nsclient++, nc_net, nsclient, and everything else 

WMI (Windows Management Instrumentation) 

● 

nsclient++ and modern solutions (including 

agentless) 

Many ways to monitor 

We will use nsclient++ for simplicity

SQL Server Trace Profiler 

SQL Server Profiler shows how SQL Server 

resolves queries internally 

This allows administrators to see exactly what 

statements are submitted to the server and 

how the server accesses the database to 

return result sets. 

Used to find an error or resolve a problem 

Not monitor the server

Monitoring Trace Profiler 

 

 

Nothing you should monitor though… 

Can be viewed from the database (normal sql) 

SELECT TextData, Duration, CPU 

 

 

FROM trace_table_name 

WHERE EventClass = 12 AND CPU < (Duration*1000) 

Normal way to use it though is from inside the 

tool

Wait States 

System view with statuses for processes 

running 

Deprecated in 2005 (and beyond) 

Shows; 

processes waiting for resources 

deadlocks 

etc

Monitoring Wait States 


select * from sysprocesses

C2 Auditing 

configured through; 

SQL Server Management Studio 

c2 audit mode option in sp_configure 

the server records both failed and successful 

attempts to access statements and objects 

Can help profile system activity and track possible 

security policy violations 

Superseded by Common Criteria Certification

Monitoring C2 Auditing 

Nothing out of the box. 

Generates “log files” (unsure of format) 


SELECT * FROM ::fn_trace_gettable('C:\Program Files\Microsoft SQL 

Server\MSSQL\Data\audittrace_20040822191554.trc', default)

Summary 

Good stuff: 

PerfMon/SysMon 

● 

System metrics 

Wait States 

● 

SQL Process metrics (ish) 

Useful: 

DML Triggers 

● 

Database events 

Not very usefull (for monitoring): 

SQL Trace and Profiler

Assignment 

Server Performance

Task/Question 

Do we have a problem

Hint 1 

What’s the server CPU load

Hint 2 

What’s the server CPU load 

Check PDH (counter) object: 


Hint 3 

What’s the server CPU load 

Check PDH (counter) object: 


Use check_nrpe (or NSClient++) 

check_nrpe –H -c CheckCounter 

● 

-a ”\Processor(_Total)\% Processor Time”

(My) Answer 

No, but most will say so 

Why do you buy that expensive server 

● 

If not to use it 

But beware! 

If load increases you will be in trouble!

New tools added in 2005 

Common Criteria Compliance 

Combines SQL Trace and security settings for 

compliance 

DMVs 

dynamic management views, catalog views 

(metadata details and current status) 

Management Studio Reports 

● 

easy way to view DMV data 

Performance Dashboard 

● 

downloadable add-on with extra reports

Common Criteria 

Builds Compliance 

on c2 audit mode and is mainly a 

certification thing as I understand it

Monitoring “C3” 

I don’t really know :P 

But I think it is much same as before…

Dynamic management 

Database views views with metrics about server 

status 

Can be combined with reports to form a nice 

monitoring/management view 

In short: 

This is the god stuff!

Monitoring DMVs 

Regular database view (normal sql) 

For instance listing waiting sessions 

SELECT 

r.session_id, r.wait_type AS wait_category, r.wait_type, r.wait_time 

FROM sys.dm_exec_requests AS r 

INNER JOIN sys.dm_exec_sessions AS s ON r.session_id = s.session_id 

WHERE 

r.wait_type IS NOT NULL AND s.is_user_process = 0x1

DDL Triggers 

Same as DML triggers but for DDL 

Can show you; 

When/if someone alters the database 

(structure)

Monitoring DDL triggers 

Same as with DML triggers 

Nothing “out of the box”. 

Can be extended (via external stored 

procedures) and submit to for instance NSCA 

or what not.

Summary 

Good stuff: 

DMVs 

● 

● 

● 

Lots of SQL Server metrics 

Really nice reports 

Downloadable add-on with extra reports 

Somewhat useful: 

DDL Triggers 

● 

Database events 

Not very useful (for monitoring): 

SQL Trace and Profiler

Assignment 

Dynamic Management Views

Task/Question 

Does the server have a problem 

Use your new found skills to diagnose the 

system and find any errors and/or problems

Hint 1 

Use Dynamic Management Views

Hint 2 

Use Dynamic Management Views 

For instance: 

run_sql 

SELECT status, wait_type, wait_time 

FROM sys.dm_exec_requests 

WHERE wait_type IS NOT NULL 

(or) 

SELECT 

r.session_id, r.wait_type AS wait_category, r.wait_type, r.wait_time 

FROM sys.dm_exec_requests AS r 

WHERE 

INNER JOIN sys.dm_exec_sessions AS s ON r.session_id = s.session_id

(My) Answer 

Absolutely! 

Now we see we have tasks waiting! 

Waiting means slow clients: not good!

More goodies from 2008 

Change Tracking 

synchronously records which rows have been 

updated 

Change Data Capture 

asynchronously reads T-Log and records data 

changes 

Extended Events 

lightweight windows monitoring technology 

(similar to SQL Trace Event) 

SQL Auditing

Part 3: Monitoring 


Second level 

● 

Third level 

● 

Fourth level 

● 

Fifth level

Monitoring 

Existing tools

Existing Nagios scripts 

MSSQL Job Monitoring 

Monitors “scheduled jobs” 

Written in java (server) 

DBTuna 

Some commercial thing 

Haven’t checked 

check_mssql_nt 

Monitors “many things” (w32 binary) 

Written in debian (called via nrpe)


check mssql databases status by snmp 

Queries status via snmp 

Check MSSQL Database Mirroring 

Queries specific tables (sys schema) 

Written in perl 

check_mssql_health 

Queries many aspects of the server 


check_mssql_write.py


check_mssql_sproc 

Monitors “things” by executing a procedure 


check_mssql_monitor 

Wrapper for sp_monitor 


check_sql 

Runs various queries and checks various things 

Written in perl


Best ones: 

check_sql 

Good ones: 

check_sql 

Check MSSQL Database Mirroring 

check_mssql_health 

check_mssql_write.py 

check_mssql_sproc 

check_mssql_monitor

WARNING! 

If you are using ODBC 

check_sql is sort of broken (I think) 

At least I do this to connect 

my $cs = "DBI:$driver:$hostname"; 

#my $cs = "DBI:$driver:" . ($database "database=$database;" : '') . 

"host=$hostname" . ($port ";port=$port" : ''); 

But I am not a Perl DBI expert…

Don’t do this from 

There are nice tools to work with this… 

“Nagios” 

use them… 

Ask you DBA and your developers 

They know what requires monitoring 

Don’t believe there is a “boxed solution” 

There seldom is 

Don’t “finish” once the server is monitored. 

Monitor your application as well! 

Don’t forget “non-events”

Assignment 

Existing scripts

Task/Question 

Use check_sql to check that 

select count(*) from orders is 0

Hint 1 

perl check_sql -h

Hint 2 

perl check_sql -h 

perl check_sql 

-H osmc -d ODBC -U osmc -P osmc 

● 

-q "select count(*) from orders“ 

● 

-e 0

(My) Answer 

Hopefully it worked out…

Monitoring 

Performance Counters

A few Good Counters 

IO 

Pages / second 

● 

\Memory\Pages/sec 

Physical disk time 

● 

\PhysicalDisk(_Total)\% Disk Time 

Database files: 

Database file size 

● 

\SQLServer:Databases()\Data File(s) Size (KB) 

Database log file size 

● 

\SQLServer:Databases()\Log File(s) Size (KB)

Monitoring 

DMVs

Dynamic Management 

dm_db_*: 

Views 

Databases and database objects 

dm_exec_*: 

Execution of user code and associated 

connections 

dm_os_*: 

Memory, locking, and scheduling 

dm_tran_*: 

Transactions and isolation

A few good DMVs 

CPU 

sys.dm_exec_query_stats 

Memory: 

sys.dm_os_sys_info 

I/O: 

sys.dm_os_wait_stats 

Blocked sessions: 

sys.dm_os_waiting_tasks 

Technet link with sample queries:

Monitoring 

The art of stealing...

Remember, remember, 

…the fifth of november 

One of the best things about DVM: 

..are the reports… 

● 

Management Studio Reports 

– easy way to view DMV data 

● 

Performance Dashboard 

– downloadable add-on with extra reports 

These are premade reports with a nice gui 

● 

● 

Something like what your “friends” with that “big expensive 

alternative” to OSS keep selling right 

Why not steal it

Management Studio 

Are; 

Reports 

XML files (*.rdl) 

With predefined queries (good) 

And a lot of nice boxes and what not (crappy) 

Look for: 

//DataSets/DataSet 

Or if you prfer: 

● 

 

–

Assignment 

Dissecting a report

Task/Question 

Open a report and steal the query… 

For instance the historical_io.rdl report

Hint 1 

The PDB (Performance Dash Board) folder has 

the reports…

Hint 2 


the reports… 

The file I called historical_io.rdl

Hint 3 



The file I called historical_io.rdl 

Look for DataSet (and then Query)

Hint 4 



The file I called historical_waits.rdl 

Look for DataSet (and then Query) 

No it is not CHECK_DEPENDENCIES

(My) Answer 

Master thief I dub thee

Monitoring 

Applications

Applications! 

Dont forget to monitor your applications 

Check that tables and columns are ”writable” 

Check that counts (rows) 

Check that new rows ”are coming” 

● 

(recent item count) 

Check that ”things” work. 

Talk to your DBA and developers!

Assignment 

Monitoring my order system

Task/Question 

Create a query which makes sure that orders 

are coming in 

For instance: 

Select count(*) from orders 

● 

● 

(in real life you probably want; 

– WHERE order_date > DATEADD(DD,- 

1,CONVERT(CHAR(8),CURRENT_TIMESTAMP,112)) 

Or something similar)

Hint 1 

Use the “run.pl” perl script

Hint 2 

Use the “run.pl” perl script 

perl run.pl "select count(*) from orders"

(My) Answer 

Whoops… we are not gonna be rich afterall

Part 4: Scripting 


Second level 

● 

Third level 

● 

Fourth level 

● 

Fifth level

Client or Server side 

Server side; 

Remote access from the monitoring server 

Requires more ”firewall openings” 

More configuration server side 

Your DBA might disprove 

Client side; 

Local access to SQL Server (remote access to agent) 

Requires less firewall openings 

● 

And you probably require this anyway 

More configuration client side 

More work ”distributing” your scripts

Which language (Server 

Perl is a good candidate 

side) 

Support SQL queries 

Fairly simple driver handling (via ODBC) 

Has “helpers” for database access 

What we have been using all this time 

Most languages can be used though 

Used by various existing scripts 

● 

● 

Python, PHP 

Java (but it has a very high overhead)

Which language (Client 

Perl is (still) a good candidate 

side) 

Makes your compatible 

Requires installation (ActiveState or similar) 

VB is a popular choice 

With the Library from op5 you get much “for free” 

PowerShell 

Probably your best bet if you wanna do cool stuff 

Many other choices as well

Perl (Client side) 

The good; 


Fairly simple driver handling (via ODBC) 

Has “helpers” for database access 

Makes your compatible 

The bad; 

Requires installation (ActiveState or similar) 

Some issues with 64bit and databases 

● 

Requires the SAME as the ODBC libraries

VB (VisualBasic) 

The good; 

Support SQL queries - 

Simple driver handling - 

Has helpers “Nagios API” 

Can do a lot of “other things” 

● 

Ie. a “check_all” is possible 

The bad; 

No “Nagios API” available 

Script will not run on Linux

PowerShell 

The good; 


Simple driver handling 

Has helpers for database (SQL) access 

Can (re)configure the database 

The bad; 

Somewhat arcane syntax 

No “Nagios API” available 

Script will not run on Linux

Just a quick PowerShell 

SQL Server Management Objects (SMO) 

slide 

Replication Management Objects (RMO) 

Analysis Services Management Objects (AMO)


Second level 

● 

Third level 

● 

Fourth level 

● 

Fifth level

Thank You! 

Michael Medin 

michael@medin.name 

http://www.linkedin.com/in/mickem 

Information about NSClient++ 

http://nsclient.org 

Slides, and examples at:

“Monitoring” SQL Server - netways

Create successful ePaper yourself

Delete template?

Save as template?