DETAILS OF THE EXPERIMENTS CONDUCTED

(TO BE USED BY THE STUDENTS IN THEIR RECORDS)

INDEX

S.No TITLE OF THE EXPERIMENT DATE OF FACULTY

SUBMISSION SIGNATURE

10

5
 PRACTICAL -1

TITLE: ORACLE Installation

1.1 Objective 1.2 Installation

1.1 OBJECTIVE: learn the procedure of ORACLE installation

1.2 ORACLE INSTALLATION:

Installing Oracle Database 11g on Windows

To install the Oracle software, you must use the Oracle Universal installer.

1. For this installation, you need either the DVDs or a downloaded version of the DVDs. In this tutorial, you
install from the downloaded version. From the directory where the DVD files were unzipped, open
Windows Explorer and double-click on setup.exe from the \db\Disk1 directory.
2. The product you want to install is Oracle Database 11g. Make sure the product is selected and click Next.

3. You will perform a basic installation with a starter database. Enter orcl for the Global Database Name
and oracle for Database Password and Confirm Password. Then, click Next

4. Oracle Configuration Manager allows you to associate your configuration information with your Metalink
account. You can choose to enable it on this window. Then, click Next.

8
5. Review the Summary window to verify what is to be installed. Then, click Install.

6. The progress window appears.

7. The Configuration Assistants window appears.

8. Your database is now being created.

9
9. When the database has been created, you can unlock the users you want to use. Click OK.

10. Click Exit. Click Yes to confirm exit.

Testing Your Installation

To test that your installation completed successfully, perform the following steps:

1. Open a browser and enter the following URL:

https://<hostname>:1158/em

10
 where <hostname> should be changed to your machine name, IP address, or localhost.

Because Enterprise Manager Database Control is a secure site, you need a certificate. Select the Accept
this certificate permanently option, and then click OK.

2. Enter system as the User Name and oracle as the Password, and then click Login

3. The Database Control Home Page appears. Your installation was successful.

Another way to work on ORACLE:

1. Gotohttps://www.oracle.com/downloads/index.html
2. Create your login and download latest Express Edition of ORACE and install in simple way
3. Run the ORACLE, It will open in Web Browser
4. Click on Application Express

11
5. Login again and then create a new database user by filling the below entries and click on creating
workspace

6. Login by using your created username and password and start using ORACLE

12
 PRACTICAL -2

TITLE: Creating Entity-Relationship Diagram using case tools

2.1 Objective 2.2 Theory (Installation Día Guide)

2.1 OBJECTIVE: applying tool to create ER model

2.2 THEORY AND CONCEPTS:

Introduction to Dia Diagram Editor:

a. Installation Guide

1. Download the installation file for your platform from http://dia-installer.de/.

2. Open the downloaded file, select preferred installation language, and press “OK”.

3. The Dia “Setup Wizard” window will appear. Click “Next”.

13
4. In the “License Agreement” window click “Next” to continue installation.

5. Choose the components you want to install and click “Next”.

14
6. Choose the installation location on your computer and click “Install”.

7. After the installation process is completed, click “Finish”.

15
b. Dia User Guide

Create an ER Diagram

In this section, basic guidelines are given on how to create ER database diagrams. An ER diagram consists of
entity sets, attributes, and the relationship sets between entity sets. Let us create an ER diagram for a database
called “Courses and Students”. The database will have two main entity sets, i.e., “Course” and “Student”. The
relation between them defines which students belong to which course.

1. Start Dia Diagram Editor.

2. On the left side of the menu click on the dropdown menu, select “Other sheets” and click on “ER”.

17
3. Now the menu consists only of shapes that are relevant to an ER diagram.

4. Let us create an entity called “Course”. Choose the “E” icon with a single frame in the shapes menu and
click on the drawing space at the center. A rectangle with the name “Entity” will appear.

18
5. Double-click on the new entity set and the properties window will show up (or right-click and choose
“Properties”). Change the name of the entity set to “Course” and click “OK”. The entity sets name will be
changed.

6. The “Course” entity set has several attributes: “courseId” (primary key), “title”, “ECTS”, “level”,
“language”. In the shape menu select the “A” icon with an oval around it and click near the created
“Course” entity set. An oval with the name “Attribute” will appear.

19
7. Double-click on the attribute and in the properties window change the name to “courseId”. Since this
attribute is also a primary key, select “Key” value “Yes”. Click “OK”.

8. In the shape menu click on the “Participation” icon and connect the entity set with the attribute.

20
9. It is also possible to connect an entity set with an attribute using different connectors. Choose the
appropriate style at the end of a new connector by clicking on “arrow style at the end of the line new
lines”. Select “line (L)” connector.

10. Proceed with the rest of the attributes of the entity set “Course”.

21
11. Attributes of the “Student” entity set are: “studentId”, “firstName”, “lastName”, “startDate”.

12. Create the relationship set between “Course” and “Student” with the name “Belongs” that also
has an attribute “signUpDate”. In the shape menu select “R” with a diamond around it and click
between the two entity sets in the drawing area.

4
13. Change the name to “Belongs” and assign attribute “signUpDate” to it.

The ER diagram for database “Courses and Students” was created successfully!

Note: saveyour diagram several times through all the creation process!

Export Created Diagram

1. Open the diagram you want to export.

2. Click on “File > Export“. Enter the name of the file, select the location you want the file to be
saved, determine file type (e.g. JPG), and click “Save”.

5
 PRACTICAL -3

TITLE : CREATING TABLES, INSERT INTO TABLES & SELECT FROM TABLES

3.1 Objective 3.2Theory and concepts

3.1 OBJECTIVE: Create tables and specify the queries in SQL

3.2 THEORY& CONCEPTS:

Introduction about SQL-
SQL (Structured Query Language) is a nonprocedural language, you specify what you want, not how
to get it. A block structured format of English key words is used in this query language. It has the
following components.

DDL (Data Definition Language)-

The SQL DDL provides command for defining relation schemas, deleting relations and modifying
relation schema.

DML (DATA Manipulation Language)-

It includes commands to insert tuples into, delete tuples from and modify tuples in the database.

View definition-
The SQL DDL includes commands for defining views.
Transaction Control- SQL includes for specifying the beginning and ending of transactions.

Embedded SQL and Dynamic SQL-

Embedded and Dynamic SQL define how SQL statements can be embedded with in general purpose
programming languages, such as C, C++, JAVA, COBOL, Pascal and Fortran.

Integrity-
The SQL DDL includes commands for specifying integrity constraints that the data stored in the
database must specify. Updates that violate integrity constraints are allowed.

Authorization-
The SQL DDL includes commands for specifying access rights to relations and views.

Data Definition Language-

The SQL DDL allows specification of not only a set of relations but also information about each relation,
including-
• Schema for each relation
• The domain of values associated with each attribute.
• The integrity constraints.
• The set of indices to be maintained for each relation.
• The security and authorization information for each relation.
• The physical storage structure of each relation on disk.

6
Domain types in SQL-

The SQL standard supports a variety of built in domain types, including-

• Char (n)- A fixed length character length string with user specified length .
• Varchar (n)- A variable character length string with user specified maximum length n.
• Int- An integer.
• Small integer- A small integer.
• Numeric (p, d)-A Fixed point number with user defined precision.
• Real, double precision- Floating point and double precision floating point numbers with
machine dependent precision.
• Float (n)- A floating point number, with precision of at least n digits.
• Date- A calendar date containing a (four digit) year, month and day of the month.
• Time- The time of day, in hours, minutes and seconds Eg. Time ’09:30:00’.
• Number- Number is used to store numbers (fixed or floating point).

DDL statement for creating a table-

Syntax-
Create table tablename
(columnnamedatatype(size), columnnamedatatype(size));

Creating a table from a table-

Syntax-
CREATE TABLE TABLENAME
[(columnname, columnname, ………)]
AS SELECT columnname, columnname… .... FROM tablename;

Insertion of data into tables-

Syntax-
INSERT INTO tablename
[(columnname, columnname, ………)]
Values(expression, expression);

Inserting data into a table from another table:

Syntax-
INSERT INTO tablename
SELECT columnname, columnname, …….
FROM tablename;

Insertion of selected data into a table from another table:

Syntax-
INSERT INTO tablename
SELECT columnname, columnname……..
FROM tablename
WHERE columnname= expression;

7
Retrieving of data from the tables-

Syntax-
SELECT * FROM tablename;

The retrieving of specific columns from a table-

Syntax-
SELECT columnname, columnname, ….
FROM tablename;

Elimination of duplicates from the select statement-

Syntax-
SELECT DISTINCT columnname, columnname
FROM tablename;

Selecting a data set from table data-

Syntax-
SELECT columnname, columnname
FROM tablename
WHERE searchcondition;

Practical Tasks:

1. Create the following tables:

i) client_master

columnname datatype size

client_no varchar2 6
name varchar2 20
address1 varchar2 30
address2 varchar2 30
city varchar2 15
state varchar2 15
pincode number6
bal_due number10,2

ii) Product_master
Columnname datatype size
Product_no varchar2 6
Description varchar2 20
Profit_percent number 10,2
Unit_measure varchar2 10
Qty_on_hand number 10
Reoder_lvl number 10
Sell_price number 10
Cost_price number 10

8
2- Insert the following data into their respective tables:

Clientno Name city pincode state bal.due

0001 Ivan Bombay 400054 Maharashtra 15000

0002 Vandana Madras 780001 Tamilnadu 0
0003 Pramada Bombay 400057 Maharashtra 5000
0004 Basu Bombay 400056 Maharashtra 0
0005 Ravi Delhi 100001 Delhi 2000
0006 Rukmini Bombay 400050 Maharashtra 0

Data for Product Master:

Product No. Desciption Profit % Unit Qty Reorder Sell Cost

Percent measured on hand lvl price
price

P00001 1.44floppies 5 piece 100 20 525 500

P03453 Monitors 6 piece 10 3 12000 11200
P06734 Mouse 5 piece 20 5 1050 500
P07865 1.22 floppies 5 piece 100 20 525 500
P07868 Keyboards 2 piece 10 3 3150 3050
P07885 CD Drive 2.5 piece 10 3 5250 5100
P07965 540 HDD 4 piece 10 3 8400 8000
P07975 1.44 Drive 5 piece 10 3 1050 1000
P08865 1.22 Drive 5 piece 2 3 1050 1000

