Cannot resolve the collation conflict

 

2 answers

1 votes

You'll need to explain the context of this question

Sorry, the question was saved before I completed it. 

Our QA team is evaluating the OpsHub integration between JIRA and QAComplete within the test environment.  As part of the process, they need access to the JIRA db.  We given access to the db, but now it's giving errors that there is a collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP437_CI_AI".  The JIRA db is using SQL_Latin1_General_CP437_CI_AI, but I'm wondering if it's possible that some of the tables are using another collation.

 

Here's the error we get within OpsHub connecting to the JIRA db:

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot resolve the collation conflict between \"SQL_Latin1_General_CP1_CI_AS\" and \"SQL_Latin1_General_CP437_CI_AI\" in the INTERSECT operation.

 

Chuck, was your error connecting Jira db using OpsHub got resolved? 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,760 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot