Modeler

Introduction

The Modeler helps with the creation of data flows within a DWH based on a metadata model. The output is either a SQL script (transformation represented by a querry) or an EXEC SQL job.

Currently only TSQL/SnowSQL compatible queries can be generated.

The Modeler is divided into two possible modeling constructs: CustomDataFlow and DataFlow.

Requirements / Limitations

None

Flow

The flow of the modeler begins at the Azure DevOps Git where the CLOE metadata files are located. Output mode SQL is used for rapid prototyping. You make changes to your modeler model, let CLOE translate the model to SQL queries written to a script, run the script and fix issues in your model. Once you are satisfied with the state of your modeler model you choose output mode JSON and let CLOE generate Exec_SQL jobs with all your queries which you can then use in your ETL process model.