Sunday, March 11, 2012

Cannot view database properties

Hello all....

I am in the process of changing all of the collation to SQL_Latin1_General_CP1_CI_AS.

I have backed up all databases, and uninstalled SQL Server 2005. I then reinstalled SQL Server 2005, setting the server collation to SQL_Latin1_General_CP1_CI_AS.

The user databases have been restored and are accessible by all applications.

If I try to view the properties of any database (system or user), I get the following error:

*********************************************************************************************************************************

TITLE: Microsoft SQL Server Management Studio

Cannot show requested dialog.


ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the equal to operation. (Microsoft SQL Server, Error: 468)

****************************************************************************************************************************************

I have tried executing the "Alter Database [dbname] Collate SQL_Latin1_General_CP1_CI_AS" procedure, but that does seem to help. Does anyone have any ideas?

Thanks,

Forch

What is the collation or all the databases?

run select * from sys.databases.

How did you restore the databases, backup/restore, attach/dettach?

|||

Master is SQL_Latin1_General_CP_C1_AS, and the rest of the system dbs is Latin1_General_CI_AI. The user dbs are evenly divided between the 2.

I can't remember how I restored.... it was probably backup / restore.

Thanks,

Forch

|||

Hi Forch,

Probably the backed up databases have the old collation, but the SQL server system databases have the new collation.

You can do:

ALTER RESTORED_DATABASE { COLLATE SQL_Latin1_General_CP1_CI_AScollation_name }

to change the collation of the restored databases to the new collation

Cheers

|||Have you tried to access the database from the query analyzer too?

No comments:

Post a Comment