Re: sql2k Collation problems.
- From: "Adrian Parker" <apparker@xxxxxxxxxxxxx>
- Date: Tue, 13 Dec 2005 08:18:55 -0000
Ok, I see what is happening now, and it's ok for people who have control
over the instance of SQL Server, but when you're a software vendor who
ships pre-configured databases to customers, it's a pain in the.....
-Adrian
"Sophie Guo [MSFT]" <v-sguo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:zyzS4r4$FHA.1240@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> I suggest that you refer to the following information:
>
> Mixed Collation Environments
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
> ar_da_1pwz.asp
>
> You may want to refer to the "Collations and tempdb" section:
>
> *The tempdb database is built each time SQL Server is started, and has the
> same default collation as the model database, which is typically the same
> as the default collation of the instance. If you create a user database
> and
> specify a different default collation than model, the user database has a
> different default collation than tempdb. All temporary stored procedures
> or
> temporary tables are created and stored in tempdb, which means that all
> implicit columns in temporary tables and all coercible-default constants,
> variables, and parameters in temporary stored procedures have different
> collations than comparable objects created in permanent tables and stored
> procedures.*
>
> I test it on my side:
>
> 1. Run Sp_helpdb tempdb
>
> Collation=SQL_Latin1_General_CP1_CI_AS
>
> 2. Run Sp_helpdb mycoll
>
> Collation=Latin1_General_CI_AS
>
> 3. Create a temporary table:
>
> create table #temptb (cola varchar(10))
>
> use tempdb
> go
> sp_help #temptb
>
> Collation=SQL_Latin1_General_CP1_CI_AS
>
> Therefore I think if we didn't explicit specify the collation of the
> temporary table, it will use the collation of the tempdb database.
>
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
.
- Follow-Ups:
- Re: sql2k Collation problems.
- From: Sophie Guo [MSFT]
- Re: sql2k Collation problems.
- References:
- sql2k Collation problems.
- From: Adrian Parker
- RE: sql2k Collation problems.
- From: Sophie Guo [MSFT]
- Re: sql2k Collation problems.
- From: Adrian Parker
- Re: sql2k Collation problems.
- From: Sophie Guo [MSFT]
- Re: sql2k Collation problems.
- From: Adrian Parker
- Re: sql2k Collation problems.
- From: Sophie Guo [MSFT]
- Re: sql2k Collation problems.
- From: Adrian Parker
- Re: sql2k Collation problems.
- From: Sophie Guo [MSFT]
- sql2k Collation problems.
- Prev by Date: Re: sql server 2000 backup and restore
- Next by Date: Re: How to uninstall MS SQL Server
- Previous by thread: Re: sql2k Collation problems.
- Next by thread: Re: sql2k Collation problems.
- Index(es):
Relevant Pages
|
Loading