Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Configure AppInsight for SQL with MS SQL for dynamic ports

Configure AppInsight for SQL with MS SQL for dynamic ports

Table of contents

Updated May 15, 2017


This article describes how to configure AppInsight for SQL when MS SQL is using dynamic port assignments. The article also includes testing the configuration using the current port assignment as well as how to determine if the MS SQL is using a dynamic port.


  • All SAM versions
  • All supported versions of MS SQL


Determine what port SQL Server is using and determine if it is using dynamic ports

  1. Open SQL Server Configuration Manager.
  2. Select SQL Server Network Configuration > Protocols for MSSQLSERVER.
  3. Click TCP/IP, and then select the IP Addresses tab in the popup box.
  4. Scroll to the bottom and find the IPALL listing.


In the above example, the SQL Server is currently using port 1433 and is also not using a dynamic port. If the TCP Dynamic Ports field is 0 or is empty, it means that MS SQL is using a dynamic port that is assigned at the startup. See the Configure a Server to Listen on a Specific TCP Port Microsoft article for additional information on dynamic ports (© 2017 Microsoft available at, obtained on May 15, 2017).
Configure AppInsight for SQL if the SQL Server is using dynamic ports:
  1. Provide the name of the server in the SQL Server Instance Name field.
  2. For SQL Server Port Type, select Use Default Port.
  3. Make sure that the SQL Server Browser service is running.
If the expected status of the components is not obtained, temporarily assign the port to the application, and then test the components. The issue could be with one of the credentials or with Windows authentication.
  1. Using the TCP Port from the above example, set the application to use a specific port by selecting 'Use static port' as the SQL Server Port Type and when the port number is filled out.
  2. For the SQL Server component, if WMI is selected, the credential used must have administrator privileges on the node containing the SQL Server.  See Verify administrator credentials for more information.
  3. Refer to the information in the AppInsight for SQL requirements and permissions article.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified