Other: Append/Prepend Target Table Name
AnsweredProblem: HVR 5 had the ability to append/prepend to the target table name through a single channel action. HVR 6 no longer has this feature.
Example:
- Source table name Customers
- Target table name (with append _1234) Customers_1234
Business Case: We are replicating data from 20 different on-prem servers to a single Database/Schema in Snowflake. All on-prem databases have the same data schema, however the unique record IDs are not globally unique. This requires us to upload the data into unique tables in Snowflake in order to avoid primary key collisions. To do so, we are appending a site number to the tables. (e.g. Customers_1234, Customers_1235, Customers_1236, etc.). Currently we are replicating 120 tables at each site, with the possibility to increase this to 500+ tables per site. Currently we have to create a separate channel action for each individual table at each site in order to append the site number. Being able to create a single channel action to append to the target table name would significantly reduce the work required to setup all of the individual table actions. Append, Prepend or Both options would be beneficial however both prepend and append would be preferred.
-
Hi Zack,
In Snowflake, do you analyze data across all sites? If so, how do you do this? Using views?
I am curious if you considered adding an extra column with the source site instead of creating tables with different table names.
Thanks,
Mark.
Please sign in to leave a comment.
Comments
1 comment