A Source Database Has No CDC Support at All — Redesign the Ingestion for It

Northwind acquires a smaller company whose order-management system runs on a managed database-as-a-service product that does not expose logical replication, a binlog, or any change-data-capture feed — only a plain SQL query interface, and the vendor has confirmed CDC will never be supported. The acquired system has an orders-equivalent table with similar churn characteristics to Northwind's own orders table (high volume, frequent status updates).

1. Given that CDC is the case study's answer for exactly this kind of table, and it's unavailable here, design the ingestion approach you'd use instead.
2. What does your approach give up compared to true CDC, and does it matter for this use case?
3. How would you decide whether the trade-off in part 2 is acceptable, rather than just asserting it is?