Mappings between levels and data independence, Database Management System

Mappings between Levels and Data Independence

The 3 levels of abstraction in the database do not exist separately of each other. There must be some correspondence, or mapping, among the levels. There are two types of mappings: the internal / conceptual mapping and the conceptual / external mapping.

The internal / conceptual mapping lies among the internal and conceptual levels, and tells the correspondence among the records and the data structures of the internal view and fields of the conceptual view and the files. If the structure of the stored database is changed, then the internal / conceptual mapping must also be changed accordingly so that the view from the conceptual level remains similar. It is this mapping that gives physical data independence for the database. For instance, we may modify the internal view of student relation by breaking the student file into two files, one containing enrolment, address and name and other containing enrolment, programme. Therefore, the mapping will make sure that the conceptual view is restored as original. The storage decision is firstly taken for optimisation purposes.

The external/conceptual view lies between the external and conceptual levels, and tells the correspondence between a particular external view and the conceptual view. Though these two levels are same, some elements discover in a particular external view may be different from the conceptual view. For example, various fields can be combined into a single (virtual) field, which can also have dissimilar names from the original fields. If the structure of the database at the conceptual level is changed, then the conceptual / external mapping must change accordingly so that the view from the external level remains constant. It is this mapping that gives logical data independence for the database. For instance, we may change the student relation to have more fields at conceptual level, yet this will never change the two user views at all.

It is also doable to have another mapping, where one external view is show in terms of other external views (this could be known as external/external mapping). This is useful if various external views are closely related to one another, as it permits you to avoid mapping each of the same external views directly to the conceptual level.

Posted Date: 3/5/2013 5:02:49 AM | Location : United States







Related Discussions:- Mappings between levels and data independence, Assignment Help, Ask Question on Mappings between levels and data independence, Get Answer, Expert's Help, Mappings between levels and data independence Discussions

Write discussion on Mappings between levels and data independence
Your posts are moderated
Related Questions
Scenario 1: Power goes out after the first instruction. What happens?

Normal 0 false false false EN-US X-NONE X-NONE

Equi Join: A join in which the joining condition is based on equality among values in the common columns. Common columns show (redundantly) in the result table. Let us Consider th

Load sample data into the database tables design and test queries to return the following information • All rows and columns for employees • All rows and columns for customers •

What is a dataset? A dataset is an in-memory database that is disconnected from any regular database, but has all the significant characteristics of a regular database. Dataset

define normalisation and functional dependency

For each 1: n relationship type R involving two entities E1 and E2, we recognize the entity type (say E1) at the n-side of the relationship type R and contain primary key of the en

A relationship set is a set of relationships of the similar type. For example, let consider the relationship among two entities sets course and student. Collection of all the in

We have a new website where I need someone to 1: Inhabit the back end with all the recruitment agencies in the UK. I require someone who is not manually going to do this, but who w

For this application, we will consider IBM DB2 catalog data (i.e., metadata) for IBM's enterprise-class servers running the z/OS (formerly OS/390 or MVS) operating system.  One of