Builder Guide
Upgrade DB: staged database inventory
Review missing database dependencies before preparing a controlled SaaS upgrade.
Open your SaaS app's Backups page and find Upgrade DB — Staged database inventory. The panel displays the latest operator-published assessment of the Core, Logs, and AI databases.
What the assessment checks
The scan compares database structure with the reviewed golden contracts: tables, column definitions and data types, SQL types, functions, views, stored procedures, dependencies, and permissions. It does not copy or display customer record values.
Stage 1: missing procedures
- Ready: the procedure passes the dependency checks and can proceed to a restored-copy rehearsal.
- Blocked: required objects, columns, types, roles, or table contracts are missing or incompatible.
- Manual review: dynamic SQL, external references, triggers, unresolved dependencies, or other conditions need an operator's review.
Expand Review missing procedures to see names and reasons. Ready does not mean installed or approved. Existing procedures are not overwritten by the missing-procedure plan.
Stage 2: missing schema and older modules
Stage 2 counts identify work needed before the remaining procedures can be installed: missing tables, columns, SQL types, functions/views, and reviewed updates to older modules. Operators must prepare migration-owned changes, including any required backfill or reference data. An inventory cannot safely decide those data transformations on its own.
Refresh and approval are different actions
Refresh inventory status reloads the latest published assessment; it does not run a scan or change a database. If no inventory appears, ask the operator to run and publish the read-only scan. Scan time and fingerprint identify the assessment; the worker must recheck current state before applying a release.
The existing Back up and upgrade this app button queues the currently registered reviewed release. It does not automatically apply the Stage 1 or Stage 2 worklist. Plan-specific staged approval and execution are not yet enabled. Do not treat this panel as a one-click schema synchronization feature.
Required safeguards
A live staged release requires verified source backups of all three databases, an actual restored-copy rehearsal, dependency and behavior checks, preserved permissions, a matching approved plan, and recorded recovery steps. A golden database update does not silently update existing customer databases.
No database credentials or SQL execution permissions are given to the browser. Builder access remains scoped to the owned SaaS app through the existing authorized API. See Database contracts for the stored-procedure boundary.
Capability review: 2026-09-14. For exact current technical availability, use the generated API Map and first-class module inventory.