Select the product you need help with

FIX: Access violation when you run a DBCC CHECKDB command against a database that contains a table that has a spatial index in SQL Server 2008 or in SQL Server 2008 R2

Article ID: 2635827 - View products that this article applies to.

SYMPTOMS

Consider the following scenario:

You have a table that has a spatial data type column in Microsoft SQL Server 2008 or SQL Server 2008 R2.
An index for the spatial data type column exists.
You try to run a DBCC CHECKDB command against the database that contains the table.

In this scenario, an access violation occurs in the SQL Server engine.

Note This issue occurs when you run a command in the DBCC CHECKDB family of commands.

Back to the top | Give Feedback

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2648098

(http://support.microsoft.com/kb/2648098/LN/ )

Cumulative update package 3 for SQL Server 2008 Service Pack 3

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. 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:

2629969

(http://support.microsoft.com/kb/2629969/LN/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2633146

(http://support.microsoft.com/kb/2633146/ )

Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1

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 R2 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:

2567616

(http://support.microsoft.com/kb/2567616/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2 (SP2) cumulative update package 7

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

2617148

(http://support.microsoft.com/kb/2617148/ )

Cumulative update package 7 for SQL Server 2008 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 2008 Service Pack 2 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:

2402659

(http://support.microsoft.com/kb/2402659/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

Back to the top | Give Feedback

STATUS

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

Back to the top | Give Feedback

MORE INFORMATION

The following table provides more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product against which the rule is evaluated.

Collapse this tableExpand this table

Rule software	Rule title	Rule description	Product versions against which the rule is evaluated
System Center Advisor	SQL Server missing update KB2635827 to prevent exception during consistency check on table with spatial index	System Center Advisor checks if this SQL Server instance contains databases with spatial indexes defined. Advisor also checks if this SQL Server instance contains the fix discussed in this article. If the fix is not present, Advisor generates an alert. Review the details that are provided in the “Information Collected” section of the advisor alert, and follow the steps discussed in this article to resolve the alert.	SQL Server 2008 SQL Server 2008 R2