FIX: When you run a query that references a partitioned table in SQL Server 2005, query performance may decrease

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for applying the hotfix package
• Whether you must restart the computer after you apply the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes after you apply the hotfix package
• The files that are contained in the hotfix package

When you run a query that references a partitioned table in Microsoft SQL Server 2005, query performance may decrease. You experience this problem if the following conditions are true:

• The query references a partitioned table.
• The query includes a range filter in the partitioned table that includes multiple partitions. For example, the query may use the BETWEEN operator or a combination of the following inequality operators:
  • > (Greater Than)
  • < (Less Than)

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

SQL Server 2005 Service Pack 1 (SP1) must be installed. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005, x86-based versions

SQL Server 2005, x64-based versions

SQL Server 2005, Itanium-based versions

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

After you install this hotfix, enable trace flag 4107 as a SQL Server startup parameter. For more information about how to turn on or turn off trace flags, about global trace flags, and about session trace flags, see the following topics in SQL Server 2005 Books Online:

• DBCC TRACEON (Transact-SQL)
• Trace flags (Transact-SQL)
• DBCC TRACESTATUS (Transact-SQL)
• Breaking changes to Database Engine features in SQL Server 2005

For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information, click the following article number to view the article in the Microsoft Knowledge Base: