SQLServerCentral / Discuss Content Posted by Gregory Larsen / Article Discussions / Article Discussions by Author / Beware of Mixing Collations - Part 1 / Latest Posts

RE: Beware of Mixing Collations - Part 1

Greg Larsen — Fri, 10 Jan 2003 08:06:00 GMT

TEMPDB table do present problem in a mixed collation environment. The TEMPDB takes on the collation of the MSDB database every time the server is restarted. One option might be to set your MSDB collation to the most common collation used, therefore minimizing the issues with collations differences across databases.Gregory Larsen, DBAIf you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples

RE: Beware of Mixing Collations - Part 1

Greg Larsen — Fri, 10 Jan 2003 08:05:00 GMT

RE: Beware of Mixing Collations - Part 1

Kevin R. Zakoski — Wed, 08 Jan 2003 10:03:00 GMT

We've run into similar problems, but it may be more important to state that it also depends on where and how a #temp table is created in TempDB. A 'Create Table #Temp' statement will default the tables collation to that of TempDB's. If you create the #temp table with a SELECT INTO #Temp from a DB with a different collation than TempDB, the #Temp table will have the collation of DB it was run from. The same holds true for regular tables you create outside your DB. When we ran into our problem, it wasn't apparent what exactly was occuring until we removed the '#' from the table name and created static tables which we could look at in more detail to resolve our problem.My suggestion is, if you must use different collations on the same server, it's best to adopt a standard for creating #temp tables within your code. If you mix Creates and Select INTO for #Temp tables in your code you will eventually get burnt.

RE: Beware of Mixing Collations - Part 1

Greg Larsen — Wed, 25 Dec 2002 19:49:00 GMT

No I have not checked into the performance issues. I might be interesting to see if there are any issues here. If I get the script I will make sure it gets posted.Gregory Larsen, DBAIf you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples

RE: Beware of Mixing Collations - Part 1

Andy Warren — Tue, 24 Dec 2002 13:45:00 GMT

Maybe of you guys can either find or repost the script and post the link back here? Others will be interested Im sure.Greg, have you looked to see what performance implications of specifying a collation in the join? I use the technique myself when I need a case sensitive join on data that is stored case insensitive.Andyhttp://www.sqlservercentral.com/columnists/awarren/

RE: Beware of Mixing Collations - Part 1

Greg Larsen — Fri, 20 Dec 2002 10:19:00 GMT

I'd like that script. Can you send it to me at greg.larsen@doh.wa.govGregory Larsen, DBAIf you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples

RE: Beware of Mixing Collations - Part 1

tomstraetman — Fri, 20 Dec 2002 08:16:00 GMT

that would be great, can you send me the script to tom.straetman@pi.bethx

RE: Beware of Mixing Collations - Part 1

dwestmore — Fri, 20 Dec 2002 08:05:00 GMT

I've had nasty problems with the collation settings. The strange thing is I had never explicitly done anything to mess about with collation settings, it seemed to happen spontaneously. I work in Italy, some kind of mess up between English and Italian versions of SQL and/or Windows.I did find a script (I think on this site, don't ask me where) for easily changing collation settings on all tables in a DB, if anyone is interested I can send it.

RE: Beware of Mixing Collations - Part 1

Russel Loski — Thu, 19 Dec 2002 06:19:00 GMT

Can mixed collations affect performance?I created a new server and database with a different default collation when I took over our small SQL Server environment. In transferring the objects from the existing server to the new production server, I used the scripts created by EM. For some reason, EM puts collation statements on all character based fields.We connect to SQL Server from Access and for several months the applications would crawl. One night I came in and changed all of the collations to use the defaults. That morning the applications ran real fast and it still runs well. I may have done something else as a side consequence, but the only thing I remember is changing the collations.Is this a known issue? I don't have the lab facilities to test it.RussRussel Loski

RE: Beware of Mixing Collations - Part 1

Steven. — Thu, 19 Dec 2002 03:56:00 GMT

Beware is right, but as long as it is known to the developers etc I have found it isn't too much of a problem.I have had to mix collations on a sql 2000 server (Binary sort order server with dbs, plus a single non case sensitive db). Once you remember that tempdb is case sensitive etc it is not too much of a problem. This has even had the bonus of helping enforce naming standards since tables in the other DB's and tempdb need to be exact.

RE: Beware of Mixing Collations - Part 1

David.Poole — Thu, 19 Dec 2002 02:20:00 GMT

I've come across this problem in SQL 6.5. Pre-SQL2000 my solution was to have a test machine that I could set up SQL Server 6.5 with whatever character set and sort order I needed to restore other peoples data, then bcp it across onto the production server.Pure brute force, but strangely satisfying!

Beware of Mixing Collations - Part 1

Greg Larsen — Sat, 14 Dec 2002 00:00:00 GMT

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/glarsen/collate_part1.asp