SQL Monitor - 2.3
Using SQL Monitor for the first time
When you have installed SQL Monitor for the first time
- Create a password to log in to SQL Monitor.
This password will be required for anyone logging in to the SQL Monitor website.
Note: If the Create password screen is not displayed when you enter the URL for SQL Monitor, check that the details for the Base Monitor machine and port number are correct and that the Base Monitor service is running.
You can subsequently change this password by clicking the Configuration tab and selecting Change password:
- Select the servers you want to monitor.
Click the Monitored Servers link in the message box, or select Manage monitored servers from the left side.
You need to supply credentials for SQL Monitor to connect to both the host machine and SQL Server instance. Click any icon for more information about the format for entering a server name and the credentials required.
- Check that SQL Monitor can connect to the servers using the supplied credentials.
The status of each server you add is shown in the Status column. When SQL Monitor is successfully monitoring the following is displayed:
If there is a problem collecting data from a server, click Show log:
Review the error message, and if required, edit the credentials, or take other remedial action. See Account permissions required by SQL Monitor.
- Go to the Global Overview page to see the current health of your monitored servers and databases.
Click the Overviews tab. All your monitored servers should be displayed, showing performance data and any raised alerts. You can start to drill down by selecting particular instances or databases from the Monitored servers list on the left side. See Using the overviews.
After you have been using SQL Monitor for a short while
- If required, organize your monitored servers into groups. This will help you manage your development or production servers more easily in SQL Monitor.
- Review any raised alerts.
You may see some alerts already raised for your servers. SQL Monitor is pre-configured with default settings for all alert types.
To review any raised alerts, go to the Alerts tab and click on an alert in the inbox to view its details. You can then start to clear alerts that you have dealt with, or configure their settings. See Working with alerts.
- Review the default settings for all alerts.
Click the Configure alerts link under Monitored servers on an overview or alert page to view all the alerts that SQL Monitor can raise, and review their default settings. You can configure an alert's settings globally (at the All Servers level) or for any group, server, database or job. See Customizing alerts.
- Set up email notification for your alerts.
Go to the Email settings page (Configuration > Email settings), and enter your SMTP mail server settings and a global email address. SQL Monitor will send emails to this email address when alerts are raised. You can later configure each type of alert to send emails to different recipients. See Setting up email notification.
When you have been running SQL Monitor overnight
- Set up a filter to see only important alerts raised since you were last at your computer.
In the Alert Inbox click to expand the Advanced filter panel, and select a time from the From the last box, or enter a custom time range. You can also filter to show only alerts raised at a certain level. Click Save as custom filter to re-apply the filter options quickly every morning:
You can save any number of useful filters to help you prioritize reading alerts in the Alert Inbox.
- Rewind time to look at the performance of your servers at a point during the night.
Go to the Global Overview page, drill down to a SQL Server instance or database, then click the Rewind time button in the top right corner:
Select a time and click Apply. All the sparkline graphs are updated to show their value at the time you select. Use the Back in Time bar to step forward or backward to see how these values change over time:
- Go to the Analysis tab to view graphs of various performance counter values for the last few hours for your key servers.
When you have been running SQL Monitor for several days
- Review the data purging options.
As SQL Monitor collects monitoring data from your servers, the size of the SQL Monitor Data Repository will increase. You can adjust how much historical data SQL Monitor stores in this database, to manage its size and ensure that you don't run out of disk space.
- Continue to tweak the configuration of alerts as they are raised.
Over time you can improve the relevance of the information SQL Monitor provides by customizing more alerts, at a more granular level. When an alert is raised, open it and click the Customize alert link to edit the settings for only the relevant object, e.g. a specific server, database or job.
- Set up different email recipients for different types of alerts or servers.
As part of each alert's configuration, you can enter a different email address, so that other colleagues in your organization are notified when a particular type of problem occurs, or a specific database is affected. See Configuring email notification settings.
- Compare the performance of various aspects of your server or database performance on different days.
Go to the Analysis tab and select the performance counter and server or database you are interested in. You can now select a comparison timeframe from the Time range drop-down box:
- When your evaluation period expires, go to the Licensing page (Configuration > Licensing) to enter your serial numbers and choose which servers you want to license.
- Go to the Monitored servers page to remove any servers you are no longer monitoring.
Was this article helpful?
Thanks for your feedback!
- Example configuration of SQL Monitor using virtualization software
- Retrieving alert settings using SQL Data Compare
- Licensing issues with SQL Monitor
- Log files in SQL Monitor
- Upgrading to a later version of SQL Monitor
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
all SQL products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs