https://community.databricks.com/t5/community-articles/the-hardest-part-of-our-sap-migration-wasn-t-the-data-it-was/m-p/158545#M1253 <P>Part 2 of my series on building an enterprise data platform on Databricks — this one's about Silver.</P><P>Part 1 covered why we ran two ingestion paths in parallel (GoldenGate CDC + JDBC batch) and kept them as separate bronze tables. If you missed it:<BR /><A href="https://medium.com/@savlahanish/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered-9c4b1e81557c" target="_blank">https://medium.com/@savlahanish/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered-9c4b1e81557c</A></P><P>Part 2 is where it got harder.</P><P>When both Bronze tables exist simultaneously, you inevitably end up with the same logical record in two places — captured differently, timestamped differently, and neither timestamp is fully reliable on its own.</P><P>Three things this covers that most CDC tutorials don't:</P><P>→ The 5-minute overlap window where _ingest_time alone gives you the wrong answer - and the tiebreaker we added to fix it</P><P>→ How CDC DELETE events silently keep deleted SAP records alive in Silver if you don't handle them explicitly in your MERGE statement</P><P>→ The natural key mistake we made on one table - only caught when a business analyst noticed transaction counts in Silver didn't match SAP</P><P>Full post:&nbsp;<A href="https://medium.com/@savlahanish/the-hardest-part-of-our-sap-migration-wasnt-the-data-it-was-timing-e30e59ca6136" target="_blank">https://medium.com/@savlahanish/the-hardest-part-of-our-sap-migration-wasnt-the-data-it-was-timing-e30e59ca6136</A></P><P>Has anyone else hit timing issues during the initial load window on a similar migration?<BR />Curious how others handled the overlap period between snapshot and streaming.</P> Mon, 08 Jun 2026 10:26:05 GMT savlahanish27 2026-06-08T10:26:05Z https://community.databricks.com/t5/community-articles/the-hardest-part-of-our-sap-migration-wasn-t-the-data-it-was/m-p/158545#M1253 <P>Part 2 of my series on building an enterprise data platform on Databricks — this one's about Silver.</P><P>Part 1 covered why we ran two ingestion paths in parallel (GoldenGate CDC + JDBC batch) and kept them as separate bronze tables. If you missed it:<BR /><A href="https://medium.com/@savlahanish/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered-9c4b1e81557c" target="_blank">https://medium.com/@savlahanish/why-we-used-two-bronze-tables-instead-of-one-and-why-it-mattered-9c4b1e81557c</A></P><P>Part 2 is where it got harder.</P><P>When both Bronze tables exist simultaneously, you inevitably end up with the same logical record in two places — captured differently, timestamped differently, and neither timestamp is fully reliable on its own.</P><P>Three things this covers that most CDC tutorials don't:</P><P>→ The 5-minute overlap window where _ingest_time alone gives you the wrong answer - and the tiebreaker we added to fix it</P><P>→ How CDC DELETE events silently keep deleted SAP records alive in Silver if you don't handle them explicitly in your MERGE statement</P><P>→ The natural key mistake we made on one table - only caught when a business analyst noticed transaction counts in Silver didn't match SAP</P><P>Full post:&nbsp;<A href="https://medium.com/@savlahanish/the-hardest-part-of-our-sap-migration-wasnt-the-data-it-was-timing-e30e59ca6136" target="_blank">https://medium.com/@savlahanish/the-hardest-part-of-our-sap-migration-wasnt-the-data-it-was-timing-e30e59ca6136</A></P><P>Has anyone else hit timing issues during the initial load window on a similar migration?<BR />Curious how others handled the overlap period between snapshot and streaming.</P> Mon, 08 Jun 2026 10:26:05 GMT https://community.databricks.com/t5/community-articles/the-hardest-part-of-our-sap-migration-wasn-t-the-data-it-was/m-p/158545#M1253 savlahanish27 2026-06-08T10:26:05Z