Posted by Greg D. Moore \(Strider\) on 10/31/52 11:43

"Peter Nurse" <PtrNrs@yahoo.com.au> wrote in message
news:1143488444.248281.213610@v46g2000cwv.googlegroups.com...
> >Could you run this and post the output:
>
> > select name, collation_name, compatibility_level from sys.databases
> > select serverproperty('Collation')


Out of curiousity, did you sp_detach_db/sp_attach_db the ASPProBU/Web DBs
from 2000->2005?

>
> 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.
>

• Next in forum: Re: How to fire a trigger without changing table data
• Prev in forum: How to fire a trigger without changing table data
• Thread view: Re: SQL Server 2005: Collation Conflict Error when selecting Database Properties

[Reply to this message]