Skip to main content

Verification Commands

Verification commands check that a project is ready without deploying anything.

verify​

Check registration, connections, folders, and migration script names.

Alias: -vf
License: Free

dbm verify
dbm -vf

Checks, in order:

  1. Whether Registration.LicensedEmail and Registration.RegistrationCode are present.
  2. If both are present, whether the license authenticates. A failure is reported, not fatal.
  3. The connection to every configured database target.
  4. Whether MigrationPath, TempPath, and SchemaPath exist. Missing MigrationPath and TempPath folders are created, unless DryRun is on.
  5. The Platform, Generated, and Application folders: every script name must follow <version> - <description>.sql, and no two scripts in the same folder may share a version number.

Example output:

Executing command: Verify
1. Checking login/register information...
Licensed Email: NOT PROVIDED
Registration Code: NOT PROVIDED
2. Authentication: SKIPPED - No credentials provided
3. Checking database connections...
Local: SUCCESS - Connection established successfully
4. Checking folder availability...
Migration Path: EXISTS - C:\Project\Database\Migration
Temp Path: EXISTS - c:\temp\
Schema Path: EXISTS - C:\Project\Database\Schema
5. Validating migration scripts...
Found 12 Application migration script file(s)
Application filename validation: SUCCESS - All 12 file(s) have valid names
Verification completed.

Script name rule: the description after <version> - must be 10 to 90 characters of letters, digits, spaces, -, or _. 100038 - fk_Comms.sql is rejected (too short); 100038 - fk_CommsSms.sql is accepted.

Tips:

  • Run dbm verify before deploy and in CI.
  • Use dbm test when you only need a connection check.
  • Set DryRun: true to stop verify from creating missing folders.