DB Chapter No 3
DB Chapter No 3
3. Describes Entities
4. DescribesAttributes (Metadata)
5. Describes Relationship
6. Describes Constraints.
Data Manipulation Language (DML):
▪ Data manipulation language is used to
1. Procedural DML
▪ User has to tell DBMS what to do and how to do. It is
tough job. More work is done by user. Hierarchal and
network models uses Procedural DML Language. C,
select name
Cobol, BASIC etc. from Employee
where ID = ‘343’
2. Non Procedural DML
▪ User just tells what to do NOT how to do. Manipulation
of data is easy. Less work is done by user and more
work is don’t by DBMS. Relational DBMS uses Non
procedural DML. It is also called “Declaration
Languages”. SQL, LISP etc.
Data Control Language (DCL):
▪ With the help of this language, DBA
controls database.
4. DBMS should provide transaction support to users and must ensure that each transaction update
data successfully.
5. DBMS should provide concurrency control. Concurrency means accessing and performing
transactions on database by multiple users at same time.
6. DBMS should ensure consistency of data. Correct data values should be available to each users.
7. DBMS should ensure that multiple transactions from different users executing concurrently will
not violate database consistency. This is called “Concurrency Transparency”
8. In case of some failure, DBMS should provide some mechanism for recovering from failure.
9. DBMS must provide a mechanism that only authorized persons should be provided access to
database.
10. DBMS must ensure data independence i-e there must be clear separation between users and
necessary.
12. DBMS should be able to import and export data from database as per users requirement.
13. DBMS must support certain utility software like report generators or form builders in order to
facilitate users.
Single User Database Environment
The database environment which supports only one user accessing the database at a
specific time.
The DBMS might have a number of users but at a certain time only one user can log into
the database system and use it.
This type of DBMS systems are also called Desktop Database systems.
DBMS
• Now if the client after making the desired operation on the desired data wants to write
back the data on the database he will have to send the whole file back to the server, thus
causing a lot of network overhead.
• The Good thing about this approach is that the server does not have lots of actions to do.
CLIENT SERVER
Advantages:
▪ Easy to manage.
▪ Maintenance is very easy.
Disadvantages:
▪ Scalability is very difficult.
▪ Lots of load on server if number of users are increased.
▪ Security issues may arise because client directly connects
database server.
In three tier architecture, another layer is present
in between client and server. This layer contains
Application Server.
First Tier:
▪ Client is present at first tier.
▪ First tier is also called “Client tier”/
“Presentation Layer”.
▪ This tier or layer contains only user interface
part of our application.
▪ The user interface is used to take input from user
and provide data to user.
▪ Client cannot directly communicate with server.
Second Tier:
▪ Application server is present at second tier.
▪ Second tier is also called “Business Tier or
Business Layer”.
▪ This tier act as interface between client layer
and data layer.
▪ When user enters data in user interface, this
data first comes to application server for
processing and specific query is generated
against each request.
▪ This query is sent to database server.
▪ Client layer communicates with database
server/data layer by using business layer.
Third Tier:
▪ Database server is present at third tier.
▪ This tier is also called “Data layer”.
▪ Database server at third tier contains database.
▪ Database server at data layer receives query
from application server, processes this query
and provides output to application layer. This
output is further sent to the user by application
layer.
Examples:
Web applications use 3 Tier Architecture.
Advantages:
▪ Scalability is easy.
▪ Less burden on server.
▪ Security is improved as clients are not directly
connected with server.
Disadvantages:
▪ Management is tough.
▪ Maintenance is difficult.
▪ Complexity is increased.