02-14-2019 03:19 PM
Contributed by @SriramGopal from Agilisium Consulting
The pipeline is designed to fetch records on an incremental basis from any RDBMS system and load to cloud storage (Amazon S3 in this case) with partitioning logic. This use case is applicable to Cloud Data Lake initiatives.
This pipeline also includes, the Date based Data Partitioning at the Storage layer and Data Validation trail between source and target.
Control Table check : Gets the last run details from Control table.
ETL Process : Fetches the incremental source data based on Control table and loads the data to S3
Control Table write : Updates the latest run data to Control table for tracking
The Control table is designed in such a way that it holds the source load type (RDBMS, FTP, API etc.) and the corresponding object name. Each object load will have the load start/end times and the records/ documents processed for every load. The source record fetch count and target table load count is calculated for every run. Based on the status (S-success or F-failure) of the load, automated notifications can be triggered to the technical team.
For every load, the data gets partitioned automatically based on the transaction timestamp in the storage layer (S3)
Sources : RDBMS Database, SQL Server Table
Targets : AWS Storage
Snaps used :
IM_RDBMS_S3_Inc_load.slp (43.6 KB)
IM_RDBMS_S3_Inc_load_S3writer.slp (12.2 KB)
IM_RDBMS_S3_Inc_load_Audit_update.slp (18.3 KB)
08-21-2019 03:49 PM
Do you have a similar pipeline/pattern that Ingests from SQL Server to Snowflake?
08-21-2019 10:08 PM
we can able to create it.
08-21-2019 03:57 PM
I’ll looking to see if we have any in the queue to upload, but I don’t think there is one yet.
You may be able to combine part of this pipeline with a part of Move data from AWS S3 to Snowflake Data Warehouse to get you close to what you want.