How to setup Enterprise Insights Self-Hosted with non-default SQL instance

Summary

There could be multiple instances of SQL other than the default instance <MSSQLSERVER>. This article provides guidance on verifying non-default instances and setting up self-hosted Enterprise Insights with a non-default instance.

Environment

Enterprise Insights Self-Hosted

Solution

Step 1: Verify if the SQL server is using a default instance or a non-default named instance. If using a non-default instance, note its name.

  • The default instance of the SQL server has the name "MSSQLSERVER". This can be seen next to the service name of SQL under services.msc. The non-Default instance has the instance name next to SQL Server service. Example: SQL Server(INSTANCE_NAME)

    (Auto-migrated image: description temporarily unavailable)
  • When connecting to the SQL server via SQL Server Management Studio, it is not required to enter the instance name for the default instance. However, to connect to a non-default instance, it is required to enter server name as <Server_name>\<Instance_name>

    (Auto-migrated image: description temporarily unavailable)
  • In the above screenshot example, the name of the non-default instance is "EXTRA_INSTANCE"

Step 2: Running the Enterprise Insights install.ps1

  • When prompted for "Please provide your data warehouse server name:" enter the SQL Server name in the format <SQL_Server_name>\<Instance_Name>

  • Refer to the below example screenshot:

    (Auto-migrated image: description temporarily unavailable)

Related Article

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.