Select the product you need help with
FIX: Index size increases significantly after you rebuild the index online and the RCSI is enabled in SQL Server 2008 or in SQL Server 2008 R2Article ID: 2812884 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 Service Pack 3 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 Service Pack 3 fix release. On This PageSymptomsWhen you rebuild an index on a database in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2, the index size of the database increases significantly if the following conditions are true:
CauseThis issue occurs because an additional 14 bytes are unexpectedly appended to each row of each object where indexes were rebuilt. Note The additional 14 bytes contain information about row versions that are required for RCSI functionality. ResolutionCumulative update informationCumulative Update 7 for SQL Server 2008 R2 Service Pack 2 (SP2)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 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:2844090 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 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:
(http://support.microsoft.com/kb/2844090/
)
Cumulative update package 7 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was releasedCumulative update 13 for SQL Server 2008 R2 SP1The fix for this issue was first released in Cumulative Update 13. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2855792 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 SP1 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:
(http://support.microsoft.com/kb/2855792/
)
Cumulative update package 13 for SQL Server 2008 R2 SP12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was releasedCumulative Update 10 for SQL Server 2008 Service Pack 3The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:2814783 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 3 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:
(http://support.microsoft.com/kb/2814783/
)
Cumulative update package 10 for SQL Server 2008 Service Pack 32629969
(http://support.microsoft.com/kb/2629969/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. ReferencesFor more information about the issue, go to the following MSDN blog website: Why did the size of my indexes expand when I rebuilt my indexes? For more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://blogs.msdn.com/b/sqlprogrammability/archive/2009/05/18/why-did-the-size-of-my-indexes-expand-when-i-rebuilt-my-indexes.aspx)
935897 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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems 822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
Naming schema for Microsoft SQL Server software update packages 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates PropertiesArticle ID: 2812884 - Last Review: June 17, 2013 - Revision: 6.0 Applies to
| Article Translations
 |
Back to the top
