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

1.2 Adc

The document discusses database concepts including database, DBMS, data abstraction, schema and instances, data independence, DDL and DML, and database architecture. It describes different levels of data abstraction including physical, logical, and view levels. It also explains centralized and client-server database architectures.

Uploaded by

Red Ghost
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views

1.2 Adc

The document discusses database concepts including database, DBMS, data abstraction, schema and instances, data independence, DDL and DML, and database architecture. It describes different levels of data abstraction including physical, logical, and view levels. It also explains centralized and client-server database architectures.

Uploaded by

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

CS 820: ADVANCED DATABASE CONCEPTS

MSIT-2K23
◗ Database, DBMS- database system
◗ File based approach-for data management
Last
Session ◗ Problems in FBA
◗ Solution provided by database Oriented
Approach
◗ Application areas of DB
◗ Basic Terminologies/Concepts
▹ Data Abstraction
▹ Schema and Instances
L e c tu re
Overview ▹ Data Independence
▹ DDL and DML
▹ Database Architecture
Data Abstraction
Data Abstraction
◗ Hides low level details (complexity) from the end
user.
◗ Pres ents an abs tract view of the data.
◗ Three levels of abstractions are provided for
database systems users:
◗ Physical level
◗ Logical level
◗ View levels
◗ Physical level: describes how a record (e.g.,
Levels of Data
customer) is stored.
Abstraction ◗ Logical level: describes data stored in database,
and the relationships among the data.
type instructor = record
ID : s tring;
name : s tring;
dept_name : s tring;
salary : integer;
end;
◗ View level: application programs hide details of
data types. Views can also hide information (such
as an employee’s salary) for security purposes.
L e v e l s of D a t a A b s t r a c t i o n - D a t a b a s e
Architectural View
S c h e m a a n d In s t a n c e s
◗ Schema – the logical structure of the
database
 Example: The database consists of information about a
set of customers and accounts and the relationship
between them
 Analogous to type information of a variable in a program
 Physical schema: database design at the physical level
 Logical schema: database design at the logical level

◗ Instance – the actual content of the


database at a particular point in time
Analogous to the value of a variable
Example of
Schema
State of the
database or
Instance
D a ta
In d e p e n d e n c e
◗ Data Independence- Separation of data & application
program
 Change of functionality at lower level doesn’t effect the
upper level
 Two types based on data abstraction levels-Physical &
Logical

◗ Physical Data Independence – the ability to modify


the physical schema without changing the logical
schema
 Applications depend on the logical schema
 In general, the interfaces between the various levels and
components should be well defined so that changes in some
parts do not seriously influence others
Logical Data Independence

Logical Schema
Physical Data Independence

Physical Schema
D D L and DML
Database Languages-DDL
◗ Two types of languages-Data Definition Language
(DDL) & Data Manipulation language (DML).
◗ DDL-Specify notations for defining the database
schema:
Example: create table instructor (
ID char(5),
name varchar(20),
dept_name varchar(20),
salary numeric(8,2))
◗ DDL compiler generates a set of table templates
stored in a data dictionary.
◗ Data dictionary contains metadata (i.e.,
Data Dictionary
data about data)
 Database schema
 Integrity constraints (date field format)
 Primary key (ID uniquely identifies the data
record)
 Referential integrity (references constraint
in SQL)
 e.g. dept_name value in any instructor
tuple must appear in department relation
 Authorization
Database Languages-DML
Procedural vs. Non-Procedural
Examples
SQL-Our Focus
D a ta b a s e A rc h it e c tu re
Database Design
Different Architectural Styles
◗ The architecture of a databas e system is
greatly influenced by the underlying computer
system on which the database is running:
▹ Centralized
▹ Client-server
■ Two-tier architecture
■ Three-tier architectures
▹ Parallel (multi-processor)
▹ Distributed
Centralized
Client Server
Client Server
Two-tier vs. Three-Tier

Front End
Front End

Back End Back End


The 3 Layers-Example
► Presentation Layer: For example, login page of Gmail where an end
user could see text boxes and buttons to enter user id, password and to
click on sign-in.

► Application Layer: As per the gmail login page example, once user
clicks on the login button, the authentication process and any other
manipulation would be run in this layer. Application layer interacts with
Database layer and sends required information to the Presentation
layer.

► Database Layer: Application layer communicates with Database layer


to retrieve the data. It contains methods that connects the database
and performs required action e.g.: insert, update, delete etc. For
instance Password update
Thank You

You might also like