October 3, 2007 at 7:35 am
Our main business application requires Latin1_General_BIN collation on our 2005 database. The system databases for our server uses SQL_Latin1_General_CP1_CI_AS collation.
I am not sure if this will cause a problem down the road. The only time I get an error now is trying to check the securables on a user login to the server. The error is "Cannot resolve the collation conflict between "Latin1_General_BIN" and SQL_Latin1_General_CP1_CI_AS" in the UNION operation.
I know I can change the system database collation, but the question is -- should I go through the hassle?
We do have other database servers which also use the CI_AS collation and I will be setting up some cross-server queries. Does anyone think this may cause a problem?
Thanks
Steve Webb
DBA
Cornerstone University
October 3, 2007 at 9:15 am
We have the same situation ... It can be annoying. If you run queries between DBs with different collation, you may have to write them like this
select * from DB_CollationA..TableA A
join DB_CollationB..TableB B on A.Fld1 = B.Fld1 collate Latin1_General_BIN
October 3, 2007 at 11:58 am
I think you will want to change the tempdb collation to match your app DB's collation, otherwise you may have issues joining temp tables to app tables.
October 3, 2007 at 1:20 pm
I have this between two dbs as well and homebrew's solution works good.
However if I did much tempdb work, I'd change that collation to match the db that gets used most.
October 3, 2007 at 1:22 pm
AFAIR tempdb collation must match Default "SERVER" collation .
* Noel
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply