We know that certain big batch jobs will be running that will take up extra resources at certain times of the day, what we would like to do is suppress these alerts so that we can keep our "tighter" thresholds during the day for when the system is open to the users.

After attending SQL in the city and listening to Grant Fritchey talk about the need to create baselines (and demo sql monitor) a feature I would like is the ability to create a baseline over 24 hours and have it stored. This could be then added to the analysis page as a Versus. ie last hour vs baseline, last day vs baseline.

i.e. only send an email for alerts with a Medium or High priority.

That's it, really - configure read-only/read-write access via Active Directory group memberships or user lists built into SQL Monitor, and allow individual users to log in using their own AD credentials.

Right now we only see the info from the job itself, while the relevant stuff is usually in the steps.

• Display the Job Name (character string) instead of hexadecimal value (SQLAgent - TSQL JobStep (Job 0x442BC6B49DA6FC41A98697F8C2F68956 : Step 1)
• In alerts configuration: Be able to exclude Long-Running query alerts (or any type of alert) for a specific time frame. For example: between 11:00PM and 5:00AM
• When selecting an alert details view, create a link to be able to come back to previous alerts summary screen instead of selecting Overviews link and then again narrowing down to alerts summary by server let’s say…

Monitoring performance of virtualized SQL servers is a bit more tricky. I'd love to see monitoring capabilities of SQL Monitor to be "VM aware" (VMware, Hyper-V)... that is, to differentiate and link the database, virtual server, physical server, and storage layers.

If I have more than one alert of the same type then it would be helpful to get more detail on the front screen.

Given the sizes of some SQL environments we found that it is necessary to have multiple base monitor servers. However currently it is cumbersome to have to navigate to multiple URL's or switch the base monitor that's tied to a web server. Having a central console that is easily and always connected to multiple base monitors would alleviate this problem. Also this could allow you to monitor from various networks and domains.

The analysis reports should be able to run on a schedule and send the via email. For instance it would be great if I could schedule the data/log size report to run every monday and send me the results via email. the ability to export these report to excel is already there, so just needs to be able to run on a schedule and send as an email attachment.

On the “Machine Unreachable” alerts, is it possible to create an additional alert (e.g. after 10 minutes) to advise that a machine is still unreachable?
This would be useful for overnight automated reboots when applying Windows updates, and the current unreachable alerts are extremely useful for that, but it would be re-assuring to know that we would continue to receive further alerts if a server had failed to come back up again (and if we also failed to see the absence of a “Machine Unreachable – Ended” alert)

It would be quite useful and timesaving if one could identify the head blocker for a blocked process (as done in SSMS's Activity Monitor, Processes tab). Otherwise when get a lot of blocked process alerts, you have to manually figure out the head blocker by analysing all the alerts.

Since only one SQL server is active in an Active\Passive cluster, you should not require multiple Monitor licenses.

Most of the alarms need more granular support for excluding/including different things. Using regular expression is a good idea and should be extended further. For example you defenitly need to be able to filter out things from the alarm on the sql server errorlog. Without it's useless.

It might be helpful to have the ability to sort these by name, esp. when this list happens to be quite long. It seems like under the current design they are sorted by database ID.

I have to scroll past 50+ db's to see the remaining info on the UI - can this be improved? Collapsing the list or adding some filtering, e.g. filter to limit to x# which is then changeable by page index, or filter by other than OK status

Include an alert to monitor replication performance. i.e based on the latency reading that you can view in Replication Monitor. The counters for this are "SQL Server Replication LogReader: Delivery Latency" and "SQL Server Replication Dist.: Delivery Latency". I'd like to be able to set the alert priority based on this.

We have multiple servers in different domains. At present there is no trust between the domains and we have a seperate login for each domain. Each domain also has its own IP address range and there may be 2 or more firewalls between the servers. Is an optional agent based approach feasable where all the work happens locally & say XML is punted back & forth over a particular port?

Increase user granularity and allow creating more than the 3 built in user accounts. For example, we have an offshore development team that would like access to their SQL instance, but can’t have access to any other instances. What I would like to do is to be able to create an account, assign permissions to that account against databases or instances, limiting the access they have to production systems. If we could get it to use AD integration rather than forms authentication as well as being able to set permissions granularly then that would be ideal.