Couple of LOB corruption bugs fixed in the latest CUs for 2005
Both 2005 SP3 CU2 and 2005 SP2 CU12 contain fixes for two bugs that cause corruption in LOB data. The first bug may happen when a column type is converted to varbinary(max), change the...
View ArticleWeekly survey: large-value character storage
(And it's official – this is blog post 39 this month, making this my most prolific month yet for blogging. An arguably dubious achievement…) In this week's survey, I'm interested in your views on the...
View ArticleClik here to view.
Importance of choosing the right LOB storage technique
Last week’s survey was on how you should store large-value character data in SQL 2005+ (see here for the survey). Here are the result as of 4/3/2009 – and I think my favorite answer is starting to...
View ArticlePerformance bug: NOLOCK scans involving off-row LOB data
Here's an interesting bug that was just recently fixed, and someone actually hit it today, so it's time to blog it. Bottom line is that if you're doing NOLOCK scans of tables involving LOB data, the...
View Article2005 corruption bug with XML index rebuild fixed in latest CU
2005 SP3 CU6 contains a fix for a corruption bug that can happen after rebuilding an XML index that contains XML elements greater than 8000 bytes. The bug was fixed in 2008 but hadn’t made it back to...
View ArticleWhy LOB data makes shrink run slooooowly (T-SQL Tuesday #006)
[Edit January 2015: Everything in this post applies to SQL Server 2012 and 2014 still.] This blog post is part of the monthly T-SQL Tuesday series that fellow-MVP Adam Machanic (twitter|blog)...
View ArticleTechNet Magazine: July 2010 SQL Q&A column
The July edition of TechNet Magazine is available on the web now and has the latest installment of my regular SQL Q&A column (and I forgot to blog about it a couple of weeks back). This month's...
View Article