Published 08 March 2018
Installing SQL Monitor
|Windows||SQL Server (any edition)|
You can install SQL Monitor on the following platforms:
SQL Monitor requires a SQL Server database to store monitoring data.
There is a known issue when using Windows Server 2019 with Windows Credential Guard enabled, in which Windows LSASS memory usage can increase over time. This is currently under investigation.
Hosting a repository on SQL Azure Database is only supported under certain circumstances. See Using an Azure SQL Database.
Because of SQL Server Express's database size restrictions, we don't recommend using it to host the SQL Monitor database. If you do, you will need to set short data retention windows.
For SQL Monitor 9.2.0 and later, the web server computer and base monitor computer (these might be the same computer) require .NET Framework 4.7.2. You can download it from the Microsoft Download Center.
IIS is optional for the SQL Monitor Web Server. For more information, see Configuring SQL Monitor with IIS.
You can open the SQL Monitor web application with:
- Firefox (latest version)
- Chrome (latest version)
- Internet Explorer 11 or later
Monitoring servers with SQL Monitor
You can monitor the following servers with SQL Monitor:
SQL Server (any edition)
Supported Cloud Platforms
SQL Monitor supports:
- Amazon EC2
- Microsoft Azure
- Microsoft Azure SQL Databases
- Microsoft Managed Instances
- Google Cloud Platform when the monitoring service is in the GCP environment
You may need to set up certain things before you can do this. For details, see Adding servers on a different network from your base monitor.
SQL Monitor supports monitoring Windows failover clusters. Other proprietary clustering server systems aren't supported, and might not behave as expected.
SQL Monitor supports availability groups on Windows failover clusters, but does not support Always On Basic Availability Groups currently.
Running SQL Monitor on a virtual machine
You can run SQL Monitor on a virtual machine, but you should make sure your VM host can deliver the required resources (CPU and RAM). If your physical machine hosts multiple VMs, for example, this will limit the resources available to SQL Monitor, which might slow performance.
If you locate the data repository database on a SQL Server instance running on a VM, we recommend you use a physical disk or partition rather than a virtual disk for the database data files. For more information about using mapped hardware in Hyper-V, see http://msdn.microsoft.com/en-us/library/cc768529(v=bts.10).aspx.
FIPS 140-2 Compliance
The Federal Information Processing Standard (FIPS) publication 140-2 sets out security requirements for cryptographic modules, including a laboratory validation program to approve them.
SQL Monitor does not itself implement any cryptographic functions, instead relying on Microsoft-provided libraries which are part of the .NET Framework. Since SQL Monitor 9.1.3, only cryptographic libraries which have been validated by Microsoft for use in FIPS environments are used by SQL Monitor.
SQL Monitor is therefore suitable for use in FIPS environments, including Windows environments where the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing setting has been enabled.