Is the Sql User Experience Monitor looking at the returned value in the row or looking at the number of rows returned?
Support won this one
We expect your SQL syntax to return one row and one value, whatever value the SQL query returns then that would be your effective statistic and then from you there you can either manually set a warning and critical threshold value or if you don't know what value to put there for warning or critical you can put a checkbox next to USE BASELINE THRESHOLDs which will just go through your historical data in the database and see what value we've BEEN polling. From there we use baseline - standard deviation to determine warning and then if we detect baseline - an increased standard deviation then the statistic would be hardcoded to change dynamically to critical. Also keep in mind every day @ 2: 15am in the morning we run a Database Maintenance job which includes some verbiage to re-run Baseline Calculation. The idea is that everyday the Baseline Calculation is run its designed to become more and more accurate over time. Let me know if that explanation helps.
Just wanted to add that you can return one row, with two columns (aka values). The first column will be your statistic data -- numerical only. The second column will displayed as the component "Message" in SAM and can be character strings.
