Bug #: 50003634 (SQL Hotfix)
Bug #: 50003611 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.
Summary
This article describes the following about this hotfix release:
-
The issues that are fixed by the hotfix package
-
The prerequisites for installing the hotfix package
-
Whether you must restart the computer after you install the hotfix package
-
Whether the hotfix package is replaced by any other hotfix package
-
Whether you must make any registry changes
-
The files that are contained in the hotfix package
Symptoms
In Microsoft SQL Server 2008, you create a filtered index on a table. Then, you run a query that references three or more tables in the FROM clause. When you run the query, you may receive incorrect results.
Cause
This problem occurs because the optimizer uses the filtered index even though the search condition that is defined in the filtered index is not specified in the query.
Resolution
Cumulative update information
The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
958186 Cumulative update package 2 for SQL Server 2008Note 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 2008 fix release. We recommend 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
Hotfix information
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 the problem described in this article. 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:
http://support.microsoft.com/contactus/?ws=supportNote 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
No prerequisites are required.
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.
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_common_core.msp
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Msgprox.dll |
2007.100.1771.0 |
202,592 |
11- |
11:52 |
x86 |
|
Replprov.dll |
2007.100.1771.0 |
576,352 |
11- |
12:05 |
x86 |
|
Replrec.dll |
2007.100.1771.0 |
790,880 |
11- |
12:05 |
x86 |
|
Sql_common_core_keyfile.dll |
2007.100.1771.0 |
14,688 |
11- |
11:39 |
x86 |
|
Xmlsub.dll |
2007.100.1771.0 |
193,376 |
11- |
12:13 |
x86 |
Sql_engine_core_inst.msp
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Datacollectorcontroller.dll |
2007.100.1771.0 |
135,520 |
11- |
11:30 |
x86 |
|
Mssqlsystemresource.ldf |
Not applicable |
524,288 |
10- |
23:20 |
Not applicable |
|
Mssqlsystemresource.mdf |
Not applicable |
63,242,240 |
10- |
23:20 |
Not applicable |
|
Sql_engine_core_inst_keyfile.dll |
2007.100.1771.0 |
14,688 |
11- |
11:39 |
x86 |
|
Sqlagent.exe |
2007.100.1771.0 |
367,456 |
11- |
12:06 |
x86 |
|
Sqlservr.exe |
2007.100.1771.0 |
40,996,192 |
11- |
12:06 |
x86 |
Sql_engine_core_shared.msp
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Distrib.exe |
2007.100.1771.0 |
76,128 |
11- |
11:31 |
x86 |
|
Dtspipeline.dll |
2007.100.1771.0 |
695,136 |
11- |
11:31 |
x86 |
|
Microsoft.sqlserver.dmf.dll |
10.0.1771.0 |
293,728 |
11- |
11:52 |
x86 |
|
Microsoft.sqlserver.management.collectortasks.dll |
10.0.1771.0 |
84,832 |
11- |
11:52 |
x86 |
|
Rdistcom.dll |
2007.100.1771.0 |
650,080 |
11- |
12:05 |
x86 |
|
Replmerg.exe |
2007.100.1771.0 |
341,856 |
11- |
12:05 |
x86 |
|
Sql_engine_core_shared_keyfile.dll |
2007.100.1771.0 |
14,688 |
11- |
11:39 |
x86 |
Workaround
To work around this problem, drop the filtered index that you created on the table.
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 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
