How to setup PROD and UAT with same SQL server for self-hosted Jira Align
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
How to setup PROD and UAT with same SQL server for self-hosted Jira Align
Environment
Jira Align Self-Hosted
Solution
Prior to Jira Align v10.127:
Prior to Jira Align 10.127 (10.126 and below), Jira Align used two Databases: the Customer Database and AgileCraftServer. The name of the customer database can be customized. However, the "AgileCraftServer" Database name is hardcoded and cannot be customized. Hence, there can be only one Database named "AgileCraftServer," which cannot be and should not be used for both PROD and UAT.
Option 1:
Use two different SQL Servers for PROD and UAT instances
Option 2:
Use the same SQL server with the default instance and named instance. Default instance can be used for PROD and named instance can be used for UAT
Refer to the article on how to configure SQL with a named instance - How to setup Jira Align Self-Hosted with non-default SQL instance
Jira Align v10.127 and above:
With Jira Align v10.127 and above, Jira Align uses only one database, which is the customer database. Hence, two different database customer names can be used for PROD and UAT.
Was this helpful?