What's changing: PowerSync Service's MSSQL (SQL Server) source connector adds two new optional connection fields: cacert (a PEM-encoded CA certificate) and tls_servername. Together they let PowerSync validate a SQL Server certificate issued by a private CA without disabling full certificate validation via trustServerCertificate.
High priority — existing docs are now inaccurate or incomplete
None identified. Filing under the waiver: the hard precondition isn't met (this is an optional field and no existing doc contradicts it), but it's a meaningful new capability with no current coverage.
For reviewer consideration — may be worth documenting
- Self-Hosted Instance Configuration (
/configuration/powersync-service/self-hosted-instances#replication) — the "SQL Server connection options" accordion lists uri, hostname, port, username, password, database, schema, authentication, additionalConfig (pollingIntervalMs, pollingBatchSize, trustServerCertificate), and heartbeat_interval_seconds, but not cacert or tls_servername. The same page already documents both fields for Postgres connections in the same section (cacert: "CA certificate content in PEM format. Required for verify-ca, optional for verify-full."; tls_servername: "Use a servername for TLS that is different from hostname."), so this would extend an already-documented pattern to SQL Server rather than introduce a new one.
Source PR: powersync-ja/powersync-service#750. Merged 2026-08-12.
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: PowerSync Service's MSSQL (SQL Server) source connector adds two new optional connection fields:
cacert(a PEM-encoded CA certificate) andtls_servername. Together they let PowerSync validate a SQL Server certificate issued by a private CA without disabling full certificate validation viatrustServerCertificate.High priority — existing docs are now inaccurate or incomplete
None identified. Filing under the waiver: the hard precondition isn't met (this is an optional field and no existing doc contradicts it), but it's a meaningful new capability with no current coverage.
For reviewer consideration — may be worth documenting
/configuration/powersync-service/self-hosted-instances#replication) — the "SQL Server connection options" accordion listsuri,hostname,port,username,password,database,schema,authentication,additionalConfig(pollingIntervalMs,pollingBatchSize,trustServerCertificate), andheartbeat_interval_seconds, but notcacertortls_servername. The same page already documents both fields for Postgres connections in the same section (cacert: "CA certificate content in PEM format. Required forverify-ca, optional forverify-full.";tls_servername: "Use a servername for TLS that is different fromhostname."), so this would extend an already-documented pattern to SQL Server rather than introduce a new one.Source PR: powersync-ja/powersync-service#750. Merged 2026-08-12.
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.