Prerequisites

Before you can set up replication, make sure you have the following requirements in place.

  • Database Permissions on Publisher -> You need DB Owner permissions on the publisher database (Dawiso production database). If you don’t have these permissions, you’ll need to request them from your Dawiso account manager.
  • Dawiso Version Requirements -> Your publisher database must be running Dawiso version 2025.8 or later. Earlier versions don’t include the necessary change tracking and replication components that replication depends on.
  • Subscriber Database -> Created dedicated target database that will serve as the subscriber in the replication setup. Make sure subscriber database version is up to date with your Dawiso instance.
  • Database Permissions on Subscriber -> You need DB Owner permissions on the subscriber database.
  • Network Access and Permissions -> The setup depends on whether your subscriber database is on the same server as your Dawiso database or on a separate server:
    • Same Server Setup - If both databases are on the same SQL Server instance, you just need to ensure that the Dawiso database user has db_owner permissions on the subscriber database.
    • Different Server Setup - If thesubscriber database is on a different server, you need to configure network access between the publisher (Dawiso database server) and the subscriber. The publisher needs to be able to connect to the subscriber to push data changes and vice versa. Create on Dawiso server linked server that will make subscriber database on subscriber server visible with db_owner role access and also the oposite, fromsubscriber server to Dawiso server also with db_owner role access.

Installation Steps

  1. Test Server Connectivity-> Verify that both servers can connect to each other by running simple SELECT queries.

    • From Dawiso database, test connection to subscriber:

      SELECT COUNT(*) FROM [< SubscriberLinkedServerName>].[<SubscriberDatabaseName>].[sys].[tables]

    • From subscriber database, test connection to Dawiso:

      SELECT COUNT(*) FROM [<DawisoLinkedServerName>].[<DawisoDatabaseName>].[sys].[tables]

  2. Create Replication Views -> If you also want to replicate tables that are not part of standardized replication you need to create views in the Dawiso database for each table you want to replicate. These views must follow specific naming conventions:

    • Schema: All views must be created in the “repl” schema
    • Naming: Views must be named “v_SNAP_dbo_” (currently only dbo schema tables are supported)
    • Primary Key: Views must include the same primary key columns as the source table (other columns could vary, there is no option to add more column)

    • Configure Subscriber Settings -> Add the replication configuration to ENV_Configuration table in the Dawiso database:

      • SubscriberServer: Linked server name for subscriber server (as seen from Dawiso) -> If both databases are on the same server please insert ”.”
      • SubscriberDatabase: Name of the subscriber database
      • PublisherServer: Linked server name for Dawiso server (as seen from subscriber) -> If both databases are on the same server please insert ”.”
      • PublisherDatabase: Name of the Dawiso database
      • CronExpression: Schedule for replication jobs (when and how often to run)
      INSERT INTO ENV_Configuration SELECT 10, 'metahub.configuration', '{"SubscriberServer":"<SubscriberLinkedServerName>","SubscriberDatabase":"<SubscriberDatabaseName>","PublisherServer":"< DawisoLinkedServerName>","PublisherDatabase":"<DawisoDatabaseName>","CronExpression":"5 * *"}', 0, 1, 'Initial Replication Configuration'

    • Initialize Replication -> Run the synchronization configuration procedure on the Dawiso database:

      EXEC [repl].[p_SYNC_Configuration]
      • This procedure will automatically set up change tracking, register your views as replication articles, create corresponding tables in subscriber, and start copying data.

    • Monitor Initial Data Load -> The initial setup happens in phases. Everything except data copying will be quick - usually under a minute. Data copying takes longer depending on the amount of data and network speed. The data is copied as of the timestamp when you ran the procedure. Any changes that happen during the initial load won’t be copied immediately, but will be picked up by the replication cycle after the initial load completes.

    • Verify Success -> Check that the installation completed successfully:

      • You should see: “NO CHANGES DETECTED!” or “SUCCESS: REPLICATION FINISHED WITH NO ERRORS!” If you see any error messages, check the full log for details.
      SELECT TOP 1 [Description] FROM [repl].[LogItem] ORDER BY [LogItem_ID] DESC

    • Ongoing Operation -> Once setup is complete, replication will run automatically according to the cron pattern you specified in the configuration.

      • For technical assistance with installation or troubleshooting, contact Dawiso support with your specific server configuration and any error messages you encounter.