JIRA 7.0.10 - Using SQL_Latin1_General_CP1_CI_AS

We are running SQL_Latin1_General_CP1_CI_AS in JIRA (OnPrem) 6.4.1 and upgrading to 7.0.10.

Can the collation remain as is? Are their any potential risks in leaving the collation as is.




1 answer

@Timothy Chin

  • This is regarding SQL Server, Your suggestion is for MySQL.
  • @Andrew Pawl is referring to what are the potential risks in JIRA if we have wrong collation as per health check.

Thank you anyways. https://confluence.atlassian.com/confkb/how-to-fix-the-collation-of-a-microsoft-sql-server-confluence-database-687216725.html

  • This helps resolving the issue.



Chander Inguva



Timothy Chin Community Champion Mar 13, 2016

Heh, my bad. Not sure why I thought he was talking about mySQL. Deleted the wrong answer.

The instructions are to fix the collation setting in Confluence and not JIRA.  Can you add the link to the instructions for JIRA?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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...

2,728 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you