Database System Environment

DBMS component modules:

Above figure illustrates the DBMS components. The figure is divided into 2 halves.
• The top half of the figure refers to various users of database environment.
• The lower half shows the internal of the DBMS responsible for storage of data and
processingof transaction
The components are listed below:
1. Query compiler: - It performs translation of high SQL into database access code and
generatesappropriate calls to run-time processor to execute code.
2. Stored Data manager (storage manager):- High level stored data manager component
moduleof DBMS, which define an interface between low-level data stored in database.
It is responsible for the interaction with the file manager.
3. File manager: - it is to manage the memory allocation on disk storage and data
dictionary thatrepresent Meta data.
4. Buffer Manager: - It is to manage fetching of data from hard disk storage units into
mainmemory of computer.
5. DDL compiler: - It performs translations of DDL statements into schema definitions and
storecorresponding schema descriptions called meta data in DBMS catalog.
6. DML compiler: - The SQL statements hence extracted by pre-compiler are submitted to
DMLcompiler. It will translate them into database access and manipulation.
This object code is for extracted DML/SQL statements and parts of SQL. It is to form
one ormore canned transactions.
7. Pre compiler: - It will identify the SQL statements/ DML statements in host language
applications program.
8. Stored database and system/ catalog: - The database and the DBMS- catalog are usually
storedon Hard disk.
DATABASE SYSTEM UTILITIES
That help the DBA manage the database system. Common utilities have the following
types of functions:
LOADING
BACKUP
Database storage reorganization
Performance monitoring
Other utilities may be available for sorting files, handling data compression, monitoring
access by users, interfacing with the network, and performing other functions.
LOADING
 loading utility is used to load existing data files such as text files or sequential files into the
database.
 The current (source) format of the data file and the desired (target) database file structure
arespecified to the utility, which then automatically reformats the data and stores it in the
database.
BACKUP
 A backup utility creates a backup copy of the database, usually by dumping the entire
database onto tape or other mass storage medium.
 The backup copy can be used to restore the database in case of disk failure.
DATABASE STORAGE REORGANIZATION
 This utility can be used to reorganize a set of database files into different file organizations,
andcreate new access paths to improve performance.
PERFORMANCE MONITORING
 Such a utility monitors database usage and provides statistics to the DBA.
 The DBA uses the statistics in making decisions such as whether or not to reorganize files
orwhether to add or drop indexes to improve performance.

Other Tools

CASE tools are used in the design phase of database systems.

Data dictionary (or data repository) system - In addition to storing catalog
information about schemas and constraints, the data dictionary stores other
information, such as design decisions, usage standards, application program
descriptions, and user information.
Application development environments, such as PowerBuilder (Sybase)
or JBuilder (Borland), have been quite popular. These systems provide an
environment for developing database applications and include facilities that help
in many facets of database systems, including database design, GUI
development, querying and updating, and application program development.
Communications software - It allow remote database access through computer
terminals, workstations, or personal computers. These are connected to the
database site through data communications hardware such as Internet routers,
phone lines, long-haul networks, local networks, or satellite communication
devices.
 Centralized and Client Server Architectures
A database management system (DBMS) is a software system that is designed to manage and
organize data in a structured manner. In order to accomplish this, DBMS uses a specific
architecture that dictates how data is stored, retrieved, and updated. Two of the most commonly
used architectures in DBMS are centralized and client-server architectures.

Centralized Architecture
A centralized architecture for DBMS is one in which all data is stored on a single server, and
all clients connect to that server in order to access and manipulate the data. This type of
architecture is also known as a monolithic architecture. One of the main advantages of a
centralized architecture is its simplicity - there is only one server to manage, and all clients use
the same data. However, there are also some drawbacks to this type of architecture. One of the
main downsides is that, because all data is stored on a single server, that server can become a
bottleneck as the number of clients and/or the amount of data increases. Additionally, if the
server goes down for any reason, all clients lose access to the data. An example of a DBMS
that uses a centralized architecture is SQLite, an open-source, self-contained, high-reliability,
embedded, full-featured, public-domain SQL database engine. SQLite's architecture is based
on the client-server model, but the entire database is contained within a single file, making it a
perfect fit for small to medium-sized applications.

Client-Server Architecture
A client-server architecture for DBMS is one in which data is stored on a central server, but
clients connect to that server in order to access and manipulate the data. This type of
architecture is more complex than a centralized architecture, but it offers several advantages
over the latter. One of the main benefits of a client-server architecture is that it is more scalable
than a centralized architecture. As the number of clients and/or the amount of data increases,
the server can be upgraded or additional servers can be added to handle the load. This allows
the system to continue functioning smoothly even as it grows in size. Another advantage of a
client-server architecture is that it is more fault-tolerant than a centralized architecture. If a
single server goes down, other servers can take over its responsibilities, and clients can still
access the data. This makes the system less likely to experience downtime, which is a crucial
factor in many business environments. An example of a DBMS that uses a client-server
architecture is MySQL, an open-source relational database management system. MySQL uses
a multi-threaded architecture, where multiple clients can connect to the server and make
requests simultaneously. The server processes these requests and returns the results to the
appropriate client.
 Classification of Database management system (DBMS)
The several criteria are normally used to classify DBMSs. Generally following are noticed,
1) DBMSs based on the data model
2) DBMSs is based on the number of users supported by the system.
3) DBMS based on number of sites over which the database is distributed.
4) DBMS based on the Cost

1) DBMSs based on the data model:

 The main data model used in many current commercial DBMSs is the relational datamodel.
 The object data model has been implemented in some commercial systems but has not had
widespread use.
 The relational DBMSs are evolving continuously, and, in particular, have been incorporating
many of the concepts that were developed in object databases.
 This has led to a new class of DBMSs called object-relational DBMSs.
 We can categorize DBMSs based on the data model: relational, object, object-relational,
hierarchical, network, and other.
 DBMSs are based on the XML (eXtended Markup Language) model, which is a tree-
structured (hierarchical) data model.
 These have been called native XML DBMSs. Several commercial relational DBMSs have
added XML interfaces and storage to their products.
2) DBMSs is based on the number of users supported by the system.
 Single-user systems support only one user at a time and are mostly used with PCs.
 Multiuser systems, which include the majority of DBMSs, support concurrent multiple users.
3) DBMS based on number of sites over which the database is distributed.
 A DBMS is centralized if the data is stored at a single computer site. A centralized DBMS
can support multiple users, but the DBMS and the database reside totally at a single computer
site.
 A distributed DBMS (DDBMS) can have the actual database and DBMS software distributed
over many sites, connected by a computer network.
 Homogeneous DDBMSs use the same DBMS software at all the sites, heterogeneous
DDBMSs can use different DBMS software at each site.
 It is also possible to develop middleware software to access several autonomous preexisting
databases stored under heterogeneous DBMSs.
 This leads to a federated DBMS (or multidatabase system), in which the participating DBMSs
are loosely coupled and have a degree of local autonomy. Many DDBMSs use client-server
architecture
4) DBMS BASED ON COST
 It is difficult to propose a classification of DBMSs based on cost.
 Today we have open source (free) DBMS products like MySQL and PostgreSQL that are
supported by third-party vendors with additional services.
 The main RDBMS products are available as free examination 30-day copy versions as wellas
personal versions, which may cost under $100 and allow a fair amount of functionality.