Well, surely at least partly in response to the CU6 mess I reported earlier today, and partly because they were due, Microsoft has released new cumulative updates that contain – among other things – updated code that avoids the symptom introduced with earlier updates (though this regression fix doesn't seem to appear in the KB articles – unless by "corruption" they meant ridiculous size increase).

SQL Server 2008 R2 Service Pack 1 Cumulative Update # 13

• KB Article: KB #2855792
• 5 fixes listed at time of publication
• Build number is 10.50.2876
• Relevant for @@VERSION 10.50.2500 through 10.50.2875

SQL Server 2008 R2 Service Pack 2 Cumulative Update # 7

• KB Article: KB #2844090
• 11 fixes listed at time of publication
• Build number is 10.50.4286
• Relevant for @@VERSION 10.50.4000 through 10.50.4285

(Also see KB #2792921 for information on new features in the SP2 CU7 release.)

My usual disclaimer: these updates are NOT for SQL Server 2008 (or SQL Server 2012). Only apply to systems where SELECT @@VERSION returns 10.50.xxxx, where xxxx is >= 2500. If xxxx < 2500, you need to start thinking about getting off the RTM branch. And based on the number of fixes making it into the SP2 updates, you might consider abandoning SP1, too, if possible…