The SQL Server Maintenance Solution processes databases in parallel by running multiple jobs with the same DatabaseBackup parameters and setting @DatabasesInParallel = 'Y'. The workers share a queue; one stored-procedure call does not create parallel workers by itself.
Last updated: October 6, 2026.
EXECUTE dbo.DatabaseBackup
@Databases = 'Billing,Orders,Inventory',
@Directory = '\\backup01\sql',
@BackupType = 'FULL',
@CleanupTime = 168,
@Compress = 'Y',
@Checksum = 'Y',
@DatabasesInParallel = 'Y',
@LogToTable = 'Y';Create two or more SQL Server Agent jobs with this same command and schedule them together. The queue assigns different databases to the workers. Start with two workers and increase concurrency only after measuring CPU, storage throughput, network capacity, and restore performance.
Group databases that share one policy
Parallel workers must use the same parameter set. If some databases require different retention, compression, backup type, or destination, divide them into policy groups. Give each group its own database list and matching worker jobs. A control table can generate those lists, but it should not launch one procedure call per database when you expect the built-in shared queue to coordinate them.
The official DatabasesInParallel documentation specifies multiple jobs with identical parameters. Its database selector supports explicit names, exclusions, and wildcard patterns.
Protect the backup destination from overload
More workers do not guarantee faster completion. Parallel full backups may saturate the same disks or network share and can compete with production workloads. Use checksums, log commands to dbo.CommandLog, alert on failed jobs, and verify that cleanup runs only after successful backup and verification. Stagger unrelated maintenance so integrity checks, index work, and backup workers do not all demand the same storage bandwidth. Microsoft’s BACKUP reference documents the underlying SQL Server options.
Test restores regularly; a shorter backup window is not useful if the files cannot meet the recovery objective. For related procedures, see verifying SQL Server backups, restoring to another server, and fixing backup access errors.
