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???
Microsoft SQL v2 Senzor returning ambigous last value
Votes:
0
5 Replies
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.
Add comment