Common Workflows

Repeatable Script Runner playbooks for multi-server work.

Fleet inventory (read-only)

Create or select a Server Group that includes the instances you manage.
Paste a read-only inventory script (versions, databases, last backup times, etc.).
Set Include Databases if you only need user DBs (exclude system DBs via filter).
Run Validate, then Execute in parallel if the script is lightweight.
Export the result grid to Excel, CSV, or JSON for the change ticket.

Put the change script in a Script Folder (or paste it) with clear GO batches.
Target a non-prod group first; use Stop-on-error if later steps depend on earlier ones.
Review the Execution Log for failed batches; fix and re-run only failed targets if needed.
Promote the same script to a prod group after sign-off — do not edit the script between environments if you can avoid it.

Name scripts so Pattern Match Routing can map files to the right server groups.
Run the folder against the fleet; confirm each file hit the intended targets in the log.

Set the run up once: add the script folder, order the files, check the exact servers and databases, and pick your execution options.
Press Ctrl+S and save the project into the same repository as the scripts, so the folder path is stored relative to the project file.
Commit the .dbsrproj alongside the SQL. Reviewers can see in the diff exactly which servers and options the release will use, and no credentials are in the file.
On release night anyone with the same servers registered opens the project with Ctrl+Shift+O and presses F5.