pk_AO_587B34_GLANCE_CONFIG_ROOM_ID' is not a constraint.

[Nhan Nguyen]

Hey mates,

I am getting a ton of ID insert error.  I am unable to create project boards and even projects.  It is not related to permissions :)

I suspect that this was because I changed the MS SQL Server collation AFTER the initial install.  

I am hoping to be able to backup the tickets/config and restore to a new Jira instance and transferring my licenses over.  Is this possible?

[Shannon S]

Hi Nhan,

To fix the collation, you actually need to create a new database with the proper collation and then import your data over. Can you confirm this is what you did?

• How to fix the collation of a Microsoft SQL Server JIRA database

So I would recommend the following:

1. Backup your current Jira to XML
2. Create a new MS SQL database with the proper collation.
3. Setup a fresh installation of Jira, and connect to the new database.
4. Restore the XML to the new instance.

Your license should transfer over just fine, no need to enter the Server ID.

Please also be sure that you're using a supported MS SQL version. In Jira Server 7.8* it would be MS SQL 2012 or 2014.

Regards,

Shannon

[Nhan Nguyen]

I skipped step #3 and #4.

I basically hooked it back to the updated database.  Will go through the complete process and report back.  Thank you for your prompt response.

[James Roxburgh]

Hi @Nhan Nguyen

It's been a few months since your post and just wondering if this resolved your issues? Have the same problem....

Thanks.

[Andrea Guarino]

same here...

[Shannon S]

@James Roxburgh and @Nhan Nguyen, 

Can you confirm that you recreated the MS SQL database from scratch with the correct settings? Once you've done that, you can proceed with importing the XML file. I can confirm this should resolve your issue.

If you continue to have issues after importing the XML backup onto a fresh MS SQL database using our supported settings, please feel free to raise a new question on Community or a ticket with our support team so we can have a look at your logs.

Regards,

Shannon

[James Roxburgh]

@Shannon S yes we did get this sorted thanks. It took a while to ensure that correct collation was being set by the DBA. That was our issue. Each time the new database was created, somehow the wrong collation was being used. We finally got there! Thanks.