3:- On the basis of above two tables answer the following queries:
i) Find out the names of all the clients.
ii) Retrieve the list of names and cities of all the clients.
iii) List the various products available from the product_master table.
iv) List all the clients who are located in Bombay.
v) Display the information for client no 0001 and 0002.
vi) Find the products with description as ‘1.44 drive’ and ‘1.22 Drive’.
vii) Find all the products whose sell price is greater then 5000.
viii) Find the list of all clients who stay in in city ‘Bombay’ or city ‘Delhi’ or ‘Madras’.
ix) Find the product whose selling price is greater than 2000 and less than or equal to 5000.
x) List the name, city and state of clients not in the state of ‘Maharashtra’.

9
SOLUTION :

1. Create the following tables:

(i) create table client_master
( client_no varchar2(6),
name varchar2(20),
address1 varchar2(30),
address2 varchar2(30),
city varchar2(15),
state varchar2(15),
pincode number(6),
bal_due number(10,2));

(ii) create table product_master

( product_no varchar2(6),
Description varchar2(20),
Profit_percentnumber(10,2),
Unit_measurevarchar2(10),
Qty_on_handnumber(10),
Reorder_level_numbernumber(10),
Sell_pricenumber(10),
Cost_price_numbernumber(10));

2. Insert the following data into their respective tables:

(i) Insert into client_master
Values(‘0001’,’ivan’,’bombay’,’maharastra’,’201001’,’15000’);

(ii) Insert into product_master

Values(‘P00001’,’1.44floppies’,’5’,’piece’,’100’,’20’,’525’,’500’);

3. Solutions
i. select name from client_master;
ii. select name, city from client_master;
iii. select description from product_master;
iv. select * from client_master where city = ‘bombay’;
v. select * from client_master where client_no = ‘0001’ orclient_no = ‘ ‘0002’;
vi. select * from product_master where description=’1.44 drive’ or ‘1.22 drive’;
vii. select * from product_master where sell_price> 5000;
viii. select * from client_master where city = ‘bombay’ or city = ‘madras’;
ix. select * from product_master where sell_price> 2000 and sell_price<= 5000;
x. select name, city , state from client_master where state not in (‘maharastra’);

10
TITLE :DATA MANIPULATION LANGUAGE

3.1 Objective 3.2 Theory and concepts

3.1 OBJECTIVE:Perform manipulation operations on created tables.

3.2 THEORY AND CONCEPTS:DML ( Data Manipulation Language) Data manipulation is

• The retrieval of information stored in the database.

• The insertion of new information into the database.
• The deletion of information from the database.
• The modification of information stored by the appropriate data model. There are basically two
types.
(i) Procedural DML:- require a user to specify what data are needed and how to get those
data.
(ii) Non Procedural DML : require a user to specify what data are needed without specifying
how to get those data.

Updating the content of a table:

In creation situation we may wish to change a value in table without changing all values in the tuple .
For this purpose the update statement can be used.

Update table name

Set columnname = experision, columnname =expression……
Where columnname = expression;

Deletion Operation:-
A delete request is expressed in much the same way as query. We can delete whole tuple ( rows) we
can delete values on only particulars attributes.

Deletion of all rows

Syntax:
Delete from tablename :

Deletion of specified number of rows

Syntax:

Delete from table name

Where search condition ;

Computation in expression lists used to select data

+ Addition - Subtraction
* multiplication ** exponentiation
/ Division () Enclosed operation

11
Renaming columns used with Expression Lists: - The default output column names can be renamed by
the user if required

Syntax:

Select column name result_columnname,

Columnname result_columnname,
From table name;

Logical Operators:
The logical operators that can be used in SQL sentenced are

AND all of must be included

OR any of may be included
NOT none of could be included

Range Searching: Between operation is used for range searching.

Pattern Searching:
Themost commonly used operation on string is pattern matching using the operation ‘like’ we describe
patterns by using two special characters.

• Percent (%) ; the % character matches any substring we consider the following examples.
• ‘Perry %’ matches any string beginning with perry
• ‘% idge % matches any string containing’ idge as substring.
• ‘ - - - ‘ matches any string exactly three characters.
• ‘ - - - % matches any string of at least of three characters.

Oracle functions:
Functions are used to manipulate data items and return result. function follow the format of function
_name (argument1, argument2 ..) .An arrangement is user defined variable or constant. The structure
of function is such that it accepts zero or more arguments.
Examples:
Avg return average value of n

Syntax:
Avg ([distinct/all]n)
Min return minimum value of expr.

Syntax:
MIN((distict/all )expr)
Count Returns the no of rows where expr is not null

Syntax:

Count ([distinct/all)expr]
Count (*) Returns the no rows in the table, including duplicates and those with nulls.
Max Return max value of expr

12
Syntax:

Max ([distinct/all]expr)
Sum Returns sum of values of n

Syntax:
Sum ([distinct/all]n)

Sorting of data in table

Syntax:
Select columnname, columnname
From table
Order by columnname;

Practical Tasks:

1 Using the table client master and product master answer the following queries.

i. Change the selling price of ‘1.44 floppy drive to Rs.1150.00

ii. Delete the record with client 0001 from the client master table.
iii. Change the city of client_no’0005’ to Bombay.
iv. Change the bal_due of client_no ‘0001, to 1000.
v. Find the products whose selling price is more than 1500 and also find the new selling price as
original selling price *15.
vi. Find out the clients who stay in a city whose second letter is a.
vii. Find out the name of all clients having ‘a’ as the second letter in their names.
viii. List the products in sorted order of their description.
ix. Count the total number of orders
x. Calculate the average price of all the products.
xi. Calculate the minimum price of products.
xii. Determine the maximum and minimum prices . Rename the tittle as ‘max_price’ and
min_price respectively.
xiii. Count the number of products having price greater than or equal to 1500.

SOLUTION:

i. update table client_master set sell_price = ‘1150’ where description=’1.44 drive’;

ii. Delete from client_master where client_no = ‘0001’;
iii. update table client_master set city=’bombay’ where client_no=’0001’;
iv. update table client_master set bal_due=1000 where client_no=’0001’;
v. select description from product_master where sell_price> 1500;
vi. select sell_price*15 “New Selling Price” from product_master;
vii. select * from client_master where city like ‘_a%’;
viii. select name from client_master where name=’_a%’;
ix. select * from product_master order by description;
x. select count(*) from product_master;
xi. select avg(sell_price) from product_master;
xii. select min(sell_price) from product_master;
xiii. select max(sell_price) “Max_price” , min(sell_price) “Min_price”;
xiv. select count(*) from product_master where sell_price>= 1500;

13
TITLE:TO IMPLEMENT CONSTRAINTS ON TABLES.

3.1 Objective 3.2 Theory and concepts

3.1 OBJECTIVE: applying constraints on the columns

3.2 THEORY AND CONCEPTS:

Data constraints: Besides the cell name, cell length and cell data type there are other parameters i.e.
other data constrains that can be passed to the DBA at check creation time. The constraints can either
be placed at column level or at the table level.

i. Column Level Constraints: If the constraints are defined along with the column definition, it
is called a column level constraint.
ii. Table Level Constraints: If the data constraint attached to a specify cell in a table reference
the contents of another cell in the table then the user will have to use table level constraints.

Null Value Concepts:-while creating tables if a row locks a data value for particular column that value
is said to be null . Column of any data types may contain null values unless the column was defined as
not null when the table was created

Syntax:

Create table tablename

(columnname data type (size) not null ……)

Primary Key: primary key is one or more columns is a table used to uniquickly identity each row in the
table. Primary key values must not be null and must be unique across the column. A multicolumn
primary key is called composite primary key.

Syntax: primary key as a column constraint

Create table tablename
(columnnamedatatype (size) primary key,….)

Primary key as a table constraint

Create table tablename
(columnnamedatatype (size), columnnamedatatype( size)…
Primary key (columnname,columnname));

Unique key concept:-A unique is similar to a primary key except that the purpose of a unique key is
to ensure that information in the column for each record is unique as with telephone or devices license
numbers. A table may have many unique keys.

Syntax: Unique as a column constraint.

Create table table name
(columnnamedatatype (size) unique);

Unique as table constraint:

Create table tablename
(columnnamedatatype (size),columnnamedatatype (size)…unique (columnname,columnname));

14
Default value concept: At the line of cell creation a default value can be assigned to it. When the user
is loading a record with values and leaves this cell empty, the DBA wil automatically load this cell with
the default value specified. The data type of the default value should match the data type of the
column

Syntax:

Create table tablename

(columnnamedatatype (size) default value,….);

Foreign Key Concept :Foreign key represents relationship between tables. A foreign key is column
whose values are derived from the primary key of the same of some other table .the existence of
foreign key implies that the table with foreign key is related to the primary key table from which the
foreign key is derived .A foreign key must have corresponding primary key value in the primary key
table to have meaning.
Foreign key as a column constraint

Syntax :
Create table table name
(columnnamedatatype (size) references another table name);

Foreign key as a table constraint:

Syntax :
Create table name
(columnnamedatatype (size)….
primary key (columnname);
foreign key (columnname)references table name);

Check Integrity Constraints: Use the check constraints when you need to enforce intergrity rules that
can be evaluated based on a logical expression following are a few examples of appropriate check
constraints.
• A check constraints name column of the coient_master so that the name is entered
in upper case.
• A check constraint on the client_no column of the client _master so that no client_no
value starts with ‘c’

Syntax:
Create table tablename
(columnnamedatatype (size) CONSTRAINT constraintname)
Check (expression));

Practical Tasks :
1 Create the following tables:
i. Sales_master
Columnname Datatype Size Attributes
Salesman_no varchar2 6 Primary key/first letter
must start with ‘S’
Sal_name varchar2 20 Not null

15
Address varchar2 Not null
City varchar2 20
State varchar2 20
Pincode Number 6
Sal_amt Number 8,2 Not null, cannot be 0
Tgt_to_get Number 6,2 Not null, cannot be 0
Ytd_sales Number 6,2 Not null, cannot be 0
Remarks Varchar2 30

