Scrapbook: SQL Server & Oracle CDC Summary
Date: 2026-02-16T16:45:00Z
Purpose
Create a concise, standalone report summarizing CDC options for SQL Server and Oracle, tailored for decision‑makers who need to understand capabilities, trade‑offs, and recommendations for MVP and later phases. This will be Report 7, building on Report 1 but more focused and actionable.
Key Points to Cover
- SQL Server: built‑in CDC vs Debezium connector vs Change Tracking. Focus on practical MVP approach (native CDC + Go poller). Include required privileges, performance, cleanup, offset handling.
- Oracle: GoldenGate (expensive, enterprise) vs Debezium Oracle connector (XStream/LogMiner). Why Oracle is out of scope for MVP; what would be needed if required later (cost, complexity).
- Comparison table summarizing each DB's best approach, required privileges,是否需要Kafka, maturity, on‑prem fit.
- Clear recommendation for each: SQL Server → native poller; Oracle → defer or use GoldenGate if budget allows.
Audience
Antonio and possibly sales/engineering teams evaluating multi‑DB support.
Structure
1. Introduction: Why separate summary? (Report 1 was broad; this zeroes in on two important enterprise DBs)
2. SQL Server CDC Deep Dive
- Built‑in CDC: how it works, enabling, change tables, query functions
- Polling implementation details (LSN tracking, idempotency)
- Pros/cons vs Debezium SQL Server connector
- Privileges and security considerations
- Performance and cleanup
- Recommended MVP approach
- GoldenGate: capabilities, cost, complexity
- Debezium Oracle connector: architecture, XStream API, licensing caveats
- Why Oracle is low priority for LATAM mid‑market
- If needed later: path and prerequisites
5. Final Recommendations
---
Will draft Report 7 accordingly.