Scripts
The Scripts feature in AnalyticsCreator allows users to define and manage custom SQL scripts that can be executed during data warehouse generation or deployment. Scripts provide flexibility for extending automated logic with manual SQL code for special tasks such as maintenance, auditing, or advanced processing.
Function
Scripts are used to insert user-defined SQL logic into the data warehouse build process. They can be categorized by type, executed conditionally, and assigned to workflow packages. Each script supports versioning, activation status, and parsed/original SQL views for validation.
Access
Scripts are managed under the DWH > Scripts section. The interface includes a list of existing scripts and an editor for creating or modifying SQL logic, defining execution order, and setting dependencies or workflow relationships.
List Scripts
The image below shows the List Scripts interface with columns labeled for easy identification.
List Screen Properties
| ID | Property | Description |
|---|---|---|
| 1 | Name | Displays the name of the script |
| 2 | Type | Indicates the script category (e.g., Pre-Load, Post-Load, Maintenance) |
| 3 | Description | Displays a short summary of the script’s purpose |
| 4 | Delete | Deletes the selected script from the project |
| 5 | New | Opens the Script Editor to define a new custom script |
Script Edit
The image below shows the Script Edit interface used for creating or modifying SQL script definitions.
Edit Screen Properties
| ID | Property | Description |
|---|---|---|
| 1 | Script type | Defines the execution category of the script (e.g., Pre-Load, Post-Load, Custom) |
| 2 | Name | Specifies a unique name for the script |
| 3 | Description | Optional explanation of the script’s purpose |
| 4 | Sequence number | Defines execution order within the same script category |
| 5 | Inactive | Marks the script as inactive (excluded from execution) |
| 6 | Original | Displays the original user-entered SQL code |
| 7 | Parsed | Displays the system-interpreted SQL code after parsing |
| 8 | Package | Lists the workflow package that includes the script |
| 9 | Run | Determines if the script executes with the associated package |
Behavior
- Scripts can be included in workflow packages to execute custom SQL during ETL.
- They support version control through parsed/original SQL views.
- Inactive scripts are skipped during runtime execution.
- Execution order is defined using the sequence number field.
Notes
- Scripts extend standard generation logic with advanced customization.
- All SQL syntax must be valid for the target system (T-SQL, Snowflake SQL, etc.).
- Use descriptive names to identify scripts in complex projects.
