August 3, 2009 at 12:02 am
Comments posted to this topic are about the item Changing Table Schema – what goes behind the scenes – Part I
August 3, 2009 at 4:22 am
Can this post be made more readable. The code part which contains almost everything is messy and mot understandable.
August 3, 2009 at 7:18 am
The formatting has been corrected.
August 3, 2009 at 9:43 am
Thanks for putting the time in to explain this. I have now discovered why a particular table got fragmented. Someone added fixed and variable length fields, poulated with default values and made them NOT NULL.
Thanks again,
ThomasLL
Thomas LeBlanc, MVP Data Platform Consultant
August 3, 2009 at 5:07 pm
Thank you - wonderful initiative to help us see stuff that may make a real difference in troubleshooting performance issues.
See elsewhere how Hugo Kornelis, armed with this knowledge, helped me solve an issue where a non-indexed heap increased in size after changing a field from CHAR to VARCHAR (instead of decreasing) - that's because the pages were never rebuilt. This article is showing everyone how to analyse this!
August 3, 2009 at 7:31 pm
There is a very fine line between basing an article on a book (Inside Microsoft SQL Server 2005: The Storage Engine - by Kalen Delaney) and plagiarizing it.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply