Database Languages in DBMS

o A DBMS has appropriate languages and interfaces to express database queries and updates.

o Database languages can be used to read, store and update the data in the database.

Types of Database Languages

1. Data Definition Language (DDL)

o DDL stands for Data Definition Language. It is used to define database structure or
pattern.
o It is used to create schema, tables, indexes, constraints, etc. in the database.
o Using the DDL statements, you can create the skeleton of the database.
o Data definition language is used to store the information of metadata like the number of
tables and schemas, their names, indexes, columns in each table, constraints, etc.
Here are some tasks that come under DDL:

o Rollno o name o age o gender o city

 o 1 o a o 12 o m o aur

o 2 o b o 15 o m o aur

o Create: It is used to create objects in the database.

o

o Alter: It is used to alter the structure of the database.

o Drop: It is used to delete objects from the database.
o Truncate: It is used to remove all records from a table.
o Rename: It is used to rename an object.
o Comment: It is used to comment on the data dictionary.

These commands are used to update the database schema that's why they come under Data definition
language.

2. Data Manipulation Language (DML)

DML stands for Data Manipulation Language. It is used for accessing and manipulating data in a
database. It handles user requests.

Here are some tasks that come under DML:

o Select: It is used to retrieve data from a database.

o Insert: It is used to insert data into a table.

o Update: It is used to update existing data within a table.

o Delete: It is used to delete all records from a table.

o Merge: It performs UPSERT operation, i.e., insert or update operations.

o Call: It is used to call a structured query language or a Java subprogram.

o Explain Plan: It has the parameter of explaining data.

o Lock Table: It controls concurrency.

3. Data Control Language (DCL)
o DCL stands for Data Control Language. It is used to retrieve the stored or saved data.

o The DCL execution is transactional. It also has rollback parameters.

(But in Oracle database, the execution of data control language does not have the feature of rolling
back.)

Here are some tasks that come under DCL:

o Grant: It is used to give user access privileges to a database.

o Revoke: It is used to take back permissions from the user.

There are the following operations which have the authorization of Revoke:

CONNECT, INSERT, USAGE, EXECUTE, DELETE, UPDATE and SELECT.

4. Transaction Control Language (TCL)

TCL is used to run the changes made by the DML statement. TCL can be grouped into a logical
transaction.

Here are some tasks that come under TCL:

o Commit: It is used to save the transaction on the database.

o Rollback: It is used to restore the database to original since the last Commit.

ACID Properties in DBMS

DBMS is the management of data that should remain integrated when any changes are done in it. It is
because if the integrity of the data is affected, whole data will get disturbed and corrupted. Therefore, to
maintain the integrity of the data, there are four properties described in the database management
system, which are known as the ACID properties. The ACID properties are meant for the transaction that
goes through a different group of tasks, and there we come to see the role of the ACID properties.

ACID Properties

The expansion of the term ACID defines for:

1) Atomicity

The term atomicity defines that the data remains atomic. It means if any operation is performed on the
data, either it should be performed or executed completely or should not be executed at all. It further
means that the operation should not break in between or execute partially. In the case of executing
operations on the transaction, the operation should be completely executed and not partially.

Example: If Remo has account A having $30 in his account from which he wishes to send $10 to Sheero's
account, which is B. In account B, a sum of $ 100 is already present. When $10 will be transferred to
account B, the sum will become $110. Now, there will be two operations that will take place. One is the
amount of $10 that Remo wants to transfer will be debited from his account A, and the same amount
will get credited to account B, i.e., into Sheero's account. Now, what happens - the first operation of
debit executes successfully, but the credit operation, however, fails. Thus, in Remo's account A, the value
becomes $20, and to that of Sheero's account, it remains $100 as it was previously present.
n the above diagram, it can be seen that after crediting $10, the amount is still $100 in account B. So, it is
not an atomic transaction.

The below image shows that both debit and credit operations are done successfully. Thus the transaction
is atomic.

2) Consistency

The word consistency means that the value should remain preserved always. In DBMS, the integrity of
the data should be maintained, which means if a change in the database is made, it should remain
preserved always. In the case of transactions, the integrity of the data is very essential so that the
database remains consistent before and after the transaction. The data should always be correct.

In the above figure, there are three accounts, A, B, and C, where A is making a transaction T one by one
to both B & C. There are two operations that take place, i.e., Debit and Credit. Account A firstly debits
$50 to account B, and the amount in account A is read $300 by B before the transaction. After the
successful transaction T, the available amount in B becomes $150. Now, A debits $20 to account C, and
that time, the value read by C is $250 (that is correct as a debit of $50 has been successfully done to B).
The debit and credit operation from account A to C has been done successfully. We can see that the
transaction is done successfully, and the value is also read correctly. Thus, the data is consistent. In case
the value read by B and C is $300, which means that data is inconsistent because when the debit
operation executes, it will not be consistent

3) Isolation

The term 'isolation' means separation. In DBMS, Isolation is the property of a database where no data
should affect the other one and may occur concurrently. In short, the operation on one database should
begin when the operation on the first database gets complete. It means if two operations are being
performed on two different databases, they may not affect the value of one another. In the case of
transactions, when two or more transactions occur simultaneously, the consistency should remain
maintained. Any changes that occur in any particular transaction will not be seen by other transactions
until the change is not committed in the memory.

Example: If two operations are concurrently running on two different accounts, then the value of both
accounts should not get affected. The value should remain persistent. As you can see in the below
diagram, account A is making T1 and T2 transactions to account B and C, but both are executing
independently without affecting each other. It is known as Isolation.

4) Durability

Durability ensures the permanency of something. In DBMS, the term durability ensures that the data
after the successful execution of the operation becomes permanent in the database. The durability of
the data should be so perfect that even if the system fails or leads to a crash, the database still survives.
However, if gets lost, it becomes the responsibility of the recovery manager for ensuring the durability of
the database. For committing the values, the COMMIT command must be used every time we make
changes.