DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 945913 - Last Review: December 31, 2007 - Revision: 1.1

Bug #: 50002089 (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.

SYMPTOMS

Consider the following scenario:
  • You have two partitioned tables in Microsoft SQL Server 2005. Assume that one table is Table1, and assume that the other table is Table2.
  • Table1 and Table2 have the same columns. Additionally, Table1 and Table2 are partitioned against the same column.
  • You create a clustered index on Table2, and then you drop the clustered index.
  • You switch a partition from Table1 to Table2.
  • You use the BULK INSERT statement together with the TABLOCK option to import valid data into Table2.
In this scenario, you receive one or more error messages that resemble the following when you run the DBCC CHECKTABLE statement against Table2:
Error message 1
Msg 2570, Level 16, State 3, Line 2
Page (PageID), slot SlotID in object ID ObjectID, index ID IndexID, partition ID PartitionID, alloc unit ID UnitID (type "In-row data"). Column "ColumnName" value is out of range for data type "DataType". Update column to a legal value.
Error message 2
Msg 8984, Level 16, State 1, Line 2
Table error: object ID ObjectID, index ID IndexID, partition ID PartitionID. A row should be on partition number PartitionNum1 but was found in partition number PartitionNum2. Possible extra or invalid keys for:
Error message 3
Msg 8988, Level 16, State 1, Line 2
Row (FileID:PageNumber:RowNumber) identified by (HEAP RID = (FileID:PageNumber:RowNumber)).

CAUSE

When you drop the clustered index, the metadata of Table2 is changed. Therefore, the metadata of the partition that you switch from Table1 differs from the metadata of Table2. This difference causes data corruption.

RESOLUTION

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
943656  (http://support.microsoft.com/kb/943656/LN/ ) Cumulative update package 5 for SQL Server 2005 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 2005 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:
937137  (http://support.microsoft.com/kb/937137/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

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:
943656  (http://support.microsoft.com/kb/943656/LN/ ) Cumulative update package 5 for SQL Server 2005 Service Pack 2

REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137  (http://support.microsoft.com/kb/937137/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 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  (http://support.microsoft.com/kb/935897/LN/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089  (http://support.microsoft.com/kb/913089/LN/ ) How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711 (http://go.microsoft.com/fwlink/?LinkId=71711)
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  (http://support.microsoft.com/kb/822499/LN/ ) 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  (http://support.microsoft.com/kb/824684/LN/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup Edition
Keywords: 
kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced KB945913
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support