Liquibase Enterprise was formerly known as Datical DB.

Planning Checklists

Owned by Former user (Deleted)
Last updated: Jan 05, 2022 by Former user (Deleted)

Use the following tables as a road map to creating, managing, and configuring projects. 

Project Structure and Content 

PlanningEffectSee 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

Provision a Postgres database for the DMC

When configured to do so, the Datical client will record operation and status information to a Postgres database. This data is displayed in the web based Deployment Monitoring Console. The DMC provides an internal Postgres database for evaluation purposes (demo mode), but for production usage a separate Postgres database is recommended (production mode).

Configuring a Project to Use the DMCDMC DB

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 in the datical.project file. You can also set up runtime credentials, where operations prompt the user or read an environment variable any time they need to access the database.  

We strongly recommend to use runtime credentials because it is more secure than stored credentials (due to the possibility of the stored password being decoded).  


Database Credential Management

Project Creation and Initialization

PlanningEffectSee also
What tool will I use to create projects?

Choices:

  • Datical DB GUI
  • Project Creation Scripts
Creating Liquibase Enterprise Projects
How do I want to initialize databases in the release pipeline before I start using Datical DB to manage changes to it? 

Choices:

  • Initialize from the existing Production database schema
  • Baseline - Capture the current state of all databases in the release pipeline
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. 
  • Plan and initialize your SCM for use by Datical DB.
  • Commit a project to the SCM using the Datical DB GUI.
Committing Projects to a Source Control Repository

Project Behavior Settings

PlanningEffectSee also
I want to configure project behavior. 

Project behavior is managed in the following areas:

  • Schema Management - the managed schema for the project
  • Snapshot & Diff - How packaging and Datical DB perform database snapshots and perform diffs between them.
  • Deployment - How Datical DB performs forecast and deploy operations
  • Credential Management - Whether to use stored credentials or runtime credentials (environment variables or user prompts).  We strongly recommend to use runtime credentials because it is more secure than stored credentials (due to the possibility of the stored password being decoded).
  • Deployment Monitoring Console Database (DMCDB) - Register the project with a DMCDB you provide.
  • Release Labels - Project-level labels applied to each changeset as it is deployed.
  • Change Log Property Substitution - Properties (variables) used in place of static values, generally used to specify behavior that varies at each step in the release pipeline.   



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:

  • deployPackager.properties file - Controls overall packaging behavior
  • metadata.properties file - Controls behavior for SQL script directories in which it appears
  • Backup and Restore - During packaging the REF database is backed up and restored multiple times. 
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


Copyright © Liquibase 2012-2022 - Proprietary and Confidential