How to setup Enterprise Insights Self-Hosted with non-default SQL instance
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
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)
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>
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:
Related Article
Was this helpful?