Health check displays the following collation warning.

[PF]

Health check displays the following collation warning:

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

In an attempt to correct, I have created a new database from a copy of production (with data) and assigned a supported collation  of 'SQL_Latin1_General_CP437_CI_AI'. I then modified 'dbconfig.xml' to reference the copied database.

Health check now displays:

The table collation: 'SQL_Latin1_General_CP1_CI_AS' is unsupported by JIRA. The Database collation: 'SQL_Latin1_General_CP437_CI_AI' is supported by JIRA.'.

Our tables reflect the supported collation, but not their columns, which still retain SQL_Latin1_General_CP437_CI_AI.

How does one update all existing Jira columns to reflect the valid collation value? We are using SQL Server for our db. Anyone have a query that will alter each existing column collation?

[Jimmy Van (GLiNTECH) · Accepted solution]

Hi Paul, You've done well so far :)

After creating the database, you need to create all the tables (empty), with the correct table & column collation.

Instructions are outlined in this article:

https://confluence.atlassian.com/jirakb/how-to-fix-the-collation-of-a-microsoft-sql-server-jira-database-776646810.html

[PF]

I ended up taking a backup of the system within Jira, creating a new database, and then modifying dbconfig.xml to point to the new db. This caused Jira to initiate a new install. Once installed as a new system, I restored the backup file using Jira's restore system. Seemed to work fine. Thanks!

[PF]

I meant to say: 

Our tables reflect the supported collation, but not their columns, which still retain the original collation of SQL_Latin1_General_CP1_CI_AS.