It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.