Collation error after OS Upgrade

We have a server which we needed to upgrade the OS on it from NT 4 Server to Windows 2000 Server.

As the system disks are seperate from the data disks. We did a fresh install of Windows, then installed SQL Server, applied service pack version 3, and then restored the master database.

From Query Analyser everything appears fine. I can query all the databases and tables, see them all, the web applications talk the database fine so all the users have recreated OK.

However ... if we try and look at the database through management console we get the following error.

A connection could not be established to ...

Reason: Cannot resolve collation conflict for like operation..

This happends logged in locally to the machine as administrator as well as connecting remotely. Does anybody have any idea what is happening?A little more info - I have run a trace to see what happens when enterprise manager connects, and the last thing it tries to run (which generates the collation error) is:

exec sp_MSdbuserpriv N'ver'|||You either have to support all collations or force your clients to reinstall SQL Server with the collation you chose.|||I am sorry but I don't understand what you mean by this?

Originally posted by Satya
You either have to support all collations or force your clients to reinstall SQL Server with the collation you chose.|||Even more info:

Looking at the query and playing a bit the following query if I run the following query against the master database, I get the "Cannot resolve collation conflict for like operation"

declare @.mode nvarchar(10)
set @.mode = N'ver'

if lower(@.mode) like N'serv%'
select 1 as result

NB if this run against another database (on the same server) it runs fine.

HELP!|||What is the default collation choose when you installed SQL Server?|||Unfortunately I didn't run the install - I asked the person running it to take the default collation which was offered.

Originally posted by Satya
What is the default collation choose when you installed SQL Server?|||You can run SERVERPROPERTY (Collation) to get it.|||Thanks for that:

The server collation is set to: Lation1_General_CI_AS
The master database collation is set to: SQL_Latin1_General_CP1_CI_AS

I guess this is the root of the problem. Is there anyway I can change the server default collation without re-installing SQL Server?sqlsql

Clustering Resource depencies

Hello,

With SQL2000 configured with MSCS, we had to stop the SQL service to add additional disk in the SQL Cluster group (in order to use these disks for databases for example).. this was due to the dependencies between the resources.
Do we still have the same issue with SQL2005 running on the cluster? Does the new mountpoint support help in this scenario?
Thanks
Jerome

Yes, the same issue does exist with SQL Server 2005 when adding disks. The new mountpoint support does not really help in this scenario as the mountpoint disk should also be added as a dependent disk to the resource group. It is possible to add the mountpoint without adding the disk to the resource group, but in that case the loss of the disk would not be detected by the cluster service; the SQL Server would attempt to continue running even without the disk (and mountpoint).

Thanks,

Don