DBMS Architecture: Kocbk Database Management System

DBMS Architecture
KOCBK
Database Management System
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.
Example of database Schema
Database Instance
• Also called 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.
• The term instance is also applied to individual
database components, e.g. record instance, table
instance, entity instance
Database 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.
Example of database state(instance)
Database schema Vs. Database state
– The database schema changes very infrequently.
– The database state changes every time the
database is updated.
• Schema is also called intension.

• State(instance) is also called extension
Three Schema Architecture of
DBMS
• Proposed to support DBMS characteristics of:
– Program-data independence.
– Support of multiple views of the data.
• Not explicitly used in commercial DBMS
products, but has been useful in explaining
database system organization
Three Schema Architecture
• Defines DBMS schemas at three levels:
– Internal schema at the internal level to describe physical storage
structures and access paths (e.g indexes).
• Typically uses a physical data model.
– 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.
– External schemas at the external level to describe the various
user views.
• Usually uses the same data model as the conceptual schema.
• 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)
Data Independence
• Logical Data Independence:
– The capacity to change the conceptual schema
without having to change the external schemas and
their associated application programs.
• Physical Data Independence:
– The capacity to change the internal schema without
having to change the conceptual schema.
– For example, the internal schema may be changed
when certain file structures are reorganized or new
indexes are created to improve database
performance
Data Independence(continued)
• When a schema at a lower level is changed,
only the mappings between this schema and
higher-level schemas need to be changed in a
DBMS that fully supports data independence.
• The higher-level schemas themselves are
unchanged.
– Hence, the application programs need not be
changed since they refer to the external schemas.
Centralized DBMS Architecture
– 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.
Centralized DBMS Architecture
Client Server Architecture of DBMS
• Specialized Servers with Specialized functions
– Print server
– File server
– DBMS server
– Web server
– Email server
• Clients can access the specialized servers as
needed
Client Server Architecture
Client
• 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:
– ODBC: Open Database Connectivity standard
– JDBC: for Java programming access
Components of DBMS
• Hardware: the device, hard discs, data I/O
channels, and all other physical components
that must be present before data can be
effectively stored in memory.
• Software: This is the most important part
since it is the software that manages
everything.
Components of DBMS
• Data: Data is the resource for which the
database management system was developed.
• Metadata is information about information.
This is data that the DBMS stores in order to
better explain the data it holds.
Components of DBMS
• Procedures
• Procedures are guidelines on how to use a
database management system in general.
• This includes procedures for setting up and
installing a database management system
(DBMS), logging in and out of DBMS software,
managing databases, taking backups, and
producing reports, among other things.
DBMS Components
• Database Access Language: basic
programming language for accessing,
inserting, updating, and deleting data from
any database.

DBMS Architecture: Kocbk Database Management System

Uploaded by

Copyright:

Available Formats

DBMS Architecture: Kocbk Database Management System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DBMS Architecture: Kocbk Database Management System

Uploaded by

Copyright:

Available Formats

DBMS Architecture

• Schema is also called intension.

– User can still connect through a remote terminal –

You might also like