Distributed Databases and Fragmentation Independence
Fragmentation independence refers to the ability of end users to store logically related information at different physical locations.
There are two types of fragmentation independence: vertical partitioning and horizontal partitioning.
Horizontal partitioning permits different rows of the same table to be stored at different remote sites. This is commonly done by organizations that maintain several branch offices, each with an identical set of table structures.
Vertical partitioning refers to the ability of a distributed system to fragment information such that the data columns from the same logical tables are maintained across the network. Oracle accomplishes this with Oracle views that hide specific columns and rows in a table.
Definition Of Distributed Databases
There is an ongoing debate over the standard definition of distributed database systems. Vendors have implemented distributed database technology in different manners.
To many database vendors, a distributed database is a geographically distributed system composed entirely of one brand of database products. On the other hand, front end applications vendors define a distributed database as a system distributed architecturally, using a blend of database products and access methods.
Finally, to hardware vendors, a distributed database is a system composed of different databases running on the same hardware platforms.
When an organization is geographically dispersed, it may choose to store its databases
A distributed database is a single logical database that is spread physically across computers in multiple locations that are connected by a data communications network.
I emphasize that a distributed database is truly a database, not a loose collection of files.
The distributed database is still centrally administered as a corporate resource while providing local flexibility and customization.
The network must allow the users to share the data; thus, a user (or program) at location X must be able to access (and perhaps update) data at location Y.
The sites of a distributed system may be spread over a large area (i.e., the United States or the world) or over a small area (i.e., a building or campus).
The computers may range from PCs, large-scale servers or even supercomputers.
A distributed database requires multiple instances of a database management system (or several DBMSs), running at each remote site.
The degree to which these different DBMS instances cooperate, or work in partnership, and whether there is a master site that coordinates requests
involving data from multiple sites distinguish different types of distributed database environments. It is important to distinguish between distributed and decentralized databases.
- on a central database server or
- to distribute them to local servers (or both).