[This is preliminary documentation and is subject to change.]

Author: Halfvares Mats, Teknikhuset AB.

Published: 2008-10-10

Applies to:

Type: How to

More information

Sometimes it is neccessary to rebuild the Content Studio full text indexes. This i always needed when you have restored a Content Studio site database on another database server or on the same server but with another name. The reason for this is that the name of the full text catalogs containing the index is given a name that is dependent on the SQL Server ID of the database ie. "ftxt_DATABASEID_CS_ContentBinary" and "ftxt_DATABASEID_XML_Data" where DATABASEID is the internal id of the database. This ID is not preserved when you restore the database as a new database but the full-text information will remain. You also will note that the database reports that the full text catalog has been lost. In this situation you will need to delete the 2 catalogs and completly rebuild them.

Starting with Content Studio 5.2 SQL Server 2000 or earlier no longer are supported with the product. Version 5.2 uses features that are not available in earlier versions of SQL Server. One of these is the varbinary(max) datatype that makes it possible to support automatic background fulltext indexing. With this datatype, documents can be fulltext indexed within a few seconds and fulltext indexing jobs used in earlier versions no longer are needed. The second script does not support this and will turn off automatic indexing if run on a version 5.2 database.


To rebuild the catalogs

You should now be able to work with the Content Studio full-text index as usual.