MSSQL and Oracle replica ports for backfills
MSSQL and Oracle sources accept an optional snapshotPort so backfills can reach a replica on a different port from the primary.
MSSQL and Oracle replica settings could override the replica host but not its port, forcing replicas to use the primary database’s port.
Both connectors now accept an optional snapshotPort for backfills. When it is unset, Artie continues to use the primary port; streaming remains on the primary connection.
Why this matters
- Support replicas hosted on a different port from the primary database
- Route snapshot traffic to the correct MSSQL or Oracle replica endpoint
- Keep existing configurations unchanged by preserving the primary-port fallback