Command-line tool for running, verifying, and cloning versioned SQL Server databases, parsing T-SQL with ScriptDom to report whether each migration is actually applied.
Most migration runners track what they executed, not what is actually in the database. SchemaScope closes that gap: it parses every versioned T-SQL script with Microsoft's ScriptDom, compares the objects it finds against the live SQL Server database, and reports each script as applied, partial, missing, or no-DDL. The walkthrough below shows the three everyday flows.
Launching SchemaScope opens an interactive menu driven by single keypresses: run migrations, verify a version, detect the current version, take a backup, or clone. The same operations run non-interactively with flags, returning CI-friendly exit codes.
Detection walks every script in the configured range and classifies it against the live database, then reports the highest fully applied version and everything still pending. Natural schema drift from later drops or renames doesn't break the result.
Full heal applies everything pending in order, from the detected version to the newest script, with prepatch support. One command takes a database that's fifteen migrations behind to fully current.
Verification deep-compares a version's objects (tables, columns, indexes, constraints, procedures, views, triggers, functions) using canonical regeneration, so whitespace and syntax differences don't cause false alarms. Backups run with progress tracking.
Clone backs up a source database and restores it under a new name in one step, so a production-shaped test database is a single command instead of a manual backup-restore dance.