Collation problem migrating 2000 > 2005

Hi,
Migrating SQL from 2000 to 2005 I did:
1/ backup of SQL2000 db :
BACKUP DATABASE [HCW] TO DISK = 'C:\data2\db.bak'
2/ restore it on 2005 :
RESTORE FILELISTONLY FROM DISK= 'C:\data2\db.bak'
RESTORE DATABASE [HCW] FROM DISK= 'C:\data2\db.bak' WITH
MOVE 'db_moss_Data' TO 'C:\Program files\Microsoft SQL
Server\MSSQL.2\MSSQL\Data\db_Data.mdf',
MOVE 'db_moss_Log' TO 'C:\Program files\Microsoft SQL
Server\MSSQL.2\MSSQL\Data\db_Log.ldf',
REPLACE
After updating connection string my .Net site works like a charm now on
2005.
Except FTS which returns following error:
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS"
and "Latin1_General_CI_AS" in the equal to operation.
What is the good practice to deal with this issue?
Thx for any help.This happened to me when some old SQL 7.0 table were brought into SQL
2000 with the conversion being done. I believe the term
"Latin1_General_CI_AS" is the old term for collation on 7.0. To solve
it I went into the table definitions with this collation and deleted
the user defined collation. When no collation is specified the
database default is inserted making it compatible with the current
database. You could also put in the value you wanted if you do not
want the default.
This fixed my problem.|||thank you.
solved by recreating the table using collation that I needed.
"miathet" <miathet@.gmail.com> wrote in message
news:1194295291.875474.263720@.o80g2000hse.googlegroups.com...
> This happened to me when some old SQL 7.0 table were brought into SQL
> 2000 with the conversion being done. I believe the term
> "Latin1_General_CI_AS" is the old term for collation on 7.0. To solve
> it I went into the table definitions with this collation and deleted
> the user defined collation. When no collation is specified the
> database default is inserted making it compatible with the current
> database. You could also put in the value you wanted if you do not
> want the default.
> This fixed my problem.
>