MS-SQL connector as a source

The ETL pipeline, to transfer customer data from an MS-SQL table to a Langstack entity, is created as follows.

To see step-by-step instructions of how to create an ETL pipeline, click here.

  • An ETL pipeline named “Tutorial_MSSQL_to_entity” is created.

  • To connect to the data source, the necessary information is added as follows:

    1. The “Connector” tab is selected.

    2. For this example, “Tutorial_MSSQL” is selected from the drop-down menu.

    3. To go to the settings, click the “Edit the settings” arrow.

  • To connect to the data destination, the necessary information is added in the Data destination section:

    1. The “Entity” tab is selected.

    2. The “TEST_MSSQL_Entity” is selected from the drop-down menu.

    3. To view the entity records, click "Go to records."

  • The default selection for ETL pipeline execution is “Immediate”.

  • To align the source fields with destination fields, the settings for the reader and writer format are defined in the “Data Format” tab. The “Reader” tab is selected by default.

  • To update the settings for how the data should be read from the MS-SQL database:

    1. The Reader stream is “Database Stream.”

    2. To add the table name, click the “Edit the settings” arrow.

  • To add the table name to read the records from

    1. The MS-SQL table name is added "TEST_MSSQL" in the section “MS-SQL format details”.

    2. Click on "Accept & Collapse" to save the information.

  • In the Source fields section, all the four fields have been added as per the image below.

  • To define that the data is written to the destination as mentioned in reader source fields without transforming it, the “Writer Mode” is selected as “Append”.

  • In the Field Mapping section, all the “Mapped Fields” are added and aligned.

  • When the ETL pipeline is executed (after Save and Publish), the records will be added to the destination entity. The bit data type in MS-SQL is mapped to the boolean data type in Langstack in the case of the field “active_status”. The 0 is converted to false and 1 is converted to true.

Last updated