Recent Activity
View allactive reservations, open branches
| ID | Status | Author | Description | Script | Created | Expires | |
|---|---|---|---|---|---|---|---|
| Branch | Ticket | Status | Database | Created | |
|---|---|---|---|---|---|
| Object | Type | Migration | Author | Description | Expires |
|---|---|---|---|---|---|
Deployment Configuration
Configure the reference database, migrations folder, and baseline path for this project.
Port Registry
Central registry of TCP ports in use across all projects on this machine.
Activity Log
Backups
Database backup files created during reference DB recreation.
Directory:
Backup Files
| Filename | Size | Created | |
|---|---|---|---|
Default Project Settings
Template values shown as examples when configuring new projects. These are the defaults displayed below each config field.
Example Templates
Dashboard Deployment Flows
The project detail page shows deployment banners. When there are pending migrations, Generate Script is available to create a SQL file for manual deployment.
Generate Script
Downloads a self-contained SQL deployment script. Does NOT touch any database.
- Collects migration
.sqlfiles from the project's migrations folder whose filenames match the required pattern0001_name.sql(e.g.,0001_initial_schema.sql); files that do not match are ignored - Generates a single SQL script that includes every discovered migration in deterministic (sorted) order, wrapped in idempotent checks
- Each migration checks
dbo.SchemaVersion— if already applied, it's skipped automatically - Database object definitions (stored procedures, functions, views) are wrapped in
sp_executesqlfor correct batch handling - The script is downloaded as
{ProjectName}_deployment.sql— ready to run in SQL Server tools that supportGObatch separators (e.g., SSMS, Azure Data Studio, sqlcmd)
Note: This is the recommended approach for production deployments. You control when and where the script runs.
Maintenance Actions
Available from the Maintenance section on the project detail page. These operations are irreversible.
Refresh Baseline
Syncs the latest repository state. If migration scripts exist, it consolidates them into the baseline .mdf, deletes the script files, then drops and recreates the reference database from the refreshed baseline. Cannot be undone.
- The project must have a configured baseline
.mdfpath - No open branches may exist — the dashboard disables this button when any feature branch is open
- At least one migration script must exist on disk
- Shows a confirmation dialog — you must explicitly confirm before anything happens
- Pulls the latest default branch from git so the baseline, version history, and migration files come from the repo source of truth
- Creates a temporary database from the synced baseline
.mdf - Applies all migration scripts to the temporary database, verifying every one succeeds
- Assigns a version number (format
YYYY.N, e.g.2026.5) and records it indbo.DbVersion - Generates a versioned deployment script and saves it to
../versions/{version}.sql(in aversionsfolder one level above the baseline.mdfdirectory) for archival - Replaces the baseline
.mdfwith the consolidated version (all migrations baked in) - Deletes migration script files that match the naming pattern (
0001_name.sql) from the migrations folder — other files are left untouched - Resets migration reservations in the coordinator database
- If the reference database already exists, takes a backup before dropping and recreating it from the refreshed baseline
Note: When migration scripts exist, all scripts matching the naming pattern are removed, the baseline contains the consolidated history, and the reference database is recreated from that refreshed baseline. If no migrations exist, the sync completes without changing the baseline or reference database. New branches will start from the refreshed state. If a failure occurs before the baseline is replaced, the temporary database is cleaned up and the original baseline is preserved. Failures after the baseline has been replaced may leave some cleanup steps only partially completed.
MCP Tools Reference
All tools available via the MigrationCoordinator MCP server. Agents call these through JSON-RPC at /rpc.