Re: Collation advice going from 2000 to 2008
- From: "Sylvain Lafontaine" <sylvainlafontaine2009@xxxxxxxx>
- Date: Mon, 8 Jun 2009 10:00:16 -0400
"JimLad" <jamesdbirch@xxxxxxxxxxx> wrote in message
news:7c459f9d-e70a-4283-9eff-7aeb2ffd59b1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Geoff,
Have you ever tried migrating a db with one collation onto a server
with a different collation. Then try using any code with a temp table
and see how you get on! :-)
This assumes you haven't been specifying collation on all joins etc...
James
Hi James, if you have trouble with a temp table and a collation when making
your joins, it's usually because you didn't use the collate database_default
option for the field(s) when creating the temporary table or had an improper
use of the USE datababase command before creating this temporary table; see
http://drsql.spaces.live.com/blog/cns!80677FB08B3162E4!1368.entry .
Pay close attention to the different result for the column
[defaultCollation] in both tables when either USE TEMPDB or USE
testCollation is used before the creation of each temporary table.
--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)
.
- Follow-Ups:
- Re: Collation advice going from 2000 to 2008
- From: JimLad
- Re: Collation advice going from 2000 to 2008
- References:
- Re: Collation advice going from 2000 to 2008
- From: JimLad
- Re: Collation advice going from 2000 to 2008
- Prev by Date: Which row inserted first
- Next by Date: Re: Collation advice going from 2000 to 2008
- Previous by thread: Re: Collation advice going from 2000 to 2008
- Next by thread: Re: Collation advice going from 2000 to 2008
- Index(es):
Relevant Pages
|