ii. Sales_order
Columnname Datatype Size Attributes
S_order_no varchar2 6 Primary/first letter must be 0
S_order_date Date 6 Primary key reference clientno of
client_master table
Client_no Varchar2 25
Dely_add Varchar2 6
Salesman_no Varchar2 6 Foreign key references
salesman_no of salesman_master
table
Dely_type Char 1 Delivery part(p)/full(f),default f
Billed_yn Char 1
Dely_date Date Can not be lessthans_order_date
Order_status Varchar2 10 Values (‘in process’;’fulfilled’;back
order’;’canceled

I. Sales_order_details
Column Datatype Size Attributes

S_order_no Varchar2 6 Primary key/foreign

key references
s_order_no of
sales_order
Product_no Varchar2 6 Primary key/foreign
key references
product_no of
product_master
Qty_order Number 8
Qty_disp Number 8
Product_rate Number 10,2

Insert the following data into their respective tables using insert statement:
Data for sales_man master table

Salesman_n Salesma Address City Pin code State Salamt Tgt_to_ Ytd Rema
o n name get Sales rk

16
 S00001 Kiran A/14 Bom 400002 Mah 3000 100 50 Good
worli bay
S00002 Manish 65,narim Bom 400001 Mah 3000 200 100 Good
an bay
S00003 Ravi P-7 Bom 400032 Mah 3000 200 100 Good
Bandra bay
S00004 Ashish A/5 Juhu Bom 400044 Mah 3500 200 150 Good
bay

(ii)
Data for salesorder table:
S_orderno S_orderdate Client no Dely Bill Salesman no Delay Orderstat
type yn date us
019001 12-jan-96 0001 F N 50001 20-jan- Ip
96
019002 25-jan-96 0002 P N 50002 27-jan- C
96
016865 18-feb-96 0003 F Y 500003 20-feb- F
96
019003 03-apr-96 0001 F Y 500001 07-apr- F
96
046866 20-may-96 0004 P N 500002 22-may- C
96
010008 24-may-96 0005 F N 500004 26-may- Ip
96

(iii)(iii)
Data for sales_order_details table:

S_order no Product no Qty ordered Qtydisp Product_rate

019001 P00001 4 4 525
019001 P07965 2 1 8400
019001 P07885 2 1 5250
019002 P00001 10 0 525
046865 P07868 3 3 3150
046865 P07885 10 10 5250
019003 P00001 4 4 1050
019003 P03453 2 2 1050
046866 P06734 1 1 12000
046866 P07965 1 0 8400
010008 P07975 1 0 1050
010008 P00001 10 5 525

17
SOLUTION :

1. create the following tables:

(i) Create table sales_master
(salesman_novarchar2(6) primary key check salesman_no in ‘S%’,
sal_namevarchar2(20) not null,
address varchar2(20) not null,
city varchar2(20),
state varchar2(20),
pincode number(8),
sal_amt number(8,2) not null check(sal_amt>0),
tgt_to get number(6,2) not null check(sal_amt>0),
ytd_sales number(6,2) not null check(sal_amt>0),
remarks varchar2(30));

(ii) create table sales_order

s_order_novarchar2(6) primary key check s_order_no in ‘0%’,
s_order_date date,
client_novarchar2(25),
dely_addvarchar2(6),
salesman_novarchar2(6) foreign key references salesman_no(sales_master),
dely_type char(1) check delt_type in ‘p’ or ‘f’ default ‘f’,
billed_yn char(1),
dely_date date check not in(dely_date<order_date),
order_statusvarchar2(10) check order_status in (‘in_process’ or ‘fulfilled’ or ‘back_order’ or
‘canceled’));

2. Insert the following data into their respective tables using insert statement:
(i) Insert into sales_master
Values(‘S0001’,’kiran’,’a/14 worli’,’bombay ’,’400002 ’,’mah ’,’3000 ’,’100 ’,’50 ’,’good’);

(ii) Insert into sales_order

Values(‘019001’,’12-jan-96’,’0001 ’,’F ’,’N ’,’50001 ’,’20-jan-96’,’IP’);

18
TITLE : MODIFYING THE STRUCTURES OF THE TABLE.

3.1 Objective 3.2 Theory and concepts

3.1 OBJECTIVE:Use of Alter table statements

3.2 THEORY AND CONCEPTS: Modifying the Structure of Tables- Alter table command is used to
changing the structure of a table. Using the alter table clause you cannot perform the following
tasks:

(i) change the name of table

(ii) change the name of column
(iii) drop a column
(iv) decrease the size of a table if table data exists.

The following tasks you can perform through alter table command.

(i) Adding new columns:

Syntax
ALTER TABLE tablename
ADD (newcolumnnamenewdatatype (size));

(ii) Modifying existing table

Syntax:
ALTER TABLE tablename
MODIFY (newcolumnnamenewdatatype (size));

NOTE: Oracle not allow constraints defined using the alter table, if the data in the table, violates
such constraints.

Removing/Deleting Tables- Following command is used for removing or deleting a table.

Syntax:
DROP TABLE tabename:

Defining Integrity constraints in the ALTER TABLE command-

You can also define integrity constraints using the constraint clause in the ALTER TABLE command.
The following examples show the definitions of several integrity constraints.

(1) Add PRIMARY KEY-

Syntax:
ALTER TABLE tablename
ADD PRIMARY KEY(columnname);

(2) Add FOREIGN KEY-

Syntax:
ALTER TABLE tablename
ADD CONSTRAINT constraintname
FOREIGN KEY(columnname) REFERENCES tablename;
Droping integrity constraints in the ALTER TABLE command:

19
You can drop an integrity constraint if the rule that if enforces is no longer true or if the constraint is
no longer needed. Drop the constraint using the ALTER TABLE command with the DROP clause. The
following examples illustrate the droping of integrity constraints.

(1) DROP the PRIMARY KEY-

Syntax:
ALTER TABLE tablename
DROP PRIMARY KEY

(2) DROP FOREIGN KEY-

Syntax:
ALTER TABLE tablename
DROP CONSTRAINT constraintname;

Practical Tasks :

Que 1. Create the following tables:

Challan_Header
Column name data type size Attributes
Challan_no varchar2 6 Primary key
s_order_no varchar2 6 Foreign key references s_order_no of
sales_order table
challan_date date not null
billed_yn char 1 values (‘Y’,’N’). Default ‘N’

Table Name :Challan_Details

Column name data type size Attributes
Challan_no varchar2 6 Primary key/Foreign key references
Product_no of product_master
Qty_disp number 4,2 not null

2. Insert the following values into the challan header and challan_details tables:

(i) Challan No S_order No Challan Date Billed

CH9001019001 12-DEC-95 Y
CH865 046865 12-NOV-95 Y
CH3965010008 12-OCT-95 Y

Data for challan_details table

Challan No Product No Qty_Disp

CH9001 P00001 4
CH9001 P07965 1
CH9001 P07885 1
CH6865 P07868 3
CH6865 P03453 4
CH6865 P00001 10

20
CH3965 P00001 5
CH3965 P07975 2

1. Make the primary key to client_no in client_master.

2. Add a new column phone_no in the client_master table.
3. Add the not null constraint in the product_master table with the columns description, profit
percent , sell price and cost price.
4. Change the size of client_no field in the client_master table.
5. Select product_no, description where profit percent is between 20 and 30 both inclusive.

SOLUTION:

1. Create the following tables:

Create table challan_header (
Chalan_novarchar2(6) primary key,
S_order_novarchar2(6) foreign key references s_order_no(sales_order),
Challan_date date not null,
Billed_ynchar(i) check billed_yn in (‘Y’ or ‘N’) default ‘N’);

create table challan_details(

challan_novarchar2(6) primary key foreign key references product_no(product_master),
qty_disp number(4,2) not null);

2. Insert the following values into the challan header and challan_details tables:
Insert into challan_header
Values(‘ch9001’,’019001’,’12-dec-95’,’Y’);

Insert into challan_details

Values(‘ch9001’,’p00001’,’4’);

21
 PRACTICAL - 4

TITLE :Normalization

4.1 Objective 4.2 Theory and concepts

4.1 OBJECTIVE: Use of Normalization

4.2 THEORY AND CONCEPTS: Normalization is the process of organizing data in a database. This
includes creating tables and establishing relationships between those tables according to rules
designed both to protect the data and to make the database more flexible by eliminating redundancy
and inconsistent dependency.

Redundant data wastes disk space and creates maintenance problems. If data that exists in more than
one place must be changed, the data must be changed in exactly the same way in all locations. A
customer address change is much easier to implement if that data is stored only in the Customers
table and nowhere else in the database.

What is an "inconsistent dependency"? While it is intuitive for a user to look in the Customers table
for the address of a particular customer, it may not make sense to look there for the salary of the
employee who calls on that customer. The employee's salary is related to, or dependent on, the
employee and thus should be moved to the Employees table. Inconsistent dependencies can make
data difficult to access because the path to find the data may be missing or broken.

There are a few rules for database normalization. Each rule is called a "normal form." If the first rule
is observed, the database is said to be in "first normal form." If the first three rules are observed, the
database is considered to be in "third normal form." Although other levels of normalization are
possible, third normal form is considered the highest level necessary for most applications.

As with many formal rules and specifications, real world scenarios do not always allow for perfect
compliance. In general, normalization requires additional tables and some customers find this
cumbersome. If you decide to violate one of the first three rules of normalization, make sure that your
application anticipates any problems that could occur, such as redundant data and inconsistent
dependencies.

The following descriptions include examples.

First normal form

• Eliminate repeating groups in individual tables.

• Create a separate table for each set of related data.
• Identify each set of related data with a primary key.

Do not use multiple fields in a single table to store similar data. For example, to track an inventory
item that may come from two possible sources, an inventory record may contain fields for Vendor
Code 1 and Vendor Code 2.

22
What happens when you add a third vendor? Adding a field is not the answer; it requires program and
table modifications and does not smoothly accommodate a dynamic number of vendors. Instead,
place all vendor information in a separate table called Vendors, then link inventory to vendors with an
item number key, or vendors to inventory with a vendor code key.

Second normal form

• Create separate tables for sets of values that apply to multiple records.
• Relate these tables with a foreign key.

Records should not depend on anything other than a table's primary key (a compound key, if
necessary). For example, consider a customer's address in an accounting system. The address is
needed by the Customers table, but also by the Orders, Shipping, Invoices, Accounts Receivable, and
Collections tables. Instead of storing the customer's address as a separate entry in each of these
tables, store it in one place, either in the Customers table or in a separate Addresses table.

Third normal form

