I built our Jira server instance in azure (using windows server 2016 vm and Azure SQL DB). All went smoothly until the instance health check ran post install and I found that the default Azure SQL db collation 'SQL_Latin1_General_CP1_CI_AS' is not supported.
The only way I have found to change this is to export the db and load it onto an instance of on-prem SQL, then change collation and migrate back into Azure SQL. This is all well and good if you have an on-prem sql instance, which unfortunately I do not.
1) What is the impact for Jira 7.13 using this database collation, safe or not?
2) As I have only just built this instance, should I just tear it down and start again? or is there an easier way to change and rebuild the DB once the installation has completed?
Thanks in advance for any insight into this!
Azure SQL should be supported but it's not that well documented.
There's a resolved issue where they confirm it's supported but should be configured using the MSSQL type.
You might as well open a support request regarding the health check and collation.
Hi there. It is quite possible (even highly likely) that there never has been a problem using a collation that is not one of the two "supported" collations. Other people have used other collations and have been fine:
It is much more likely that the reason for having those two "supported" collations is due to a lack of understanding of how collations work (or at least work in SQL Server) than it is from their being actual functional requirements tied to those two collations. I am 99.999999999% certain that the only things that matter are:
So to answer your questions:
Take care, Solomon...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events