You are currently offline, waiting for your internet to reconnect

FIX: A SQL Server 2008 query returns incorrect results when you create a spatial index in a table that contains a composite primary key

Bug #: 50003457 (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.
SYMPTOMS
Consider the following scenario:
  • For a Microsoft SQL Server 2008 query, you create a spatial index that joins or filters a range of values that are returned by a spatial method.
  • The base table contains a composite primary key.
  • The column order of the primary key constraints in the base table differs from the column order of the columns in the base table.
In this scenario, when you run the query, the query returns incorrect results.
CAUSE
This problem occurs because the spatial index in SQL Server 2008 uses an incorrect column order for a composite primary key in an execution plan.
RESOLUTION
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 2008
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 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
WORKAROUND
To work around this problem, use one of the following methods:
  • Specify the primary key columns in the same order that is specified in the primary key constraint definition.
  • Use a single-column surrogate primary key.
  • Remove the spatial index for the SQL Server 2008 query.
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:
958186 Cumulative update package 2 for SQL Server 2008
REFERENCES
For more information about the list of builds that are available after the release of SQL Server 2008, 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
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 the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New 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
multicolumn synthetic
Properties

Article ID: 957815 - Last Review: 09/23/2008 18:52:51 - Revision: 2.1

  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Standard
  • kbbug kbfix kbqfe kbexpertiseadvanced KB957815
Feedback