• Eliminate fields that do not depend on the key.

Values in a record that are not part of that record's key do not belong in the table. In general, anytime
the contents of a group of fields may apply to more than a single record in the table, consider placing
those fields in a separate table.

For example, in an Employee Recruitment table, a candidate's university name and address may be
included. But you need a complete list of universities for group mailings. If university information is
stored in the Candidates table, there is no way to list universities with no current candidates. Create
a separate Universities table and link it to the Candidates table with a university code key.

EXCEPTION: Adhering to the third normal form, while theoretically desirable, is not always practical.
If you have a Customers table and you want to eliminate all possible interfield dependencies, you must
create separate tables for cities, ZIP codes, sales representatives, customer classes, and any other
factor that may be duplicated in multiple records. In theory, normalization is worth pursing. However,
many small tables may degrade performance or exceed open file and memory capacities.

It may be more feasible to apply third normal form only to data that changes frequently. If some
dependent fields remain, design your application to require the user to verify all related fields when
any one is changed.

Other normalization forms

Fourth normal form, also called Boyce Codd Normal Form (BCNF), and fifth normal form do exist, but
are rarely considered in practical design. Disregarding these rules may result in less than perfect
database design, but should not affect functionality.

Normalizing an example table

These steps demonstrate the process of normalizing a fictitious student table.

1. Unnormalized table:

23
 Student# Advisor Adv-Room Class1 Class2 Class3
1022 Jones 412 101-07 143-01 159-02
4123 Smith 216 101-07 143-01 179-04

2. First normal form: No repeating groups

Tables should have only two dimensions. Since one student has several classes, these classes
should be listed in a separate table. Fields Class1, Class2, and Class3 in the above records are
indications of design trouble.

