Database Mirroring keeps a customer-managed Microsoft SQL Server database in sync with your SuperOffice Online tenant, giving you a local replica for reporting, analytics, pattern recognition, and any long-running processing that doesn't need to live behind the REST API.

The new client is outbound-only: a small Windows application connects from your host to SuperOffice over standard HTTPS, streams change events from the cloud, and applies them to your replica within seconds. There is no public endpoint to host, no IIS site, no inbound firewall rule, and no SuperOffice-issued certificate to install or renew. Authentication uses short-lived JWT access tokens with rotating refresh tokens, securely stored in your replica database using Windows DPAPI.

Changes are captured at the source using Change Data Capture (CDC) and streamed through Kafka, so the replica reflects activity in SuperOffice Online in near real time rather than on a scheduled batch. New tables in the source schema are detected and added automatically, and tenant lifecycle events such as database moves, restores, suspensions, and resumptions are handled transparently with an automatic re-snapshot.

Database Mirroring is an add-on to your SuperOffice Online subscription and is intended for technical teams able to operate the client and its replica database.

• Outbound-only architecture — no inbound ports, no IIS, no public endpoint to host or harden.
• Near-real-time replication using Change Data Capture (CDC) and Kafka; typical end-to-end latency in seconds.
• Modern security — short-lived JWT access tokens with rotating refresh tokens, encrypted at rest in the replica database with Windows DPAPI.
• Single Windows executable that installs as a Windows Service; multiple instances (for example, Test and Production) supported side-by-side on the same host.
• Automatic schema evolution — new tables in the source CRM are detected and added on the next schema-check cycle.
• Configurable destination schema — preserves the source [crm7] schema by default, or override to dbo (or another schema) for downstream compatibility.
• Browser-based provisioning with consent and session naming, completed in minutes.
• Built-in diagnostics — Windows Event Log, NLog file/sink targets, and Application Insights supported out of the box.
• Resilient to tenant lifecycle events — database moves, restores, suspensions, and resumptions trigger a transparent automatic re-snapshot.
• Self-service recovery — re-sync individual tables on demand with the resync-tables CLI command.

New outbound-only Database Mirroring client

This release introduces a completely re-architected Database Mirroring client that replaces the legacy WCF-based mirroring service for new deployments.

Highlights:

• Outbound-only connectivity — no public endpoint, no IIS site, no SuperOffice-issued certificates, and no inbound firewall rules to maintain.
• Near-real-time replication powered by Change Data Capture (CDC) and Kafka, with end-to-end latency typically measured in seconds rather than hours.
• Modern security — short-lived JWT access tokens with rotating refresh tokens, encrypted at rest in the replica database using Windows DPAPI.
• Simpler operations — a single command-line executable (SuperOffice.Online.Replication.Client.exe) that installs as a Windows Service.
• Automatic schema detection — new tables in the source CRM are picked up automatically.
• Choice of destination schema — [crm7] by default, or set TablePrefix to dbo (or another schema) before provisioning.
• Self-service recovery — the new resync-tables CLI command re-snapshots specific tables without operator intervention.

Customers running the legacy WCF mirroring service can continue to do so and should plan a migration using the documented parallel-run plus database-rename cutover procedure. See the migration guide in the SuperOffice documentation for details.