What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Why does my WMI Microsoft SQL Server 2005 sensor not work anymore?

Votes:

0

Your Vote:

Up

Down

After a Windows update, the WMI Microsoft SQL Server 2005 sensor does not work anymore. What is the reason for this?

prtg sensor sql sql-server sql-server-2005 windows windows-update wmi

Created on Dec 12, 2012 10:41:01 AM by  Gerald Schoch [Paessler Support]

Last change on Dec 9, 2020 8:09:25 AM by  Brandy Greger [Paessler Support]



4 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies as of PRTG 22

Deprecated sensor type WMI Microsoft SQL Server 2005

With the latest updates of SQL Server 2005, which were delivered by Microsoft in August 2012, you cannot monitor it with PRTG anymore. Therefore, monitoring SQL Server 2005 is discontinued. The following updates cause this issue:

  • Security Update for SQL Server 2005 Service Pack 4 (KB2716429)
  • Security Update for SQL Server 2005 Service Pack 4 (KB2716427)

We have made a reasonable effort to fix this from our side, but were unable to do so. Please ask the vendor for support in this matter.

Created on Dec 12, 2012 10:47:30 AM by  Gerald Schoch [Paessler Support]

Last change on Jun 1, 2022 11:20:13 AM by  Brandy Greger [Paessler Support]



Votes:

2

Your Vote:

Up

Down

You can still monitor your SQL Server 2005 with Custom Sensor PTF.SQLspXML

This sensor parses -multi channel- data from your SQL Server to PRTG.

First create a new Stored Procedure on your SQL Server using the code below:

CREATE PROCEDURE spSQLCounters
AS
BEGIN
SELECT
	 counter_name AS Channel
	,cntr_value   AS Value
	,1            AS IsInt
	,'#'          AS Unit
FROM sys.dm_os_performance_counters
WHERE counter_name IN (
	 'Active Temp Tables'
	,'Connection Reset/sec'
	,'Event Notifications Delayed Drop'
	,'HTTP Authenticated Requests'
	,'Logical Connections'
	,'Logins/sec'
	,'Logouts/sec'
	,'Mars Deadlocks'
	,'Non-atomic yield rate'
	,'Processes blocked'
	)
ORDER BY counter_name
END 

This will return a result set like:

ChannelValueIsIntUnit
Active Temp Tables1871#
Connection Reset/sec2380179151#
Event Notifications Delayed Drop01#
HTTP Authenticated Requests01#
Logical Connections1031#
Logins/sec14566071#
Logouts/sec14565041#
Mars Deadlocks01#
Non-atomic yield rate28300171#
Processes blocked01#

PTF.SQLspXML will consume this result set and literally parse it into PRTG. More examples and how to setup the sensor is described in the download.

Note: you can use

SELECT * FROM sys.dm_os_performance_counters

To get a complete listing of all counters that you can monitor.

Regards,

Created on Dec 12, 2012 7:14:59 PM by  PRTG Tools Family [prtgtoolsfamily.com] (13,333) 3 4



Votes:

0

Your Vote:

Up

Down

Is there a way to connect with PTF.SQLspXML to other than default SQL instance running on a different TCP port?

Created on Jun 7, 2016 9:18:29 PM by  Tomasz (173) 1 1



Votes:

0

Your Vote:

Up

Down

Hi Tomasz,

Please see the table below.

Default-s=myServerName
Instance name-s=myServerName\myInstanceName
Portnumber-s=myServerName,1234

It's not necessary to specify an instance name when specifying the port

Created on Jun 8, 2016 1:31:19 PM by  PRTG Tools Family [prtgtoolsfamily.com] (13,333) 3 4



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.