This page explains how to set up SQL Monitor with IIS 7 later. You can follow the instructions whether you've installed SQL Monitor already or not.

For instructions for IIS 6, see IIS 6.

1. Before you start

1. Make sure your IIS server has ASP.NET enabled. If you installed IIS using Add or Remove Programs or the Configure Your Server wizard, ASP.NET should be enabled already. For more information, see Problems with IIS and ASP.NET.
2. Make sure your IIS service account has full control over the folders listed under web service account on the Permissions page.
3. If you've already installed SQL Monitor, stop the SQL Monitor web service:
   1. From the Start menu, open services.msc.
   2. In the list, select the SQL Monitor web service and click the stop button in the toolbar.

2. Install SQL Monitor to work with IIS

If you've already installed SQL Monitor, skip this section. 

1. Run the SQL Monitor installer on your IIS server, and on the Choose web server page, select I'll use an IIS web server:
    
2. Click Next.
3. On the Installation options page, under Install web interface files to, enter a folder to extract the website files to:
    
4. Follow the SQL Monitor installer steps until you reach the Add the SQL Monitor website to your web server page:
   
   Don't click Finish yet – we'll come back to the installer later.

3. Configure the application pool

The SQL Monitor website needs an application pool with these properties:

• .NET Framework version: 4.0 (for SQL Monitor 4.3 and later), or 2.0 (for older SQL Monitor versions)
• Managed pipeline mode: integrated

To make sure you have a valid application pool

1. Open IIS Manager.
2.  On the right, under Actions, select View Application Pools. This lists the application pools on the server with their properties. Note the .Net Framework Version and Managed Pipeline Mode columns:
   

If you don't have an application pool with the right properties, you can modify the properties of an existing application pool. 

You might not want to do this if the application pool is used by other applications. If so, you can create a new application pool just for SQL Monitor.

To create a new application pool

1. On the right, click Add Application Pool.
   The Add Application Pool dialog box opens.
   Enter a name for the application pool (eg .NET 4.0)
2. In the .NET Framework version dropdown menu:
   
   • If you're using SQL Monitor 4.3 or later, select NET Framework v4.0.30319.
   • If you're using an earlier version of SQL Monitor, select NET Framework v2.0.50727. 
3. In the Managed pipeline mode dropdown, make sure Integrated is selected.
4. Click OK.

4. Configure the SQL Monitor website

1. In IIS Manager, under Connections, right-click the IIS server and select Add Web Site:
    
   The Add Web Site dialog opens:
   
2. Under Site name, enter a name for the website (eg SQL Monitor).
3. Click Select.

4. In the Application pool dropdown menu, select the application pool you want to use.

5. Under Properties, make sure you've selected an application pool with the properties:
   .NET Framework version: 4.0 (if you're using SQL Monitor 4.3 or later) or 2.0 (if you're using an older version)
   Pipeline mode: integrated

6. Click OK.
7. Under Physical path, enter the path to the location of the SQL Monitor website files. By default, this is C:\Program Files\Red Gate\SQL Monitor 4\Web
   If you're installing SQL Monitor, you can copy the path from the SQL Monitor installer:
    
8. Under Port, specify an available port number. 
9. Specify any other options you need (eg binding or certification).
10. Click OK.

5. Finish

1. Test the configuration:
   
   1. In IIS Manager, under Connections, make sure the SQL Monitor website is selected. 
   2. On the right, under Actions, click Browse. The SQL Monitor website opens in your default browser.
2. If you're installing SQL Monitor, in the SQL Monitor installer, select the I've added the SQL Monitor web interface to my web server checkbox and click Finish.

SQL Monitor is now set up with IIS.

Further reading

• Create a Web Site (IIS 7) in the Microsoft documentation