What's changing: SQL Server (MSSQL) replication no longer detects or automatically adapts to source schema changes. Each replication stream now pins to the CDC capture instance and table set it started with. Adding a table, changing columns, or handling a dropped/renamed table now requires deploying the sync configuration as a new replication stream instead of relying on automatic detection and in-place adoption.
High priority — existing docs are now inaccurate or incomplete
- Implementing Schema Changes (
/maintenance-ops/implementing-schema-changes#sql-server-specifics) — The "SQL Server Specifics" section states "Schema change handling for SQL Server is supported from PowerSync Service v1.20.2" and describes several changes as automatically detected and handled without redeployment, including: "New capture instances are automatically detected for tables in your Sync Streams/Sync Rules. If a capture instance is newer than the one currently in use, PowerSync will automatically use the new capture instance," and CREATE/DROP/RENAME table sections describing automatic snapshotting and bucket cleanup. This is no longer accurate. PowerSync now keeps a stream pinned to its original capture instance and schema for its lifetime, only warns when a newer capture instance appears, and requires deploying a new replication stream to pick up dropped/renamed/added tables or changed columns.
- Error Codes Reference (
/debugging/error-codes#psync-s16xx-mssql-replication-issues) — The "PSYNC_S16xx: MSSQL replication issues" section only documents PSYNC_S1601. The PR introduces PSYNC_S1602 (table missing, not CDC-enabled, or fails fixed-table-set validation at stream start) and PSYNC_S1603 (a replicated table was dropped or renamed during active replication), neither of which appear in this reference yet.
For reviewer consideration — may be worth documenting
None.
Source PR: powersync-ja/powersync-service#727. Merged 2026-08-11. Publish updates only after this change ships in a release.
Filed automatically by Claude Code (claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.
What's changing: SQL Server (MSSQL) replication no longer detects or automatically adapts to source schema changes. Each replication stream now pins to the CDC capture instance and table set it started with. Adding a table, changing columns, or handling a dropped/renamed table now requires deploying the sync configuration as a new replication stream instead of relying on automatic detection and in-place adoption.
High priority — existing docs are now inaccurate or incomplete
/maintenance-ops/implementing-schema-changes#sql-server-specifics) — The "SQL Server Specifics" section states "Schema change handling for SQL Server is supported from PowerSync Service v1.20.2" and describes several changes as automatically detected and handled without redeployment, including: "New capture instances are automatically detected for tables in your Sync Streams/Sync Rules. If a capture instance is newer than the one currently in use, PowerSync will automatically use the new capture instance," and CREATE/DROP/RENAME table sections describing automatic snapshotting and bucket cleanup. This is no longer accurate. PowerSync now keeps a stream pinned to its original capture instance and schema for its lifetime, only warns when a newer capture instance appears, and requires deploying a new replication stream to pick up dropped/renamed/added tables or changed columns./debugging/error-codes#psync-s16xx-mssql-replication-issues) — The "PSYNC_S16xx: MSSQL replication issues" section only documentsPSYNC_S1601. The PR introducesPSYNC_S1602(table missing, not CDC-enabled, or fails fixed-table-set validation at stream start) andPSYNC_S1603(a replicated table was dropped or renamed during active replication), neither of which appear in this reference yet.For reviewer consideration — may be worth documenting
None.
Source PR: powersync-ja/powersync-service#727. Merged 2026-08-11. Publish updates only after this change ships in a release.
Filed automatically by Claude Code (
claude-sonnet-5). A human must verify the scope, prepare the docs PR, and publish it only once this update has been released.