Setting Up iBase database replication in SQL Server

Set up iBase database replication in SQL Server. Ensure that the environment is correctly prepared.

Publications and subscriptions for entity and link data, security data, and audit data can be created in any order:
Data type iBase file SQL Server database
Security data <database name>.ids <database_name>_Sec
Entity and link data <database name>.idb <database_name>
Audit data — <database_name>_Log
Note: In database names that are derived from iBase file names, characters outside the range of A– Z, a– z, 0– 9, and space are converted to underscores. An underscore is also appended to the database name if the iBase file name consists of a single word.

Typically security data is configured first and the audit data is configured last.

Before you can initialize a subscription, you must to transfer an initial snapshot of data to each Subscriber, and it is possible that the entity and link data is too large to download.

If you intend to apply the initial snapshot for the entity and link database over a communications link, then follow the steps in Configuring Subscribers. However, if the entity and link database is too large for this, follow the steps in Applying the snapshot manually using removable media.

Before any databases are created

Before the iBase administrators create any new iBase databases, you might want to predefine the security for these databases by restricting permissions to the Public role for the Model database (which is the template for new user databases). For details, see the Administration Center document Managing Access Control. The information in this document applies to all types of iBase database.

You should also agree a database naming convention with the iBase administrator. The database name must not exceed 119 characters.

Note: All servers, which are to be configured for merge replication must be set to the same time.

Configuring the Distributor and Publisher

  1. Enable the server that you are using as the Distributor and Publisher for replication. If you want to create push subscriptions or named pull subscriptions, also enable the servers that you are using as Subscribers.

  2. Configure the Distributor.

  3. At the Publisher, create publications for the security data, entity and link data, and optionally the audit data.

    For more information, see

  4. Back up the replicated databases, scripts, and appropriate system databases. See Backing Up and Restoring Replicated Databases for details.

    Note: The iBase administrator must to set up the databases at the Publisher before you can configure replication. Details are given in each section.

Configuring Subscribers

Follow these steps if you intend to initialize the subscriptions by applying the initial snapshot over your communications link:

  1. Create a subscription to the publication that contain the:
  2. Set up the Merge Agents to run at an appropriate interval, for example 1 second for the entity and link data. If the Subscriber is to be read-only, configure the Merge Agents to prevent uploads to the Publisher.
  3. Back up the replicated databases, scripts, and appropriate system databases. See Backing Up and Restoring Replicated Databases for details.

Applying the snapshot manually using removable media

Follow these steps if you cannot apply the initial snapshot of the entity and link data over a communications link:
  1. At the Publisher, perform a full backup of the replicated, publication database. Distribute the backup file to the subscriber sites.
  2. At each Subscriber, restore the publication database over the empty subscription database.
  3. Create a subscription and then synchronize it with the Publisher.
  4. Set up the Merge Agent for each subscription to run continuously at a 1 second interval. If a Subscriber is to be read-only, configure the Merge Agents to prevent uploads to the Publisher.
  5. Back up the replicated databases, scripts, and appropriate system databases. See Backing Up and Restoring Replicated Databases for details.