DB Ghost Builder™
Overview
DB Ghost Builder builds databases from individual object scripts (CREATE TABLE, CREATE PROCEDURE etc.). It seamlessly handles all
dependency issues and highlights any syntax errors.
Designed to be the perfect companion to your daily/continuous build process it enables you to regard your "source database" as a
set of object creation scripts. When these scripts are under source control then the source control system maintains a full audit
trail of changes as development staff check them out, make changes and then check them back in again.
Once a new database has been built successfully it can be used as the source database for a compare and upgrade of any target database,
such as the test or production database using the compare functionality of the DB Ghost Change Manager.
The Builder is delivered as a sub function of the Database Change Manager™ application which itself
is contained within the single installer (DBGhost.msi)
Features
- Builds databases from individual object scripts
- Highlights syntax errors
- Discovers dependency problems
- Command line or API execution for total process automation (requires Automation Toolkit™)
- Creates a single script for the database build that can be reused
- Allows insertion of a custom script at the end of the build to make any post build modifications to the schema or data
Screenshots
The Builder functionality is incorporated within the DB Ghost Database Change Manager™ application.
The license for the Builder enables the following option:
In order to build a new database a template database must exist to provide the settings for database level attributes (FileGroups, Physical file location, collation etc.):
Enter the name of the new database and if it needs to persist after the build completes. The database may not need to be kept if only a build verification is required:
Choose the location of the object creation scripts:
Processing options such as capturing the build SQL and a report file are specified here:
DB Ghost Builder builds the database from the source scripts handling all dependencies:
Once the build is complete any "hard" dependency and syntax errors are highlighted enabling swift resolution of issues, especially when combined with
a continuous build process: