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?



1 answer

0 vote

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 Join to answer
Community showcase
Davin Studer
Published yesterday in Confluence

FUME – A Better Confluence User Macro Editor Experience

...\\.title', editorDiv: 'userMacroEditorDiv', isNew: function(){ return AJS.$('#user-macro-form').prop('name') == 'addusermacro' ? true : false; }, editor: null, isDirty...

28 views 0 3
Read article

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