Replicating and synchronizing databases
iBase database replication is the process of automatically distributing copies of iBase data and database objects between SQL Server instances in different locations and keeping this data synchronized. The data is copied by use of SQL Server merge replication, using the standard tools provided in SQL Server. iBase database replication provides more tools to manage the iBase database. All servers that are involved in replication must use the same SQL Server version.
In iBase database replication, one of the iBase database servers is configured as the Publisher, and empty iBase databases are created at the other locations. To start replication, the SQL Server administrator either configures a subscription that downloads a snapshot of the data over the communications link or transfers the data on removable media using a backup file.
Owing to the complexity of SQL Server replication, the users who configure and maintain the underlying SQL Server databases require appropriate SQL Server training. Analysts do not require any additional skills to operate iBase within a replicated environment. Senior analysts with responsibility for operations such as merging, batch editing and deleting, restoring, and purging, and reviewing conflicts require an understanding of the replication environment.
What does iBase database replication contain?
- Conflict Viewer dialog - for reviewing the data conflicts that might occur when two users change the same record within the same replication cycle. Conflicts are reviewed on a record by record basis at the publisher site.
- File Manager dialog for uploading files into one database for replication to the databases at other sites. Files might be a database template, audit archive files, and so on.
- Update Database Schema dialog for applying changes to the database design.
- Status report to show whether replication is configured in SQL Server.