0% found this document useful (0 votes)
3 views

Lecture 3 Database Architecture and Data Independence

The document discusses database architecture, emphasizing the importance of standardization for ease of development and integration. It outlines the ANSI three-schema architecture, which includes external, conceptual, and internal schemas, facilitating data organization and user-specific views. Additionally, it highlights the concept of data independence, allowing changes in storage structure without affecting application programs.

Uploaded by

inshaaltariq774
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views

Lecture 3 Database Architecture and Data Independence

The document discusses database architecture, emphasizing the importance of standardization for ease of development and integration. It outlines the ANSI three-schema architecture, which includes external, conceptual, and internal schemas, facilitating data organization and user-specific views. Additionally, it highlights the concept of data independence, allowing changes in storage structure without affecting application programs.

Uploaded by

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

DATABASE Lecture

3
ARCHITECTURE Prepared by:Rabbia
Basharat
DATABASE
ARCHITECTURE
Database Architecture
o Standardization of database systems is very beneficent in terms of
future growth, because once a system is defined to follow a
specific standard, it provides us the ease of use in a number of
aspects
o First, it is easier to develop, because the standards which are already
define will be used for developing the system
o Secondly, if any organization wants to create an application
software that will provide additional support to the system,
it will be an easier task for them to develop such system and
integrate them into existing database applications
o Database architecture refers to the design and structure of a
database system
o It involves determining the best way to organize, store, and retrieve
data
DATABASE
o ARCHITECTURE
It plays a crucial role in ensuring the efficiency, scalability, and
reliability of a database system, and can have a significant impact
on the overall performance of the applications that rely on the
database
o Database architecture proposed by ANSI SPARK in 1978, known as
ANSI three- schema architecture, is being used worldwide and
is the only most popular agreed upon standard for
database systems

Schema
A schema refers to the structure or organization of a database or
a structured
document. It can define the types of data that can be stored, the
relationships between data elements, and the constraints or rules
that govern the data. A schema acts as a blueprint or template
for data storage, ensuring consistency and integrity in the database
or document.
DATABASE
ARCHITECTURE
Three-level Schema Architecture for Database Development
o Three level schema architecture define the data when using database
o It separate users view from the physical representation because
different users look the same data with different views
o The users of each level are different and interact with data on their
own level
o Also, this three level schema provide the facility to stored the
data in single format but can provide multiple view to the users
o Sometimes we need to make a changes in data format:
 change at user level
 change in stored location (practically stored)
o So by splitting these level, it is easy to make these changes
DATABASE
ARCHITECTURE

Three-level Schema
Architecture
DATABASE
o ARCHITECTURE
The three schemas as defined by ANSI are as
follows:
1. External Schema
The external schema, also known as the
user schema
represents or viewschema,
the database's interface with the users or applications
 It defines how the data is presented or viewed by different user
groups or specific applications
 One organization having different groups of users and each group
may have different views of database according to their
need and according to their job nature
 The external schema focuses on the specific data needs of each
user or group or application
DATABASE
ARCHITECTURE
DATABASE
ARCHITECTURE
2. Conceptual Schema
 The conceptual schema logical structure
represents of the the
organization overall
entire database and
 It describes the relationships between different
entities anddefines the integrity constraints that ensure
data accuracy and consistency
 Here all entities, attributes, and their relationship are
representation
 The conceptual schema provides an abstract view of the
database that is independent of any specific physical storage
considerations
 It contains semantic information's about the
datameaning, security and integrity information
DATABASE
ARCHITECTURE
DATABASE
ARCHITECTURE
3. Internal Schema
 The internal schema consists of two separate schemas, a logical
schema and a physical schema
 The logical schema is the representation of
management
data for technology
a e.g.ofrelational data
type
 It defines the storage structures, access methods, indexing
techniques, and other physical implementation details
 It is more concern with DBMS
 The physical schema represents how the
data is physically stored and organized in the
underlying storage systems or devices
 It may encompass aspects like data storage
format (e.g., file formats), partitioning strategies,
storage devices, and access methods
 It is more concern with the underlying Operating System
DATABASE
oARCHITECTURE
The representation of
data
in binary form which
stored on disc is
is
responsibility the
of the OS
o Binary form of data on
disc
would be stored by
OS according to the
specified direction by
DBMS
DATABASE
ARCHITECTURE
Inter-schema Mapping
o The mechanism through which the records or data at one level is
related to the changed format of the same data at another level is
known as mapping
o It also part of 3-level architecture
o We have two types of mapping
1.External-conceptual mapping
Specifies mapping between objects in the external view to
those in the logical model
2.Conceptual-internal mapping
Specifies mapping between objects in the logical model to
those in the physical model-data independence
DATABASE
ARCHITECTURE
DATA Lecture
3
INDEPENDENCE Section-II
Prepared by:Rabbia
Basharat
DATA
INDEPENDENCE
Data Independence
o Data independence is a big advantage of three level architecture
o It is the immunity of applications to change in storage structure
and access strategy
o Application programs will not effect when there is any change made
by DBMS in storage structure or access strategy
o Changes in lower level do not effect the upper level
o Data Independence has two main types:
1. Logical data independence
2. Physical data independence
DATA
1.INDEPENDENCE
Įogical data independence
o Logical data independence refers to the independence of the
external view or application program from logical schema or
conceptual schema of the database
o It allows us to make changes to the structure of the database (such
as adding or modifying columns, relationships or files) without
requiring changes to the application programs, queries, or
reports that use the database
o In other words, we can change how data is organized and related at
the logical level without affecting how users interact with the
data

Deleting attribute or file at conceptual level


will create problem at external level
DATA
2.INDEPENDENCE
Physical data independence
o Physical data independence refers to the independence of the
logical schema from the way data is stored and accessed at the
lowest level
o It allows to make changes to the physical storage mechanisms, such
as storage devices, file organization, indexing methods,
reorganizing the file structure or data compression
techniques, without affecting the logical or conceptual schema
o This means that you can optimize the performance and storage
efficiency
Data of the
independence database
an essential without
concept disrupting
in database the as
design logical
structure or user interactions
is
promotes it
scalability, and ease of maintenance. It
flexibility, allows the database structure or storage
developers to disrupting
needed without mechanisms as
the applications relying on the
data.
modify
THANK
YOU

You might also like