Scribd
Upload
9 views12 pages

UNIT-I Chapter-2

Chapter 2 covers database system concepts and architecture, focusing on data models, schemas, and instances. It explains the three-schema architecture, which includes internal, conceptual, and external levels, and discusses data independence, emphasizing logical and physical data independence. Additionally, it outlines various database languages and interfaces, as well as the tools and utilities available in the database system environment.

Uploaded by

mvbvijay935
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
9 views12 pages

UNIT-I Chapter-2

Chapter 2 covers database system concepts and architecture, focusing on data models, schemas, and instances. It explains the three-schema architecture, which includes internal, conceptual, and external levels, and discusses data independence, emphasizing logical and physical data independence. Additionally, it outlines various database languages and interfaces, as well as the tools and utilities available in the database system environment.

Uploaded by

mvbvijay935
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Chapter-2

Database System Concepts &


Architecture
Concepts:
1. Data Models, Schemas and Instances
2. Three- Schema Architecture and Data Independence
3. Database Languages and Interfaces
4. The Database System Environment
Data Models, Schemas and Instances
Data Abstraction:
Data abstraction generally refers to the suppression of details of data organization and
storage, and the highlighting of the essential features for an improved understanding of data.
One of the main characteristics of the database approach is to support data abstraction so
that different users can perceive data at their preferred level of detail.
Data Model:
A data model—a collection of concepts that can be used to describe the structure of a
database—provides the necessary means to achieve this abstraction.
Categories Of Data Models:
1. High Level or Conceptual Data Model(provides concepts that are close to the way users
perceive data)
2. Low level or Physical Data Model(provides concepts that describe the details of how
data is stored on the computer storage media eg magnetic disks)
3. Representational or Implementation Data Model(provides concepts that may be easily
understood by end users)
4. Entity Relationship Model(Entity(realm world object or concept),
relationship(association among entities), attribute(describes an entity))
5. Relational Model(data stored in the form of table)
6. Hierarchical Model(data stored in the form of tree)
7. Network Model(Data stored in the form of Linked list)
8. Self describing data models(combines the description of the data with data values
themselves)
Schemas, Instances, and Database State
• The description of a database is called the database schema.
Three-Schema Architecture:
Internal Level:
The internal level has an internal schema, which describes the physical storage structure of
the database. The internal schema uses a physical data model and describes the complete
details of data storage and access paths for the database.
Conceptual Level:
The conceptual level has a conceptual schema, which describes the structure of the whole
database for a community of users. The conceptual schema hides the details of physical
storage structures and concentrates on describing entities, data types, relationships, user
operations, and constraints. Usually, a representational data model is used to describe the
conceptual schema when a database system is implemented. This implementation conceptual
schema is often based on a conceptual schema design in a high-level data model.
External Level:
The external or view level includes a number of external schemas or user views. Each external
schema describes the part of the database that a particular user group is interested in and
hides the rest of the database from that user group. As in the previous level, each external
schema is typically implemented using a representational data model, possibly based on an
external schema design in a high-level conceptual data model.
Data Independence:
• The three-schema architecture can be used to further explain the concept of data
independence, which can be defined as the capacity to change the schema at one level of
a database system without having to change the schema at the next higher level. We can
define two types of data independence:
1. Logical Data Independence
2. Physical Data Independence
Logical Data Independence:
Logical data independence is the capacity to change the conceptual schema without having to
change external schemas or application programs. We may change the conceptual schema to
expand the database (by adding a record type or data item), to change constraints, or to
reduce the database (by removing a record type or data item). In the last case, external
schemas that refer only to the remaining data should not be affected.
Physical Data Independence:
Physical Data Independence is the capacity to change the internal schema without having to
change the conceptual schema. Hence, the external schemas need not be changed as well.
Changes to the internal schema may be needed because some physical files were reorganized
—for example, by creating additional access structures—to improve the performance of
retrieval or update.
Database Languages and Interfaces
DBMS Languages:
1. DDL(Data Definition Language(create, alter, drop and truncate))
2. DML(Data Manipulation Language(insert, update and delete))
3. DCL(Data Control Language(grant and revoke))
4. TCL(Transaction Control Language(commit, rollback, savepoint))
5. SDL(Storage Definition Language)
6. VDL(View Definition Language)

DBMS Interfaces:
7. Menu based Interfaces for Web Clients or Browsing
8. Apps for Mobile Devices
9. Form based Interfaces
10. Graphical user Interface
11. Natural language Interfaces
12. Keyword based Database Search
13. Speech Input and Output
14. Interfaces for Parametric Users(bank tellers)
15. Interfaces for the DBA
The Database System Environment
Database System Utilities:
Tools, Application Environments, and Communications Facilities:
• Other tools are often available to database designers, users, and the DBMS. CASE tools12
are used in the design phase of database systems. Another tool that can be quite useful in
large organizations is an expanded data dictionary (or data repository) system.
• In addition to storing catalog information about schemas and constraints, the data
dictionary stores other information, such as design decisions, usage standards, application
program descriptions, and user information. Such a system is also called an information
repository.
• This information can be accessed directly by users or the DBA when needed. A data
dictionary utility is similar to the DBMS catalog, but it includes a wider variety of
information and is accessed mainly by users rather than by the DBMS software. Application
development environments, such as PowerBuilder (Sybase) or JBuilder (Borland), have
been quite popular.
• These systems provide an environment for developing database applications and include
facilities that help in many facets of database systems, including database design, GUI
development, querying and updating, and application program development. The DBMS
also needs to interface with communications software, whose function is to allow users at
locations remote from the database system site to access the database through computer
terminals, workstations, or personal computers.
• These are connected to the database site through data communications hardware such as
Internet routers, phone lines, long-haul networks, local networks, or satellite
communication devices. Many commercial database systems have communication
packages that work with the DBMS.
• The integrated DBMS and data communications system is called a DB/DC system. In
addition, some distributed DBMSs are physically distributed over multiple machines. In this
case, communications networks are needed to connect the machines. These are often
local area networks (LANs), but they can also be other types of networks.

You might also like