Article ID: 920347
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Developer Edition
Bug #: 438282 (SQLBUDT)
Bug #: 449130 (SQLBUDT)
Bug #: 715 (SQL Hotfix)
Bug #: 637 (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.
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Information about whether you must restart the computer after you install the hotfix package
- Information about whether the hotfix package is replaced by any other hotfix package
- Information about whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
Consider the following scenario:
- The SQL Server 2005 query optimizer evaluates a query that has a predicate.
- The query predicate contains one alternative that is an index union.
For example, the following query is a query predicate that contains one alternative that is an index union:
select * from table where (c1 <Comparison operator> value1 OR c1 <Comparison operator> value2) and c2 <Comparison operator> value3)
In this scenario, the query optimizer may incorrectly estimate the cardinality as lower than the actual cardinality. When this problem occurs, the estimated cost of the query also becomes lower than the actual cost. When the estimated cost of the query is lower than the actual cost, the SQL Server 2005 query optimizer may use this query instead of a more efficient query.
CAUSE
This problem occurs because of a bug in the SQL Server index strategy code.
RESOLUTION
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.
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:
913089 How to obtain the latest service pack for SQL Server 2005
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 replacement information
This hotfix does not replace any other hotfixes.
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 of 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 hotfix, 32-bit
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.sqlenum | 9.0.2164.0 | 908,064 | 15-Jun-2006 | 03:32 | Not Applicable |
| Ms.ss.mgdsqldumper.dll | 2005.90.2164.0 | 75,552 | 15-Jun-2006 | 03:29 | Not Applicable |
| Msgprox.dll | 2005.90.2164.0 | 197,920 | 15-Jun-2006 | 03:29 | Not Applicable |
| Replprov.dll | 2005.90.2164.0 | 547,616 | 15-Jun-2006 | 03:31 | Not Applicable |
| Replrec.dll | 2005.90.2164.0 | 782,112 | 15-Jun-2006 | 03:32 | Not Applicable |
| Sbmsmdlocal.dll | 9.0.2164.0 | 15,661,856 | 15-Jun-2006 | 03:33 | Not Applicable |
| Sqlaccess.dll | 2005.90.2164.0 | 347,936 | 15-Jun-2006 | 03:31 | Not Applicable |
| Sqlservr.exe | 2005.90.2164.0 | 28,950,872 | 15-Jun-2006 | 03:33 | Not Applicable |
SQL Server 2005 hotfix, 64-bit
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.sqlenum | 9.0.2164.0 | 875,296 | 15-Jun-2006 | 04:12 | Not Applicable |
| Ms.ss.mgdsqldumper.dll | 2005.90.2164.0 | 75,552 | 15-Jun-2006 | 03:29 | Not Applicable |
| Ms.ss.mgdsqldumper.dll | 2005.90.2164.0 | 91,424 | 15-Jun-2006 | 04:10 | Not Applicable |
| Msgprox.dll | 2005.90.2164.0 | 259,360 | 15-Jun-2006 | 04:10 | Not Applicable |
| Replprov.dll | 2005.90.2164.0 | 745,248 | 15-Jun-2006 | 04:12 | Not Applicable |
| Replrec.dll | 2005.90.2164.0 | 1,008,416 | 15-Jun-2006 | 04:12 | Not Applicable |
| Sbmsmdlocal.dll | 9.0.2164.0 | 15,661,856 | 15-Jun-2006 | 03:33 | Not Applicable |
| Sqlaccess.dll | 2005.90.2164.0 | 355,104 | 15-Jun-2006 | 04:11 | Not Applicable |
| Sqlservr.exe | 2005.90.2164.0 | 39,251,232 | 15-Jun-2006 | 04:13 | Not Applicable |
SQL Server 2005 hotfix, 64-bit for Itanium processors
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.sqlserver.sqlenum | 9.0.2164.0 | 875,296 | 15-Jun-2006 | 03:29 | Not Applicable |
| Ms.ss.mgdsqldumper.dll | 2005.90.2164.0 | 75,552 | 15-Jun-2006 | 03:29 | Not Applicable |
| Ms.ss.mgdsqldumper.dll | 2005.90.2164.0 | 163,104 | 15-Jun-2006 | 03:29 | Not Applicable |
| Msgprox.dll | 2005.90.2164.0 | 542,496 | 15-Jun-2006 | 03:28 | Not Applicable |
| Replprov.dll | 2005.90.2164.0 | 1,617,184 | 15-Jun-2006 | 03:29 | Not Applicable |
| Replrec.dll | 2005.90.2164.0 | 2,141,472 | 15-Jun-2006 | 03:29 | Not Applicable |
| Sbmsmdlocal.dll | 9.0.2164.0 | 48,733,984 | 15-Jun-2006 | 03:30 | Not Applicable |
| Sqlaccess.dll | 2005.90.2164.0 | 349,472 | 15-Jun-2006 | 03:28 | Not Applicable |
| Sqlservr.exe | 2005.90.2164.0 | 72,208,672 | 15-Jun-2006 | 03:30 | Not Applicable |
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, 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
Keywords: kbtshoot kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB920347
