Components

diagram

Dawiso Database

The production tables that hosts the application’s configuration and data.
Serves only for application purposes, all of the analytical traffic is redirected to Subscriber DB to avoid impacting production.

Component that orchestrates jobs at Dawiso DB.
Task responsible for the replication kick off will be added to Task Scheduler during Initial Load based on Configuration_Value at ENV_Configuration.
Based at configured schedule, the cron patter will be added and gonna determine replication frequency.

For each table that will be synchronized to Subscriber DB there is a corresponding view that exposes the exact set of columns to replicate.
Tables listed in this documentation are default tables for synchronization and corresponding views are already created according to standard replication.
There is a possibility to create more views if it is necessary to synchronize more tables.
Views in this schema act as the authoritative contract for synchronization and only the data exposed by these views is replicated.

SQL Server native change-tracking mechanism that record INSERT / UPDATE / DELETE events.
Source for incremental syncs into subscriber.
Change Tracking at the replicated tables will be enabled during Initial Load based on Views of Selected Tables.
Note: Monitor CT table sizes and the performance impact of the capture mechanism and define a retention policy for CT data to avoid unbounded growth.

Predefined set of tables that serves as configuration for the whole Dawiso synchronization with subscriber.
Includes information about subscriber, synchronized articles, logs and deltas.
Records are inserted during Initial Load and Replication procedures afterwards.

Periodic snapshots (point-in-time exports) of data at Views of Selected Tables inner joined with CHANGETABLE().
Implemented as physical snapshot tables that will be copied to Subscriber DB, serving only for Replication purposes.

Implemented as physical snapshot tables that are copies of Snapshots at Dawiso DB, serving only for Replication purposes.
After replication is over, current Snapshots will be available at Subscriber DB till the next synchronization when the data will be overwritten be newer records.

Predefined set of tables that serves as configuration for the whole Dawiso synchronization.
Includes information about subscriber, synchronized articles, logs and deltas.
Records are copied from Dawiso DB so the data is matching.

Standard views that expose curated columns and business-friendly joins optimized for customer convenience to provide insights from Dawiso.
Views reference Source Tables at Subscriber DB so Product DB is not stressed by analytical queries.

Subscriber DB can optionally provision per-customer tables to support customer-specific customizations, derived tables, or shared materializations.
This option is the matter of previous mutual agreement within Dawiso and the Customer.
Dawiso takes full resposibility of keeping these tables valid in time so any work asscoited with maintenance will be charged proportionally.

Per-customer views can be created in isolated schema to support customer-specific logic or access patterns without altering the Standard Views.
Customer will have DDL rights for this schema and it’s in his own responisbility to follow Release Notes and keep views valid in time.