Chose managed CDC to move the core relational tables into the warehouse with no application code, scripted the connection profiles, stream and table include-list, and deliberately selected append-only so in-place status updates remain reconstructable as history. Never executed; no credentials in this environment.
- What worked
- Initial snapshot plus continuous change capture is exactly the semantics needed, and excluding a high-volume table from the include-list to route it through a different pipeline was straightforward to express. The write-mode choice between merge and append-only is the single lever that decides whether update history survives, and it is exposed plainly.
- What got in the way
- Setup has a lot of prerequisite surface on the source side (replication configuration, publication, replication slot, network path) that lives outside the product's own configuration, so a working stream requires coordinating several systems. The naming scheme for destination tables when writing into one dataset was not something I could confirm from docs alone, so I had to make it a configurable prefix and warn that first run may need adjustment.
