SQL server 2008 R2 Collation and Fisheye Collation mismatch

I have a SQL server 2008 R2 as backend for Fisheye/Crucible (3.1.4)

"fishscru" is the name of the database.

The SQL server DBA says the following:

--------------------------------

SQL14VWT\SQL14VWT's default collation is "SQL_Latin1_General_CP1_CI_AS" (case

insensitive).The collation for "fishcru" is "Latin1_General_CS_AS" (case sensitive).

Errors can generate when joining temporary tables with persistent tables

when there is a collation difference of this sort. Temporary tables (unless explicitly specified)

will create with the server’s default collation, which is different than your databases’.

If you attempt to join the two tables on a character field, you’ll get an exception relating to a

collation mismatch.

----------------------------------

Will this be a potential problem down the road?

Thanks

Bzoo

1 answer

This widget could not be displayed.

Hi Bill,

No, you can expect no problems, your configuration would work fine. FishEye/Crucible would not create any temporary tables so the default collation of Latin1_General_CS_AS specified for your "fishcru" schema would be fine.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

137 views 1 3
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