SMS2>2003 database upgrade problems (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003



Message

kcross -> SMS2>2003 database upgrade problems (11/18/2004 6:02:25 AM)

I cant find any articles on what to do with database upgrade problems. Can someone point me in the right direction please.
Specifically ive got a " Cannot resolve collation conflict for not equal to operation" error.

Thanks in advance

Kim[:o]



brogers -> RE: SMS2>2003 database upgrade problems (11/22/2004 11:20:07 PM)

where do you see this error?

Collation conflicts truly suck...are you moving to a new sql server? Did you install your original SQL server using a collation or sort order other than the default?



kcross -> RE: SMS2>2003 database upgrade problems (12/6/2004 6:56:55 AM)

Brian - thanks for the response - sorry Ive taken so long to reply. Ive found out with sojme more research that the collation order is locale specfic - the server I have problems with must be US english and not UK english as all the others. That resolves the " why the difference" . And as youve intimated - the test sql server was uk english and a different collation order to the database being tested. Reinstalled sql server with the Latin1_general..... collation order and the test worked fine.

Cheers

Kim



kcross -> RE: SMS2>2003 database upgrade problems (10/3/2007 5:57:24 AM)

Bizaar - Ive just got a problem with collation orders and done a search on colation order - found an article I wrote several years ago - which helped me  - but just thought I would add a bit more detail -
The locale setting referred to here is on the advanced tab of regional settings within control panel and the collation order associated with English-US is SQL_Latin1_General_CP1_CI_AS and English UK is Latin1_General_CI_AS

Thats it




kcross -> RE: SMS2>2003 database upgrade problems (6/20/2008 6:42:01 AM)

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.[:D]

_____________________________

Frank Aune
ITpro.no
Norway



jnelson993 -> RE: SMS2>2003 database upgrade problems (6/20/2008 10:26:26 AM)

From 11/18/2004 to 6/20/2008 ... it only took you 3 years & 7 months to get a solution?  That's persistence! :)



bjohn -> RE: SMS2>2003 database upgrade problems (6/20/2008 1:07:45 PM)

LOL



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.3125