Scribd
Upload
3 views3 pages

Chapter 2 Database

Chapter 2 discusses the 3-tier ANSI-SPARC architecture in Database Management Systems, which includes external, conceptual, and internal levels, each serving distinct user needs and data abstraction. It also explains data independence, highlighting physical and conceptual data independence, and outlines various types of databases such as centralized, personal computer, client/server, distributed, homogeneous, and heterogeneous databases. Each database type has unique characteristics and usage scenarios, catering to different organizational requirements.

Uploaded by

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

Chapter 2 Database

Chapter 2 discusses the 3-tier ANSI-SPARC architecture in Database Management Systems, which includes external, conceptual, and internal levels, each serving distinct user needs and data abstraction. It also explains data independence, highlighting physical and conceptual data independence, and outlines various types of databases such as centralized, personal computer, client/server, distributed, homogeneous, and heterogeneous databases. Each database type has unique characteristics and usage scenarios, catering to different organizational requirements.

Uploaded by

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

Chapter 2: Database Environment

The Three Level ANSI-SPARC Architecture


The 3-tier architecture is a commonly used architectural approach in Database
Management Systems (DBMSs) for the design and development of applications that work
with databases. The 3-tier architecture divides an application’s components into three
tiers or layers. Each layer has its own set of responsibilities.
DBMS 3-Tier architecture divides the complete system into three inter-related but
independent modules as shown below:

External Level:- An external level specifies a view of the data in terms of conceptual
level tables. Each external level view is used to cater to the needs of a particular category
of users. For Example, FACULTY of a university is interested in looking course details of
students, STUDENTS are interested in looking at all details related to academics, accounts,
courses and hostel details as well. So, different views can be generated for different users.
The main focus of external level is data abstraction.
Conceptual Level:- At conceptual level, data is represented in the form of various
database tables. For Example, STUDENT database may contain STUDENT and COURSE
tables which will be visible to users but users are unaware of their storage. Also referred
as logical schema, it describes what kind of data is to be stored in the database.
Internal Level:- At the physical level, the information about the location of database
objects in the data store is kept. Various users of DBMS are unaware of the locations of
these objects. In simple terms, physical level of a database describes how the data is being
stored in secondary storage devices like disks and tapes and also gives insights on
additional storage details.
Data Independence
Data independence means a change of data at one level should not affect another level.
Two types of data independence are present in this architecture:
Physical Data Independence:- Any change in the physical location of tables and indexes
should not affect the conceptual level or external view of data. This data independence is
easy to achieve and implemented by most of the DBMS.
Conceptual Data Independence:- The data at conceptual level schema and external level
schema must be independent. This means a change in conceptual schema should not
affect external schema. e.g.; Adding or deleting attributes of a table should not affect the
user’s view of the table. But this type of independence is difficult to achieve as compared
to physical data independence because the changes in conceptual schema are reflected in
the user’s view.
Types of Databases
Centralized Database:-
A Centralized Database is a type of database that is stored, located as well as maintained
at a single location only. This type of database is modified and managed from that location
itself. This location is thus mainly any database system or a centralized computer system.
The centralized location is accessed via an internet connection (LAN, WAN, etc). This
centralized database is mainly used by institutions or organizations.

Personal Computer Database:- A "personal computer database" refers to a database


designed for single-user access, typically stored on a personal computer and used for simple
data management.

Client/Server Database:- A "client-server database" is a system where data is stored on


a central server and accessed by multiple client computers across a network, allowing many
users to access the data simultaneously.

Distributed Database:- A distributed database is basically a type of database which


consists of multiple databases that are connected with each other and are spread across
different physical locations. The data that is stored in various physical locations can thus
be managed independently of other physical locations. The communication between
databases at different physical locations is thus done by a computer network.
Homogeneous Databases:- Homogeneous databases are characterized by all
participating nodes sharing the same database management System (DBMS) and schema
structure. These databases are designed to offer a unified and consistent view of data
across all nodes.

Heterogeneous Databases:- Contrary to homogeneous databases, heterogeneous


databases allow nodes in a distributed system to use different DBMS software. This
approach provide diverse requirements and facilitates seamless integration between
nodes employing different technologies.

You might also like