Consider the following scenario. You install SQL Server 2005 on a computer that has multiple processors. You run a trace that contains a text filter. The text filter uses the LIKE comparison or the NOT LIKE comparison. Additionally, the size of the text filter is greater than 47 bytes. In this scenario, you may find that CPU utilization is high for many processors.

Note In SQL Server Profiler, this problem also occurs if the following conditions are true:

•	The rows are created by SQL Server Profiler.
•	The default text filter that is used to exclude the rows is greater than 47 bytes.

Back to the top

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: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:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

To work around this issue, use one of the following methods:

•	Reduce the size of the text filter to less than 47 bytes.
•	If it is possible, do not use a text filter. For example, you can use a corresponding numeric column as a filter instead.

Back to the top

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: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: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top