Scribd
Upload
36 views

Database System Concepts and Architecture

The document discusses database system concepts and architecture. It covers topics such as data models and their categories, schemas and instances, the three-schema architecture, centralized and client-server architectures, and two-tier and three-tier client/server architectures.

Uploaded by

09whitedevil90
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
36 views

Database System Concepts and Architecture

The document discusses database system concepts and architecture. It covers topics such as data models and their categories, schemas and instances, the three-schema architecture, centralized and client-server architectures, and two-tier and three-tier client/server architectures.

Uploaded by

09whitedevil90
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/ 7

lOMoARcPSD|39225634

Database System Concepts and Architecture

Intro To Database Appl (Montgomery College)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university


Downloaded by White Devil ([email protected])
lOMoARcPSD|39225634

Database System Concepts and Architecture


Outline
Data Models and Their Categories
Schemas, Instances, and States
Three-Schema Architecture
Centralized and Client-Server Architectures
Two-Tier and n-Tier Client/Server Architectures
Data Models

Data Model
A set of concepts to describe the structure of a database, the operations for manipulating these
structures, and certain constraints that the database should obey.
Data Model Structure and Constraints:
Constructs are used to define the database structure.
Constructs typically include elements (and their data types) as well as groups of elements (e.g. entity,
record, table), and relationships among such groups
Constraints specify some restrictions on valid data; these constraints must be enforced at all times
Data Models(continued)

Data Model Operations:


These operations are used for specifying database retrievals and updates by referring to the constructs
of the data model.
Operations on the data model may include basic model operations (e.g. generic insert, delete, update)
and user-defined operations (e.g. compute student gpa, update inventory)
Categories of Data Models
1. 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.)
2. Physical (low-level, internal) data models:
Provide concepts that describe details of how data is stored in the computer. These are usually specified
in an ad-hoc manner through DBMS design and administration manuals
3. Implementation (representational) data models:
Provide concepts that fall between the above two, used by many commercial DBMS implementations
(e.g. relational data models used in many commercial systems).
Schema versus Instances
Database Schema:
The description of a database.
Includes descriptions of the database structure, data types, and the constraints on the database.
Schema Diagram: An illustrative display of (most aspects of) a database schema.
Schema Construct: A component of the schema or an object within the schema, e.g., STUDENT, COURSE.

Downloaded by White Devil ([email protected])


lOMoARcPSD|39225634

Database State:
The actual data stored in a database at a particular moment in time. This includes the collection of all the
data in the database. Also called database instance (or occurrence or snapshot).
The term instance is also applied to individual database components, e.g. record instance, table instance,
entity instance
Initial Database State: Refers to the database state when it is initially loaded into the system.
Valid State: A state that satisfies the structure and constraints of the database.

NOTE: The database schema changes very infrequently.


The database state changes every time the database is updated.

Schema is also called intension.


State is also called extension.

Downloaded by White Devil ([email protected])


lOMoARcPSD|39225634

Example of a Database Schema

Example of a database state

Three-Schema Architecture
Proposed to support DBMS characteristics of:
Program-data independence.
Support of multiple views of the data.
The Three-Schema Architecture defines DBMS schemas at three levels:
1. Internal schema at the internal level to describe physical storage structures and access paths (e.g.
indexes).
Typically uses a physical data model.

Downloaded by White Devil ([email protected])


lOMoARcPSD|39225634

The three-schema architecture

2. Conceptual schema at the conceptual level to describe the structure and constraints for the whole
database for a community of users.
Uses a conceptual or an implementation data model.

3. External schemas at the external level to describe the various user views.
Usually uses the same data model as the conceptual schema.
Three-Schema Architecture (Cont’d)
Mappings among schema levels are needed to transform requests and data.
Programs refer to an external schema, and are mapped by the DBMS to the internal schema for
execution. Data extracted from the internal DBMS level is reformatted to match the user’s external view
(e.g. formatting the results of an SQL query for display in a Web page)
Centralized and Client-Server DBMS Architectures
Centralized DBMS:
Combines everything into single system including- DBMS software, hardware, application programs, and
user interface processing software. User can still connect through a remote terminal – however, all
processing is done at centralized site.

Downloaded by White Devil ([email protected])


lOMoARcPSD|39225634

A Physical Centralized Architecture

Basic 2-tier Client-Server Architectures


Specialized Servers with Specialized functions
1. Print server
2. File server
3. DBMS server
4. Web server
5. Email server
Clients can access the specialized servers as needed
Logical two-tier client server architecture

Clients
Provide appropriate interfaces through a client software module to access and utilize the various server
resources.
Clients may be diskless machines or PCs or Workstations with disks with only the client software
installed.
Connected to the servers via some form of a network (LAN: local area network, wireless network, etc.)
DBMS Server
Provides database query and transaction services to the clients.
Relational DBMS servers are often called SQL servers, query servers, or transaction servers.
Applications running on clients utilize an Application Program Interface (API) to access server databases
via standard interface such as:

Downloaded by White Devil ([email protected])


lOMoARcPSD|39225634

ODBC: Open Database Connectivity standard


JDBC: for Java programming access
Client and server must install appropriate client module and server module software for ODBC or JDBC
Two Tier Client-Server Architecture
A client program may connect to several DBMSs, sometimes called the data sources.
In general, data sources can be files or other non-DBMS software that manages data.
Other variations of clients are possible: e.g., in some object DBMSs, more functionality is transferred to
clients including data dictionary functions, optimization and recovery across multiple servers, etc.
Three Tier Client-Server Architecture
Common for Web applications.
Intermediate Layer called Application Server or Web Server:
Stores the web connectivity software and the business logic part of the application used to access the
corresponding data from the database server.
Acts like a conduit for sending partially processed data between the database server and the client.

Three-tier Architecture Can Enhance Security:


Database server only accessible via middle tier.
Clients cannot directly access database server.
Three-tier client-server architecture

Downloaded by White Devil ([email protected])

You might also like