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:
- Whether
Registration.LicensedEmailandRegistration.RegistrationCodeare present. - If both are present, whether the license authenticates. A failure is reported, not fatal.
- The connection to every configured database target.
- Whether
MigrationPath,TempPath, andSchemaPathexist. MissingMigrationPathandTempPathfolders are created, unlessDryRunis on. - The
Platform,Generated, andApplicationfolders: 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 verifybeforedeployand in CI. - Use
dbm testwhen you only need a connection check. - Set
DryRun: trueto stopverifyfrom creating missing folders.