Published 21 October 2021
Starting with SQL Monitor v10.2, Base Monitors of SQL Monitor can only be installed on Windows Server 2012 and newer. Support for running the SQL Monitor website on versions earlier than Windows Server 2012 was removed in SQL Monitor v12.0.
We've moved to .NET 5; Microsoft does not support versions earlier than Windows Server 2012 as deployment targets for .NET 5. This also means that SQL Monitor 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:
SQL Monitor requires a SQL Server database to store monitoring data.
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).
- Edge (Microsoft supported versions)
Monitoring servers with SQL Monitor
Roadmap for retiring support for SQL Server versions
Versions of SQL Monitor starting from v. 12.0 no longer support monitoring SQL Server 2005, and versions of SQL Monitor released after 1st August 2022 will no longer support monitoring SQL Server 2008. Microsoft ended extended support for these SQL Server versions in 2014 and 2019 respectively.
There are no plans to retire support for monitoring other SQL Server versions (including SQL Server 2008 R2).
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.
- Amazon RDS SQL Servers (excluding multi-AZ failover instances).
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.