Scribd
Upload
10 views5 pages

dbms1 Part4

hg

Uploaded by

omsaidesai9
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views5 pages

dbms1 Part4

hg

Uploaded by

omsaidesai9
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

DBMS Interfaces

• Menu-based
Provides users with menus of available options or operations, simplifying interaction.
Suitable for novice users who don’t need to know SQL commands.
Examples: ATMs offering menu-based transactions (withdrawals, deposits).

• Forms-based, designed for naïve users


Users interact with the database by filling forms that map to underlying database operations.
Common in web applications where users enter data through forms (e.g., customer
registration).
Example: A hotel reservation system where a user fills a form with guest details, which are
stored in the database.

• Graphics-User interface
Provides a visual interface with buttons, menus, and windows to interact with the DBMS.
Useful for both beginners and experts due to its intuitive design.
Examples:Oracle SQL Developer- provides GUIs for table creation, query execution,
and data visualization.
• Natural language
Allows users to query the database using natural language (like English) rather than SQL.
Typically used in chatbots or voice-activated systems.
Examples: Chatbots integrated with DBMS to fetch customer information.
• Speech as Input and Output
The speech input is detected using a library of predefined words and used to set up the
parameters that are supplied to the queries. For output, a similar conversion from text
or numbers into speech takes place.
Examples: Applications with limited vocabularies such as inquiries for telephone directory,
flight arrival/departure, and credit card account information.
• Parametric interfaces
Usually a small set of abbreviated commands is included, with the goal of minimizing the
number of keystrokes required for each request. For example, function keys in a terminal
can be programmed to initiate various commands.
Example: A bank teller is able to use single function keys to invoke routine and repetitive
transactions such as account deposits or withdrawals, or balance inquiries.
• Interfaces for the DBA
Provides tools for maintenance, tuning, and security management. These interfaces offer
advanced functions like creating user accounts, granting account authorization, backup,
indexing, and performance monitoring.
 Examples:

1
• Oracle Enterprise Manager: A tool for managing Oracle databases.
Classification of DBMS
The classification of DBMS (Database Management Systems) is based on various factors
such as the data model, architecture, data distribution, and user interaction. Below are the
main types of DBMS classifications:
Based on data model
Hierarchical DBMS
 Organizes data in a tree-like structure with parent-child relationships.
 Each parent can have multiple children, but each child has only one parent.
Network DBMS
 Data is organized using graph structures, with many-to-many relationships (a child
can have multiple parents).
 Uses pointers to represent connections between records.
Relational DBMS (RDBMS)
 Stores data in tables (relations) with rows and columns.
Object-Oriented DBMS (OODBMS)
 Data is represented as objects (as in object-oriented programming).
 Supports inheritance, encapsulation, and polymorphism.
Based on data distribution
Centralized DBMS
 The entire database is stored at a single location (server or mainframe).
 Users access it remotely over a network.
Distributed DBMS (DDBMS)
 The database is spread across multiple locations, connected by a network.
 Supports both replication and fragmentation of data.
Based on number of users
Single-User DBMS
 Supports only one user at a time.
Multi-User DBMS
 Allows multiple users to access the database simultaneously.

2
DBMS ENVIRONMENT

1. DDL (Data Definition Language) Statements:


These are commands used to define or modify the structure of database objects, such as
tables, schemas, or indexes.
Examples: CREATE TABLE, ALTER TABLE, DROP TABLE.
2. DBA (Database Administrator) Staff:
These are users with administrative privileges to manage the database. They control access
and overall database integrity.
Example: A DBA could create a new user account, allocate database storage, or manage
queries for better performance.
3. Privileged Commands:
Commands that only the DBA or superuser can execute. These could involve altering critical
system settings or user permissions.
3
Example: Granting or revoking privileges from users (GRANT ALL PRIVILEGES).
4. Casual Users / Application Programmers:
Casual users interact with the database using predefined queries, while programmers write
applications that interact with the database using complex queries.
Example: A casual user might run a report from a business application. A programmer may
write SQL queries within a software system to retrieve customer records.
5. Interactive Query:
This refers to queries run by users to retrieve specific information from the database.
Example: Running a SELECT * FROM Customers WHERE Country = 'USA' query to get a list of
U.S.-based customers.
6. DDL Compiler:
DDL Compiler converts the DDL commands into machine understandable format
which enables DBMS to perform the given DDL operation.
Example: When a user issues a CREATE TABLE command, the DDL compiler breaks it down
into internal actions to build the table.
7. Query Compiler / Optimizer:
The query compiler translates user queries (usually written in SQL) into an executable
program./instruction .
8. Precompiler:
The precompiler is a tool that helps convert SQL commands (used to communicate with
databases) that are written inside a regular programming language (like C, Java, or Python)
into something that the database can understand and execute. Example: A precompiler
might handle SQL queries embedded within a Java or C++ application.
9. DML Compiler: A DML (Data Manipulation Language) Compiler is a component of a
Database Management System (DBMS) that processes and translates high-level DML
statements (such as SELECT, INSERT, UPDATE, and DELETE) written by users into a
lower-level, machine-readable code that can be executed by the database system.
11. Host Language Compiler:
Host Language Compiler is responsible for compiling the main programming code (like C,
Java, etc.) while the precompiler deals with the SQL part.
12. Query Evaluation Engine:
The Query Evaluation Engine acts like a "middleman" between your query and the
database. It understands what you are asking for, finds the best way to get the data, and
then retrieves the results as efficiently as possible.
13. Transaction Manager:
It starts, manages, and terminates transactions, ensuring that they follow the rules of ACID
properties (Atomicity, Consistency, Isolation, Durability).Example: If two users are updating
the same record, the transaction manager ensures that the updates don't conflict.

4
14. Concurrency Control:
Concurrency control is crucial in ensuring that databases can handle multiple transactions at
the same time without compromising data integrity or consistency
15. Runtime database processor: Runtime database processor is responsible for
interpreting, executing, optimizing, and managing all real-time interactions between the
database and its users or applications.
16. Disk Storage / Buffer Manager:
The Disk Storage/Buffer Manager in a Database Management System (DBMS) is responsible
for managing how data is stored on and retrieved from the disk.

You might also like