Live registration reopens October 1, 2026, in 12d 19h 55mNotify me

Backup, Restore, and Database Integrity

Backup design, restore testing, integrity checks, and corruption response.

292 associated posts117 primary posts

[Video] Office Hours: Ask Me Anything About SQL Server at the Volcano Hekla

I drove up the volcano Hekla in central Iceland - also known as the Gateway to Hell - and parked the Defender here:

While my travel companions hiked up higher (and took that photo), I set up the tripod and camera, then went through your highly-upvoted questions from https://pollgab.com/room/brento.

Read more about [Video] Office Hours: Ask Me Anything About SQL Server at the Volcano Hekla 2 comments — Join the discussion

[Video] Office Hours: Ask Me Anything About Microsoft SQL Server

Got questions that aren't a good fit for DBA.StackExchange.com, and you want my opinion? Post them here and upvote the questions you'd like to see me talk through. This weekend, I hopped into my home studio and did a half-hour session because so many good questions had piled up:

https://www.youtube.com/watch?v=j7XFeXcOZgU

Read more about [Video] Office Hours: Ask Me Anything About Microsoft SQL Server 1 comment — Join the discussion
Production DBA

How to Patch SQL Server

Microsoft releases SQL Server Cumulative Updates about every 60 days. This is a part of your job that you're going to be doing a lot, so let's get good at it! Here's the strategy I like to use.

Pick what patch you're going to apply. Generally speaking, you should be on the most recent Cumulative Update available for your version. (Years ago, folks only applied Service Packs, but starting with SQL Server 2017, Service Packs are gone. Microsoft only ships Cumulative Updates now.)

Read more about How to Patch SQL Server 54 comments — Join the discussion
Production DBA

SQL Server Suddenly Frozen? You Might Be Snapshotting Too Many Databases.

Snapshot backup tools like Azure Site Recovery and Veeam are great for sysadmins. They let you quickly replicate a virtual machine to somewhere else without knowing too much about the server's contents.

To pull it off, they use the Windows Volume Shadow Copy Service to do snapshot backups - often referred to as VSS snaps. In a nutshell:

Read more about SQL Server Suddenly Frozen? You Might Be Snapshotting Too Many Databases. 37 comments — Join the discussion

3 Ways to Run DBCC CHECKDB Faster

In my last post, I talked about how you can get 43%-67% faster backups. Today, I'm using that same SQL Server setup to discuss how throwing more CPU cores might help you check for corruption faster if you've already got modern fast storage. I don't expect everyone to go to this level of detail by any means, but it's the kind of tuning you can do when you're facing multiple terabytes of production data per server and shrinking maintenance windows.

Read more about 3 Ways to Run DBCC CHECKDB Faster 20 comments — Join the discussion
Production DBA

Back Up SQL Server 43%-67% Faster by Writing to Multiple Files.

Even if you're not writing to different physical drives, you can get faster backups with Microsoft SQL Server when you back up to multiple files. Your exact numbers are going to vary based on your server and your utter inability to rub two sticks together to make fire, but let's see how I do.

Here's the hardware I'm using:

Read more about Back Up SQL Server 43%-67% Faster by Writing to Multiple Files. 38 comments — Join the discussion

Can I Offload DBCC CHECKDB To Another Server?

You want to check for corruption, but you don't want to slow down your primary production server.

In this post, I'm specifically talking about offloading the corruption checking process. I'm not talking about doing corruption checking on both the primary and other servers - that's wonderful, and if you're doing that, you should hug yourself. You're doing a good job. Who's a good dog? You are! Good dog.

Read more about Can I Offload DBCC CHECKDB To Another Server? 29 comments — Join the discussion