SQL Server Backup Recovery on SQL Server Scripts

SQL Server Copy-Only Backup Script for Dev Restore

Mon, 20 Apr 2026 00:00:00 +0000

A copy-only backup is a special SQL Server backup that is independent of the normal backup sequence. It does not reset the differential base or interrupt the transaction log backup chain, making it the correct choice when you need an ad-hoc backup for a development or test environment restore without affecting production recovery options.

Purpose and Overview

In a standard SQL Server backup strategy, full backups establish a new differential base and log backups form a continuous chain. If you take an unplanned full backup mid-schedule, the next differential backup becomes larger than expected because the base changed. If you take an unplanned log backup, you may break an automated restore chain that depends on log sequence numbers.

SQL Server: Find Databases With No Recent Backup

Sun, 19 Apr 2026 00:00:00 +0000

Finding databases that have not been backed up recently is one of the most important checks a DBA can run. A database that grows unnoticed without a backup is a data loss event waiting to happen. This script queries msdb.dbo.backupset against sys.databases to surface any online user database with no full backup in the last 24 hours, or that has never been backed up at all.

Purpose and Overview

SQL Server does not alert you by default when a database backup is overdue. If a scheduled backup job fails silently or a new database is created without being added to the backup plan, that database will accumulate changes with no recovery point. The only way to detect this proactively is to query the backup history in msdb.

SQL Server Backup Compression: Enable and Verify

Fri, 17 Apr 2026 00:00:00 +0000

Backup compression reduces the on-disk size of SQL Server backup files and can significantly shorten backup duration by reducing the amount of data written to disk. This post shows how to enable compression at the server level, verify the setting is active, and confirm compression ratios from backup history using the msdb catalog.

Purpose and Overview

SQL Server backup compression has been available since SQL Server 2008, but it was initially limited to Enterprise and Developer editions. From SQL Server 2016 SP1 onward it is available in all editions including Standard and Express. Despite this, many instances still run with compression disabled because the default setting is off.

SQL Server Backup History: Duration and Size Report

Mon, 13 Apr 2026 00:00:00 +0000

Query Backup Duration and File Size from SQL Server History

This script queries SQL Server's msdb backup history to report the backup type, start and finish time, duration in minutes, and file size in both megabytes and gigabytes for every backup across all user databases on the server.

Purpose and Overview

Knowing that a backup completed is only part of the picture. DBAs also need to understand how long each backup took and how large the resulting files are. A backup that used to finish in ten minutes now taking an hour is worth investigating. A backup file that is half its usual size may indicate a failed or partial operation. This script, adapted from the DBA-Scripts collection by Bulent Gucuk, joins sys.databases with msdb.dbo.backupset and msdb.dbo.backupmediafamily to surface both duration and size in a single result set. Running it regularly gives you a baseline so that anomalies are easy to spot.

SQL Server Backup Status Report: All Databases

Fri, 10 Apr 2026 00:00:00 +0000

Check SQL Server Backup Age Across All Databases

This script queries the SQL Server backup history catalog to report the most recent full, differential, and transaction log backup for every database, including how many hours and minutes ago each backup completed.

Purpose and Overview

Database backups are your last line of defense against data loss. Knowing exactly when each database was last backed up — and how old that backup is right now — is a fundamental DBA responsibility. This script, originally written by Tim Ford, joins master.sys.databases with the msdb backup history tables to produce a single report covering all backup types for all databases. It shows the backup finish time, the physical backup file path, and elapsed time in both hours and minutes, making it straightforward to spot any database that has missed a scheduled backup.

SQL Server Verify Backup Files: RESTORE VERIFYONLY

Mon, 06 Apr 2026 00:00:00 +0000

Verify SQL Server Backup Files with RESTORE VERIFYONLY

Backup files that cannot be restored are worthless, and many DBAs discover problems only when they attempt an actual restore under pressure. The scripts in this article use RESTORE VERIFYONLY to confirm that backup files are readable and internally consistent before a real disaster occurs.

Purpose and Overview

RESTORE VERIFYONLY reads a backup file and validates its structure without writing any data to a database. It checks that the backup set is complete, that all volumes are readable, and that header metadata is intact. It does not verify that every data page is logically consistent, but it catches the most common failure modes: truncated files, corrupted headers, and missing media families.

SQL Server Point-in-Time Restore with STOPAT

Sun, 05 Apr 2026 00:00:00 +0000

Recover a SQL Server Database to a Specific Point in Time

SQL Server's RESTORE LOG ... WITH STOPAT lets you roll a database back to any exact moment covered by your backup chain. This guide walks through querying backup history in msdb, executing the restore sequence, and verifying the result.

Purpose and Overview

Data loss incidents — accidental deletes, bad deployments, runaway updates — rarely happen at a convenient backup boundary. Point-in-time restore solves this by replaying transaction logs only up to a target timestamp, leaving the database in a consistent state as of that moment.