Why Use Database Replication?
Database replication is the process of copying a database so that two or more copies can exchange updates of data or replicated objects. ... Each copy of the database is called a replica, and each contains a common set of tables, queries, forms, reports, macros, and modules. ...
Each replica is part of a replica set, which contains the Design Master and the other replicas for a database. The Design Master is the only replica where you can make changes to the database’s design and objects. ...
With database replication, you can:
· Share data among offices You can use database replication to create copies of a corporate database to send to each satellite office. ...
· Share data among dispersed users New information that is entered into the database while sales representatives are out of the office can be synchronized anytime the sales representatives establish an electronic link with the corporate network. As part of their workday routine, sales representatives can dial into the network, synchronize the replica, and work on the most current version of the database. ...
See Also For more information on partial replicas, see “Replicating Part of a Database” later in this chapter.
· Make server data accessible If your application doesn’t need to have immediate updates to data, you can use database replication to reduce the network load on your primary server. Introducing a second server with its own copy of the database improves response time. ... Replication requires less centralized administration of the database while offering greater access to centralized data. ... If you make changes to the design of the database, the changes are transmitted during the next synchronization exchange; you don’t have to distribute complete new versions of the software.
· Back up data At first glance, database replication may appear to be very similar to copying a database. However, while replication initially makes a complete copy of the database, thereafter it simply synchronizes that replica’s objects with the original objects at regular intervals. This copy can be used to back up data if the original database is destroyed. Furthermore, users at any replica can continue to access the database during the entire backup process.
Although database replication can solve many of the problems inherent in distributed database processing, it is important to recognize the situations in which replication is less than ideal. You may not want to use replication if:
· There are large numbers of record updates at multiple replicas Applications that require frequent updating of existing records in different replicas are likely to have more record conflicts than applications that simply insert new records into a database.
To link to this page, copy the following code to your site:
All Papers Are For Research And Reference Purposes Only!
You may not turn these papers in as your own! You must cite our web site as your source!
