/
How To: Gather Data on Liquibase Enterprise Utilization

How To: Gather Data on Liquibase Enterprise Utilization

Owned by Ryan Campbell
Last updated: Feb 05, 2025 by Amy Smith
1 min read

From time to time, Liquibase may ask you to provide data on database target utilization. This utilization data comes from two locations: the DDB project repositories and the DMC database.

Collecting the datical.project files from the DDB project repositories

  1. Clone each active project locally (the ddb repo only).

  2. Run this command inside each ddb repo, which removes sensitive data: hammer debug export --include=datical.project

  3. Collect the zip file that is generated. The location of this file will be in the output for the command. By default it goes into a Reports\Debug folder.

  4. Include these zip files in the response to Liquibase.

You will see that the datical.project contains placeholders beginning with “<DBDEF_NAME>_” username="<DBDEF_NAME>_DBG_UN" password="<DBDEF_NAME>_DBG_PW". These are not the actual values from your file, but values inserted by the hammer debug export command.

Query the DMC Database

The DMC database contains information required to verify the completeness of database utilization.

  1. Retrieve the connection details for your DMC database from the dmcDB entry in one of the datical.project files collected above or from the Client Connect page in the Administration section of the DMC.

  2. Log into the DMC database via a tool such as Squirrel using the connection details from step 1.

  3. Run the following query:

select p.name as project, dp.name pipeline, dps.name as step, dps.dbms from dprj_pipeline_step dps inner join dprj_pipeline dp on (dp.id = dps.pipeline_id) inner join dprj_project p on (p.id = dp.project_id) where dps.name not like '%REF%' order by dps.dbms, p.name, dp.name, dps.step_order;

  1. Include the output from this query in the response to Liquibase.

 

 

Copyright © Datical 2012-2020 - Proprietary and Confidential