Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
20 views

Module 1

The document discusses database systems and their components. It covers characteristics of databases, categories of users, advantages of DBMS, data models and schemas. It also describes the three levels of schema architecture - internal, conceptual and external schemas.

Uploaded by

nagraj1312003
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
20 views

Module 1

The document discusses database systems and their components. It covers characteristics of databases, categories of users, advantages of DBMS, data models and schemas. It also describes the three levels of schema architecture - internal, conceptual and external schemas.

Uploaded by

nagraj1312003
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Module 1

1) A simplified database system environment .

characteristics of the database approach in concise points:

1. Selfdescribing nature through metadata.


2. Insulation between programs and data via a data manipulation language (DML).
3. Data abstraction hides complexity for users.
4. Multiple views of data without duplication.
5. Concurrent data access for multiple users.
6. Support for multiuser transaction processing.
7. Data integrity and security mechanisms in place.

categories of end users summarized into four points:

1. Casual end users: Middle or highlevel managers who occasionally access the
database for varied information using a sophisticated query language.

2. Naive or parametric end users: These users form a sizable portion of the user base
and perform standard queries and updates using predefined transactions. Examples
include bank tellers, reservation agents, and shipping clerks.
3. Sophisticated end users: Engineers, scientists, and business analysts who deeply
understand the database management system (DBMS) to implement complex
applications tailored to their specific requirements.

4. Standalone users: Individuals who maintain personal databases using specialized


software packages for personal use, such as tax programs. They create and manage
their own internal databases for specific purposes.

the advantages of using the database management system (DBMS)

1. Controlling Redundancy: DBMS eliminates data redundancy, reducing wasted


storage space and effort, while ensuring consistency. Redundancy, such as indexes,
can enhance query performance.

2. Restricting Unauthorized Access: DBMS provides a robust security and


authorization subsystem to prevent unauthorized access, enforced automatically by the
system.

3. Persistent Storage for Program Objects: Objectoriented database systems


facilitate the storage of complex runtime objects, ensuring their persistence beyond
program termination.

4. Efficient Query Processing: DBMS provides optimized storage structures and


search techniques for efficient query execution, enhancing performance.

5. Backup and Recovery: DBMS offers backup and recovery facilities to mitigate
hardware or software failures, ensuring data integrity and continuity of operations.

6. Multiple User Interfaces: DBMS supports various user interfaces tailored to


different user needs, including query languages, programming interfaces, forms, and
menudriven interfaces.

7. Representation of Complex Relationships: DBMS can represent and manage


complex relationships among data efficiently, enabling easy retrieval and updating of
related data.

8. Enforcing Integrity Constraints: DBMS enforces integrity constraints such as


data types, referential integrity, and uniqueness, ensuring data consistency and
accuracy.

9. Inferencing and Actions Via Rules: In deductive and active database systems,
declarative rules allow for inference of new data and initiation of actions
automatically, reducing the need for custom application programs.
categories of data models and schemas:

1. Highlevel or Conceptual Data Models: These models provide concepts close to


how users perceive data, using entities, attributes, and relationships. Entities represent
realworld objects, attributes describe properties of entities, and relationships represent
associations between entities. Examples include the EntityRelationship Model (ER
Model).

2. Lowlevel or Physical Data Models: These models describe how data is stored on
computer storage media, such as magnetic disks. They are designed for computer
specialists and focus on technical details of data storage.

3. Representational (or Implementation) Data Models: These models offer


concepts understandable to end users but are not too distant from the computer storage
organization. They bridge the gap between highlevel and lowlevel models, hiding
many storage details while being implementable directly on computer systems.

Schemas: A database schema is the description of a database specified during


database design. It encompasses the structure, constraints, and relationships of the data
in the database. It defines the logical and physical organization of the database,
including tables, columns, keys, and relationships. Schemas provide a blueprint for
creating and managing databases efficiently.

Three schema architecture


1. Internal Level:
Schema: Internal Schema
Description: Describes the physical storage structure of the database using a physical
data model.
Details: Includes complete details of data storage and access paths, focusing on the
technical aspects of how data is stored and accessed.

2. Conceptual Level:
Schema: Conceptual Schema
Description: Describes the structure of the entire database for a community of users.
Details: Hides the physical storage structures, focusing on entities, data types,
relationships, user operations, and constraints. It's implemented using a
representational data model, often based on a highlevel data model.

3. External or View Level:


Schema: External Schemas or User Views
Description: Includes multiple external schemas, each representing a specific view of
the database for a particular user group.
Details: Describes only the part of the database relevant to a user group, hiding the
rest. Each external schema is typically implemented using a representational data
model, possibly based on a highlevel data model for external schema design.

You might also like