Question:
what is database replication?
Sharat Laishram
2013-10-09 22:27:41 UTC
what is database replication
Six answers:
Markandrew
2013-10-09 22:38:16 UTC
it is defined as electronic copying of data from a database in one or more servers to another database, so that same information is shared to all users



this can also be called distributed database where a user can access data without interfering others' work



its done in 3 ways



snapshot : data from one server is copied to another server or database or even same server



merging : data from two or more databases is merged into one and provided



transactional : a initial copy of database if provided to the users and then periodic updates are updated
Damian
2013-10-11 05:19:26 UTC
Database replication is the frequent electronic copying data from a database in one computer or server to a database in another so that all users share the same level of information. The result is a distributed database in which users can access data relevant to their tasks without interfering with the work of others. The implementation of database replication for the purpose of eliminating data ambiguity or inconsistency among users is known as normalization.



Database replication can be done in at least three different ways:



Snapshot replication: Data on one server is simply copied to another server, or to another database on the same server.

Merging replication: Data from two or more databases is combined into a single database.

Transactional replication: Users receive full initial copies of the database and then receive periodic updates as data changes.
Zazila Lai
2013-10-10 07:48:43 UTC
Database replication can be used on many database management systems, usually with a master/slave relationship between the original and the copies. The master logs the updates, which then ripple through to the slaves. The slave outputs a message stating that it has received the update successfully, thus allowing the sending (and potentially re-sending until successfully applied) of subsequent updates.



Multi-master replication, where updates can be submitted to any database node, and then ripple through to other servers, is often desired, but introduces substantially increased costs and complexity which may make it impractical in some situations. The most common challenge that exists in multi-master replication is transactional conflict prevention or resolution. Most synchronous or eager replication solutions do conflict prevention, while asynchronous solutions have to do conflict resolution. For instance, if a record is changed on two nodes simultaneously, an eager replication system would detect the conflict before confirming the commit and abort one of the transactions. A lazy replication system would allow both transactions to commit and run a conflict resolution during resynchronization. The resolution of such a conflict may be based on a timestamp of the transaction, on the hierarchy of the origin nodes or on much more complex logic, which decides consistently on all nodes.



Database replication becomes difficult when it scales up. Usually, the scale up goes with two dimensions, horizontal and vertical: horizontal scale-up has more data replicas, vertical scale-up has data replicas located further away in distance. Problems raised by horizontal scale-up can be alleviated by a multi-layer multi-view access protocol. Vertical scale-up causes fewer problems in that internet reliability and performance are improving.



When data is replicated between database servers, so that the information remains consistent throughout the database system and users cannot tell or even know which server in the DBMS they are using, the system is said to exhibit replication transparency.
Ashu
2013-10-10 06:31:31 UTC
The process of creating and managing duplicate versions of a database.



Replication not only copies a database but also synchronizes a set of replicas so that changes made to one replica are reflected in all the others.



The beauty of replication is that it enables many users to work with their own local copy of a database but have the database updated as if they were working on a single, centralized database. For database applications where users are geographically widely distributed, replication is often the most efficient method of database access.
ritesh
2013-10-11 05:01:44 UTC
The process of creating and managing duplicate versions of a database.
?
2013-10-10 05:30:04 UTC
Database Replication means it replicates the data from one Db to another DB.



If you want the training on DB replication check this site( http://www.mysqldbatraininghyd.com/)



Thanks,

Sukanya juhaaaaa.


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...