Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

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
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: 

  1. Provision a database for use by Datical DB as an audit database.
  2. Configure the first project to use the audit database. Upon first access, the Datical DB audit database schema is loaded into the audit database. 
  3. Configure other projects to use the audit database. 
For 2 and 3: 
Configuring a Project to Use the Audit DMC 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 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

...

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).
  • Audit Database - Register the project with an audit database 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

...