I have set up an Microsoft SQL v2 as previous is deprecated and it stopped working. o I have made SQL file with exact same code, the initial get is taking VERY long, after that, the value is returns but as soon as I set up lower warning and error limit, sensor jumps to red and show only "0" as last value - this is unacceptable as you cannot rely on monitoring anymore. Any info on this issue???
Article Comments
None - I am checking the actual value that comes from the database - that is my primary data for that particular sensor.
Jun, 2017 - Permalink
Dear DarkMaster
The value channel should not be affected by a warning or error limit. What behavior do you exactly get?
Jun, 2017 - Permalink
I get exactly the described behavior in my first post - the actual value from database is getting trough BUT the limits that I set, namely the lower warning and error limit get confused as the last value is mainly at 0, max is the value...the the last value stays at 0...so the notification is not correct as it is at 0 and I get constant notification of the lower error limit...is this comprehensible? I will try to post link to image of this....
Jun, 2017 - Permalink
Dear DarkMaster
Please contact support@paessler.com with an description, and screenshots. The screenshots should include
- sensor overview
- sensor "Logs" tab
- sensor live or 2 day graph, whichever demonstrates the issues best
- the sensor "Notifications" tab
Jun, 2017 - Permalink
Dear DarkMaster
Are you using the "Execution Time", or the "Query Execution Time" to check? The latter would be more precise as the first one also includes the time to start the underlying C# Exe file which performs the database connection.
Jun, 2017 - Permalink