Step 2. Add the Additional Inputs

For more insights, you can provide additional inputs (optional) such as DDL and orchestration scripts.

DDL files help in retrieving schema-level information and generating corresponding recommendations for the target. In addition to this, scheduler or orchestrator scripts identify and map dependencies between the jobs, scripts, queries and plot their lineage.

To add additional inputs, follow the below steps:

In DDL script, provide scripts (DDL, SQL, Properties, ZIP) to define the schema of the database. The uploaded DDL script acts as a metadata reference for the source scripts. This helps in populating column-level lineage, identifying element metadata, and Zaloni integration.

Steps:

Prerequisites
Step 1. Provide Primary Inputs
Step 2. Add the Additional Inputs
Step 3. Update the Source Configuration
Step 4. Configure the Recommendation Settings

In Input for Schema Optimization, upload the CSV file to obtain schema optimization recommendations. It includes partitioning, bucketing, and clustering recommendations in the target schema.

Note:

If the selected source code type is EDW Execution Log and source is Snowflake, in the Other Artifacts field, you can upload files containing warehouse load data and metering information to get capacity and cost related insights.

In Cron Job (Shell), provide cron files for scheduling jobs.

Note:

If Informatica script is selected, you can provide additional information to resolve and update the database connection name with the datastore name. It helps to plot the lineage more accurately by establishing a relationship with the databases.

The Additional Information includes:

Connection: Provide the target database details.
Database Type: Choose the database type-Oracle, Vertica, Netezza, SQL Server, and Teradata.
Database Info: Provide Database information.
Username: Provide username.

Click to add multiple mappings.

Click Source Configuration to update the input dataset.

Next Step:

Step 3. Update the Source Configuration