Avoiding SQL Server collation woes in the TempDB

by Michael S. Kaplan, published on 2006/05/30 13:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/05/30/610889.aspx


Kimberly L. Tripp has a great post entitled Changing Database Collation and dealing with TempDB Objects.

Definitely worth a read -- this is a problem I have bitten by in the past and have been defensively using per-column collation in TempDB operations when the solution Kim suggests is actually much simpler in just about all of the cases one might hit.

Thanks, Kim!

To her advice I will add my old reminder that at least for testing purposes, Case/kana/accent/width sensitive collations are better. Because it is MUCH easier to go from sensitive to insensitive than the other way around....

 

This post sponsored by K (U+004b, a.k.a. LATIN CAPITAL LETTER K)


Nikonboy on 19 May 2011 2:13 AM:

This post is now here www.sqlskills.com/.../tempdb.aspx

Michael S. Kaplan on 19 May 2011 10:44 AM:

Kinda funny that the Permalink broke. Not funny ha-ha, but you know....

Michael S. Kaplan on 19 May 2011 10:46 AM:

The old link was www.sqlskills.com/.../PermaLink.aspx


referenced by

2007/10/08 Wanna take a look at the collation bug Kim pointed out? You're in for a hell of a Tripp!

go to newer or older post, or back to index or month or day