Published 17 August 2020
Starting with SQL Monitor v10.2, SQL Monitor Base Monitors can no longer be installed on Windows Server 2012 or earlier. For the time being, this only affects the Base Monitor. Support for running the SQL Monitor website on Windows Server 2012 or earlier will be removed in the future.
We've moved to .NET Core 3.1; Microsoft does not support Windows Server 2012 or earlier as deployment targets for .NET Core 3.1. This also means that SQL Monitor Base Monitors cannot be installed on unsupported desktop operating systems. Refer to Microsoft's installation guidance for specific versions.
Installing SQL Monitor
|Windows||SQL Server (any edition)|
You can install all components of SQL Monitor on the following platforms:
The Base Monitor in versions prior to 10.2, and the web application on any version can also be installed on:
SQL Monitor requires a SQL Server database to store monitoring data.
-- See: SQL Monitor database requirements.
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: Installing SQL Monitor on IIS.
You can open the SQL Monitor web application with:
- Firefox (latest version).
- Chrome (latest version).
- Internet Explorer 11 or later.
- Edge (Microsoft supported versions)
Monitoring servers with SQL Monitor
You can monitor the following servers with SQL Monitor:
SQL Server (any edition)
For connecting to servers using WinRM the monitored server must have Windows Management Framework 3.0 or greater installed
Supported Cloud Platforms
SQL Monitor supports:
- Amazon EC2.
- Microsoft Azure virtual machines.
- Microsoft Azure SQL Databases (SQL Server authentication).
- Microsoft Managed Instances (SQL Server authentication).
- 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 currently support Always On Basic Availability Groups.
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.