JIRA Health Analyser is showing below error. Our SQL-Database collation is already set to latin1 then also its showing the below error.
So, my Question is
It can cause problems with searching, user IDs, attachments, JIRA Software displays, Service Desk calls, and all sorts of places.
You might not run into any problems. But you probably will sooner or later. And it's quite likely that later versions of JIRA will simply not run when you try to upgrade (Confluence has already done this)
To fix it, you can backup JIRA, point it to a valid database, and re-import, or you can stop it, and use the database tools to change the collation.
Just to add to Nic's answer, (for MSSQL 2012 at least), modifying the collation to an existing database is a bit tricky as all constraint items (may include Primary Keys, Foreign Keys, and Indexes) need to be removed before the collation can be updated. Once the collation has been updated, all of those constraints will need to be rebuilt. Depending on the size of your JIRA instance, and whether or not you've made any custom modifications to the database itself, it's usually much simpler to stand up a new database with the correct collation set and use a JIRA Backup file to re-import the data. When the correct collation is set at the database level, JIRA will rebuild all of the needed tables with the correct collation upon the first startup with the new database.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs