Skip to main content
All CollectionsTx
Working with Tx Projects
Working with Tx Projects

Overview and first steps to working with Tx projects

S
Written by Serge Gershkovich
Updated over a week ago

Tx Projects are currently available for the following:

  • Plan: Tx is a standalone product license that includes all the features of existing SqlDBM plans and data automation and transformation features

  • Databases:

    • Snowflake

    • other CDPs will be included in the future

How to get started with Tx

In SqlDBM, Tx stands for Transformational, represented as a new type of project. To begin, a new Transformational Project needs to be created.

Steps to Start a Transformational Project

  1. Save the Project

  2. Set Up a User Connection

Currently, Tx Projects allow for Snowflake database connections and Azure DevOps as the code repository. Soon, support will be extended to additional cloud data platforms and repositories.

Setting Up a User Connection

After the project is saved, a prompt requesting to set up a connection will be shown. A list of available user connections is displayed where any existing ones can be chosen, or a new user connection can be configured.

Initial Configuration

  • The first time the project user connection is configured, the user will be asked to choose an existing branch.

  • Creating a new branch is a feature coming soon.

User Connections and Repositories

  • User connections are individually configured, but the Git repository is saved at the project level.

  • All users working on the same project will link to the same repository.

  • By default, the user connection to a database creates a location, which is a logical mapping to a certain database and schema.

Start Transforming Data

Steps to Begin Data Transformation

  1. Add Sources: Sources are where data is obtained for transformations. See the related article to learn how to add sources.

  2. Add a Node from the DAG: From the Directed Acyclic Graph (DAG) where sources are represented, select a source and add a node by choosing which template to use.

    • Authors can edit or write custom templates to perform desired data transformations. See the related article on Tx Templates.

  3. Create Tx Objects: The Tx object is created based on the data structure from the source and the columns defined in the template. This consists of:

    • A Column grid.

    • The logic block defining how data for this node is created or loaded. See the related article on Tx Objects.

Working with Tx Objects

Understanding Dependencies

In the DAG, the dependency between the Tx Object and the related sources is shown as an arrow linking the elements. This does not create a constraint but indicates that the Select statement for the Tx Object depends on the related source.

Data Preview

  • Tx Sources: Data Preview provides a brief sample of records sourced directly from the database, offering valuable context about the entities.

  • Tx Objects: The Select Data button allows for a data preview of the select statement in the logic definition. See the related article on Data Preview and Tx Objects.

Integration with Relational Diagram (ERD)

Both Tx Sources and Tx Objects can be added to the Relational Diagram (ERD), allowing relational modeling to be in sync with the transformational, visualizing all elements in the diagram.

Editing and Viewing Elements in ERD Diagram

  • Sources: These are existing elements in the database that do not have transformations. Therefore, they can be edited in the same way as relational elements.

  • Tx Objects: These objects have transformations, so they can only be viewed as a grid structure. Manipulation of Tx Objects must be done from within Tx.

  • Virtual Relationships: Only virtual relationships can be included with these elements.


​

See also:

Did this answer your question?