Professional Documents
Culture Documents
ADBMS Lec1
ADBMS Lec1
Hardware
Data is stored on Disk
Data operated on in main memory
Database System - Components
Software
Database server
Database management system (DBMS)
DBMS provided by specific vendor
DBMS is not ( but may come with)
• Application Development Tools
• Application Software
• Report Writer
• System utilities
Users
Application Programmers
End Users
Database Administrators
Database Applications
Banking: transactions
Airlines: reservations, schedules
Universities: registration, grades
Sales: customers, products, purchases
Online retailers: order tracking, customized
recommendations
Manufacturing: production, inventory, orders,
supply chain
Human resources: employee records, salaries,
tax deductions
Persons involved in large database
Database administrators(DBAs): Responsible for
managing the database system, authorizing access,
coordinating & monitoring uses, acquiring resources.
Database designers: Responsible for designing the
database, identifying the data to be stored, choosing the
structures to represent and store this data.
End Users: The persons that use the database for
querying, updating, generating reports, etc. ( Casual,
Parametric and Sophisticated)
System Analysts/Application programmers: Design
and implement canned transactions for parametric
users.
Persons behind the scene
Persons involved in design, development, operation, and
maintenance of the DBMS software and system environment.
DBMS designers and implementers:
Design and implement the DBMS software package itself.
Tool developers:
Design and implement tools that facilitate the use of the
DBMS software. Tools include design tools, performance tools,
special interfaces, etc.
Operators and maintenance personnel:
Work on running and maintaining the hardware and software
environment for the database system.
Database Users and Administrators
Database
What is a Database?
Collection of persistent data
Collection of true propositions
Made up of entities, relationships, properties
Implements a data model
What is a Database?
Stores enterprise information over time
Outlasts the running of a computer program
Updated and retrieved in OLTP
operational/production system
Offers decision support via data warehouse
Entities and Relationships
Entity is a person, place, event or thing,
about which we wish to store information
Relationship is a connection between
entities, about which we wish to store
information
A relationship can be considered a special
case of entity
Properties
Entities have properties
Properties are the characteristics of an
entity
Properties can be simple or complex
Data and Data Models
Database is a collection of true propositions
Data model is an abstract, self-contained,
logical representation
Implementation of the data model on a
specific platform
Why Database?
Shared data
Reduced redundancy
Reduced inconsistent data
Transaction support
Support for data integrity
Security enforcement
Support for standards
Conflicting requirements can be met
Data Independence
Database separates logical and physical
representation of data
Allows changes to application programs without
changing the structure of the underlying data
and vice versa
Relational Systems
Most important innovation in database history
Based on logic and mathematics
Data is perceived as tables, only
Operators derive new tables from existing
A table is a “relation,” mathematically
Not Relational Systems
Hierarchic
Network
Object etc..
Main costs of using a DBMS
High initial investment in hardware, software,
training and possible need for additional
hardware.
Overhead for providing generality, security,
recovery, integrity, and concurrency control.
When DBMS may be unnecessary
If the database and applications are simple, well
defined, and not expected to change.
If there are stringent real-time requirements that
may not be met because of DBMS overhead.
If access to data by multiple users is not
required
History of Database Systems
1950s and early 1960s:
Data processing using magnetic tapes for storage
• Tapes provided only sequential access
Punched cards for input
Late 1960s and 1970s:
Hard disks allowed direct access to data
Network and hierarchical data models in widespread
use
Ted Codd defines the relational data model
• Would win the ACM Turing Award for this work
• IBM Research begins System R prototype
• UC Berkeley begins Ingres prototype
High-performance (for the era) transaction processing
History (cont.)
1980s:
Research relational prototypes evolve into commercial
systems
• SQL becomes industrial standard
Parallel and distributed database systems
Object-oriented database systems
1990s:
Large decision support and data-mining applications
Large multi-terabyte data warehouses
Emergence of Web commerce
Early 2000s:
XML and XQuery standards
Automated database administration
Later 2000s:
Giant data storage systems
• Google, Yahoo,, Amazon, ..
Database Systems
Architecture
DataBase Management System
(DBMS)
High-level
Query Q Answer
Translates Q into
best execution plan
DBMS for current conditions,
runs plan
Keeps data safe
and correct
despite failures,
concurrent Data
updates, online
processing, etc.
Database Systems Architecture
Three levels of architecture ( External,
Conceptual, Internal)
Mappings
Database Administrator (DBA)
Database Management System (DBMS)
Database Communications
Client/Server Architecture
Utilities
Distributed Processing
Database Architecture
……
Server
Client Client Server Client
site1 Site2 Site3 Site n
Communication Network
Three-tier Client/Server
Database Database
Server Management
System
Classification of DBMS
By Data Model
Relational Data Model