Connect your
operational database
to your business systems.

Select the tables and business fields, preserve record identity, and verify database permissions. A read-only model and an application using two-way sync have different write requirements. The selected database connector determines its key, change-detection, and schema restrictions.

Postgres connector requirements

No. The Postgres connector uses logical replication, while the MySQL setup documents database triggers for change logging. The separate Postgres Heroku connector also uses triggers when replication rights are unavailable. Follow the guide for the exact connector and hosting environment.

MySQL change logging setup

Each selected table needs a single-column primary key with a database-generated default. Composite primary keys are unsupported. The connected role also needs the documented ownership and replication permissions; confirm the hosting-specific procedure before changing replication settings.

Postgres key and replication requirements

A database view cannot be a writable destination for two-way sync. View support also varies by connector. Use a supported table when both sides need to accept writes, and confirm the selected source object separately when it only supplies data.

Two-way sync and read-only objects

Renaming a schema, table, or column requires updating the Stacksync configuration. Treat the rename as a coordinated schema change: inspect the affected mappings, follow the documented update procedure, and verify representative records before expanding the sync again.

Postgres schema restrictions