kcross
Posts: 114
Score: 1 Joined: 9/13/2001 From: Chippenham, Wiltshire, UK Status: offline
|
and this bit fromFaune is great as well: I really, really like easy - or at least fast - solutions! It was different collation on the tables that was the problem. Some had ' Latin1_General_CI_AS' while others wrongfully had ' SQL_Latin1_General_CP1_CI_AS' . I ran the following commands in SQL Query Analyser on database SMS and the SMS 2003 upgrade ran successfully! --Show which different collations you have in the tables select distinct collation from syscolumns --Open SQL Server to allow change to the syscolumns table go exec sp_configure N' allow updates' , 1 go reconfigure with override go -- Update collationid so that you only have <NULL> or ' Latin1_General_CI_AS' as collation update syscolumns set collationid = 53256 where collationid <> 53256 go -- And finally, prove that the update has been done right select collationid, collation from syscolumns where collation = ' Latin1_General_CI_AS' Now I can go to lunch and enjoy the taste of victory. _____________________________ Frank Aune ITpro.no Norway
_____________________________
Kim in the UK....
|