SQL Server Soldier :: News from the frontlines of the database wars

Day 24 of 31 Days of Disaster Recovery: Handling Corruption in a Clustered Index

Welcome to day 24 of my 31 Days of Disaster Recovery series. Previously, I’ve talked about several different forms of corruption: Nonclustered Index, Allocation Pages, and Tempdb. these were all fairly simple to fix. Today I’m going to dive into a scenario that is a little more complex, clustered indexes.…

9 comments, 833 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 31 January 2013

Day 23 of 31 Days of Disaster Recovery: Restoring Differential Backups With New Files

It’s day 23 of my 31 Days of Disaster Recovery series, and today’s blog post is inspired from an email i received in response to day 20′s blog post The Case of the Backups That Wouldn’t Restore. A friend shared a story with me via email about a partial restore…

4 comments, 913 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 29 January 2013

Day 22 of 31 Days of Disaster Recovery: Which DBCC CHECK Commands Update Last Known Good DBCC

The end of the day is quickly approaching as I finish this blog post. This is day 22 in my series 31 Days of Disaster Recovery, and I want to examine which DBCC CHECK commands update the last known good DBCC check that is tracked in the header of the…

3 comments, 854 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 27 January 2013

Day 21 of 31 Days of Disaster Recovery: Who Deleted That Data?

Welcome back for day 21 of my 31 Days of Disaster Recovery series. Today I want to talk about trying to track down who deleted data from a table. This little investigation started out as a question on the #sqlhelp hash tag on Twitter from Wayne Sheffield (blog|@DBAWayne) whom I…

1 comments, 863 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 26 January 2013

Day 20 of 31 Days of Disaster Recovery: The Case of the Backups That Wouldn’t Restore

I have decided to spend day 20 of my 31 Days of Disaster Recovery series by relating a true tale from my harried past days of Production DBA Operations. This is a cautionary tale with an important moral. This is the case of the backups that wouldn’t restore. If you…

8 comments, 767 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 25 January 2013

Day 19 of 31 Days of Disaster Recovery: How Much Log Can a Backup Log

It’s day 19 of my 31 Days of Disaster Recovery series, and today I want to talk about how much log is in a backup file. A common misconception is that when you restore a backup, you get an exact copy of the database as it was when it was…

6 comments, 755 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 24 January 2013

Day 18 of 31 Days of Disaster Recovery: How to CHECKDB Like a Boss

Day 18 of my 31 Days of Disaster Recovery series is drawing to a close. It’s 11:22 PM here, and I’ve been working feverishly to finish today’s post before the calendar flips over to tomorrow. This started out as sharing a simple script I use for running DBCC CHECKDB against…

6 comments, 602 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 23 January 2013

Day 17 of 31 Days of Disaster Recovery: When are Checksums Written to a Page

Today is day 17 of 31 Days of Disaster Recovery. The series has skipped a couple of days due to real life imposing itself, but we’re getting back on track by digging into the Checksum page verification option and offering up some proof that the checksum value doesn’t get written…

2 comments, 1,369 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 21 January 2013

Day 16 of 31 Days of Disaster Recovery: Disaster Recovery Gems From Around The Net

It’s day 16 of my series 31 Days of Disaster Recovery. I’ve seen a lot of great DR related posts recently. I want to do kind of a round-up of some of the other must-read disaster recovery posts and articles out there. Last Time CheckDB was Run by Jason Brimhall…

7 comments, 544 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 18 January 2013

Day 15 of 31 Days of Disaster Recovery: Running DBCC CheckTable in Parallel Jobs

Welcome back to my 31 Days of Disaster Recovery series. Today is day 15, and I want to answer a question I was asked a while back. Paul Randal (blog|@PaulRandal) wrote a blog post explaining alternative options for checking integrity of a very large database if you are not able…

3 comments, 745 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 17 January 2013

Day 14 of 31 Days of Disaster Recovery: Fixing a Corrupt Tempdb

Welcome to day 14 of my 31 Days of Disaster Recovery series. I’ve previously discussed handling corruption for nonclustered indexes and allocation pages. Today, I’m going to talk about a specific corruption that is very simple to fix; however, it does mean taking the server offline briefly. How brief depends…

5 comments, 982 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 16 January 2013

Day 13 of 31 Days of Disaster Recovery: Standard Backup Scripts

31 Days of Disaster Recovery

Today’s post took longer to prepare than I had anticipated which is why day 13 is being published on day 14. This won’t derail the 31 Days of Disaster Recovery series, even if it runs over into February. Day 13′s topic is standard backup scripts. Read more

11 comments, 721 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 15 January 2013

Day 12 of 31 Days of Disaster Recovery: Extreme Disaster Recovery Training

31 Days of Disaster Recovery

Fittingly, today’s focus on disaster recovery as part of my 31 Days of Disaster Recovery is to announce a full day of training, Extreme Disaster Recovery, being offered at SQLBits XI. This training will be the only pre-conference session being led by two… Read more

7 comments, 587 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 12 January 2013

