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.
When 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:
The Read Committed Snapshot Isolation (RCSI) level is enabled on the database.
The index is rebuilt online.
Note This issue also occurs in Microsoft SQL Server 2005.
This 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.
Cumulative update information
The issue was first fixed in the following cumulative update of SQL Server.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
The 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 Cumulative update package 13 for SQL Server 2008 R2 SP1
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:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the issue, go to the following MSDN blog website: