You can't. SQL 2005 uses a different format. You need to rebuild them
completely.
> What is the easiest way to migrate full text indexes from SQL2K to SQL2K5?
Ravi Lobo - 10 Apr 2008 15:50 GMT
Thank you, Hilary!
I undertsand when you say - REBUILD, you meant - RECREATE.
> You can't. SQL 2005 uses a different format. You need to rebuild them
> completely.
> > What is the easiest way to migrate full text indexes from SQL2K to SQL2K5?
Hilary Cotter - 10 Apr 2008 18:20 GMT
IIRC they will both do the same thing!
> Thank you, Hilary!
> I undertsand when you say - REBUILD, you meant - RECREATE.
[quoted text clipped - 3 lines]
>> > What is the easiest way to migrate full text indexes from SQL2K to
>> > SQL2K5?
Ravi Lobo - 10 Apr 2008 18:32 GMT
Thank you, again!
> IIRC they will both do the same thing!
>
[quoted text clipped - 5 lines]
> >> > What is the easiest way to migrate full text indexes from SQL2K to
> >> > SQL2K5?
Mark Harrison - 01 May 2008 06:48 GMT
> You can't. SQL 2005 uses a different format. You need to rebuild them
> completely.
This is an interesting question as I am facing a similar issue at present.
I have a bunch of Version80 databases with full text catalogs on SQL Server
2000 servers that are going to be moved to a SQL Server 2005 cluster. The
intention is to keep them as Version80 databases (for the most part) and the
intention was to carry the full text catalog across to save rebuilding them.
However it seems that even though the database remains as Version80 I need to
rebuild the catalog anyway.
Is that what you think? It seems to be the case from my testing though I
have to say that my understanding of full text indexing is less than complete.
Hilary Cotter - 01 May 2008 10:27 GMT
Yes, that is correct, you will need to rebuild them.
>> You can't. SQL 2005 uses a different format. You need to rebuild them
>> completely.
[quoted text clipped - 15 lines]
> have to say that my understanding of full text indexing is less than
> complete.