Error 446 - Collation not same on Master as it is on Model/Tempdb

  • Hi

    A couple of months ago I moved databases from one server to another.  I moved master but don't think I moved model/tempdb

    Recently whenever I want to add a new user to a database (any database) in SQL Server 2000, I get the error message: Error 446: Cannot resolve collation conflict for equal to operation.  I ran the following T_SQL:

    select databasepropertyex('master','collation')

    select databasepropertyex('model','collation')

    select databasepropertyex('tempdb','collation')

    The results were:

    Latin1_General_CI_AS

    SQL_Latin1_General_CP1_CI_AS

    SQL_Latin1_General_CP1_CI_AS

    How do I now make the master use the same collation as the model and tempdb???

  • This was removed by the editor as SPAM

  • Collation can be set at multiple levels in SQL Server.  You can set Collation at the instance, database, or object level.  From what I am seeing from your post, your new server has a different default collation at the instance level that your old server did.  Just curious, was your old server a SQL Server 7 server?  Anyway, you may want to rebuild your Master DB and assign it the SQL collation that your new server instance is set to.  Check out this link for rebuilding your Master DB.  By the way, make sure you have backups of all of your database objects and data prior to rebuilding your Master DB.  You can also detach your user databases prior to rebuiding Master. 

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_install_8w8p.asp

    If this is a production server, I would recommend creating the same scenario on a test server and walking through the Master rebuild there prior to doing this on a production server. 

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • Hi,

    I have almost the same problem.

    I would like to insert a new database user to a database and the error message of collation conflict appears. I have checked the master database has a different collation than the model and tempdb.

    It is SQL Server 2000.

    Could someone please help me to solve this issue?

    Many thanks,

    Gergo

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply