I created an SQL sensor (Microsoft SQL v2). as it worked, i recognized a little mistake resulting in "wrong" output. I modified the query, saved the file again in the original place, but the sensor still uses the "original" query (as i could confirm by logging the query details). Even rebooting the whole probe did not change anything.

So my question is: How can i modify the underlying query of an SQL sensor without re-creating the whole sensor (with all its settings) ?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Dear Arnold,

does that sensor run on a remote probe? In this case, the .sql file has to be changed on that computer.


Jul, 2018 - Permalink

No, there is just one local probe.


Jul, 2018 - Permalink

Dear Arnold,

if the old file is overwritten, the sensor has to use the current one, as the SQL statement is not cached. For analysis, please create a second sensor with the overwritten .sql file. Do you get the old, or the current version?


Jul, 2018 - Permalink

Is there a way to change the SQL Query File using the API?


Feb, 2019 - Permalink

Setting the executed .sql-file with an API call is not supported. Please set this the only supported way by creating the sensor by hand.


Mar, 2019 - Permalink