Spreadsheets often use the third dimension, but tables should not. Another way to look at this
problem is with a one-to-many relationship, do not put the one side and the many side in the
same table. Instead, create another table in first normal form by eliminating the repeating
group (Class#), as shown below:

Student# Advisor Adv-Room Class#

1022 Jones 412 101-07
1022 Jones 412 143-01
1022 Jones 412 159-02
4123 Smith 216 101-07
4123 Smith 216 143-01
4123 Smith 216 179-04

3. Second normal form: Eliminate redundant data

Note the multiple Class# values for each Student# value in the above table. Class# is not
functionally dependent on Student# (primary key), so this relationship is not in second normal
form.

The following tables demonstrate second normal form:

Students:

Student# Advisor Adv-Room

1022 Jones 412
4123 Smith 216

Registration:

Student# Class#
1022 101-07
1022 143-01
1022 159-02
4123 101-07
4123 143-01
4123 179-04

4. Third normal form: Eliminate data not dependent on key

24
In the last example, Adv-Room (the advisor's office number) is functionally dependent on the
Advisor attribute. The solution is to move that attribute from the Students table to the Faculty
table, as shown below:

Students:

Student# Advisor
1022 Jones
4123 Smith

Faculty:

Name Room Dept

Jones 412 42
Smith 216 42

25
 PRACTICAL – 5

TITLE: Creating CURSOR

5.1 Objective 5.2 Theory and concepts

5.1 OBJECTIVE: Use of cursor

5.2 THEORY AND CONCEPTS:

The central purpose of the Oracle PL/SQL language is to make it as easy and efficient as possible to
query and change the contents of tables in a database. You must, of course, use the SQL language to
access tables, and each time you do so, you use a cursor to get the job done. A cursor is a pointer to a
private SQL area that stores information about the processing of a SELECT or data manipulation
language (DML) statement (INSERT, UPDATE, DELETE, or MERGE). Cursor management of DML
statements is handled by Oracle Database, but PL/SQL offers several ways to define and manipulate
cursors to execute SELECT statements.

SELECT-INTO offers the fastest and simplest way to fetch a single row from a SELECT
statement. The syntax of this statement is
SELECT select_list INTO variable_list FROM remainder_of_query;
EXAMPLE:
Get the last name for a specific employee ID (the primary key in the employees table):
DECLARE
l_last_nameemployees.last_name%TYPE;
BEGIN
SELECT last_name
INTO l_last_name
FROM employees
WHERE employee_id = 138;

DBMS_OUTPUT.put_line (
l_last_name);
END;
Fetch an entire row from the employees table for a specific employee ID:
DECLARE
l_employeeemployees%ROWTYPE;
BEGIN
SELECT *
INTO l_employee
FROM employees
WHERE employee_id = 138;

DBMS_OUTPUT.put_line (
l_employee.last_name);
END;

26
Using the Cursor FOR Loop
The cursor FOR loop is an elegant and natural extension of the numeric FOR loop in PL/SQL. With a
numeric FOR loop, the body of the loop executes once for every integer value between the low and
high values specified in the range. With a cursor FOR loop, the body of the loop is executed for each
row returned by the query.
The following block uses a cursor FOR loop to display the last names of all employees in
department 10:
BEGIN
FOR employee_rec IN (
SELECT *
FROM employees
WHERE department_id = 10)
LOOP
DBMS_OUTPUT.put_line (
employee_rec.last_name);
END LOOP;
END;

5.3 Example for practice

EXAMPLE:

BEGIN
updateabcd set no=22 where name='ramDA';
if SQL%FOUND then
dbms_output.put_line('success');
else
dbms_output.put_line('failed');
end if;
end;

DECLARE
ROWS_AFFECTED CHAR(4);
BEGIN
updateabcd set no=23 where name='ram';
ROWS_AFFECTED :=TO_CHAR(SQL%ROWCOUNT);
if SQL%ROWCOUNT>0 then
dbms_output.put_line(ROWS_AFFECTED ||'success');
else
dbms_output.put_line('failed');
end if;
end;

27
 PRACTICAL – 6

TITLE: Creating Procedure and Functions

6.1 Objective 6.2 Theory and concepts

6.1 OBJECTIVE: learning of procedure and functions in SQL

6.2 THEORY AND CONCEPTS:

A procedure is a block that can take parameters (sometimes referred to as arguments) and be invoked.
Procedures promote reusability and maintainability. Once validated, they can be used in number of
applications. If the definition changes, only the procedure are affected, this greatly simplifies
maintenance. Modularized program development:
✓ Group logically related statements within blocks.
✓ Nest sub-blocks inside larger blocks to build powerful programs.
✓ Break down a complex problem into a set of manageable well defined logical modules and
implement the modules with blocks.

Procedure and function blocks:

Procedure:
- No return.
- PROCEDURE name IS
Function:
- Returns a value
- FUNCTION name RETURN data-type IS
Syntax for procedure:
Create [or Replace] PROCEDURE procedur_name
(parameter1 [model1] datatype1,
(parameter2 [model2] datatype2,
…)
IS|AS
PL/SQL Block;

Example:
Create [or Replace] PROCEDURE leave_emp
(v_id IN emp.empno%TYPE)
IS
BEGIN
DELETE FROM emp
WHERE empno=v_id;
END leave_emp;

Syntax for function:

Create [or Replace] function function_name
(parameter1 [model1] datatype1,
(parameter2 [model2] datatype2,
…) return type
IS|AS
PL/SQL Block;

28
Example:
Create [or Replace] PROCEDURE leave_emp
(v_id IN emp.empno%TYPE)
IS
BEGIN
DELETE FROM emp
WHERE empno=v_id;
END leave_emp;

6.3 Example for practice

PROCEDURE FOR GCD NUMBERS

SQL> create or replace procedure pro
is
a number(3);
b number(3);
c number(3);
d number(3);
begin
a:=&a;
b:=&b;
if(a>b) then
c:=mod(a,b);
if(c=0) then
dbms_output.put_line('GCD is');
dbms_output.put_line(b);
else
dbms_output.put_line('GCD is');
dbms_output.put_line(c);
end if;
else d:=mod(b,a);
if(d=0) then
dbms_output.put_line('GCD is');
dbms_output.put_line(a);
else
dbms_output.put_line('GCD is');
dbms_output.put_line(d);
end if;
end if;
end;
/

Enter value for a: 8

old 8: a:=&a;
new 8: a:=8;
Enter value for b: 16
old 9: b:=&b;
new 9: b:=16;
Procedure created.

SQL> set serveroutput on;

SQL> execute pro;
GCD is 8

29
PL/SQL procedure successfully completed.

IMPLEMENTATION OF FACTORIAL USING FUNCTION

SQL>create function fnfact(n number)
return number is
b number;
begin
b:=1;
for i in 1..n
loop
b:=b*i;
end loop;
return b;
end;
/

SQL>Declare
n number:=&n;
y number;
begin
y:=fnfact(n);
dbms_output.put_line(y);
end;
/

Function created.

Enter value for n: 5

old 2: n number:=&n;
new 2: n number:=5;
120

PL/SQL procedure successfully completed.

Create a procedure which generate all the prime numbers below the given number
and count the no.of prime numbers.

Create or replace procedure prime_proc(n IN number,tot OUT number) as

i number;
c number;
j number;
Begin
i:=1;
tot:=0;
while(i<=n)
loop
j:=1;
c:=0;
while(j<=i)

30
loop
if(mod(I,j)=0) then
c:=c+1;
end if;
j:=j+1;
end loop;
if(c=2) then
dbms_output.put_line(i);
tot:=tot+1;
end if;
i:=i+1;
end loop;
end;
/
Sql>procedure created.
declare
t number;
begin
prime_proc(10,t);
dbms_output.put_line(‘the total prime no .are’||t);
end;

Valid Test Data:

sql>set serveroutput on

OUTPUT
sql>/
2
3
5
7
The total prime no.are 4

31
 PRACTICAL – 7

TITLE: Creating Packages and triggers

7.1 Objective 7.2 Theory and concepts

7.1 OBJECTIVE: learning of packages and triggers in SQL

7.2 THEORY AND CONCEPTS: Packages are PL/SQL constructs that enable the grouping of related
PL/SQL objects, such as procedures, variables, cursors, functions, constants, and type declarations.
Informix Dynamic Server does not support the package construct.

A package can have two parts: a specification and a body. The specification defines a list of all objects
that are publicly available to the users of the package. The body defines the code that is used to
implement these objects, such as, the code behind the procedures and functions used within the package.

The general PL/SQL syntax for creating a package specification is:

CREATE [OR REPLACE] PACKAGE package_name {IS | AS}

procedure_specification
..function_specification
..variable_declaration
..type_definition
..exception_declaration
..cursor_declaration
END [package_name];

The general PL/SQL syntax for creating a package body is:

CREATE [OR REPLACE] PACKAGE BODY package_name {IS | AS}

..procedure_definition
..function_definition
..private_variable_declaration
..private_type_definition
..cursor_definition
[BEGIN
executable_statements
[EXCEPTION
..exception_handlers]]
END [package_name];

The package body is optional. If the package contains only variable, cursor and type definitions then
the package body is not required.

As the package specification is accessible to users of the package, it can be used to define global variable
definitions within PL/SQL.

32
The Migration Workbench automatically creates packages during the conversion process for the
following reasons:

• The Utilities package, which is used to emulate built-in Informix Dynamic Server functions, is
not available in Oracle.

• Packages have to be created to emulate Informix Dynamic Server GLOBAL variable

definitions.

A trigger is a named PL/SQL block stored in the Oracle Database and executed automatically when a
triggering event takes place. The event can be any of the following:

A data manipulation language (DML) statement executed against a table e.g., INSERT, UPDATE, or
DELETE. For example, if you define a trigger that fires before an INSERT statement on the customers
table, the trigger will fire once before a new row is inserted into the customers table.
A data definition language (DDL) statement executes e.g., CREATE or ALTER statement. These
triggers are often used for auditing purposes to record changes of the schema.
A system event such as startup or shutdown of the Oracle Database.
A user event such as login or logout.
The act of executing a trigger is also known as firing a trigger. We say that the trigger is fired.

Oracle trigger usages

Oracle triggers are useful in many cases such as the following:

Enforcing complex business rules that cannot be established using integrity constraint such as UNIQUE,
NOT NULL, and CHECK.
Preventing invalid transactions.
Gathering statistical information on table accesses.
Generating value automatically for derived columns.
Auditing sensitive data.

How to create a trigger in Oracle

To create a new trigger in Oracle, you use the following CREATE TRIGGER statement:

CREATE [OR REPLACE] TRIGGER trigger_name

{BEFORE | AFTER }triggering_event ON table_name
[FOR EACH ROW]
[FOLLOWS | PRECEDES another_trigger]
[ENABLE / DISABLE ]
[WHEN condition]
DECLARE
declaration statements
BEGIN
executable statements
EXCEPTION
exception_handling statements
END;

7.3 Example for practice:

Write a PL/SQL program to demonstrate Packages.

Step1: Creating package specification
CREATE or replace PACKAGE emppackage AS
procedure emp_proc2;

33
function fname2(a in number,b in out number)
return number;
end;
Step2: Creating package definition or body
CREATE or replace PACKAGE body emppackage AS
procedure emp_proc2
is
begin
updateemp
setsal=sal+sal*0.10
wherecomm<>sal*0.09;
DBMS_OUTPUT.PUT_LINE ('I am a procedure ');
end emp_proc2;
function fname2(a in number,b in out number)
return number is
begin
b:=a;
return b;
end fname2;
END;
Step3: Calling function / procedure of a package in a program
declare
a number:=10;
b number:=10;
begin
a:=emppackage.fname2(20,b);
dbms_output.put_line(a || b);
emppackage.emp_proc2;
end;
/
Output
2020
I am a procedure
PL/SQL procedure successfully completed.

Example:
Write PL/SQL queries to create Triggers.
SQL>create or replace trigger t11
before update on emp
for each row
begin
if :new.sal<1000
then
dbms_output.put_line('trigger fired');
end if;
end;
Trigger created.
Trigger gets fired when update is performed on EMP table
SQL> update emp
setsal=500
whereempno=69000;
Output
trigger fired

34
1 row updated.

Query: Write a transparent audit system from a table cust_master. The system must keep track of
records that are being deleted or updated.
TABLE:
SQL>select * from cust_mast;
CUST CUST_NAME DOB
-
c1Meenakshi 26-SEP-91
c2Shivani 27-DEC-92
c3Shantanu 30-SEP-72
PL/SQL code block
SQL>set serveroutput on
SQL> create trigger audit_sys before delete or update on cust_mast
for each row
begin
insert into audit_sys values(:old.cust_no,:old.cust_name,:old.dob);
end;
/

Output
Trigger created.
SQL>delete from cust_mast where cust_no=’c3’;
1 row deleted.
SQL>select * from audit_sys;
CUST CUST_NAME DOB
-
c3Shantanu 30-SEP-72
SQL>update cust_mast set dob=’25-nov-1990’ where cust_no=’c2’;
1 row updated.
SQL>select * from audit_sys;

CUST CUST_NAME DOB

-
c3Shantanu 30-SEP-72
c2Shivani 27-DEC-92

35
 PRACTICAL – 8

TITLE: Design and implementation of Payroll Processing System

8.1 Objective 8.2 Theory and concepts8.3 Exercise

8.1 OBJECTIVE:Design and implementation of payroll processing system

8.2 THEORY AND CONCEPTS:

Payroll Processing refers to the complete set of steps involved in calculating the total remuneration of
each employee. The process typically involves three to four stages and tasks such as defining salary
structures, gathering employee data, components, deductions, allowances, and setting up the
necessary policies with respect to taxes and other adjustments, and then calculating the total salary
after adjusting all the company policies. After the salaries are disbursed, filing, reporting and providing
payslips to employees also comes under the entire payroll processing cycle.
In simplest words, if payroll is the amount paid by the employer to employee, payroll processing is the
whole methodology to accurately calculate the net pay of the employees as per statutorycompliances
and company policies.

-- Database
-- Table structure for table loginn
CREATE TABLE loginn (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
e_mailtinytext NOT NULL,
passlongtext NOT NULL
);
-- Dumping data for table loginn
INSERT INTO loginn (idd, e_mail, pass) VALUES
(1, 'dev', 'dev');
-- Table structure for table empp
CREATE TABLE empp (
iddint(11) NOT NULL PRIMARY KEY AUTO_INCREMENT,
first_namevarchar(100) NOT NULL,
last_namevarchar(100) NOT NULL,
e_mailvarchar(100) NOT NULL UNIQUE KEY,
pass text NOT NULL,
d_o_b date NOT NULL,
gndrvarchar(10) NOT NULL,
contctvarchar(20) NOT NULL,
nidint(20) NOT NULL,
addrvarchar(100) DEFAULT NULL,
deprtmntvarchar(100) NOT NULL,
degvarchar(100) NOT NULL,
imgg text NOT NULL
);
-- Dumping data for table empp
INSERT INTO empp (idd, first_name, last_name, e_mail, pass, d_o_b, gndr, contct, nid, addr, deprtmnt, deg,
imgg) VALUES
(121, 'Mohit', 'Kumar', '[email protected]', '1234', '1994-04-04', 'Male', '01919', 12221, 'Razarbagh', 'IT', 'Head',
'images/no.jpg'),
(122, 'Mohan', 'Kumar', '[email protected]', '1234', '2018-01-01', 'Male', '0202', 323, 'Ad ', 'CS', 'CS',
'images/no.jpg'),

36
(123, 'Ram', 'Singh', '[email protected]', '1234', '1990-02-02', 'Male', '5252', 6222, 'Thames, UK', 'Creative', 'MSc',
'images/sw-google.png'),
(124, 'Govind', 'Iyer', '[email protected]', '1234', '1971-12-01', 'Male', '9595', 5929, 'Chemsford, USA',
'Creative', 'MSc', 'images/test.jpg'),
(125, 'Shyam', 'Manja', '[email protected]', '1234', '1971-06-28', 'Male', '8585', 5258, 'LA, USA', 'SpaceTech',
'BSc', 'images/330px-Elon_Musk_Royal_Society.jpg'),
-- Table structure for table emp_leave
CREATE TABLE emp_leave (
iddint(11) DEFAULT NULL,
tokenint(11) NOT NULL PRIMARY KEY AUTO_INCREMENT,
start date DEFAULT NULL,
end date DEFAULT NULL,
reason char(100) DEFAULT NULL,
statuss char(50) DEFAULT NULL,
FOREIGN KEY (idd) REFERENCES empp (idd) ON DELETE CASCADE ON UPDATE CASCADE
);
-- Dumping data for table emp_leave
INSERT INTO emp_leave (idd, token, start, end, reason, statuss) VALUES
(101, 301, '2019-04-07', '2019-04-08', 'Sick Leave', 'Approved'),
(102, 302, '2019-04-07', '2019-04-08', 'Urgent Family Cause', 'Approved'),
(103, 303, '2019-04-08', '2019-04-08', 'Concert Tour', 'Approved'),
(105, 304, '2019-04-26', '2019-04-30', 'Launching Tesla Model Y', 'Pending'),
(104, 305, '2019-04-08', '2019-04-09', 'Emergency Leave', 'Pending');
-- Table structure for table projectt
CREATE TABLE projectt (
piddint(11) NOT NULL PRIMARY KEY AUTO_INCREMENT,
eiddint(11) DEFAULT NULL,
p_namevarchar(100) DEFAULT NULL,
due_date date DEFAULT NULL,
sub_date date DEFAULT '0000-00-00',
markkint(11) NOT NULL,
statussvarchar(50) DEFAULT NULL,
FOREIGN KEY (eidd) REFERENCES empp (idd) ON DELETE CASCADE ON UPDATE CASCADE
);
-- Dumping data for table projectt
INSERT INTO projectt (pidd, eidd, p_name, due_date, sub_date, markk, statuss) VALUES
(213, 101, 'Database', '2019-04-07', '2019-04-04', 10, 'Submitted'),
(214, 102, 'Test', '2019-04-10', '0000-00-00', 0, 'Due'),
(215, 105, 'Maruti Model Y', '2019-04-19', '2019-04-06', 10, 'Submitted'),
(216, 105, 'Maruti Model X', '2019-04-03', '2019-04-03', 10, 'Submitted'),
(217, 103, 'Statistical', '2019-04-19', '2019-04-04', 6, 'Submitted'),
-- Table structure for table rank
CREATE TABLE rankk (
eiddint(11) NOT NULL PRIMARY KEY,
pointsint(11) DEFAULT 0,
FOREIGN KEY (eidd) REFERENCES empp (idd) ON DELETE CASCADE ON UPDATE CASCADE
);
-- Dumping data for table rank
INSERT INTO rankk (eidd, points) VALUES
(101, 10),(102, 0),(103, 6),(104, 0),(105, 20);
-- Table structure for table salaryy
CREATE TABLE salaryy (
iddint(11) NOT NULL PRIMARY KEY,
baseeint(11) NOT NULL,
bonussint(11) DEFAULT NULL,
totint(11) DEFAULT NULL,
FOREIGN KEY (idd) REFERENCES empp (idd) ON DELETE CASCADE ON UPDATE CASCADE
);
-- Dumping data for table salaryy
INSERT INTO salaryy (idd, basee, bonuss, tot) VALUES

37
(101, 55000, 10, 60500), (102, 16500, 0, 16500), (103, 65000, 6, 68900), (104, 78000, 0, 78000), (105, 105000,
20, 126000);
COMMIT;

38
 PRACTICAL – 9

TITLE: Design and implementation of Library information system

9.1 Objective 9.2 Theory and concepts9.3 Exercise

9.1 OBJECTIVE:Design and implementation of Library information system

9.2 THEORY AND CONCEPTS:

A Library Management System is a software built to handle the primary housekeeping functions of a library.
Libraries rely on library management systems to manage asset collections as well as relationships with their
members. Library management systems help libraries keep track of the books and their checkouts, as well as
members’ subscriptions and profiles.
Library management systems also involve maintaining the database for entering new books and recording books
that have been borrowed with their respective due dates.

CREATE TABLE resr_status (

idd INT,
status_val VARCHAR(50),
CONSTRAINT res_status PRIMARY KEY (idd)
);
CREATE TABLE catgry (
idd INT,
catgry_name VARCHAR(100),
CONSTRAINT catgry PRIMARY KEY (idd)
);
INSERT INTO catgryVALUES(101, 'maths'),(102, 'physics'),(103, 'chemistry'),(104, 'biology'),(105, 'english');
CREATE TABLE bokk (
idd INT,
titlee VARCHAR(500),
catgry_id INT,
pub_date DATE,
copies_owned INT,
CONSTRAINT bokk PRIMARY KEY (idd),
CONSTRAINT bokk_catgry FOREIGN KEY (catgry_id) REFERENCES catgry(idd)
);
CREATE TABLE authr (
idd INT,
first_name VARCHAR(300),
last_name VARCHAR(300),
CONSTRAINT authr PRIMARY KEY (idd)
);
CREATE TABLE bok_authr (
bokk_id INT,
author_id INT,
CONSTRAINT bokkauthor_bokk FOREIGN KEY (bokk_id) REFERENCES bokk(idd),
CONSTRAINT bokkauthor_author FOREIGN KEY (author_id) REFERENCES authr(idd)
);
CREATE TABLE membr_status (
idd INT,
status_val VARCHAR(50),
CONSTRAINT membrstatus PRIMARY KEY (idd),
);
CREATE TABLE membr (
idd INT,
first_name VARCHAR(300),

39
last_name VARCHAR(300),
joined_date DATE,
actv_status_id INT,
CONSTRAINT membr PRIMARY KEY (idd),
CONSTRAINT membr_status FOREIGN KEY (actv_status_id) REFERENCES membr_status(idd)
);
CREATE TABLE resrvtn (
idd INT,
bokk_id INT,
membr_id INT,
resrvtn_date DATE,
resrvtn_status_id INT,
CONSTRAINT resrvtn PRIMARY KEY (idd),
CONSTRAINT res_bokk FOREIGN KEY (bokk_id) REFERENCES bokk(idd),
CONSTRAINT res_membr FOREIGN KEY (membr_id) REFERENCES membr(idd)
);
CREATE TABLE finee_paymtn (
idd INT,
membr_id INT,
paymtn_date DATE,
paymtn_amount INT,
CONSTRAINT finee_paymtn PRIMARY KEY (idd),
CONSTRAINT fineepay_membr FOREIGN KEY (membr_id) REFERENCES membr(idd)
);
CREATE TABLE loann (
idd INT,
bokk_id INT,
membr_id INT,
loann_date DATE,
retrned_date DATE,
CONSTRAINT loann PRIMARY KEY (idd),
CONSTRAINT loann_bokk FOREIGN KEY (bokk_id) REFERENCES bokk(idd),
CONSTRAINT loann_membr FOREIGN KEY (membr_id) REFERENCES membr(idd)
);
CREATE TABLE finee (
idd INT,
bokk_id INT,
loann_id INT,
finee_date DATE,
finee_amount INT,
CONSTRAINT finee PRIMARY KEY (idd),
CONSTRAINT finee_bokk FOREIGN KEY (bokk_id) REFERENCES bokk(idd),
CONSTRAINT finee_loann FOREIGN KEY (loann_id) REFERENCES loann(idd)
);
COMMIT;

40
 PRACTICAL – 10

TITLE: Design and implementation of Student information system

10.1 Objective 10.2 Theory and concepts10.3 Exercise

10.1 OBJECTIVE:Design and implementation of student information system

10.2 THEORY AND CONCEPTS:

A Student Information System, or SIS, is a web-based platform that helps schools and colleges take data online
for easier management and better clarity. That's at its most basic.
The SIS system is able to collect school-wide data online so that it can be easily accessed by teachers, parents,
students, and administrators. That includes records of tests, attendance, appraisal performance, and plenty more.
Essentially, a SIS allows the school to make data points for lots of areas in one place so that it's easy to keep track
of progress and performance.

Code:-
-- Database
-- Table structure for table dev
CREATE TABLE dev (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
namevarchar(40) NOT NULL,
e_mailvarchar(40) NOT NULL,
passvarchar(40) NOT NULL
);
-- Dumping data for table dev
INSERT INTO dev (idd, name, e_mail, pass) VALUES
(1, 'Mohan Kumar', '[email protected]', 'kumar'), (2, 'Rohan Singh', '[email protected]', 'kumar');
-- Table structure for table coursee
CREATE TABLE coursee (
coursee_idint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
coursee_short_namevarchar(250) NOT NULL,
coursee_full_namevarchar(250) NOT NULL,
coursee_datevarchar(50) NOT NULL
);
INSERT INTO coursee (coursee_id, coursee_short_name, coursee_full_name, coursee_date) VALUES
(44, 'M.C.A', 'MASTER OF COMPUTER APPLICATION', '25-04-2019'), (45, 'M.S.C', 'MASTER OF
SCIENCE', '25-04-2019'), (46, 'B.COM', 'BACHELOR OF COMMERCE', '25-04-2019'), (48, 'M.B.A ',
'MASTER OF BUSINESS ADMINISTRATION', '25-04-2019');
-- Table structure for table folow
CREATE TABLE folow (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
to_user_idint(20) NOT NULL,
from_user_idint(20) NOT NULL
);
-- Dumping data for table folow
INSERT INTO folow (idd, to_user_id, from_user_id) VALUES
(29, 23, 20), (33, 20, 32), (37, 0, 21), (38, 21, 21), (40, 21, 20), (45, 30, 20), (46, 40, 20), (47, 20, 20);
-- Table structure for table folowing
CREATE TABLE folowing (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
from_user_idvarchar(20) NOT NULL,
to_user_idvarchar(20) NOT NULL
);
-- Table structure for table folows
CREATE TABLE folows (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,

41
to_user_idint(20) NOT NULL,
from_user_idint(20) NOT NULL
);
-- Table structure for table postss
CREATE TABLE postss (
post_idint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
from_user_idvarchar(3) NOT NULL,content longtext NOT NULL,
imagevarchar(255) NOT NULL,
timestamptimestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
);
-- Dumping data for table postss
INSERT INTO postss (post_id, from_user_id, content, image, timestamp) VALUES
(10, '1', 'Priyankachopra', 'priyanka chopra.jpg', '2019-05-08 15:37:52'),
(70, '1', 'This website is developed by Social Codia.', 'socialcodia.png', '2020-04-27 21:15:56'),
(15, '1', 'The results of the best video ever try to get the way this can be its own incomplete website and I will be
its own incomplete website and I will be its own incomplete website and I will be its own incomplete website
and I will be its own incomplete websit', 'Screenshot_2019-05-05-20-08-26-
893_com.mxtech.videoplayer.ad.png', '2019-05-08 17:12:44'),
(17, '8', 'True Love &hearts;︕ ', '918369709214_status_eace0e54cee646309b0da5f908d6731f.jpg', '2019 -05-08
19:14:13'),
(21, '8', 'Wow , Looking great Mohan... 😘😘😘', 'IMG_20190513_223507454.jpg', '2019-05-13
22:22:56'),
(22, '8', 'Ramzan Mubarak Mohan... 😘😘😘', 'B612_20190509_075024_942.jpg', '2019-05-13 22:24:01'),
(25, '20', 'Mohan Kumar The Boss', '6.jpg', '2019-05-19 05:55:07'),
(35, '20', 'Your genes decide whether you will own a dog or not, pawsible? Although dogs and other pets are
common household membrs across the globe, little is known how they impact our daily life and health.',
'dogsgenes.jpeg', '2019-05-20 00:28:40'),
(47, '21', 'demo post from student_id = 21', 'mohit.png', '2019-10-10 17:07:40'),
(48, '21', 'stack image', 'stock-vector-editable-square-frame-banner-template-for-social-media-post-red-black-
and-white-geometric-shape-1415216360.jpg', '2019-10-10 17:06:33'),
(59, '21', 'Rohan Singh', 'rohan - Copy.jpg', '2019-10-21 05:19:12');
-- Table structure for table stdnts
CREATE TABLE stdnts (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
rollnovarchar(255) NOT NULL,
standerdvarchar(255) NOT NULL,
user_namevarchar(40) NOT NULL,
namevarchar(255) NOT NULL,
gndrvarchar(255) NOT NULL,
contctvarchar(255) NOT NULL,
e_mailvarchar(255) NOT NULL,
passvarchar(255) NOT NULL,
cityyvarchar(255) NOT NULL,
imagevarchar(255) NOT NULL
);
-- Dumping data for table stdnts
INSERT INTO stdnts (idd, rollno, standerd, user_name, name, gndr, contct, e_mail, pass, cityy, image)
VALUES
(20, '1', 'BCA', 'mohit', 'Mohan Kumar', 'male', '9867503256', '[email protected]', 'kumar', 'Thane',
'mohit.png'), (21, '2', 'Botanology', 'rohan', 'Rohan Singh', 'female', '9867503256', '[email protected]',
'kumar', 'Sipah', 'rohan.jpg'), (22, '6', '3', 'sohan', 'Sohan Kumar', 'male', '82684000646',
'[email protected]', 'kumar', 'Thane', '6.jpg'), (27, '10', '1', 'ibbu', 'Ram Kumar', 'male', '9920322293',
'[email protected]', 'kumar', 'Mumbra, Thane', '');
-- Table structure for table teacher
CREATE TABLE teacher (
iddint(10) NOT NULL PRIMARY KEY AUTO_INCREMENT,
namevarchar(40) NOT NULL,
e_mailvarchar(30) NOT NULL,
contctvarchar(13) NOT NULL,
gndrvarchar(7) NOT NULL,

42
positionvarchar(50) NOT NULL,
passvarchar(20) NOT NULL,
addrvarchar(255) NOT NULL,
imagevarchar(60) NOT NULL
);
-- Dumping data for table teacher
INSERT INTO teacher (idd, name, e_mail, contct, gndr, position, pass, addr, image) VALUES
(1, 'Mohan Kumar', '[email protected]', '9555555256', 'male', 'Manager', 'kumar', 'kausa, mumbra, thane',
'mohan.png'),
(8, 'Rohan Kumar', '[email protected]', '7156478954', 'female', 'Head Teacher', 'kumara', 'Sipah', 'rohan.jpg');
COMMIT;

43
 PRACTICAL – 11

TITLE: Automatic Backup of Files and Recovery of Files

11.1 Objective 11.2 Theory 11.3 Viva Question

11.1 OBJECTIVE:Automatic Backup of Files and Recovery of Files

11.2 THEORY AND CONCEPTS: Data is the heart of the enterprise, it's crucial to protect it and to
protectorganization's data, one need to implement a data backup and recovery plan. Backing up filescan
protect against accidental loss of user data, database corruption, hardware failures, andeven natural
disasters. It's our job as an administrator to make sure that backups areperformed and that backup tapes
are stored in a secure location.

Creating a Backup and Recovery Plan

Data backup is an insurance plan. Important files are accidentally deleted all the time.Mission-critical
data can become corrupt. Natural disasters can leave office in ruin. With asolid backup and recovery
plan, one can recover from any of these.

Figuring Out a Backup Plan

It takes time to create and implement a backup and recovery plan. We'll need to figure outwhat data
needs to be backed up, how often the data should be backed up, and more. To helpwe create a plan,
consider the following:
• How important is the data on systems? The importance of data can go a long way inhelping to
determine if one need to back it up—as well as when and how it should bebacked up. For critical
data, such as a database, one'll want to have redundant backupsets that extend back for several
backup periods. For less important data, such as dailyuser files, we won't need such an elaborate
backup plan, but 'll need to back up the dataregularly and ensure that the data can be recovered
easily.

• What type of information does the data contain? Data that doesn't seem important to wemay be
very important to someone else. Thus, the type of information the data contains can help we
determine if we need to back up the data—as well as when and how thedata should be backed up.

• How often does the data change? The frequency of change can affect our decision onhow often
the data should be backed up. For example, data that changes daily should bebacked up daily.

• How quickly do we need to recover the data? Time is an important factor in creating abackup
plan. For critical systems, we may need to get back online swiftly. To do this,we may need to alter
our backup plan.

• Do we have the equipment to perform backups? We must have backup hardware toperform
backups. To perform timely backups, we may need several backup devices andseveral sets of
backup media. Backup hardware includes tape drives, optical drives, andremovable disk drives.
Generally, tape drives are less expensive but slower than othertypes of drives.

• Who will be responsible for the backup and recovery plan? Ideally, someone should bea primary
contact for the organization's backup and recovery plan. This person may alsobe responsible for
performing the actual backup and recovery of data.

44
 • What is the best time to schedule backups? Scheduling backups when system use is aslow as
possible will speed the backup process. However, we can't always schedulebackups for off-peak
hours. So we'll need to carefully plan when key system data isbacked up.

• Do we need to store backups off-site? Storing copies of backup tapes off-site is essential
to recovering our systems in the case of a natural disaster. In our off-site storagelocation, we should
also include copies of the software we may need to install tore-establish operational systems.

The Basic Types of Backup

There are many techniques for backing up files. The techniques use will depend on the typeof data we're
backing up, how convenient we want the recovery process to be, and more.

If we view the properties of a file or directory in Windows Explorer, we'll note an attributecalled
Archive. This attribute often is used to determine whether a file or directory should bebacked up. If the
attribute is on, the file or directory may need to be backed up. The basictypes of backups we can perform
include

• Normal/full backups All files that have been selected are backed up, regardless of thesetting of
the archive attribute. When a file is backed up, the archive attribute is cleared.If the file is later
modified, this attribute is set, which indicates that the file needs to bebacked up.

• Copy backups All files that have been selected are backed up, regardless of the settingof the
archive attribute. Unlike a normal backup, the archive attribute on files isn'tmodified. This allows
us to perform other types of backups on the files at a later date.

• Differential backups Designed to create backup copies of files that have changed sincethe last
normal backup. The presence of the archive attribute indicates that the file hasbeen modified and
only files with this attribute are backed up. However, the archiveattribute on files isn't modified.
This allows to perform other types of backups on thefiles at a later date.

• Incremental backups Designed to create backups of files that have changed since themost recent
normal or incremental backup. The presence of the archive attributeindicates that the file has been
modified and only files with this attribute are backed up.When a file is backed up, the archive
attribute is cleared. If the file is later modified, thisattribute is set, which indicates that the file needs
to be backed up.

• Daily backups Designed to back up files using the modification date on the file itself. Ifa file has
been modified on the same day as the backup, the file will be backed up. Thistechnique doesn't
change the archive attributes of files.In we backup plan we'll probably want to perform full backups
on a weekly basis and supplement this with daily, differential, or incremental backups. We may
also want to createan extended backup set for monthly and quarterly backups that includes
additional files thataren't being backed up regularly.

Tip We'll often find that weeks or months can go by before anyone notices that a file or datasource is
missing. This doesn't mean the file isn't important. Although some types of dataaren't used often, they're
still needed. So don't forget that we may also want to create extrasets of backups for monthly or quarterly
periods, or both, to ensure that we can recoverhistorical data over time.

Differential and Incremental Backups

The difference between differential and incremental backups is extremely important. Tounderstand the
distinction between them. As it shows, with differential backups we back upall the files that have
changed since the last full backup (which means that the size of thedifferential backup grows over time).
With incremental backups, we only back up files thathave changed since the most recent full or

45
incremental backup (which means the size of theincremental backup is usually much smaller than a full
backup).

Once we determine what data we're going to back up and how often, we can select backupdevices and
media that support these choices.

Selecting Backup Devices and Media

Many tools are available for backing up data. Some are fast and expensive. Others are slowbut very
reliable. The backup solution that's right for our organization depends on manyfactors, including

• Capacity: The amount of data that we need to back up on a routine basis. Can the backuphardware
support the required load given our time and resource constraints?

• Reliability: The reliability of the backup hardware and media. Can we afford to sacrificereliability
to meet budget or time needs?

• Extensibility: The extensibility of the backup solution. Will this solution meet our needsas the
organization grows?

• Speed: The speed with which data can be backed up and recovered. Can we afford tosacrifice
speed to reduce costs?

• Cost: The cost of the backup solution. Does it fit into our budget?

Common Backup Solutions

Capacity, reliability, extensibility, speed, and cost are the issues driving our backup plan. Ifwe
understand how these issues affect our organization, we'll be on track to select anappropriate backup
solution. Some of the most commonly used backup solutions include
• Tape drives Tape drives are the most common backup devices. Tape drives usemagnetic tape
cartridges to store data. Magnetic tapes are relatively inexpensive butaren't highly reliable. Tapes
can break or stretch. They can also lose information overtime. The average capacity of tape
cartridges ranges from 100 MB to 2 GB. Comparedwith other backup solutions, tape drives are
fairly slow. Still, the selling point is the lowcost.

• Digital audio tape (DAT) drives DAT drives are quickly replacing standard tape drivesas the
preferred backup devices. DAT drives use 4 mm and 8 mm tapes to store data.DAT drives and tapes
are more expensive than standard tape drives and tapes, but theyoffer more speed and capacity.
DAT drives that use 4 mm tapes can typically recordover 30 MB per minute and have capacities of
up to 16 GB. DAT drives that use 8 mmtapes can typically record more than 10 MB per minute and
have capacities of up to 36GB (with compression).

• Auto-loader tape systems Auto-loader tape systems use a magazine of tapes to createextended
backup volumes capable of meeting the high-capacity needs of the enterprise.With an auto-loader
system, tapes within the magazine are automatically changed asneeded during the backup or
recovery process. Most auto-loader tape systems use DAT tapes. The typical system uses magazines
with between 4 and 12 tapes. The maindrawback to these systems is the high cost.

• Magnetic optical drives Magnetic optical drives combine magnetic tape technology withoptical
lasers to create a more reliable backup solution than DAT. Magnetic opticaldrives use 3.5-inch and
5.25-inch disks that look similar to floppies but are muchthicker. Typically, magnetic optical disks
have capacities of between 1 GB and 4 GB.

46
 • Tape jukeboxes Tape jukeboxes are similar to auto-loader tape systems. Jukeboxes usemagnetic
optical disks rather than DAT tapes to offer high-capacity solutions. Thesesystems load and unload
disks stored internally for backup and recovery operations.Their key drawback is the high cost.

• Removable disks Removable disks, such as Iomega Jaz, are increasingly being used asbackup
devices. Removable disks offer good speed and ease of use for a single drive orsingle system
backup. However, the disk drives and the removable disks tend to bemore expensive than standard
tape or DAT drive solutions.

• Disk drives Disk drives provide the fastest way to back up and restore files. With diskdrives, you
can often accomplish in minutes what takes a tape drive hours. So whenbusiness needs mandate a
speedy recovery, nothing beats a disk drive. The drawbacksto disk drives, however, are relatively
high costs and less extensibility.

Before we can use a backup device, we must install it. When we install backup devices otherthan
standard tape and DAT drives, we need to tell the operating system about the controllercard and drivers
that the backup device uses. For detailed information on installing devicesand drivers, see the section
of Chapter 2 entitled "Managing Hardware Devices and Drivers."

Buying and Using Tapes

Selecting a backup device is an important step toward implementing a backup and recoveryplan. But
we also need to purchase the tapes or disks, or both, that will allow we toimplement our plan. The
number of tapes we need depends on how much data we'll be backing up, how often we'll be backing
up the data, and how long we'll need to keepadditional data sets.

The typical way to use backup tapes is to set up a rotation schedule whereby we rotatethrough two or
more sets of tapes. The idea is that we can increase tape longevity by reducingtape usage and at the
same time reduce the number of tapes we need to ensure that we havehistoric data on hand when
necessary.

One of the most common tape rotation schedules is the 10-tape rotation. With this rotationschedule, we
use 10 tapes divided into two sets of 5 (one for each weekday). The first set of tapes is used one week
and the second set of tapes is used the nextweek. On Fridays, full backups are scheduled. On Mondays
through Thursdays, incrementalbackups are scheduled. If we add a third set of tapes, we can rotate one
of the tape sets to anoff-site storage location on a weekly basis.

Tip: The 10-tape rotation schedule is designed for the 9 to 5 workers of the world. If we're in a24 x 7
environment, we'll definitely want extra tapes for Saturday and Sunday. In this case,use a 14-tape
rotation with two sets of 7 tapes. On Sundays, schedule full backups. OnMondays through Saturdays,
schedule incremental backups.

Viva Questions:

1. Define backup and recovery.

2. What are the factors associated with backup solution?
3. What are the advantages/uses of using backup and recovery?
4. What are the different types of backup?
5. What are the types of SQL server backups?

47
 PRACTICAL – 12

TITLE: Mini project (Design & Development of Data and Application)

12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE: Objective of inventory control system project is to design a database to record proper
variety of required items in inventory, maintain optimized inventory, safety stock levels and obtain low
raw material prices, storage cost, insurance cost, taxes

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

▪ Enter, modify, delete items in inventory

▪ Enter, modify, delete suppliers of inventory items

▪ View details of inventory items and all associated costs to aid in decision
making on placing orders with suppliers

▪ View details of suppliers of inventory items

▪ Generate reports on inventory re-order level to aid in decision making in

procurement of inventory items

48
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team

Any special requirement of h/w, s/w environment, tools -No

Project deliverables

ER Diagrams,

Converting ER Diagrams into Tables

Making SQL Queries

49
12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE:Material Requirements Processing (MRP) is a standard supply planning system to help
businesses, primarily product-based manufacturers, understand inventory requirements while balancing
supply and demand. Businesses use MRP systems, which are subsets of supply chain management
systems, to efficiently manage inventory, schedule production and deliver the right product—on time
and at optimal cost.

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

o Identifying requirements to meet demand

The first step of the MRP process is identifying customer demand and the requirements
needed to meet it, which starts with inputting customer orders and sales forecasts.

o Using the bill of materials required for production, MRP then disassembles demand
into the individual components and raw materials needed to complete the build while
accounting for any required sub-assemblies.

o Checking inventory and allocating resources

Utilizing the MRP to check demand against inventory and allocating resources
accordingly, you can see both what items you have in stock and where they are—this
is especially important if you have inventory across several locations. This also lets
you see the status of items, which gives visibility into items that are already allocated
to another build, as well as items not yet physically in the warehouse that are in transit,
or on order. The MRP then moves inventory into the proper locations and prompts
reorder recommendations.

o Scheduling production
Using the master production schedule, the system determines how much time and labor
are required to complete each step of each build and when they need to happen so that
the production can occur without delay.

o The production schedule also identifies what machinery and workstations are needed
for each step and generates the appropriate work orders, purchase orders and transfer
orders. If the build requires subassemblies, the system takes into account how much
time each subassembly takes and schedules them accordingly.

o Identifying issues and making recommendations

Finally, because the MRP links raw materials to work orders and customer orders, it

50
 can automatically alert your team when items are delayed and make recommendations
for existing orders: automatically moving production in or out, performing what-if
analyses, and generating exception plans to complete the required builds.

Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team

Any special requirement of h/w, s/w environment, tools –No

Project deliverables

ER Diagrams,

Converting ER Diagrams into Tables

Making SQL Queries

51
12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE: Objective of Hospital management system project is to design database for recording
and managing hospital information to reduce the burden of handling manually the activities of all
sections of hospital like reception, lab, inpatient/outpatient management and patient billing etc., which
improve the processing efficiency.

12.2 THEORY AND CONCEPTS:

Scope of Mini Project - Project description listing out functionalities / features to be developed–

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

▪ Enter, modify, delete out-patient details, in-patient details, doctors details

▪ Enter, modify, delete patients’ treatment details, charges of all diagnostic

activities

▪ Booking of appointments with doctors

▪ View patient details, doctors’ details, treatment details

▪ Search facility on specialisation, availability of doctors, charges of diagnostic

tests, charges for Operation Theatre, ICU, different room categories

▪ Generate and view bills

52
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion) – 6 hrs

Team size – 3 students/project team

Any special requirement of h/w, s/w environment, tools – No

Project deliverables
ER Diagrams,
Converting ER Diagrams into Tables
Making SQL Queries

53
12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE: Objective of Railway reservation system project is to design a database to efficiently
manage Railway Reservation SYSTEM for a city tour.

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

▪ Enter, modify, delete staffs details

▪ Enter, modify, delete passengers details

▪ Enter, modify and delete Train details (Train No, Category, Vendor etc.)

▪ View details of reservation day wise, month wise etc.

▪ View details of regular passengers

▪ View staffs details categories wise

▪ Generate reports of unsold seat train wise, Class wise etc.

54
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team

Any special requirement of h/w, s/w environment, tools -No

Project deliverables
ER Diagrams,
Converting ER Diagrams into Tables
Making SQL Queries

55
 12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE:Objective of personal information system project is

Personal Information Management Systems (or PIMS) are systems that help give individuals more
control over their personal data. PIMS allow individuals to manage their personal data in secure, local
or online storage systems and share them when and with whom they choose. Providers of online
services and advertisers will need to interact with the PIMS if they plan to process individuals’ data.
This can enable a human centric approach to personal information and new business models.

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

o Database: PIS core offering consists of a database for storing employee information.
HR professionals can store all personnel data into the system that can be accessed from
any time, from anywhere.

o Time and Labor Management: Functions like time and labor management requires a
lot of time. PIS packages allow employees to input their hours worked and help
managers to instantly verify vacation requests, and the information is fed to the payroll
directly.

o Payroll Activity: Payroll activity is another important component of an HRIS or PIS

model. HR can unload or download employee hours easily, and issue checks or payroll
deposits to employees.

o Benefits: Some PIS packages allow employers to develop and maintain medical,
retirement, and other benefits through their software.

o Employee Interface: Most PIS packages allow limited user access for an employee.

o Hiring and Retention: Hiring and retention are the most crucial components of PIS.

56
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team

Project deliverables

ER Diagrams, Converting ER Diagrams into Tables and Making SQL Queries.

Any special requirement of h/w, s/w environment, tools -No

57
12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE:The process of identifying users depends on the type of device they are using (e.g.
a smartphone or laptop) and whether they are using a web browser or mobile app. For example, a user
visiting web pages in a web browser, either on a mobile device or computer, would be identified by
browser-based identification methods. A user playing a mobile-app game on a smartphone or tablet
would be identified by a mobile identifier.

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

o A user identification or user ID is an entity used to identify a user on a website,

software, system or within a generic IT environment. It is the most common
authentication mechanism used within computing systems.

o Regardless of the type of user and their rights, each user has a unique identification that
distinguishes it from other users. System administrators use these IDs to assign
privileges, track user activity and manage overall operations on a particular system,
network or application.

o Many analytics technologies can’t identify unique users if they use multiple devices
across multiple sessions, as each time a user does this, a new user is counted. By having
a unique user ID, this eliminates this issue, allowing for all activity being attributed to
one user in an analytics report

58
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team

Any special requirement of h/w, s/w environment, tools

Project deliverables

ER Diagrams,

Converting ER Diagrams into Tables

Making SQL Queries

59
12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE:Timetable management software helps design timetables and mark attendance for
teachers and students.It helps to regulate proper schedules and allocate faculty according to their
availability by outlining the classes, sections, and other details fed into the system. Adopting a digital
system for timetable management enhances the authenticity of data as it would be sensitive towards
manipulations and boosts efficiency due to workflow automation

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

o unplanned systems can be taxing: A well-timed routine can help by keeping students
and teachers involved and disciplined. It will also save time by lowering the amount of
time spent in chaos and confusion.

o Faculty distribution is equitable: The timetable management system evenly distributes

lectures to each faculty member and prevents work from being distributed based on
events.

o Rearrangement of the timetable based on circumstances: When necessary, new classes

could be added or removed from the timetable.

o Event and holiday calendar planner: Holidays and events could be added in the backend
which can further be viewed by the user in the form of a fully furnished yearly calendar.

60
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team.

Any special requirement of h/w, s/w environment, tools –No

Project deliverables

ER Diagrams,

Converting ER Diagrams into Tables

Making SQL Queries

61
12.1 Objective 12.2 Theory and concepts

12.1 OBJECTIVE:Objective of this project is to design database for recording and managing day to
day activity of a hotel to reduce the burden of handling manually the activities of all sections of hotel
like reception, employee, booking status, Visitors check in, check out status, and billing etc., which
improve the processing efficiency.

12.2 THEORY AND CONCEPTS:

Scope of Mini Project (project description listing out functionalities / features to be developed)

Scope of project will include the following:

o Develop ER Diagrams

o Design Database by converting ER Diagrams to Tables

o Development of DDL, DML and Database Queries to achieve the following

functionalities

▪ Enter, modify, delete employee details

▪ Enter, modify, delete visitors details

▪ Enter, modify, and delete Room details (Room No, Category etc.)

▪ View details of reservation day wise, month wise etc.

▪ View details of regular visitors

▪ View staffs details categories wise

▪ Generate reports of unsold Room Fare wise, Class wise etc.

62
Technology to be used – MySql

Timeline of Mini Project (in terms of no. of lab classes required for project completion)– 6 hrs

Team size – 3 students/project team.

Any special requirement of h/w, s/w environment, tools –No

Project deliverables
ER Diagrams,
Converting ER Diagrams into Tables
Making SQL Queries

63