SQL Server monitoring tools generally require somewhere to install the service that does the monitoring.
In SQL Response 1, we required you to install an Alert Repository – a combination of a Windows service to collect data from your monitored servers and a repository for storing the collected data. In SQL Response 2, it’s likely that you will be able to have more control over the location and properties of the data store, but you will still need to install the service that actually runs the monitoring somewhere.
The key attribute for this service is that, quite logically, it requires access to all the servers you want to monitor – it needs to be able to login to both the physical server and to the SQL Server instance for everything you want to monitor.
Some questions about setting up the monitoring service
- Do you have a dedicated box for this kind of thing? Or do you tend to install the monitoring service on one of your less important servers that may run one or two less critical instances?
- Do you have an account set up that can access all servers specifically for the purpose of using a monitoring tool?
- Have you run into difficulties in the past trying to install and configure a monitoring tool? What was the biggest issue? Separate domains? Credentials issues?
- How much control do you want over the storage of monitoring data? Control the type, location, size, name, permissions of the data store and so on?
- Do you want to run your own custom reporting against the data store?
Or tell us anything else about how you’d like to configure the overall topography of your monitoring solution.