75 backup parameters, clicked together and checked before the job ever runs.

The error message arrives at 2 a.m., in the job history.

DatabaseBackup has 75 parameters. Many exclude each other, some only apply to LOG or DIFF, others only to LiteSpeed, SQL Backup, SQLsafe or Data Domain Boost. Get one wrong and the procedure refuses with "The value for the parameter ... is not supported", usually during the first scheduled run. sqmOlaBackupBuilder moves that moment to the second you click.

What it needs.

Categories on the left, the finished command on the right.

Show-sqmOlaBackupGui uses the Visual Studio dark theme of the other powershelldba.de tools. Only parameters you actually set end up in the command; everything left at (Standard) keeps Ola's default.

1. CategoriesBasics, target and retention, compression and performance, encryption, conditions, file names and directories, options, third-party software, execution. The badge shows how many parameters are set in each.
2. Fields with helpDrop-downs for every Y/N and value list, pickers for databases and availability groups (keywords, include, exclude, wildcards), folder picker, token menu for @DirectoryStructure and @FileName.
3. PresetsUser databases FULL / DIFF / LOG, system databases, ad-hoc COPY_ONLY, striping and tuning, dry run. A preset keeps the target directory you already entered.
4. Command and findingsRegenerated on every change, with VS-style syntax highlighting. Copy, save as file, save and load the whole configuration as JSON (@EncryptionKey is never saved).

The procedure's own rules, checked while you click.

More than 100 checks are taken from the parameter block of DatabaseBackup itself. Errors mean Ola would refuse the call; hints flag things that are allowed but rarely intended, such as no @CleanupTime or @LogToTable = 'N'.

Four formats, one source of truth.

EXECUTE [master].[dbo].[DatabaseBackup]
    @Databases     = 'USER_DATABASES, -Test%',
    @Directory     = '\\backupsrv\sql',
    @BackupType    = 'FULL',
    @Verify        = 'Y',
    @CleanupTime   = 168,
    @Compress      = 'Y',
    @Checksum      = 'Y',
    @NumberOfFiles = 2,
    @LogToTable    = 'Y';

Let Ola confirm the call before it is scheduled.

Some rules depend on the server: edition, version (ZSTD needs SQL Server 2025, QAT Standard or Enterprise), existing directories, certificates, credentials, installed backup software. The dry run sends the command with @Execute = 'N'; Ola then checks everything and only prints the BACKUP, VERIFY and cleanup commands it would run. Nothing is backed up.

1. ConnectWindows or SQL authentication. The status line shows SQL version, edition and the installed Ola version; databases, availability groups, certificates, asymmetric keys and credentials become drop-downs.
2. Dry runServer messages appear under Dry run / server output, errors in red.
3. Create jobIn the SQL Agent job format, after a confirmation. Refused while the validation list shows errors.

The same generator for deployment scripts.

Install, then the GUI, or one call.

# Installation - AllUsers when elevated, otherwise CurrentUser
Install.cmd

# GUI (or double-click Start-sqmOlaBackupBuilder.cmd without installing)
Show-sqmOlaBackupGui -SqlInstance SQL01

# Log backup every 15 minutes as an Agent job
$p = @{ Databases = 'USER_DATABASES'; BackupType = 'LOG'; ChangeBackupType = 'Y'; CleanupTime = 168; LogToTable = 'Y' }
Test-sqmOlaBackupParameter -Parameter $p
New-sqmOlaBackupCommand -Parameter $p -Format AgentJob -ScheduleType Interval -IntervalMinutes 15 -JobOutputFile

The last servers and the login name are remembered in %APPDATA%\sqmOlaBackupBuilder\config.json; the password never is. Tests\Test-sqmOlaBackupBuilder.ps1 -MaintenanceSolution MaintenanceSolution.sql compares the parameter list with a new Ola release, so new parameters show up immediately.

Build your first backup job in a minute.

No dependencies to install: unzip, double-click Start-sqmOlaBackupBuilder.cmd, pick a preset.