0% found this document useful (0 votes)
29 views32 pages

Unit I Introduction 1

Uploaded by

bisol27639
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)
29 views32 pages

Unit I Introduction 1

Uploaded by

bisol27639
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

Unit I: Introduction

Dr. Anushree Tripathi

Department of Computer Science and Engineering


National Institute of Technology Patna (NITP)

3rd September, 2024


Syllabus (Theory)
UNIT I: Introduction

• Introduction: Purpose of database systems, View of data


• Data models & interface
• Database language
• Transaction management
• Storage management, database administrator
• Database users
• Overall system structure
• Classification of Database Management System
• Three- Schema Architecture
Introduction

DATA + BASE + MANAGEMENT + SYSTEM


Introduction (contd.)
Example

Course registrations

Research
laboratories Courses

Institute
Database

Students Faculties
Introduction (contd.)
Collection of programs that enables user to create and
maintain a database

DBMS Defining: Specify data type, structures and


constrains

Constructing: Storing data

Manipulating: Querying the database to retrieve


specific data, updating the database

Sharing: Allows multiple users to access


database simultaneously
File system versus DBMS

File system DBMS

Data redundancy Separation of data and metadata

Concurrent use of system by large


Difficult to maintain consistency
number of users

Difficult to anticipate all requests Program-data independence


Why do Learn DBMS?

Security

Consistency

Less redundancy
Purpose of database systems

• To control redundancy
• To restrict unauthorized access
• To provide persistent storage for program objects
• To provide search techniques for efficient query
processing
• To provide multiple user interfaces
Introduction (contd.)
Characteristics

Self-describing nature Insulation between


(Description of database structure program and data
and constraints) (program-data independence)

Sharing of data and


Support of multiple views of
multiuser transaction
data
processing
View of data

Views
Base Table
Previously
defined views Virtual Table
Single Table (View) CREATE VIEW
Physical
derived from
storage of No physical SQL Command
other tables
tuples existence
View of data (contd.)

• Limitation
Limits update operations
• Uses
Provides data independence
Data models

Data Abstraction Data Model

Suppression of details Provides the way to


of data and highlighting achieve data
essential features abstraction
Data models (contd.)
• Collection of concepts to describe the structure of a
database
• Structure of a database defined by data types,
relationships and constraints
• Include set of basic operations
• Dynamic aspect or behaviour of a database application
Data models (contd.)
Categories

High-level or conceptual
data models

Data Models

Representational/Impleme- Low-level or physical data


ntation data models model
Conceptual / High-level data models
• Use concepts such as entities, attributes and relationships
• Object data models represents as a new family of higher-level
implementation data models, closer to conceptual data models

Entity Attribute Relationship

• Real world • Properties of • Association


object/ concept entity among entities
• Example: • Example: • Enrolled-on
Student, project student name, relationship
enrollment between
number student and
course
Representational/Implementation
data models
• Concepts that may be understood by end users
• Hides some details of data storage but can be
implemented on a computer system in a direct way
• Mostly used in traditional commercial DBMSs
• Includes
Relational
Network
Hierarchical
• Represent data by using record structures, called as
record-based data models.
Low-level or physical data model
• Describes the details of how data is stored on the
computer storage media
• Representing information such as record formats, record
orderings and access paths.
• Access path: provides efficient searching for particular
database records
• Not useful for end users
Schemas and Instances
• Description of a database
• Specified during database
design and not change
frequently
Schema • Schema diagram: Displayed
schema, only some aspects
• Schema construct: Object in
schema

• Current set of occurrences


in the database
Instances • Each schema construct has
its own current set of
instances
Schemas and Database State

Database
Schema
State

Data in a
Specify to
database at a
define a new
particular
database
moment in time

Extension of
Intension
schema
Three- Schema Architecture
End Users

External schema View Level


External schema External schema

External/Conceptual
Mapping
Conceptual schema Logical (Conceptual) Level
Conceptual/Internal
Mapping
Physical (Internal) Level
Physical/Internal schema

Stored Database
Three- Schema Architecture (contd.)
Need of Three- Schema Architecture

Data
Independence

Logical data Physical data


independence independence
DBMS Interfaces
• User-friendly DBMS interfaces:
Menu-based interfaces
Apps for mobile devices
Forms-based interfaces
Graphical user interfaces
Natural language interfaces
Keyboard based database search
Speech input and output
Interfaces for parametric users
Interfaces for the DBA
Menu-based interfaces

• Provide list of options (menus)


• No requirement of memorization of specific commands
and syntax of query language
• Pull-down menus of web-based user interfaces, used in
browsing interfaces
Apps for mobile devices
• Provide access to data for mobile users
• Limited menus of options
• Example: Bill payments and websites
Forms-based interfaces

• Displays a form to each user


• Used for naive users
• Form specification languages to specify forms
Graphical user interfaces

• Displays a schema to users in diagrammatic form


• Users specify a query by manipulating the diagram
• GUIs utilize both menus and forms
• Use a pointing device
Natural language interfaces

• Accepts requests in some languages to understand easily


• Schema similar to the database conceptual schema
• Refers to words in its schema and set of standard words
in its dictionary
Keyboard-based database search

• Similar to web search engines, accepts strings of natural


language words and match them with documents at
specific sites
• Use pre-defined indexes on words and ranking functions
• Keyword-based querying has emerged for relational
database
Speech input and output

• Limited use of speech as input query and output


• Speech input is detected using a library of predefined
words
• Conversion from text or numbers into speech
Interfaces for parametric users

• Parametric users: Use small set of operations that must


performed repeatedly
• Example: Bank transactions
• Small set of abbreviated commands used
Interfaces for the DBA

• Include privileged commands used only by DBA’s staff


• Commands such as creating accounts, granting account
authorization, changing schema and reorganizing storage
structures of a database

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy