A database logo is not enough. Check the exact capability and contract.
Burst Load source and target roles, CDC modes, hosting, log access, recovery, replica identity, supplemental logging, keys, and apply profiles can all change behavior.
trialstarter{...}activescaleUNCHANGED_TOASTConfirm Burst Load and CDC capabilities from one source.
Validate the exact capture or loading interface.
Preserve values or surface a visible incompatibility.
Shared catalog
Start with the engine roles the product actually exposes.
The Omni Loader database catalog identifies Burst Load sources and targets plus CDC source and relational destination roles. Engine detail pages use that same source for descriptions and supported types.
CDC source contract
Know what each reader emits.
Before-images, schema events, truncate, LOB handling, and managed-service support differ by source and capture mode.
Target contract
Validate mappings before loading or applying.
Omni Loader maps scalar, temporal, binary, JSON, and engine-specific values into target dialects. Preflight should reject unsafe key, sizing, or bulk behavior before execution.
Keep exploring
See the connected parts of the platform.
Check the exact path before committing.
Bring versions, tables, types, keys, hosting, and movement pattern. We will identify compatibility risks for Burst Load, CDC, or both.