InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 19:31:26 GMT20http://www.sqlservercentral.com/Forums/Topic1066254-391-1.aspxtempdb is dynamically created and always copy collation of the mater db. Temporary tables are stored in tempdb. So if your db has different collation than master db has any operation with temporary table will cause collation conflict.Fri, 18 Feb 2011 07:12:39 GMTsdffdfad faadffadhttp://www.sqlservercentral.com/Forums/Topic1066254-391-1.aspxHello,I dont understand when you're telling me "conflit between tempdb and youre database".The server collation its different in both instances and there's an aplication that automatically will create databases. So i cant change anything in the sp's.Hope you can help me so that i can change collation in one of the instances or that you tell me the best way with less impact so that i can correct the problem.Thanks and regards,JMSM :-)Fri, 18 Feb 2011 07:10:06 GMTJMSMhttp://www.sqlservercentral.com/Forums/Topic1066254-391-1.aspxThis is usually conflict tempdb x yourdb, so rewrite stored procedures and add collate database_default. You can, however, try alter table alter column and unify collationFri, 18 Feb 2011 06:02:50 GMTsdffdfad faadffadhttp://www.sqlservercentral.com/Forums/Topic1066254-391-1.aspxHello,Does any know how can i resolve the following issue with the minimum impact in the production environment.There are a lot of databases that were migrated from a SQL Server Instance with a collation to anotherwith another collation.I apreciate if you can help me to find the fastest and secure solution.Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" Thanks and regards,JMSM :)Fri, 18 Feb 2011 04:18:40 GMTJMSM