Database Collation health check fails in Jira Server when using SQL Server

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

Purpose

This check retrieves the collation of the database and determines if it is within the list of collations supported by Atlassian. This article focuses on Microsoft SQL Server. For more about details please check Database Collation Health Check fails in Jira Server.

Understanding the Results 

The database collation '<collation>' and table collation '<collation>' are supported by JIRA.

The database is configured using a supported collation.

The database collation '<collation>' and table collation '<collation>' are not supported by JIRA.

The JIRA instance is using an unsupported configuration. See the Solution for steps on how to resolve this issue.

The database collation '<collation>' is unsupported by JIRA. The table collation '<collation>' is supported by JIRA.

The JIRA instance is using an unsupported configuration. See the Solution section for steps on how to resolve this issue.

The table collation '<collation>' is unsupported by JIRA. The database collation '<collation>' is supported by JIRA.

The JIRA instance is using an unsupported configuration. See the Solution section for steps on how to resolve this issue.

Solution 

To fix this, the database collation needs to be corrected. The best and recommended way to achieve this is:

  1. Create a new database with the required collation as per the appropriate documentation in Connecting JIRA to a Database.
  2. Follow our Switching Databases to migrate JIRA from the old databases (with the incorrect collation) to the new one, with the correct collation.
  3. If the recommended method for some reason is not suitable for your scenario, please follow this link Fixing collation manually to manually fix the collation at the database server side manually.

Supported Collations in Microsoft SQL Server

  • SQL_Latin1_General_CP437_CI_AI
  • Latin1_General_CI_AI

How to Verify Table Collations

SELECT DISTINCT C.collation_name 
FROM   sys.tables AS T 
       INNER JOIN sys.columns C 
               ON T.object_id = C.object_id 
WHERE  collation_name IS NOT NULL; 

How to Verify Database Collations

SELECT CONVERT (varchar(256), DATABASEPROPERTYEX('database_name','collation'));  replace the'database_name' with your Jira Database name
OR
SELECT name, collation_name
FROM sys.databases
WHERE collation_name NOT IN ('SQL_Latin1_General_CP437_CI_AI','Latin1_General_CI_AI');

There is a known bug where Latin1_General_CI_AI is displayed as an unsupported database in JIRA. The bug fix is released on JIRA 7.8.0  JRASERVER-59378 - Getting issue details... STATUS

DescriptionThis check retrieves the collation of the database and determines if it is within the list of collations supported by Atlassian. This article focuses on Microsoft SQL Server.
ProductJira, Confluence, Bamboo, Bitbucket, Fisheye, Crucible
PlatformServer
Last modified on Mar 23, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.