Skip to main content
All tables, except those explicitly listed as “blocked” below, are mirrored. New tables added in future versions of SuperOffice, as well as any customer-defined tables created in the Service product, are picked up automatically by the client on its next schema-check cycle. Customer-defined tables that are deleted are propagated to the replica. If a table is created, mirrored, deleted, re-created, and mirrored again in a way that prevents an in-place schema update, the client drops the table and requests a fresh snapshot for it. The reason column explains why a table is not mirrored. If you believe a table on this list should be mirrored, contact us.
The new client adds a few exclusions on top of the legacy list to keep the replica cleaner and faster - notably the binaryobject table (large binary content, not useful for analytics) and various dictionary information tables (internal metadata cache). These are listed below alongside the historical exclusions.