Consider a scenario where you organization needs to have databases at different locations globally so that users from that location can use that database in their application. This would drastically reduce the network traffic and the time taken to download information from the database. To apply this concept you should be using a distributed database.

______________________________________________________________________________


______________________________________________________________________________

When we mean distributed database we say that all the inputs to a particular database from any location should be replicated in the other databases as soon as possible. Not only inputs but also deletions to the databases should be reflected. In short, any change done to a database must be applied to all the other databases globally. Then only, all the users will be seeing the same data in their application.

Managing such distributed databases from a single location is a tedious task without a proper application to look after that. There comes the Distributed Database Management. Tools for distributed database management allow you to manage the entire database from a central location as if you have all the databases in your system. This enables the database administrator to easily work on the different databases just like switch to different folders in a windows explorer.

The tool for distributed database management sits between the application and the databases. So that the queries are routed to the appropriate database and the inserts are reflected in all the databases. This also helps in distributed transaction control. An object oriented schema is used to achieve this. An approach called the containment approach is used in optimizing the interfaces used for working on the data. This addresses the needs to switch offices and nodes. Keeping these points in mind you can go for a distributed database management if you business needs it and if your business is spread globally.