FIX: The query performance is slower when you run the query in SQL Server 2005 than when you run the query in SQL Server 2000

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Bug #: 50001716 (SQL Hotfix)
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.
SYMPTOMS
Consider the following scenario. You have a parameterized query. In the WHERE clause of the query, you specify the following search conditions:
  • You use a comparison operator to compare the value of a column to the value of a parameter.
  • You use the LIKE operator to match the value of the same column to the value of a different parameter.
For example, the query contains the following statements.
DECLARE @para1 VARCHAR(50)DECLARE @para2 VARCHAR(50)SET @para1 = 'Ad%'SET @para2 = 'A'SELECT * FROM Person.ContactWHERE (LastName LIKE @para1) AND (LastName > @para2)
In this scenario, the query performance is slower when you run the query in Microsoft SQL Server 2005 than when you run the query in Microsoft SQL Server 2000. For example, when you run the query in SQL Server 2000, the query takes 1.2 seconds to finish running. When you run the query in SQL Server 2005, the query takes 9 seconds to finish running.
CAUSE
This problem occurs because the execution plan that SQL Server 2005 uses for the query is less optimal than the execution plan that SQL Server 2000 uses for the query.

In SQL Server 2005, the execution plan uses the comparison operator to seek tables. In SQL Server 2000, the execution plan uses the LIKE operator to seek tables. The comparison operator returns more rows than the LIKE operator returns. Therefore, the query performance is slower.
RESOLUTION
The fix for this issue was first released in Cumulative Update 4. 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:
941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2
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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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.

After you install Cumulative Update 4, you must enable trace flag 4119. After you enable trace flag 4119, the execution plan uses the LIKE operator to seek tables in SQL Server 2005.

For more information about trace flags in SQL Server 2005, visit the following Microsoft Developer Network (MSDN) Web site:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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:
941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2
REFERENCES
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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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:
913089 How to obtain the latest service pack for SQL Server 2005
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:
822499 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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 942659 - Last Review: 10/19/2007 19:29:01 - Revision: 1.1

Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Workgroup Edition

  • kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced KB942659
Feedback