Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,412,037
Community Members
 
Community Events
169
Community Groups

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

0 votes

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
TAGS

Atlassian Community Events