Day 11 of 31 Days of Disaster: Converting LSN Formats

31 Days of Disaster Recovery

Welcome back to my series 31 Days of Disaster Recovery. Today is day 11, and today I want to talk about converting LSN formats. I had intended to write this blog post a long time ago, but I never seemed to get around to it.… Read more

7 comments, 967 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 12 January 2013

Day 10 of 31 Days of Disaster Recovery: Monitoring for Corruption Errors

31 Days of Disaster Recovery

It’s day 10 of my 31 Days of Disaster Recovery series, and I want to talk about monitoring for corruption errors. There are four errors related to corruption for which everyone should raise alerts and send notifications. The four alerts are 823, 824, 825, and… Read more

7 comments, 652 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 11 January 2013

Day 9 of 31 Days of Disaster Recovery: Use All the Checksums

31 Days of Disaster Recovery

Welcome to day 9 of my 31 Days of Disaster Recovery series. Today, I want to talk about the three ways you can use CHECKSUM to protect yourself from and identify corruption. Checksum is the default page verification option in SQL Server 2005+ and helps… Read more

20 comments, 1,204 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 9 January 2013

Day 8 of 31 Days of Disaster Recovery (T-SQL Tuesday #38): Resolutions for All DBAs

T-SQL Tuesday #38

This post is not only day 7 of my 31 Days of Disaster Recovery series, it is also participating in T-SQL Tuesday #38 hosted this month by Jason Brimhall (blog|@sqlrnnr). The theme for this month’s T-SQL Tuesday is resolutions or resolving or just… Read more

7 comments, 666 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 8 January 2013

Day 7 of 31 Days of Disaster Recovery: Writing SLAs for Disaster Recover

Day 7 of 31 Days of Disaster Recovery: Writing SLAs for Disaster Recovery

31 Days of Disaster Recovery

Today is day 7 in my series on disaster recovery. I thought I would switch gears for today and write about disaster recovery Service-Level Agreements (SLAs). Specifically, I’m talking about Recovery Point… Read more

14 comments, 861 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 8 January 2013

Day 6 of 31 Days of Disaster Recovery: Dealing With Corruption in Allocation Pages

31 Days of Disaster Recovery

Yesterday, I covered corruption in nonclustered indexes, the easiest type of corruption to handle. Today, I’m going to move on to something slightly more complex, yet still really simple to… Read more

17 comments, 762 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 6 January 2013

Day 5 of 31 Days of Disaster Recovery: Dealing With Corruption in a Nonclustered Index

31 Days of Disaster Recovery

Welcome to day 5 of my series on disaster recovery. I want to start digging into some corruption scenarios. We’ll start off with the easiest form of corruption to fix, a nonclustered index.

The generic steps we will go through for any corruption scenario are… Read more

11 comments, 1,718 reads

Posted in SQL Server Soldier :: News from the frontlines of the database wars on 6 January 2013

Get Your Own Blog

Contact the author

All Blogs

Feeds

Archives for this blog

Archives: January 2013

Day 24 of 31 Days of Disaster Recovery: Handling Corruption in a Clustered Index

Day 23 of 31 Days of Disaster Recovery: Restoring Differential Backups With New Files

Day 22 of 31 Days of Disaster Recovery: Which DBCC CHECK Commands Update Last Known Good DBCC

Day 21 of 31 Days of Disaster Recovery: Who Deleted That Data?

Day 20 of 31 Days of Disaster Recovery: The Case of the Backups That Wouldn’t Restore

Day 19 of 31 Days of Disaster Recovery: How Much Log Can a Backup Log

Day 18 of 31 Days of Disaster Recovery: How to CHECKDB Like a Boss

Day 17 of 31 Days of Disaster Recovery: When are Checksums Written to a Page

Day 16 of 31 Days of Disaster Recovery: Disaster Recovery Gems From Around The Net

Day 15 of 31 Days of Disaster Recovery: Running DBCC CheckTable in Parallel Jobs

Day 14 of 31 Days of Disaster Recovery: Fixing a Corrupt Tempdb

Day 13 of 31 Days of Disaster Recovery: Standard Backup Scripts

Day 12 of 31 Days of Disaster Recovery: Extreme Disaster Recovery Training

Day 11 of 31 Days of Disaster: Converting LSN Formats

Day 10 of 31 Days of Disaster Recovery: Monitoring for Corruption Errors

Day 9 of 31 Days of Disaster Recovery: Use All the Checksums

Day 8 of 31 Days of Disaster Recovery (T-SQL Tuesday #38): Resolutions for All DBAs

Day 7 of 31 Days of Disaster Recovery: Writing SLAs for Disaster Recover

Day 7 of 31 Days of Disaster Recovery: Writing SLAs for Disaster Recovery

Day 6 of 31 Days of Disaster Recovery: Dealing With Corruption in Allocation Pages

Day 6 of 31 Days of Disaster Recovery: Dealing With Corruption in Allocation Pages

Day 5 of 31 Days of Disaster Recovery: Dealing With Corruption in a Nonclustered Index