Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Consider the following scenario. You run a full-text query against a catalog in Microsoft SQL Server 2005. The query may be very complex or retrieve lots of data. At the same time, the catalog is being rebuilt. In this scenario, you may receive the following error message when you run the query:
Msg 7619, Level 16, State 1, Line 1
The execution of a full-text query failed. "The content index is corrupt."
Additionally, a minidump file is generated on the server. The following error message is logged in the SQL Server 2005 error log:
An index corruption was detected in component SmartBuffer1 in catalog CatalogName.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must have SQL Server 2005 Service Pack 2 installed on the computer.
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2005
You have to restart the Microsoft Search service and the SQL Server service after you apply this hotfix.
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
After you apply this hotfix, you must run the following statements for each affected catalog. Additionally, you must run these statements for every newly created catalog or for catalogs that are rebuilt.
declare @mmchkpt_interval int
set @mmchkpt_interval = 1048576 -- 1Gigabyte (GB)
Note In this code, CatalogName is a placeholder for the catalog name.
After you run these statements for a catalog, you run the following statement.