This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Information about whether you must restart the computer after you install the hotfix package
- Information about whether the hotfix package is replaced by any other hotfix package
- Information about whether you must make any registry changes
- The files that are contained in the hotfix package
You enable full-text search for Microsoft Windows SharePoint Services 2.0. Then, you upgrade an instance of Microsoft SQL Server 2000 to SQL Server 2005. When you perform a full-text search operation on a Windows SharePoint Services 2.0 site, you may notice that some search results are missing. If you perform the same full-text search operation before you upgrade the instance of SQL Server 2000 to SQL Server 2005, you obtain all the search results.Note
If you use Microsoft Office SharePoint Portal Server 2003, you may experience this problem only if SharePoint Portal Server 2003 hosts Windows SharePoint Services 2.0 Web sites.
This problem occurs if the following conditions are true:
- You use the FREETEXT predicate to perform the full-text search operation.
- You include words that you want to search for in double quotation marks.
For example, you perform the following full-text search:
WHERE FREETEXT('"computer software hardware"')
This problem occurs because SQL Server 2005 considers words that are enclosed in double quotation marks to be a phrase. Therefore, SQL Server 2005 performs a phrase match. However, SQL Server 2000 will match any word in the string enclosed in the double quotation marks.
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.
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, submit a request to 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.
You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.
For more information about how to obtain SQL Server 2005 Service Pack 1, 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 must restart 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.
SQL Server 2005 32-bit version
Collapse this tableExpand this table
|File name||File version||File size||Date||Time||Platform|
Steps required after you install the hotfix
This hotfix adds trace flag 7613 to SQL Server. After you enable trace flag 7613, SQL Server 2005 full-text search operations will match any word in the string that is enclosed in double quotation marks instead of using a phrase match.
For more information about how to enable a trace flag in SQL Server 2005, see the "Remarks" section in the following Microsoft Developer Network (MSDN) Web site:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates