Functionality of DDBMS is attractive. However, implementations of required protocols and algorithms are complex and can cause problems that may outweigh advantages.
Alternative and more simplify approach to data distribution is provided by a replication server.
Every major database vendor has replication solution.
Database Replication is the process of copying and maintaining database objects, such as relations, in multiple databases that make up a distributed database system.
Changes applied at one site are captured and stored locally before being forwarded and applied at each of the remote locations.
Replication uses Distributed database technology to share data between multiple sites, but a distributed database and replicated database are not the same.
In a distributed database, data is available at many locations, but a particular relation resides at only one location whereas Replication means that the same data is available at many sites.
If Regimmanuel Estate had a distributed database then the relation PropertyforRent describing the properties for rent would be found on only one database server, such as the server in Accra, and not on the server in Kumasi and Takoradi servers.
Replication means the same data is available at multiple locations. Therefore if Regimmanuel Estates had a replicated database then the
PropertyFor Rent could be available on the Accra, Kumasi and Takoradi servers.
Replication object is a database object such as a relation, index, view, procedure, or function existing on multiple servers in a distributed database system.
In a replication environment, any updates made to a replication object at one site are applied to the copies at all other sites.
A master site controls a replication group and the objects in that group.
This is achieved by maintaining a complete copy of all objects in a replication group and by propagating any changes to a replication group to any slave sites.
For a replication environment with many master sites, all of those sites communicate directly with one another to continually propagate data changes in the replication group.
Synchronous – updates to replicated data are part of enclosing transaction.
If one or more sites that hold replicas are unavailable transaction cannot complete.
Large number of messages required to coordinate synchronization.
Asynchronous - target database updated after source database modified. Delay in regaining consistency may range from few seconds to several hours or even days.
Allow asynchronous distribution of changes to individual tables, collections of tables, views, or partitions of tables according to pre-defined schedule.
Common approach for snapshots uses the recovery log, minimizing the extra overhead to the system.
Database that is portable and physically separate from a centralized database server but is capable of communicating with server from remote sites allowing the sharing of corporate data.
0 comments
Post a comment