Distributed database

A distributed database is a <a href="/facts/Database/VYcpkevb">database</a> in which data is stored across different physical locations. It may be stored in multiple <a href="/facts/Computers/SQe1aK05">computers</a> located in the same physical location (e.g. a data centre); or maybe dispersed over a <a href="/facts/Computer_network/3w5RM99p">network</a> of interconnected computers. Unlike <a href="/facts/Parallel_computing/nQzcpzQt">parallel systems</a>, in which the processors are tightly coupled and constitute a single database system, a distributed database system consists of loosely coupled sites that share no physical components.
System administrators can distribute collections of data (e.g. in a database) across multiple physical locations. A distributed database can reside on organised <a href="/facts/Network_servers/dEaYFD7r">network servers</a> or <a href="/facts/Blockchain_(database)/8H43GgWy">decentralised independent computers</a> on the <a href="/facts/Internet/Xw1rVvJU">Internet</a>, on corporate <a href="/facts/Intranets/0KfpheJH">intranets</a> or <a href="/facts/Extranets/8kHaVSEr">extranets</a>, or on other organisation <a href="/facts/Computer_network/3w5RM99p">networks</a>. Because distributed databases store data across multiple computers, distributed databases may improve performance at <a href="/facts/End-user/7IM9qu7N">end-user</a> worksites by allowing transactions to be processed on many machines, instead of being limited to one.
Two processes ensure that the distributed databases remain up-to-date and current: <a href="/facts/Replication_(computing)/QIaooMjL">replication</a> and <a href="/facts/Data_transmission/1yAhaANd">duplication</a>.

<ol><li>Replication involves using specialized software that looks for changes in the distributive database. Once the changes have been identified, the replication process makes all the databases look the same. The replication process can be complex and time-consuming, depending on the size and number of the distributed databases. This process can also require much time and computer resources.</li>
<li>Duplication, on the other hand, has less complexity. It identifies one database as a <a href="/facts/Master%2fslave_(technology)/8APze020">master</a> and then duplicates that database. The duplication process is normally done at a set time after hours. This is to ensure that each distributed location has the same data. In the duplication process, users may change only the master database. This ensures that local data will not be overwritten.</li></ol>
Both replication and duplication can keep the data current in all distributive locations.
Besides distributed database replication and fragmentation, there are many other distributed database design technologies. For example, local autonomy, synchronous, and asynchronous distributed database technologies. The implementation of these technologies can and do depend on the needs of the business and the sensitivity/<a href="/facts/Confidentiality/JFMubsQm">confidentiality</a> of the data stored in the database and the price the business is willing to spend on ensuring <a href="/facts/Data_security/7E5dIy7G">data security</a>, <a href="/facts/Data_consistency/WUxG1d41">consistency</a> and <a href="/facts/Data_integrity/g3XGbKIH">integrity</a>.
When discussing access to distributed databases, <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a> favors the term distributed query, which it defines in protocol-specific manner as "[a]ny SELECT, INSERT, UPDATE, or DELETE statement that references tables and rowsets from one or more external OLE DB data sources".
<a href="/facts/Oracle_Database/FHv5g732">Oracle</a> provides a more language-centric view in which distributed queries and <a href="/facts/Distributed_transaction/CjCS2nhu">distributed transactions</a> form part of distributed SQL.

Distributed database open-in-new

Distributed database