Use the following tables as a road map to creating, managing, and configuring projects.
Project Structure and Content
Planning | Effect | See also |
---|---|---|
What are the phases in the release pipeline for applications? | When you create the project, you create a step for each phase in the release pipeline. The step includes connection information and step settings. | Identifying Databases for the Release Pipeline |
What are the release pipeline contents? | When you configure a project, you specify the database schema it manages. You choose from single-schema, multi-schema, and multi-database projects. | Release Pipeline Contents: Database Schema |
Create an audit database. | An audit database is used by projects to record operation activity. The audit database does not need to be the same type as the managed databases in the release pipeline. You need to do the following:
| For 2 and 3: Configuring a Project to Use the Audit Database |
Determine how to manage database credentials. | Typically you create a service user for Datical DB on each database in the release pipeline. You then configure project steps to use the credentials. By default credentials are stored with the project file. You can also set up dynamic credentials, where operations prompt the user or read an environment variable any time they need to access the database. | Database Credential Management |
Project Creation and Initialization
Planning | Effect | See also |
---|---|---|
What tool will I use to create projects? | Choices:
| Creating Datical Projects |
How do I want to initialize databases in the release pipeline before I start using Datical DB to manage changes to it? | Choices:
| Initializing Databases in the Project |
Oracle: I want to set up auto-permissions and auto-synonyms. | Automate generation of permissions and synonyms through each database in the release pipeline. | Configuring Auto-Permissions and Auto-Synonyms for Oracle |
I want to commit the product to a Source Code Management (SCM) repository. |
| Committing Projects to a Source Control Repository |
Project Behavior Settings
Planning | Effect | See also |
---|---|---|
I want to configure project behavior. | Project behavior is managed in the following areas:
| Configuring Project Settings |
I want to configure step behavior. | Step behavior settings vary by type of database used in the project. | Configuring Step Settings (DbDefs) |
I want to manage how SQL files are packaged into changesets. | Packaging behavior has several characteristics:
| Configuring Packaging for Projects |
Rules: I want to use Datical DB rules to enforce standards and practices for database changes. | Datical DB uses built-in checks to alert you if database object requirements are not met. You can also create rules for the project that reflect your IT standards and practices. | Configuring Rules for a Project |