SQL server 2008 R2 Collation and Fisheye Collation mismatch

[Bill Mariasoosai]

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

[Piotr Swiecicki]

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,