Versions Compared

Old Version 1

changes.mady.by.user Anonymous

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

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

...

Note

This functionality is maintained for backward compatibility with older methodologies.  

The current recommended methodology for introducing database changes is to check SQL scripts into a source control repository and then package them into changesets using deploy packager. 

Overview

You can create changesets for database schema changes directly In the Datical DB GUI. The changesets are inserted into the changelog directly. When the changeset is successfully deployed, the databaseChangeLog table in the tracking schema is updated. 

...

  1. Click a project (Deployment Plan) in the left column. Changesets you create are inserted into the changelog for this project.
  2. Click Add a Change Set.
  3. Select the type of changeset to create from the list. You can search types using the Filter box. 
  4. Click Next
  5. Provide the information required by the changeset type. There may be several pages, depending on the type. 
  6. Click Finalize. 
  7. Provide changeset information for identification, labels, contexts, and deployment behavior. 
  8. Click Finish. 

Most commonly used Change Set Types for newer Versions 7.9 and higher

  • For Oracle use “Execute with sqlplus for Oracle Databases” in the “SQL Script Executors for Liquibase Business & Enterprise” section of the Changeset Wizard

  • For SQL Server use “Execute with sqlcmd for Microsoft SQL Server & Azure SQL Databases” in the “SQL Script Executors for Liquibase Business & Enterprise” section of the Changeset Wizard (sqlcmd needs to be installed and pointed to by PATH environment variable)

  • For Azure SQL use “Execute with sqlcmd for Microsoft SQL Server & Azure SQL Databases” in the “SQL Script Executors for Liquibase Business & Enterprise” section of the Changeset Wizard (sqlcmd needs to be installed and pointed to by PATH environment variable)

  • For DB2 use “Execute with clpplus for DB2 Databases" in the “SQL Script Executors for Liquibase Business & Enterprise” section of the Changeset Wizard (clpplus needs to be installed and pointed to by PATH environment variable)

  • For PostgreSQL use “Execute with psql for Postgres Databases” in the “SQL Script Executors for Liquibase Business & Enterprise” section of the Changeset Wizard (psql needs to be installed and pointed to by PATH environment variable)

  • For EnterpriseDB use “Execute with edbplus for EnterpriseDB databases” in the “SQL Script Executors for Liquibase Business & Enterprise” section of the Changeset Wizard

  • Image Added

Most commonly used Change Set Types for older Versions 7.8 and lower

  • For Oracle use “Execute with SQLPlus” in the “Oracle Utilities” section of the Changeset Wizard

  • For SQL Server use “Execute with SQLCMD” in the “Other” section of the Changeset Wizard (sqlcmd needs to be installed and pointed to by PATH environment variable)

  • For DB2 use “Execute with CLPPlus” in the “Other” section of the Changeset Wizard (clpplus needs to be installed and pointed to by PATH environment variable)

  • For PostgreSQL use “Execute with psql” in the “Other” section of the Changeset Wizard (psql needs to be installed and pointed to by PATH environment variable)

  • For EnterpriseDB use “Custom SQL (External File)” in the “Other” section of the Changeset Wizard

  • Image Added


Note

The change set type for executing an external custom SQL script using the JDBC driver has been renamed:

  • In newer Versions 7.9 and higher it is now called "Execute a SQL Script file using JDBC"
  • In older Versions 7.8 and lower it was previously called "Custom SQL (External File)"