Published 31 January 2017
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.
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 purge SQL Monitor data frequently.
For SQL Monitor 6.0.5 and later, the web server computer and base monitor computer (these might be the same computer) require .NET Framework 4.5.2. You can download it from the Microsoft Download Center.
For SQL Monitor 4.3 and later, you'll need .NET Framework 4. You can download it from the Microsoft Download Center.
For older versions of SQL Monitor, you'll need .NET Framework 3.5. You can download it from the Microsoft Download Center.
If you have .NET 4 installed, you still need .NET 3.5 SP1.
IIS (version 7 or 8) 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)
You can monitor servers on a different network from your base monitor, for example those hosted on Azure or Amazon EC2.
However, you 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.
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.