Configure Velox databases
Velox uses system connection roles for configuration, logging and data. Current deployments can share some roles, but do not assume that a selectable separation is fully implemented or required. Use the release-specific database runbook.
Before you begin
Obtain approved, version-matched VxConfig and VxData creation or upgrade scripts, database names, authentication method, encryption requirements and separate least-privilege runtime credentials. Take restorable backups before changing an existing database.
Configure
- Have a database administrator create or upgrade each database with the approved scripts in their documented order.
- Review every script target before execution; never run a fresh-build master against an existing database.
- Verify the resulting schema/version using the release runbook.
- Create runtime logins and grant only the required database rights.
- In the Velox system connection configuration, define named database entries and assign the required
Config,LogandDataroles for production and test contexts. - Test each connection from Designer, then repeat under the service identity where Windows authentication is used.
- Record database versions and validation results without recording passwords.
Recovery
If a schema step or connection test fails, stop services and do not continue with later scripts. Preserve the error and executed-script list. Restore the pre-change database or follow the database runbook's forward-fix procedure; do not improvise manual schema edits.