Cannot resolve the collation conflict

[Chuck Bishop]

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.

[Sandeep Jain]

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

[Nic Brough -Adaptavist-]

You'll need to explain the context of this question