Sign Up

Have an account?

Sign In

Don't have account,

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.


Have an account?

Sorry, you do not have permission to ask a question, You must login to ask a question.

Need An Account,

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Search
Ask A Question
Home/ Questions/Q 90514
Next
In Process

Mains Answer Writing Latest Questions

Manjit Kumar
  • 1
  • 1
Begginer
Asked: 2024-07-19T23:08:29+05:30 In:

DBMS

  • 1
  • 1

Describe the three-schema architecture. why do we need mapping between schema levels?

question

Related Questions

Leave an answer

You must login to add an answer.

Need An Account,

5 Answers

  1. Vishakha Singh
    Begginer

    The three-schema architecture is a framework used in database systems to separate the database’s physical storage from its conceptual and external representations. This architecture helps manage the complexity of data and promotes data abstraction and independence. The three levels in this architecture are:

    1. Internal Schema (Physical Level):
      • This level describes how data is physically stored in the database. It involves the storage structures, indexing techniques, and file organization methods used to store data efficiently. The internal schema is concerned with performance optimization and efficient data retrieval.
    2. Conceptual Schema (Logical Level):
      • The conceptual schema provides a unified view of the entire database, abstracting away the details of physical storage. It defines the logical structure of the data, including entities, attributes, relationships, constraints, and data types. The conceptual schema represents the database as perceived by the database administrator (DBA) and focuses on the logical organization of data.
    3. External Schema (View Level):
      • The external schema consists of multiple user views, each tailored to meet the specific needs of different users or applications. These views provide a customized perspective of the database, showing only relevant data and hiding other details. External schemas ensure that users interact with the data in a way that is most meaningful to them without needing to understand the underlying complexity.

    Why Do We Need Mapping Between Schema Levels?

    Mapping between schema levels is crucial for several reasons:

    1. Data Abstraction and Independence:
      • Logical Data Independence: The ability to change the conceptual schema without affecting the external schemas or user views. This means that changes in the logical structure, such as adding new entities or attributes, do not impact how users interact with the data.
      • Physical Data Independence: The ability to change the internal schema without affecting the conceptual schema or external schemas. This allows changes in physical storage (e.g., reorganizing files, adding indexes) to optimize performance without altering the logical representation of the data.
    2. Flexibility and Adaptability:
      • Mapping enables the database system to adapt to changing requirements at different levels. For example, new user requirements can be accommodated by modifying or adding external schemas without altering the conceptual schema.
    3. Security and Access Control:
      • External schemas can be designed to provide controlled access to data, ensuring that users only see what they are authorized to see. This separation helps enforce security policies and data privacy.
    4. Consistency and Integrity:
      • Mapping ensures that changes at one level do not lead to inconsistencies at other levels. This maintains data integrity and consistency across the entire database system.
    5. Simplification of Data Management:
      • By separating concerns, the three-schema architecture simplifies data management tasks. Database administrators can focus on optimizing physical storage, while developers and users can work with logical and external views without worrying about underlying complexities.

    In summary, the three-schema architecture and the mappings between schema levels provide a structured approach to managing databases, enhancing flexibility, security, and independence across different layers of data abstraction.

  2. Vaibhav Malekar
    Begginer

    In a DBMS, the three-schema architecture organizes data management effectively:

    1. Conceptual Schema: Acts as the blueprint, defining high-level data structure and relationships without technical details. It describes what data is stored, like having Customers, Orders, and Products tables.
    2. Logical Schema: Provides a detailed layout, specifying how data is organized within tables and their relationships. It defines attributes, data types, and relationships, such as OrderID and CustomerID in the Orders table and its link to the Customers table.
    3. Physical Schema: Focuses on the actual implementation, detailing how data is stored on disks, including file structures and indexing methods for efficient retrieval.

    Mapping ensures each schema level aligns with the others, translating the high-level design into practical implementation and ensuring efficient data storage and retrieval. Without mapping, discrepancies could lead to inefficient data management and errors.

    Example: Imagine your database as a house with three floors: the conceptual, logical, and physical levels. The conceptual schema is like the blueprint of the entire house—it’s a high-level design of what rooms (data) should be where, but it doesn’t detail the materials used. The logical schema is like the detailed architectural plan—it organizes the layout with specific rooms and their functions but still doesn’t address the construction methods. The physical schema is akin to the actual construction—how the rooms are built with concrete and nails.

  3. Sirisha Siri
    Begginer
    This answer was edited.

    The three-schema architecture is a framework for database systems that separates the database into three levels of abstraction: the internal level, the conceptual level, and the external level. This architecture was proposed by the ANSI/X3/SPARC Study Group on Database Management Systems in 1975 and is designed to provide data abstraction and independence.

    Three Levels of Schema Architecture

    Internal Schema (Physical Level):

    • Description: The internal schema defines the physical storage structure of the database. It includes details on how data is stored, indexed, and accessed. This level focuses on the efficiency of data storage and retrieval.
    • Concerns: Storage allocation, file organization, indexing, and data compression.

    Conceptual Schema (Logical Level):

    • Description: The conceptual schema represents the logical structure of the entire database as perceived by the database administrator. It hides the physical storage details and provides a unified view of the data, defining entities, relationships, constraints, and data types.
    • Concerns: Data models, relationships, constraints, and integrity rules.
        • External Schema (View Level):
      • Description: The external schema consists of multiple user views. Each view is a subset of the database tailored to the needs of a particular user or group of users. It provides a way to present data in different formats and structures to different users.
      • Concerns: User-specific views, access control, and data customization.

        Why Mapping Between Schema Levels is Needed

        Mapping between the schema levels is crucial for the following reasons:

        Data Abstraction:

        • Purpose: Data abstraction hides the complexities of the database’s physical storage from users and applications. This allows users to interact with the database without needing to understand its underlying physical structure.
        • Implementation: Mapping translates requests and data from one level to another, providing a seamless interface for users.

        Data Independence:

        • Logical Data Independence: The ability to change the conceptual schema without altering the external schemas or application programs. This ensures that modifications in the logical data structure do not affect how users view the data.
        • Physical Data Independence: The ability to change the internal schema without impacting the conceptual schema. This allows changes in physical storage (like reorganization or optimization) without affecting the logical structure or user views.

        Customization:

        • User-Specific Views: Different users require different views of the data. Mapping allows the creation of customized views tailored to specific needs, enhancing usability and security.
        • Access Control: By defining different external schemas, the system can enforce access control, ensuring users only see the data they are authorized to access.

        Simplification of Database Management:

        • Maintenance: Changes in data structure or storage mechanisms can be managed efficiently. Optimizations at the physical level can be performed without disrupting logical organization or user views.
        • Consistency: Mapping helps maintain data consistency across different levels, ensuring that updates and changes propagate correctly.

          The three-schema architecture is essential for managing data abstraction and independence in database systems. Mapping between the internal, conceptual, and external schemas provides a structured approach to handling the complexity of databases. It ensures that changes at one level do not adversely affect other levels, facilitates customization for different users, and supports efficient and consistent database management.

           

        • Animesh Maity
          Begginer

          The three-schema architecture separates database definition into three levels:

          1. External Schema (Views): Customized views for different users.
          2. Conceptual Schema: Overall logical structure, independent of storage.
          3. Internal Schema: Physical storage details (invisible to users).

          Mappings connect these levels:

          • External to Conceptual: Translates user views into the database’s logical structure.
          • Conceptual to Internal: Translates requests into instructions for physically stored data.

          This layered approach offers benefits:

          • Data Independence: Changes to storage won’t affect user views.
          • Security: Users only see authorized data.
          • Flexibility: New user views can be added easily.

        Resources & Suggestions

        Mains Answer Writing Latest Articles

        On: February 24, 2025

        Daily Answer Writing Practice Questions (24 February 2025)

        The rise of the work-from-home culture has brought about several ethical issues in private organizations. In this context, do you believe it is ethical for an employee to engage in moonlighting? Discuss. (Answer in 150 words) घर से काम करने ...

        On: February 22, 2025 Comments: 0

        Indo-US Relation: Areas of Cooperation & Conflicts

        Key Areas: Defense, technology, trade, energy, and regional cooperation. Key Areas of Cooperation 1. Defense and Security Transition from buyer-seller to co-production and technology sharing. India as a Major Defense Partner (MDP) and inclusion in STA-1. Access to advanced technologies, ...

        On: February 22, 2025 Comments: 0

        भारत-अमेरिका संबंध: सहयोग और संघर्ष के क्षेत्र

        मुख्य विषय: भारत-अमेरिका संबंधों की मजबूती, विशेषकर रक्षा, प्रौद्योगिकी और क्षेत्रीय सहयोग में प्रगति। सहयोग के प्रमुख क्षेत्र 1. रक्षा एवं सुरक्षा सहयोग भारत और अमेरिका के बीच रक्षा संबंधों का विस्तार। प्रमुख रक्षा साझेदार (MDP) का दर्जा और STA-1 ...

        Explore Our Blog