What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

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




I did read on www:


that you will remove in future (2month) ado sql sensor from 16.x.25. When can I expect another version of ado sql sensor. I using this sensor and I must planing clear transition from my version of prtg to newest 16.x.23 and next 16.x.25.

I have version of prtg. I can't use another sensor for firebird database and now I can't upgrade prtg to 16.x.23 because in this version you blocked adding new sensor ado sql.

ado firebird sql

Created on Apr 4, 2016 7:47:07 PM

Last change on Mar 28, 2022 12:12:33 PM by  Frank Hadasch [Paessler Support] (0) 1

4 Replies



The new ADO SQL sensor is planned to be released before in version 16.x.24. Even if it wouldn't be ready until version 16.x.25, you could still clone an existing ADO SQL sensor to another device. Those mentioned sensors will still work when already in place, you just wouldn't be able to create them newly through the Add Sensor dialogue or when doing a fresh install of PRTG with version 16.x.25 or greater.

Kind regards.

Created on Apr 5, 2016 2:24:32 PM by  Erhard Mikulik [Paessler Support]



OK , I will be waiting for 16.x.24 with new ADO SQL sensor. Thanks

Created on Apr 5, 2016 2:53:44 PM



You can still clone the ADO SQL Sensors you already have and modify them after you upgraded.

I've installed Preview Version today with the new ADO SQL v2 Sensor and get the following error now when using it against SQL Server 2012 An item with the same key has already been added.

Could my error be related to the following microsoft Knowledge Base article (for reporting server)?: https://support.microsoft.com/en-us/kb/2997020

Created on May 6, 2016 10:43:56 AM



Hello Florian,

We are able to reproduce this in the PRTG stable and Preview version and can confirm this is a current bug. We will be providing a fix for the same in a fex days. Please bear with us.

Created on May 11, 2016 1:58:03 PM by  [email protected]

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.