This article has been archived. It is offered "as is" and will no longer be updated.
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.
In Microsoft SQL Server 2005, when you run a Full-Text query, you may receive the following error message:
Msg 9937, Level 16, State 5, Line <Line> Too many full-text columns or the full-text query is too complex to be executed.
In SQL Server 2005, there are some Full-Text catalog properties that control when to cancel a Full-Text query. In this specific case, the value of an internal Full-Text catalog property is reached, and this causes the query to be canceled.
The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
983329 Cumulative update package 10 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
This fix adds a new stored procedure that is called sp_fulltext_maxrestrictionnodes. This procedure lets you see what the current setting is and gives you an option to change the procedure if you must.
The syntax for the new procedure is as follows:
sp_fulltext_maxrestrictionnodes <catalog name> -- to see current configuration value. The default is 200,000sp_fulltext_maxrestrictionnodes <catalog name>, <max nodes> -- to set the value to a desired value
For example, if you want to double the value of nodes to 400,000 for a catalog that is named Mytestcatalog, you can execute the following query: