FIX: Full Text RANK Results May Vary After Catalog Repopulation (312410)

   Build         File Version     File name      Modified Date
   ---------------------------------------------------------------------

   8.00.0564     9.107.6815.4     Tquery.dll     Dec 27 2001 4:21:27 AM
				

MORE INFORMATION

When this problem appears, the ranking value associated with a given row may be slightly different after a catalog is repopulated. In addition, this change in row ranking may cause small changes in the relative position of a row if the resultset is ordered on the RANK column.

Important: The fix for this problem requires a change in the underlying structure of the full text catalog files. To allow for the catalog format change, the search service immediately initiates a full catalog rebuild the first time you start MSSearch after you apply the hotfix. While the catalog is being rebuilt it does not reflect all of the data in the full-text indexed tables, which means that you should schedule the hotfix installation at a time when you can have the catalog temporarily offline while MSSearch rebuilds the catalog. If there is no such time, another option is to apply the hotfix to a different server with a copy of the production database, and then rebuild the catalog there. Next, apply the hotfix and move the new catalog to the production server. The specific steps for this process are: If this is necessary because a scheduled outage window is not available, then:

1. Dump, and then load the database on a SQL Server instance that is running on a secondary server.
2. Apply this FTS fix to the secondary server, and then restart MSSearch to initiate a catalog rebuild.
3. After the catalog population on the secondary server completes, stop MSSearch on the primary server, and then apply the hotfix.
4. Before you restart MSSearch on the production server, use the steps outlined in the "MOVING OR COPYING FT CATALOGS BETWEEN SQL SERVERS" heading of the following Microsoft Knowledge Base article to move the new catalogs from the secondary server to the production server:

   240867 INF: How to Move, Copy, and Back Up Full-Text Catalog Folders and Files

After you apply the hotfix, you may notice the following error messages in your Application event log after you restart the MSSearch service. These messages reflect that MSSearch initiated a catalog rebuild due to the catalog format change, and you can ignore the messages when they immediately follow the hotfix installation:

• Source: Microsoft Search (Indexer)
  Error: The Content Index for project <SQLServer$SQL2K SQL0001200005> cannot be loaded. Error: c0041821 - The content index data on disk is for the wrong version. .
• Source: Microsoft Search (Gatherer)
  Error: Project <SQLServer$SQL2K SQL0001200005> is being reset.
• Source: Microsoft Search (Indexer)
  Error: The project <SQLServer$SQL2K SQL0001200005> cannot be initialized. Error: c0041821 - The content index data on disk is for the wrong version.
• Source: Microsoft Search (Indexer)
  Error: The Content Index for project <SQLServer$SQL2K SQL0001200005> cannot be loaded. Error: c0041800 - The content index is corrupt.
• Source: MssCi
  Error: Content index corruption detected in component CI-RcovStorageObj1 in catalog C:\Program Files\Microsoft SQL Server\MSSQL$SQL2K\FTDATA\SQL0001200005\Build\Indexer\NlFiles.
• Source: Microsoft Search (Gatherer)
  Error: The previous crawl was reset, or was otherwise interrupted. A full crawl of all content sources will be automatically started. <Project SQLServer$SQL2K SQL0001200005>