Professional Documents
Culture Documents
Topic 2 Concepts and Architecture PDF
Topic 2 Concepts and Architecture PDF
Let's have a simple diagram to see how they all fit together to form a
database management system.
Data is that resource, for which DBMS was designed. The motive behind
the creation of DBMS was to store and utilise data.
In a typical Database, the user saved Data is present and meta data is
stored.
Metadata is data about the data. This is information stored by the DBMS
to better understand the data stored in it.
Users
Query processor
This is the intermediary between the user queries and the database. The
query processor interprets the queries of users and makes them
actionable commands that can be understood by the database to
perform the appropriate functionality.
Optimization engine
The optimization Engine allows the DBMS to provide insights into the
performance of the database in terms of optimizing the database itself
and queries. When coupled with database monitoring tools, it can
provide a powerful toolset to gain the best performance out of the
database.
Metadata catalog
This is the centralized catalog of all the objects within the database.
When an object is created, the DBMS keeps a record of that object with
some metadata about it using the metadata catalog. Then, this record
can be used to:
• Verify user requests to the appropriate database objects
• Provide an overview of the complete database structure
Log manager
This component will keep all the logs of the DBMS. These logs will
consist of user logins and activity, database functions, backups and
restore functions, etc. The log manager ensures all these logs are
properly recorded and easily accessible.
Reporting & monitoring tools
Reporting and monitoring tools are another standard component that
comes with a DBMS. Reporting tools will enable users to generate
reports while monitoring tools enable monitoring the databases for
resource consumption, user activity, etc.
Data utilities
In addition to all the above, most DBMS software comes with additional
inbuilt utilities to provide functionality such as:
• Data integrity checks
• Backup and restore
• Simple database repair
• Data validations
• Etc.
The user doesn’t need to know the database schema details such as
data structure, table definition etc. user is only concerned about data
which is what returned back to the view level after it has been fetched
from database (present at the internal level).
External level is the “top level” of the Three Level DBMS Architecture.
Database Languages:
The execution of DDL statements results in new tables which are stored
in "system catalog" also called data dictionary or data directory.
Data definition language allows the user to specify the storage and
access methods using a special language called data storage and
definiton language.
Procedural DML
Using procedural DML, the user can specify "what" data needs to be
retrieved and "how" to retrieve the required data. This means that the
user has to express the operations that would retrieve the desired data.
DML initiates by evaluating these operations. The result of evaluation is
again operated until the desired data is retrieved. The DML statements
are embedded into high-level languages to perform selective and
iterative operations.
Non-procedural DML
Non-procedural languages are also called declarative language that
specify "what" data is to be retrieved but does not specify "how" the data
is to be retrieved. These languages are easy to learn as the user simply
needs the desired data. It is the responsibility of database system
choose an optimal procedure in order to retrieve the required data.
DBMS translates the DML statements into set procedures and retrieves
the data.
In DBMS (Data Base Management System), there are mainly four kinds
of commands are available. They are: DQL, DDL, DML, TCL, and DCL
• The schema does not physically contain the data itself; instead,
it gives information about the shape of data and how it can be
related to other tables or models.
• The complexity & the size of the schema vary as per the size of the
project. It helps developers to easily manage and structure the
database before coding it.
1. Logical Schema
2. Physical Schema
3. View Schema
1. Physical Database Schema
A physical database schema specifies how the data is stored physically
on a storage system or disk storage in the form of Files and Indices.
Designing a database at the physical level is called a physical schema.
3. View Schema
The view level design of a database is known as view schema. This
schema generally describes the end-user interaction with the database
systems.
Difference between the Physical and Logical Database Schema
It contains the column names and It does not contain any column
their data types. name or datatype.
The designer has both formal and informal sources of information. The
process of defining problems might initially appear to be unstructured.
Company end users are often unable to describe precisely the larger
scope of company operations or to identify the real problems
encountered during company operations.
c. Define Objectives:
The designer must recognize the existence of two sets of limits: scope
and boundaries. The system’s scope defines the extent of the design
according to operational requirements. Will the database design
encompass the entire organization, one or more departments within the
organization, or one or more functions of a single department? Knowing
the scope helps in defining the required data structures, the type and
number of entities, the physical size of the database, and so on.
2. Database Design:
The second phase focuses on the design of the database model that will
support company operations and objectives. This is arguably the most
critical DBLC phase: making sure that the final product meets user and
system requirements. As you examine the procedures required to
complete the design phase in the DBLC, remember these points:
This step is required only when a new dedicated instance of the DBMS
is necessary for the system. The DBMS may be installed on a new
server or it may be installed on existing servers. One current trend is
called virtualization. Virtualization is a technique that creates logical
representations of computing resources that are independent of the
underlying physical computing resources.
After the database has been created, the data must be loaded into the
database tables. Typically, the data will have to be migrated from the
prior version of the system. Often, data to be included in the system
must be aggregated from multiple sources. Data may have to be
imported from other relational databases, non relational databases, flat
files, legacy systems, or even manual paper-and-pencil systems
During this step, the DBA tests the database to ensure that it maintains
the integrity and security of the data. Data integrity is enforced by the
DBMS through the proper use of primary and foreign key rules. In
database testing you must check Physical security allows, Password
security, Access rights, Data encryption etc.
As the database and application programs are created and tested, the
system must also be evaluated from a more holistic approach. Testing
and evaluation of the individual components should culminate in a
variety of broader system tests to ensure that all of the components
interact properly to meet the needs of the users. To ensure that the data
contained in the database are protected against loss, backup and
recovery plans are tested.
5. Operation
Once the database has passed the evaluation stage, it is considered to
be operational. At that point, the database, its management, its users,
and its application programs constitute a complete information system.
The beginning of the operational phase invariably starts the process of
system evolution.
So, all programs that access the data in the database work through the
DBMS.
The DBMS uses the data dictionary to look up the required data
component structures and relationships which relieves you from coding
such complex relationships in each program.
4. Security Management
The DBMS provides backup and data recovery to ensure data safety
and integrity.
Current DBMS systems provide special utilities that allow the DBA to
perform routine and special backup and restore procedures. Recovery
management deals with the recovery of the database after a failure,
such as a bad sector in the disk or a power failure. Such capability is
critical to preserving the database’s integrity.
The data relationships stored in the data dictionary are used to enforce
data integrity. Ensuring data integrity is important DBMS functionality in
transaction-oriented database systems.