I suggest you ...

Enhance Upsert to enable simplified cloning for staging and handling of deletes

We use upsert to pull 1-on-1 copies from our production environment to staging. In case a source system does not correctly log modified rows, we use the hashing transform to calculate a checksum and use column compare to trigger row updates and last modified timestamps from upsert.

However, sometimes we like to either replicate or flag rows that were deleted in the source system. The way it is now, we have to pull from the source system and the copy, sort, join, and match on keys being available left or right (indicates insert or delete) and if the calculated checksum from the source matches the stored checksum in the copy (update or unchanged).

If upsert was allowed to detect deletes internally and optionally handle them by either flagging a row or replicating deletion, that would greatly simplify this flow and increase usability.

41 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Ramon Bertrand shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base