Transparencies in DBMs stands for separation of high level semantics of system from low level implementation issues. High level semantics stands for end point user and low level concerns with complicated hardware implementation of data.

Types of Transparencies

1. NETWORK / LOCATION Transparency:-

   DDMs users should not be concerned about the type of DBMs they are using. The network should not be visible to the user. Thus to provide new transparency, we need following statements:-

2. The query language that will be used should not include any location specification. In this way location transparency can be achieved.
3. The data that is stored in a relation should not contain any location specific name so that naming transparency can be assured.
4. Every data base object must have a system wide unique name.
5. The location information can be found using data dictionary.

6. Using aliases, we can move database objects transparently.

7. Replication Transparency:-

   It states that the replicas are created should be controlled by system, not by user. The user should not have any doubt whether the fetched data is coming from a replicated copy of relation or from actual copy of relation. To achieve replication transparency, concurrency control protocol needs to be used which assures that update of data taking place in one copy should also be updated in other copies. In this way, transparencies regarding replicas of data can be maintained.

8. Fragmentation Transparency:-

   It states that fragments are created to store the data in distributed manner should remain transparent and all data management work required to control fragments should be done by system, not by user. In this task, when a user uses a query, global query is distributed in many sites to fetch data for fragments and this data is put together at end to generate result. The system ensures that the total procedure of query decomposition and re-composition should be transparent to the user.