|
|
Posted by bradsbulkmail on 10/02/52 11:43
Your problem is that TempDB is using a different collation than your
application DBs. When performing operations where TempDB is used (such
as JOINs or ORDER BYs) on char/vchar columns you'll get this error
message because the result set doesn't match the collation order of
the application DB. THe only way I know how to correct this is to
create a new database, migrate the data from the old DB to the new DB,
drop the old DB and then rename the new DB to the same name as the old
one. You can also BCP out the data, drop and rebuild the database and
then BCP the data back in, but most folks don't know how to use BCP.
Brad
On 27 Mar 2006 11:40:44 -0800, "Peter Nurse" <PtrNrs@yahoo.com.au>
wrote:
>>Could you run this and post the output:
>
>> select name, collation_name, compatibility_level from sys.databases
>> select serverproperty('Collation')
>
>name collation_name
> compatibility_level
>----------------------------------------------------------------------------------------------------------
>master Latin1_General_CI_AS
> 80
>tempdb Latin1_General_CI_AS
> 90
>model Latin1_General_CI_AS
> 90
>msdb
>SQL_Latin1_General_CP1_CI_AS 90
>pubs Latin1_General_CI_AS
> 80
>Northwind Latin1_General_CI_AS
> 90
>ASPProBU SQL_Latin1_General_CP1_CI_AS
> 80
>ASPProWeb SQL_Latin1_General_CP1_CI_AS
> 80
>ASPPro Latin1_General_CI_AS
> 80
>
>(9 row(s) affected)
>
>
>----------------------------------------------------------------------------------------------------------
>Latin1_General_CI_AS
>
>(1 row(s) affected)
>
>
>
>>Assuming that all databases are in mode 80, try running
>>"sp_dbcmptlevel Northwind, 90" and see if this changes anything.
>
>Doesn't seem to fix anything.
Navigation:
[Reply to this message]
|