﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administration / SQL Server 7,2000  / Collation inconsistancies / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 19 Jun 2013 19:46:04 GMT</lastBuildDate><ttl>20</ttl><item><title>Collation inconsistancies</title><link>http://www.sqlservercentral.com/Forums/Topic496210-5-1.aspx</link><description>hi folksI’ve had a SQL 2000 server restored (using Veritas 9.1) to another server also running SQL 2000. I now have a collation problem.When trying to add users to a database, I receive a "Error 446: Cannot resolve collation conflict for equal to operation" message.I noted that tempdb and user tables collation don’t match - so I was going to change the user tables. However, the master collation doesnt match tempdb, model or msdb. Server is set to SQL_Latin1_General_CP1_CI_ASMaster - SQL_Latin1_General_CP1_CI_AStempdb, model, msdb - Latin1_General_CI_ASI was under the impression that when tempdb was recreated it inherited the master database's collation? This doesn’t seem to be happening.any ideas?much appreciatedN.</description><pubDate>Wed, 07 May 2008 05:35:12 GMT</pubDate><dc:creator>njw</dc:creator></item></channel></rss>