Posted by Erland Sommarskog on 11/03/58 11:43

Peter Nurse (PtrNrs@yahoo.com.au) writes:
>>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

Thanks for the output. Unfortunately, it did not reveal anything.

Are you familiar with the Profiler and can run a Profiler trace?
Start Profiler, and in the lower right check Show All Event Categories.
Then find "Errors and Warnings" and right-click to selecr the entire
event category. Now, right-click a database and select Properties.

This should reveal exactly which statement that bombs. If you are
uncertain on how to read the trace, save the trace to file, and
put it in a zip file and attach it a post, or just put it on a web
site and post a link.

Note that the trace will include a couple of Error 208. These are false
alarms, and should be ignored. We are looking for error 468.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Order by in a INSERT INTO..SELECT
• Prev in forum: Re: SQL Server 2005: Collation Conflict Error when selecting Database Properties
• Thread view: Re: SQL Server 2005: Collation Conflict Error when selecting Database Properties

[Reply to this message]