Monitoring servers with SQL Monitor

Information on supported versions of monitored servers can be found on their specific pages:

• SQL Server
• PostgreSQL

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 .NET. 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.

For more information on how SQL Monitor protects sensitive data, see How SQL Monitor protects secrets.

Installing SQL Monitor

IIS

IIS is optional for the SQL Monitor Web Server. For more information, see: Installing SQL Monitor on IIS.

Supported browsers

You can open the SQL Monitor web application with:

• Firefox (latest version).
• Chrome (latest version).
• Edge (Microsoft supported versions)