Database System Concepts and Architecture

1
Database System Concepts and Architecture
2
Data Models

• Data Model
• A set of concepts to describe the structure of a
  database.
• Provides the necessary means to achieve this
  abstraction. 
• Data Model Operations
• Operations for specifying database retrievals and
  updates by referring to the concepts of the data
  model.

3
Data Models

• Categories of data models
• Conceptual (high-level, semantic) data models
  Provide concepts that are close to the way many
  users perceive data. (Also called entity-based
  or object-based data models.)
• Physical (low-level, internal) data models
  Provide concepts that describe details of how
  data is stored in the computer.
• Implementation (record-oriented) data models
  Provide concepts that fall between the above two,
  balancing user views with some computer storage
  details.

4
Schemas, Instances, Database State

• Database Schema The description of a database.
  Includes descriptions of the database structure
  and the constraints that should hold on the
  database.
• Schema Diagram A diagrammatic display of (some
  aspects of) a database schema
• Schema Construct Objects in the schema
• Database state The actual data stored in a
  database at a particular moment in time (or the
  current set of instances)
• Valid state A state that satisfies the structure
  and constraints specified in the schema
• Schema is also called intension, whereas state is
  called extension.

5
Three-Schema Architecture

• Defines DBMS schemas at three levels
• Internal schema at the internal level to describe
  data storage structures and access paths.
  Typically uses a physical data model.
• Conceptual schema at the conceptual level to
  describe the structure and constraints for the
  whole database.
• External schemas at the external level to
  describe the various user views. Usually uses the
  same data model as the conceptual level.
• Mappings are needed Users refer to own external
  schema, and are mapped by the DBMS to the
  conceptual and to the internal schema for
  processing.

6
(No Transcript)
7
Data Independence

• Logical Data Independence The capacity to change
  the conceptual schema without having to change
  the external schemas or their application
  programs.
• Physical Data Independence The capacity to
  change the internal schema without having to
  change the conceptual schema.

8
Data Independence

• Full data independence
• When a schema at a lower level is changed, only
  the mappings between this schema and higher-level
  schemas need to be changed.
• The higher-level schemas themselves are
  unchanged. Hence, the application programs need
  not be changed since the refer to the external
  schemas.

9
DBMS Languages

• Data Definition Language (DDL)
• Used by the DBA and database designers to specify
  the conceptual schema of a database.
• Storage definition language (SDL)
• Used to specified the internal schema
• View definition language (VDL)
• Used to specify user views.
• Data Manipulation Language (DML)
• Used to specify database retrievals and updates.
• In current DBMSs, a comprehensive integrated
  language is used for all except storage
  definition.

10
DBMS Languages

• Types of DML
• Procedural (low level) DML must be embedded in a
  host language, a general-purpose programming
  language such as COBOL, PL/1 or PASCAL
• Nonprocedural (high level) DML can be embedded
  or can be applied directly (query language).
• Embedded language is called data sublanguage

11
DBMS Interfaces

• Web-based interfaces for Web Client or Browsing
• Forms-based interface
• Graphical user interface (Point and Click, Drag
  and Drop etc.)
• Natural language interface
• Interface for parametric users using function
  keys
• Interfaces for the DBA
• Creating accounts, granting authorizations
• Setting system parameters
• Changing schemas or access path

12
DBMS Component Modules

• Stored data manager
• Buffer manager module
• Runtime database processor
• Query compiler
• Pre-compiler
• Client program
• Database server
• Application server

13

• INSERT FIGURE 2.3

Typical component modules of a DBMS. Dotted lines
show accesses that are under the control of the
stored data manager.
14
Database System Utilities

• To perform certain functions such as
• Loading data stored in files into a database
• Back up the database periodically on tape
• File reorganization database file structures
• Performance monitoring
• Other functions, such as sorting, user
  monitoring, data compression, interfacing with
  the network, etc.

15
Tools, Application Environments, Communication
Facilities

• Data dictionary/repository
• Used to store schema descriptions and other
  information such as design decisions, application
  program descriptions, user information, usage
  standards, etc.
• Active data dictionary is accessed by DBMS
  software and users/DBA.
• Passive data dictionary is accessed by users/DBA
  only.

16
Centralized and Client/Server Architectures for
DBMSs

• Centralized DBMSs Architecture
• Basic Client/Server Architectures
• Specialized servers
• Client machines
• Two-tier Client/Server Architectures for DBMSs
• Query server or transaction server or SQL server
• Client machines
• Three-tier Client/Server Architectures for Web
• Middle tier application server or Web server

17
Classification of DBMSs

• Based on the data model used
• Traditional Relational, Network, Hierarchical.
• Emerging Object-oriented, Object-relational.
• Other classifications
• Single-user (typically used with micro-
  computers) vs. multi-user (most DBMSs).
• Centralized (uses a single computer with one
  database) vs. distributed (uses multiple
  computers, multiple databases)