Replicate by default attempts to achieve parity when creating target tables by applying the source DDL on the target database.
Desired State:
Replicate features configurable controls to determine what kinds of DDL are applied to the target database such as if NULL constraints should exist.
Business Case:
Certain sources create tables with heavy amounts of constraints and restrictions because they are part of a transactional system that must maintain integrity. A very common use case of Replicate is to pipeline data from these types of systems to data lakes or data warehouses. When logic begins to be applied to the data lake or data warehouse for downstream processing, such as a soft delete process, this can result in processing failures because Replicate has made every attempt to duplicate the source endpoint constraints on the target, which is often not used for the same purpose as the source. The workaround is a manual, customer-driven process to manage target tables from that point forward because Replicate does not have options to ignore these integrity constraints.
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.
