SQL Monitor - 2.3
Installation guide - SQL Monitor
SQL Monitor is a web application that runs in your browser. It does not require anything to be installed on the SQL Servers you want to monitor.
SQL Monitor comprises three main components that need to be installed:
- Web Server
The Web Server delivers all the pages for the SQL Monitor web interface
- Base Monitor service
The Base Monitor is a Windows service that continuously monitors your SQL Servers
- Data Repository database
The Data Repository is an MS SQL Server database that stores all the data collected by the Base Monitor service
Click in the installation wizard to read more about a SQL Monitor component or installation option.
For information about installing on an IIS server, see Using SQL Monitor with IIS.
If you have encountered error messages when installing SQL Monitor, see Account credentials required when installing SQL Monitor.
Where to install components
The Web Server and Base Monitor service can be installed on the same computer, or on different computers on your network.
The SQL Server database for the Data Repository can be hosted on any SQL Server instance, but the Base Monitor computer will need access to this database.
Note: Installing the Web Server and Base Monitor service on the same computer that's hosting the SQL Server instances you want to monitor is not recommended.
The Base Monitor service computer needs to be able to connect to the following:
- the SQL Servers you want to monitor, for collecting data about their performance
- the Data Repository database, for storing the collected data
The Web Server should be accessible by any PC or device on which you want to view the SQL Monitor client, and must be able to connect to the Base Monitor.
The Data Repository requires a SQL Server 2005 or 2008 database.
The Base Monitor and Web Server computers should always be switched on.
Installing the SQL Monitor Web Server
- Run the SQL Monitor installer on the computer that you want to host the Web Server.
If you choose to install only the Web Server, the installation wizard will finish once the Web Server is installed; otherwise the wizard will continue with options for installing the Base Monitor and Data Repository.
- Choose whether to install the SQL Monitor Web Server or use an existing IIS Web server.
If your computer is already in use as an IIS Web Server, you can choose to configure IIS to add SQL Monitor. See Using SQL Monitor with IIS.
If this is not the case, you will need to install the SQL Monitor Web Server. The SQL Monitor Web Server is a self-contained XSP Web Server that runs using the .NET 3.5 runtime.
- Select a TCP port for incoming connections to the Web Server.
Use the default port of 8080 unless it is already in use.
- If you are installing just the Web Server, click Finish to close the installation wizard and automatically open SQL Monitor in your browser. You can then download the Base Monitor installer to another computer and install the Base Monitor and Data Repository.
We recommend that you copy the SQL Monitor URL link displayed on the final page of the wizard.
If you are installing both components, the wizard will continue automatically with options for installing the Base Monitor service and Data Repository database.
Installing the SQL Monitor Base Monitor service
- Specify where to install the files that will run the service, and provide a writable folder for the configuration file.
The configuration file stores the location of the Data Repository and the connection string for accessing the database. The configuration file requires a writeable location so that it can be updated by SQL Monitor if you move the Data Repository database to a different SQL Server instance.
- Select a TCP port to use for communicating with the Web Server and the Data Repository.
Use the default port of 7399 unless it is already in use.
You now need to create a SQL Server database to use for the Data Repository, and ensure the Base Monitor service can connect to it.
Setting up the Data Repository
The SQL Monitor Data Repository requires an MS SQL Server 2005 or 2008 database to store all the data it collects from your monitored servers.
We recommend that you estimate the eventual size of your database using the guidelines described in Supported platforms and hardware requirements, and use a SQL Server management tool to create a database with settings appropriate to your environment. You can then follow the instructions below on using an existing database.
Note: If you are installing the Data Repository on a virtual machine, make sure that the SQL Server database is installed on a physical disk mapped to the virtual machine. Storing the Data Repository database on a virtual disk will affect performance and is not recommended.
Using an existing database for the Data Repository
If you have followed our recommendations and created a new database, it should be completely empty, i.e., it should not contain any tables.
You can also select a database created during installation of a previous version of SQL Monitor v2.
To specify your Data Repository database:
- Click Set Up Data Repository and then select Use an existing SQL Server database.
- Click Next, then select the SQL Server instance.
- In the Database box, select the database you want to use; databases on the SQL Server should be automatically detected, and appear in the list.
You can type an instance name or IP address directly into the Server box if the instance name does not appear in the drop-down list.
- Click Next. SQL Monitor checks the database. Once the database connection has been confirmed, click Close.
Note: To make sure CPU isn't wasted on monitoring files that don't need monitoring, we recommend that you configure your antivirus settings to ignore SQL Monitor database
To create a new database for the Data Repository
- Click Set up Data Repository and then select Create a new SQL Server database.
- Click Next, then enter the SQL Server instance name.
You can type an instance name or IP address directly into the SQL Server box if the instance name does not appear in the drop-down list.
- By default, SQL Monitor will create a database called
RedGateMonitor. To use a different name, in the Database box, type the name you want.
- Under Create database using, one of the following:
- Use current credentials to use the account that you are currently logged into.
- Specify an account. If you select Windows authentication, SQL Monitor assumes this account is in the current domain. To use a different domain account, enter credentials in the format username@domain-name or domain-name\username. Enter the password.
The specified account must have Create Database permissions.
- Click Create Now to create the database. Once database creation has been confirmed, click Close. If you go back a page in the wizard, this will not undo the creation of the database.
Note: If you have antivirus software installed on your server, we recommend that you configure it to stop monitoring the folders where your SQL Monitor database
.ldf are stored; this can free up valuable CPU.
Error when creating the database?
If you encounter an "Invalid sequential schema version" or "Database is not empty...." error when creating the database, see Errors when creating a Data Repository database.
If the error is related to permissions, see also Account credentials required when installing SQL Monitor.
Connecting to the Data Repository database
The Base Monitor service requires credentials to connect to the database you just created in order to store and retrieve collected data. This account must have administrator privileges (db_owner database role) on the database.
If you connect to the database using Windows authentication, the Windows account you select will also be used to run the SQL Monitor Base Monitor service. If the account does not have permissions to run a Windows service, then it will be granted these permissions.
The user name defaults to your current domain. You can change the domain in the User name box using either of the following formats:
SQL Server authentication
You can connect to the database using SQL Server authentication. If you provide SQL Server login credentials, the Base Monitor service will run under the Local Service account.
If you encounter an error message when connecting to the database, see Account credentials required when installing SQL Monitor.
SQL Monitor can send data back to Red Gate about the features you use and any application errors you encounter. This helps us to improve SQL Monitor for future releases.
Data is anonymized before we receive it, and no confidential information is sent to us.
If you are happy to allow this data to be sent, select Send error reports, and optionally enter your email address. We will only contact you in the event of an error for which we require further information, to help us eliminate bugs.
- Review all your installation options on the Summary page. If you want to change anything, use the Back button to edit the required page.
Note: Once your database for the Data Repository has been created, it will not be deleted if you go back and set up a different Data Repository.
- Click Install to start installing SQL Monitor using the selected settings.
- When installation has completed, click Finish to launch SQL Monitor.
To start using SQL Monitor, you first need to create a password to use when logging in to the SQL Monitor pages.
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