Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Database System Concepts and Architecture

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 21

Chapter 2

Database System Concepts and Architecture

Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley

Chapter 2 Outline
Data Models, Schemas, and Instances Three-Schema Architecture and Data Independence Database Languages and Interfaces The Database System Environment Centralized and Client/Server Architectures for DBMSs Classification of Database Management Systems
Copyright 2011 Ramez Elmasri and Shamkant Navathe

Data Models, Schemas, and Instances


Data abstraction

Suppression of details of data organization and storage Highlighting of the essential features for an improved understanding of data

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Data Models, Schemas, and Instances (cont'd.)


Data model

Collection of concepts that describe the structure of a database Provides means to achieve data abstraction Basic operations
Specify retrievals and updates on the database

Dynamic aspect or behavior of a database application


Allows the database designer to specify a set of valid operations allowed on database objects

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Categories of Data Models


High-level or conceptual data models

Close to the way many users perceive data Describe the details of how data is stored on computer storage media

Low-level or physical data models

Representational data models

Easily understood by end users Also similar to how data organized in computer storage
Copyright 2011 Ramez Elmasri and Shamkant Navathe

Categories of Data Models (cont'd.)


Entity

Represents a real-world object or concept

Attribute

Represents some property of interest Further describes an entity

Relationship among two or more entities

Represents an association among the entities Entity-Relationship model


Copyright 2011 Ramez Elmasri and Shamkant Navathe

Categories of Data Models (cont'd.)


Relational data model

Used most frequently in traditional commercial DBMSs

Object data model

New family of higher-level implementation data models Closer to conceptual data models

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Categories of Data Models (cont'd.)


Physical data models

Describe how data is stored as files in the computer Access path


Structure that makes the search for particular database records efficient

Index
Example of an access path Allows direct access to data using an index term or a keyword

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Schemas, Instances, and Database State


Database schema

Description of a database Displays selected aspects of schema Each object in the schema

Schema diagram

Schema construct

Database state or snapshot

Data in database at a particular moment in time

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Three-Schema Architecture and Data Independence


Internal level

Describes physical storage structure of the database Describes structure of the whole database for a community of users Describes part of the database that a particular user group is interested in

Conceptual level

External or view level

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Three-Schema Architecture and Data Independence (cont'd.)

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Data Independence
Capacity to change the schema at one level of a database system

Without having to change the schema at the next higher level

Types:

Logical Physical

Copyright 2011 Ramez Elmasri and Shamkant Navathe

DBMS Languages
Data definition language (DDL)

Defines both schemas Specifies the internal schema Specifies user views/mappings to conceptual schema Allows retrieval, insertion, deletion, modification

Storage definition language (SDL)

View definition language (VDL)

Data manipulation language (DML)

Copyright 2011 Ramez Elmasri and Shamkant Navathe

DBMS Languages (cont'd.)


High-level or nonprocedural DML

Can be used on its own to specify complex database operations concisely Set-at-a-time or set-oriented

Low-level or procedural DML

Must be embedded in a general-purpose programming language Record-at-a-time

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Centralized and Client/Server Architectures for DBMSs


Centralized DBMSs Architecture

All DBMS functionality, application program execution, and user interface processing carried out on one machine

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Basic Client/Server Architectures


Servers with specific functionalities Client machines
Appropriate interfaces to utilize these servers Local processing power to run local applications

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Two-Tier Client/Server Architectures for DBMSs


Server handles

Query and transaction functionality related to SQL processing User interface programs and application programs

Client handles

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Two-Tier Client/Server Architectures (cont'd.)


Open Database Connectivity (ODBC)

Provides application programming interface (API) Allows client-side programs to call the DBMS
Both client and server machines must have the necessary software installed

JDBC

Allows Java client programs to access one or more DBMSs through a standard interface

Copyright 2011 Ramez Elmasri and Shamkant Navathe

Classification of Database Management Systems


Data model

Relational Object Hierarchical and network (legacy) Native XML DBMS

Number of users

Single-user Multiuser
Copyright 2011 Ramez Elmasri and Shamkant Navathe

Classification of Database Management Systems (cont'd.)


Number of sites

Centralized Distributed
Homogeneous Heterogeneous

Cost

Open source Different types of licensing

Copyright 2011 Ramez Elmasri and Shamkant Navathe

You might also like