Happy New Year! The January edition of TechNet Magazine is available on the web now and has the latest installment of my regular SQL Q&A column. This month's topics are: Using backups for corruption recovery Why snapshot isolation is required when using change tracking, and its performance implications Is DBCC CHECKDB a really comprehensive integrity [...]
Paul S. Randal
In Recovery...
TechNet Magazine: January 2010 SQL Q&A column
Posted on: January 4, 2010 1:09 pm
Couple of LOB corruption bugs fixed in the latest CUs for 2005
Posted on: March 10, 2009 4:49 pm
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 large-value-types-out-of-row option to true, insert a row, and then try to update it – described in KB 961648. The second bug [...]
Comprehensive tempdb blog post series
Posted on: January 16, 2009 9:24 am
Over the last few weeks Sunil Agarwal (from the SQL Storage Engine team) has posted a great series of blog articles about tempdb and the version store, over on my old stomping ground – the Storage Engine blog. The articles are well worth reading – the links are: Managing tempdb part 1 and part 2 Version [...]
Available for download: Our High-Availability hands-on labs and SQL Server 2008 JumpStart materials
Posted on: March 12, 2008 5:23 pm
A couple of weeks ago I blogged about the three tracks of the SQL Server 2008 JumpStart course that SQLskills.com taught internally for Microsoft and some MVPs – see here for details. Well, the content is now available to download! Note that this was based on CTP-5 (November 2007 CTP) and there have been *lots* [...]
Inside the Storage Engine: When do versioning tags get added?
Posted on: December 31, 2007 8:53 pm
Ok – so we did more partying than we thought so blog posts have been a little sparse this month, but here’s one to end off the year. There’s a popular impression that turning on snapshot isolation and then rebuilding indexes will cause all rows in the table to get the extra 14-byte versioning tags. [...]
