FIX: Full Text Query May Return 0 Rows When Valid Results are Present

Article translations Article translations
Article ID: 296456 - View products that this article applies to.
This article was previously published under Q296456
BUG #: 353643 (SHILOH_BUGS)
BUG #: 101390 (SQLBUG_70)
Expand all | Collapse all

On This Page

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.

RESOLUTION

SQL Server 2000

To 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.0

To 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.

STATUS

Microsoft 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.

MORE INFORMATION

SQL Server 2000
With the correction, you now receive a 7643 error message when you experience the full text maximum restriction node limitation.

Server: Msg 7643, Level 16, State 1, Line 1
Your search generated too many results. Please perform a more specific search.


SQL Server 7.0
With the correction, you now receive the following 7627 error message when you experience the full text maximum restriction node limitation:
Server: Msg 7627, Level 16, State 1, Line 1
Your search generated too many results. Please perform a more specific search.

Properties

Article ID: 296456 - Last Review: October 31, 2003 - Revision: 4.1
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbbug kbfix KB296456

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com