docs: MSSQL schema change handling and new error codes (powersync-docs #568) - #76
Open
bean1352 wants to merge 2 commits into
Open
docs: MSSQL schema change handling and new error codes (powersync-docs #568)#76bean1352 wants to merge 2 commits into
bean1352 wants to merge 2 commits into
Conversation
….25.0 - Update PSYNC_S1601 action: redeployment required, re-enabling CDC alone is not enough (capture instance gets a new object ID) - Add PSYNC_S1602: table not ready (CDC not enabled or table missing) - Add PSYNC_S1603: table dropped/renamed/recreated or identity mismatch - Add PSYNC_S1604: MSSQL connection configuration error - Add PSYNC_R2201: wildcard table/schema name not supported by connector - Add PSYNC_S4106: Sync Config reprocess blocked by concurrent deployment - Add MSSQL replication constraints section in powersync-service.md: no wildcard table names, every table must exist with CDC enabled, schema changes require Sync Config redeployment Source: powersync-docs #568 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QvSGF6y5LDhE2bf6GAWYPf
michaelbarnes
changed the title
michaelbarnes
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Source docs PR: powersync-ja/powersync-docs#568
What changed in docs
PowerSync Service v1.25.0 changed MSSQL schema change handling: each deployment is now pinned to specific CDC capture instances and does not adopt schema changes automatically. The PR also added new MSSQL error codes (
PSYNC_S1601updated, plusPSYNC_S1602,PSYNC_S1603,PSYNC_S1604,PSYNC_R2201,PSYNC_S4106) and documented that wildcard table names (%) are not supported for SQL Server.Skill updates in this PR
skills/powersync/references/powersync-debug.md: UpdatedPSYNC_S1601action (redeploy Sync Config required, not just re-enable CDC). AddedPSYNC_R2201,PSYNC_S1602,PSYNC_S1603,PSYNC_S1604, andPSYNC_S4106to the key error codes table.skills/powersync/references/powersync-service.md: Added an "MSSQL Replication Constraints (v1.25.0+)" subsection after the Quick Start block covering: no wildcard table names, every listed table must exist with CDC enabled, schema changes require Sync Config redeployment, and what happens when a pinned capture instance is removed.Notes for reviewer
The v1.25.0 behavior change is significant: the old
PSYNC_S1601action ("re-enable CDC; replication resumes automatically") is now wrong. Any agent that followed that instruction would leave the user stuck. The updated row reflects the correct flow.The snyk-agent-scan demo endpoint returned 403 from the network proxy in this environment. The
validate.mjsscript passed with zero warnings. The edits contain no credentials, connection strings, hex strings, or credential-harvesting language, so no false positives are expected.A dedicated
mssql-schema-changes.mdreference file was considered but not created. The existing two files cover the actionable parts (error codes and setup constraints). The full step-by-step schema change workflows are in the docs and linked frompowersync-service.md; a new reference file would mostly duplicate that content without adding agent-usable rules.Generated by Claude Code