FIX: Full Text Query May Return 0 Rows When Valid Results are Present (296456)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
This article was previously published under Q296456 BUG #: 353643 (SHILOH_BUGS) BUG #: 101390 (SQLBUG_70)
SYMPTOMS SQL Server may incorrectly return the following message
when valid full text results are present: "0 rows
effected" This condition is verified by ensuring that the full text
catalogs are properly up-to-date and by using the Transact-SQL LIKE command to
explore qualifying rows. CAUSE The full text search service limits the number of rows it
qualifies for a given search condition. The limit is approximately 20,000
matches. SQL Server is not properly checking the return status and simply
returns an empty result set to the client. RESOLUTIONSQL Server 2000To resolve this problem, obtain the latest
service pack for Microsoft SQL Server 2000. For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base: 290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
SQL Server 7.0To resolve this problem, obtain the latest
service pack for Microsoft SQL Server 7.0. For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base: 301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
NOTE: The following hotfix was created prior to Microsoft SQL Server
7.0 Service Pack 4. The English version of this fix should have the
following file attributes or later:
File name Platform
----------------------
s70989i.exe Intel
NOTE: Because of file dependencies, the most recent hotfix or feature
that contains the preceding files may also contain additional
files. WORKAROUND Redefine the search criteria to qualify a smaller set of
rows. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
SQL Server 2000
This problem was first corrected in Microsoft SQL Server 2000 Service Pack
2.
SQL Server 7.0
This problem was first corrected in Microsoft SQL Server 7.0 Service Pack
4.
Modification Type: | Major | Last Reviewed: | 10/31/2003 |
---|
Keywords: | kbBug kbfix KB296456 |
---|
|