DBMS Assignments

Shailendra Kumar Yadav (HND/Fourth Semester)
Abstract
DATABASE MANAGEMENT
International School of Management and [Email address]
Technology
Submitted to: Shiv Poudel Sir
10/05/2020
SYSTEM
Section-H
Database Management System 2020
Contents
Part 1:......................................................................................................................................................................................1
Introduction:.......................................................................................................................................................................1
Presentation slides for Analyzing Different Types of Database Management System......................................................2
Conclusion:......................................................................................................................................................................17
Part 2:....................................................................................................................................................................................18
Introduction:.....................................................................................................................................................................18
ER Model:........................................................................................................................................................................18
Entity:...........................................................................................................................................................................19
Attributes:.....................................................................................................................................................................19
Relationships between Entities:.......................................................................................................................................21
ER Diagram Symbols:......................................................................................................................................................21
ER Diagram of Library Management System:.................................................................................................................23
Class Diagram:.................................................................................................................................................................23
Data Flow Diagram (DFD):................................................................................................................................................25
Database Schema:............................................................................................................................................................27
Analyzation of design of relation database for optimization of system performance:....................................................29
Design of Library Management System:.........................................................................................................................30
Login.............................................................................................................................................................................30
Dashboard.....................................................................................................................................................................31
Assession Mapping.......................................................................................................................................................31
Author...........................................................................................................................................................................33
Book..............................................................................................................................................................................34
Book Categories...........................................................................................................................................................35
Book Issue Returns.......................................................................................................................................................36
Fine...............................................................................................................................................................................37
Members.......................................................................................................................................................................38
Members Category.......................................................................................................................................................39
Subjects.........................................................................................................................................................................40
Testing of system functionalities and performance:........................................................................................................41
Implementation of different features for database maintenance and security:.............................................................49
Database Maintenance:....................................................................................................................................................50
Database Security:............................................................................................................................................................53
Evaluation of effectiveness of designed system against client requirements:.................................................................57
Prerequisite Specifications:..............................................................................................................................................57
Benefits and Effectiveness of the system:........................................................................................................................58
Conclusion:.......................................................................................................................................................................58

1
Part 3:....................................................................................................................................................................................59
Introduction:.....................................................................................................................................................................59
System monitoring and optimizing tools:........................................................................................................................59
Effectiveness of Database Management Tools:...............................................................................................................69
Advantages of database management tools:....................................................................................................................70
Shortcoming of database management tools:...................................................................................................................70
Enhancement that can be done in the system:..................................................................................................................72
Conclusions:.....................................................................................................................................................................73
Bibliography..........................................................................................................................................................................74

2
Part 1:
Produce a presentation slides which analyses different types of database management system.
 Compare and contrast the different types of database models.
 Assess how relational database models and the process of normalization can provide reliable
and efficient data structures.
 Critically evaluate different database management systems available in relation to open
source and vendor-specific platforms, justifying the criteria used in the evaluation

3
Introduction:
The scenario is about the Cosmos International College which is a newly established educational
organization located in the heart of Mahendrapul, Pokhara which gives the courses related to
Management. There are limited number of students studying in this college. So, the records are
maintaining in a excel file. There is also facility of library and consists of large number of books.
There is too difficult to keep records of large number of books and students which has get which
books for their purpose of study. So, the college has decided to develop a web application to manage
its library. They should keep records of large number of books and their category, books which have
been issued and the books that needs to be returned. They should also provide dashboard for admin
which gives the overview of books category, total number of a available books, the total number of
books issued, the total penalty collected over the fiscal year. They should be also secure and effective
login system for the admin and the librarian with admin having full right to access the system and the
librarian being able to view stock, issue books and accept book returns.
In this task, I am going to give a presentation slides which analyses different types of database
management system. I am going to compare and contrast about the different types of database
models. I will also asses how relational database models and the process of normalization can
provide reliable and efficient data structures. I will also evaluate different database management
systems available in relation to open source and vendor-specific platforms with useful criteria.
A database is a systematic collection of data. They support electronic storage and manipulation of
data. Databases make data management easy[ CITATION Gurnd \l 1033 ]. A database is an integrated
collection of data, usually so large that it has to be stored on secondary storage devices such as disks
or tapes. This data can be maintained as a collection of operating system files, or stored in a DBMS
(database management system). Database Management System (DBMS) is a software for storing and
retrieving users' data while considering appropriate security measures. It consists of a group of
programs which manipulate the database. The DBMS accepts the request for data from an
application and instructs the operating system to provide the specific data. In large systems, a DBMS
helps users and other third-party software to store and retrieve data.
Presentation slides for Analyzing Different Types of Database Management System

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19
Conclusion:
In this task, I am going to give a presentation slides which analyses different types of database
management system. I am going to compare and contrast about the different types of database
models. I will also asses how relational database models and the process of normalization can
provide reliable and efficient data structures. I will also evaluate different database management
systems available in relation to open source and vendor-specific platforms with useful criteria.

20
Part 2:
Design a database management system using a relational model to meet client requirements
and develop a database management system using a suitable platform.
 Produce a design for a relational database management system to meet client requirements
 Analyze how the design will optimize system performance.
 Develop a fully functional system which meets client and system requirements, using an open
source language
 Test the system for functionality and performance.
 Implement effective features in the solution to handle concurrency, security, user
authorizations and data recovery.
 Critically evaluate the effectiveness of the system design and development against client and
system requirements.
Introduction:
In this task, I will produce Entity Relationship (ER) diagram, Data Flow Diagram (DFD), Class
Diagram and Database Schema design for a relational database management to meet client’s
requirements. I will also analyze how the design will optimize system performance which I produce
during this task. I will use MS SQL to develop a fully functional system which meets client and
system requirements. I will test developed system for functionality and performance. I will also
implement the effective features in the solution to handle concurrency, security, user authorization
and data recovery. At lastly, I will evaluate the effectiveness of the system design and development
against clients and system requirement.
A relation schema can be thought of as the basic information describing a table or relation. This
includes a set of column names, the data types associated with each column, and the name associated
with the entire table. For example, a relation schema for the relation called Members could be
expressed using the following representation: Members ( MemberID: integer, MemberName: string,
MemberAddress: string, Emailaddress: text, ConatctNo: integer, UserName: string, Password: string,
Status: string, Remarks: text ) A relational database schema is a collection of relation schemas,
describing one or more relations. Domain is synonymous with data type. Attributes can be thought of
as columns in a table. Therefore, an attribute domain refers to the data type associated with a column.
A relation instance is a set of tuples (also known as rows or records) that each conform to the schema
of the relation.
ER Model:
Entity Relationship Diagram, also known as ERD, ER Diagram or ER model, is a type of structural
diagram for use in database design. An ERD contains different symbols and connectors that visualize
two important information: The major entities within the system scope, and the inter-relationships
among these entities[ CITATION Vis12 \l 1033 ]. It is the model that describes data in terms of entities,
relationships and attributes. It has entity as object and show relationships that is connection between
objects and attributes that shows the properties that characterize or describes entities or relationship.
It is a graphical representation used in computing for organization of data. It is used in development
stage to find the different element used in the project with the relationship between them. The
various elements that are used in ER diagram of Library Management System. are: -

21
Entity:
It is an object in the real world that is distinguishable from other objects. It may be thing,
place, event or object within a system. In library management system, the following entities
are given below: -
 Member
 Book
 Fine
 Subject
 Author
 Book issue return
 Book category
 Member category
 Assession mapping
Attributes:
It is a property or description of an entity. A library management system member entity could
have attributes describing the MemberID, MemberName, MemberAddress, Emailaddress,
ConatctNo, UserName, Password, Status, Remarks. In library management system, the
following attributes are given below: -
Attributes of Member
 MemberID
 MemberName
 MemberAddress
 EmailAddress
 ContactNo
 UserName
 Password
 Status
 Remarks
Attributes of Author
 AuthorID
 AuthorName
 Description
Attributes of book
 BookId
 BookName
 AuthorID
 Remarks
 SubjectID
 BookCategoryID
Attributes of Subject

22
 SubjectID
 SubjectName
 Remarks
Attributes of fine
 FineID
 LastDays
 MemberID
 Amount
 Remarks
 MemberCategoryID
Attributes of Assession Mapping
 AssessionID
 BookID
 Status
Attributes of BookIssuereturn
 BookIssueReturnID
 MemberID
 IssueDate
 DueDate
 ReturnDate
 LateDate
 FineAmount
 Remarks
 StaffMemberId
 Status
 AssessionID
Attributes of MemberCategory
 MemberCategoryID
 MemberCategoryName
 Remarks
Attributes of BookCategory
 BookCategoryID
 BookCategoryName
 Description

23
Relationships between Entities:

Relationship is an association among two or more entities. There are generally four types of
relationship between entities. They are given below; -
 One-to-one:
One-to-one relationship is a key constraint that indicates that one entity can be associated
with one of another entity. An example of one-to-one relationship is when a member has a
member id and a member id belong to one member.
 One-to-many:
One-to-many relationship is a key constraint that indicates that one entity can be associated
with many of another entity. An example of a one-to-many relationship is when a member
can read in only one library, and a library have many members.
 Many-to-one:
Many-to-one relationship is a key constraint that indicates many of one entity can be
associated with one of another entity. An example of many-to-one relationship is many
members can read book in a library.
 Many-to-many:
Many-to-many relationship is a key constraint that indicates that many of one entity can be
associated with many of another entity. An example of a many to-many relationships is
members can read many books, and many books can read by same member.
ER Diagram Symbols:
It is graphical representation of relationship between entities. There are many symbols used to draw
the ER Model of anything are as follows: -

24
ER Diagram of Library Management System:
Class Diagram:
“Class diagram is a static diagram. It represents the static view of an application. Class diagram is
not only used for visualizing, describing, and documenting different aspects of a system but also for
constructing executable code of the software application.”[ CITATION Tut19 \l 1033 ] Class diagram
describes the attributes and operations of a class and also the constraints imposed on the system. It is
one of the most helpful UML diagram kinds as it obviously maps the structure of a specific scheme
by modeling its classes, characteristics, activities and object interactions and it shows a collection of
classes, interfaces, associations, constraints and collaborations and also knows as structural diagram
as well as it is helpful for developers and other team members too.
Benefits of class diagram:
 It describes the static view of the system.

25
 It helps to illustrate the data model for information and doesn’t matter how simple or
complex is data model.
 It understands the summary of the application’s schematics.
 It creates through charts that highlight any code that needs to be programmed as well as
enforced within the framework outlined.
There are different UML tools to make class diagram such as star UML, Argo UML, Magic Draw,
Lucid Chart and Visual Paradigm. So, I am going to class diagram of Employee Management
System using Visual Parading tool and here is the screenshot of class diagram that I have made, here
we can see the class diagram of Employee Management System that I have made using UML tools.

26
Data Flow Diagram (DFD):

“A Data Flow Diagram (DFD) is a traditional way to visualize the information flows within a
system. A neat and clear DFD can depict a good amount of the system requirements graphically. It
can be manual, automated, or a combination of both.”[ CITATION Vis12 \l 1033 ] A data flow diagram
shows the way information flows through a process or system. It includes data inputs and outputs,
data stores, and the various subprocesses the data moves through. DFDs are built using standardized
symbols and notation to describe various entities and their relationships. Data flow diagrams are also
categorized by level. Starting with the most basic, level 0, DFDs get increasingly complex as the
level increases. As you build your own data flow diagram, you will need to decide which level your
diagram will be. There are some symbols used in Data Flow Diagrams (DFDS). They are given
below: -
Symbol Description
Source or Sink: Source is short of data source which represents any
source of data that is defined as outside the boundary of the process
that the DFD is modeling. In a same way, Sink is any destination for
data that is outside the boundary of the process that the DGD is
modeling.
Processing step: A DFD process represents an activity that process
data; presumably the processing is important enough to play a
significant role in the business process that the DFD id modeling.
Data store: A collection of data needed by the business process. A

data store is not the same as database that it represents a more
abstract way of referring to any accumulation of data that is used by
the process.
Data flows: In DFDs, data flows are represented by arrows. The
arrows are labelled with the data that move along the arrow.
Levelling of DFDs:
DFDs are built using standardized symbols and notation to describe various entities and their
relationships. Data flow diagrams are also categorized by level. Starting with the most basic, level 0,
DFDs get increasingly complex as the level increases. As you build your own data flow diagram, you
will need to decide which level your diagram will be. There are some symbols used in Data Flow
Diagrams (DFDS).
 Level 0:
Level 0 is also known as context diagram and that are the most basic DFDs. Level 0 DFD are
designed to be an abstraction view, which shows the system as a single process node with its

27
connections to external entities (Anon., n.d.). The entire system represented as a single
bubble with input and output data indicated by incoming/outgoing arrows.
 Level 1:
In this level, level 0 (context diagram) is decomposed into multiple processes. Firstly, we
highlight the main functions of the system and breakdown the high-level process of context
diagram into subprocesses. It Keep the external entities unchanged. It prepares the list of
processes and data stores. The logical DFD consists of 6 main processes like login, add book,
add member, add fine, search report, admin activity. The librarian being a part of the system
and also the user, is not shown as an external entity, but the role is taken care of by the use of
the authorization process.
The above DFDs were logical in nature where interaction between processes was shown
considering that a process sending information to another process does so only after
processing the information received from the external entity. The given diagram is based on
the actual situation where information once received by a process is stored in the data store.
Any process now requiring this information will take it from the data store.
 Level 2:
The Level 2 represents the details of individual processes that have been defined in the Level
1. The sub processes are numbered from 1.1, 1.2, … and so on. Such detailed data flow at
times defines from the logical working to the physical working of a system. Internal data
stores additionally may be mentioned so as to complete the data input, storage and output. In

28
the printing press system, the following processes have been considered for further expanding
as sub processes.
Database Schema:
“A database schema represents the logical configuration of all or part of a relational database. It can
exist both as a visual representation and as a set of formulas known as integrity constraints that
govern a database”[ CITATION Luc18 \l 1033 ]. Database schema is an abstraction which is used to
represent the storage of data in database. It not only describes the organization of data but also
represents the relationship between various tables in a database.
There are two types of database schemas.
 Logical Database Schema
This represents how the data is organized in terms of tables, and how the different attributes
in the different tables link them. Different database management systems use different syntax
to define the logical architecture and constraints of a database which is called logical database
schema.
 Physical Database Schema
This represents how data is stored physically on disk storage.
The difference between these two schemas could be seen in the table below

29

30
Analyzation of design of relation database for optimization of system performance:

Database systems are designed to manage large bodies of information. These large bodies of
information do not exist in isolation. They are part of the operation of some enterprise whose end
product may be information from the database or may be some device or service for which the
database plays only a supporting role. Database design mainly involves the design of the database
schema. The design of a complete database application environment that meets the needs of the
enterprise being modeled requires attention to a broader set of issues. In this text, we focus initially
on the writing of database queries and the design of database schemas.
A high-level data model provides the database designer with a conceptual framework in which to
specify the data requirements of the database users, and how the database will be structured to fulfill
these requirements. The initial phase of database design, then, is to characterize fully the data needs
of the prospective database users. The database designer needs to interact extensively with domain
experts and users to carry out this task. The outcome of this phase is a specification of user
requirements. Next, the designer chooses a data model, and by applying the concepts of the chosen
data model, translates these requirements into a conceptual schema of the database. The schema
developed at this conceptual-design phase provides a detailed overview of the enterprise. The
designer reviews the schema to confirm that all data requirements are indeed satisfied and are not in
conflict with one another. The designer can also examine the design to remove any redundant
features. The focus at this point is on describing the data and their relationships, rather than on
specifying physical storage details. In terms of the relational model, the conceptual-design process
involves decisions on what attributes we want to capture in the database and how to group these
attributes to form the various tables. The “what” part is basically a business decision, and we shall
not discuss it further in this text. The “how” part is mainly a computer-science problem. There are
principally two ways to tackle the problem. A fully developed conceptual schema indicates the
functional requirements of the enterprise. In a specification of functional requirements, users describe
the kinds of operations (or transactions) that will be performed on the data. Example operations
include modifying or updating data, searching for and retrieving specific data, and deleting data. At
this stage of conceptual design, the designer can review the schema to ensure it meets functional
requirements. The process of moving from an abstract data model to the implementation of the
database proceeds in two final design phases. In the logical-design phase, the designer maps the
high-level conceptual schema onto the implementation data model of the database system that will be
used. The designer uses the resulting system-specific database schema in the subsequent physical-
design phase, in which the physical features of the database are specified. These features include the
form of file organization and the internal storage structures;
“The relational model uses a collection of tables to represent both data and the relationships among
those data. Each table has multiple columns, and each column has a unique name”[ CITATION cha15 \l
1033 ]. Tables are also known as relations. The relational model is an example of a record-based
model. Record-based models are so named because the database is structured in fixed-format records
of several types. Each table contains records of a particular type. Each record type defines a fixed
number of fields, or attributes. The columns of the table correspond to the attributes of the record
type. The relational data model is the most widely used data model, and a vast majority of current
database systems are based on the relational model.
The entity-relationship (E-R) data model uses a collection of basic objects, called entities, and
relationships among these objects. An entity is a “thing” or “object” in the real world that is
distinguishable from other objects. The entity-relationship model is widely used in database design.

31
ER diagrams help to visualize database design ideas, identify the mistakes and design flaws, and help
to make corrections before executing the changes in the database. Visualizing a database schema
with an ERD, we can have a full picture of the entire database schema. We can easily locate entities,
view their attributes and identify the relationships they have with others. All these allow us to
analyze an existing database and to reveal database problems easier.
Using database schema provides the opportunity to simplify administration of backup, restore and
security and database management by allowing database entities or objects, to be logically grouped
together. Schemas help to manage the logical entities separately from one another, but still allow
objects to work together where required. This helps in optimizing the system performance.
Design of Library Management System:
The Library management system has been designed using C# programming language based on .NET
entity framework and visual studio as IDE. Firstly, an application has been designed using database.
The database required for the Library management system has been designed in SQL server
management studio as the database management software. The design of Library management
system is presented below: -
Login
A login is first and foremost part of application, set of credentials used to authenticate a user. Most
often, these consist of username and password. Logins are used by websites, computer applications
and mobile apps. They are a security measure designed to prevent unauthorized access to
confidential data. When you enter valid username and password, you are not allowed to access data
in the application. If the entered username and password match with data stored in the database, the
user is logged into the system, otherwise shows invalid messages.

32
Dashboard
The dashboard form is displayed on the application when the user enters the confidential username
and password. It allows access to all kinds of functionalities that show the time, whether, and useful
data. The user must signup their valid details before log into the systems.
Assession Mapping
Assession Mapping holds the book id and status detail. We can access the view of which admin can
used the which author, books, subjects in the application.

33

34
Author
Author holds all the description about book author name. It shows the lists of author of different
books in the library managements system.

35
Book
Book holds all the description about books. In book page we can find the details about available
books, authors, etc. It saves our time to find required book.

36
Book Categories
Book Category holds all the details about books. The admin can access the categories of different
books.
Book Issue Returns

Book Issue Return holds all the details about book issue, return, late date. Admin and librarian can
access the Book Issue Return page.

37
Fine
Fine holds all the details about collected fine amount and late days record. Admin can access the fine
page to see collected amount.

38
Members
Member holds the description of member. Admin can create, edit and delete the member. Without
valid username and password member cannot able access the system.

39
Members Category
Member Category holds all the details about member. Admin can access the Member Category page.

40
Subjects
Subject holds the subject id, subject name and description. Admin can create new data into the
system. As well as admin can edit and delete the data.

41
Testing of system functionalities and performance:

“Software testing is a process, to evaluate the functionality of a software application with an intent
to find whether the developed software met the specified requirements or not and to identify the
defects to ensure that the product is defect-free in order to produce a quality product”[ CITATION Raj20 \l
1033 ]. The library management systems were developed for the management of books, authors, fine,
subject, category of books etc. for the digitalization of library. It provides the functionality for edit,
update, create a book, subjects, fine, members in the system. The testing of system is done to check
the designed software works properly or not.

42
Action:
When I enter
the valid
username and
password in the
system.
Result:
The result is
shown in the
screen.

43
Action:
When I have
edited data in
Book Category.
Result:
The result is
shown in the
screen.

44
Action:
When I have
created new
author.
Result:
The result is
shown in the
screen.
Action:
When I have
created new
data in subject.
Result:

45
The result is
shown in the
screen.
Action:
When I have
edited data in
Book.
Result:
The result is
shown in the
screen.

46
Action:
When I have
created new
data in Book
Issue Return.

47
Result:
The result is
shown in the
screen.
Action:
When I have
created new
data in member.

48
Result:
The result is
shown in the
screen.
Action:
When I have
created new
data in member
category.
Result:
The result is
shown in the
screen.
Action:

49
When I have
created new
data in fine.
Result:
The result is
shown in the
screen.
Implementation of different features for database maintenance and security:

“Database maintenance is an activity designed to keep a database running smoothly. A number of
different systems can be used to build and maintain databases, with one popular example being
MYSQL”[ CITATION Mar20 \l 1033 ]. The maintenance of databases is generally performed by people
who are comfortable and familiar with the database system and the specifics of the particular
database, although some maintenance tasks can be performed by people who do not have experience.
Database Maintenance is a term we use to describe a set of tasks that are all run with the intention to
improve your database. There are routines meant to help performance, free up disk space, check for
data errors, check for hardware faults, update internal statistics, and many other obscure (but
important) things.
Library Management System has always had a companion program called ‘Database Maintenance’
(or ‘System Utilities’ back before 2009) that is installed with it. Unfortunately, it is a widely
unknown portion of the program. I am sure people see it in the Start Menu, but most people never
click on it, which is unfortunate. The ‘Database Maintenance’ program should be run at least every
14 days in order to keep your server at its peak ‘Health’.
This article is meant to give you a little bit of a crash course on what exactly our ‘Database
Maintenance’ does to your database.
Our Database Maintenance program has four main ‘Categories’ of routines:
1. Log File Maintenance
2. Integrity Check
1. Log File maintenance
SQL Databases contain a ‘Log File’ that keeps track of every single transaction that happens in the
database. Using these log files, you can actually restore a database to the state it was at any point in
time before. So, if something bad happens to your database (either corruption, accidentally, or
maliciously), you can recover your data as it was the instant before the event happened. So the Log

50
files are extremely important parts of the system, and they require their own special maintenance as
well.
2. Integrity Check
Over time, your database will go through numerous changes. Data will be added and removed, tables
will be added, modified, and removed. The database’s overall schema will change. Indexes will be
added, rebuild, deleted, and re-created. Data columns will be added, modified, and removed. The
database will go through thousands upon thousands of changes just as a natural course of its lifespan.
But each change, no matter how small, has the potential to introduce corruption into the database.
Indexes can have corrupt pages, table can have bad records, the schema can contain inaccurate
references. These different types of corruption can cause anything from simple performance issues to
complete schema failure and catastrophic data loss. But this is where the Integrity Check comes into
play. The Database Integrity Check examines and analyzes the database in its entirety, and can detect
and repair most any corruption it comes across. The database integrity check should be run on a
regular, reoccurring, weekly schedule. The Integrity Check is your best weapon to prevent
catastrophic data loss. Library Management System has a built in Integrity Check that any OTP user
with Admin rights can run on demand. If any corruption was detected or repaired, Library
Management System will immediately inform the user of the details, severity, and actions taken. In
nearly all cases, that is where the corruption will end, and there will be no need for further action.
But if you run an integrity check and Library Management System reports that an issue was detected
but was not resolved, please contact the Office Tools Technical Support team immediately. Our data
specialists have decades of experience working with SQL Server databases and have been able to
recover data that others though were completely irrecoverable.
So please, work with your IT Services and make sure that your SQL Server has a database
maintenance routine scheduled to run every week. Doing this simple preventative maintenance can
keep your database (and therefore your company) running at smoothly.
Database Maintenance:
Database maintenance aids in smoothing running of the system using various routines. Some of the
categories of database routines that are used are provided below:
 Transactions
“A transaction is a sequence of operations performed (using one or more SQL statements) on
a database as a single logical unit of work. The effects of all the SQL statements in a
transaction can be either all committed (applied to the database) or all rolled back (undone
from the database)”[ CITATION SQL20 \l 1033 ]. A database transaction must be atomic, consistent,
isolated and durable. A transaction is a unit of work that is performed against a database.
Transactions are units or sequences of work accomplished in a logical order, whether in a
manual fashion by a user or automatically by some sort of a database program.
A transaction is the propagation of one or more changes to the database. For example, if you
are creating a record or updating a record or deleting a record from the table, then you are
performing a transaction on that table. It is important to control these transactions to ensure
the data integrity and to handle database errors.
Practically, you will club many SQL queries into a group and you will execute all of them
together as a part of a transaction.
Properties of Transactions:

51
Transactions have the following four standard properties, usually referred to by the acronym ACID.
 Atomicity – It ensures that all operations within the work unit are completed successfully.
Otherwise, the transaction is aborted at the point of failure and all the previous operations are
rolled back to their former state.
 Consistency – It ensures that the database properly changes states upon a successfully
committed transaction.
 Isolation – It enables transactions to operate independently of and transparent to each other.
 Durability – It ensures that the result or effect of a committed transaction persists in case of a
system failure.
Transaction Control:
The following commands are used to control transactions.
 COMMIT − to save the changes.
 ROLLBACK − to roll back the changes.
 SAVEPOINT − creates points within the groups of transactions in which to
ROLLBACK.
 SET TRANSACTION − Places a name on a transaction.
 Triggers
A trigger is a stored procedure in database which automatically invokes whenever a special event in
the database occurs. A trigger is a special type of stored procedure that automatically runs when an
event occurs in the database server. DML triggers run when a user tries to modify data through a data
manipulation language (DML) event. DML events are INSERT, UPDATE, or DELETE statements
on a table or view. These triggers fire when any valid event fires, whether table rows are affected or
not.

52
DDL triggers run in response to a variety of data definition language (DDL) events. These events
primarily correspond to Transact-SQL CREATE, ALTER, and DROP statements, and certain system
stored procedures that perform DDL-like operations.
The benefits of triggers are listed below:
 Helps to enforce referential integrity q11
 Helps in enforcing security authorizations
 Helps to prevent invalid transactions
 Stored Procedure
A stored procedure is a prepared SQL code that you can save, so the code can be reused over and
over again. So, if you have an SQL query that you write over and over again, save it as a stored
procedure, and then just call it to execute it. You can also pass parameters to a stored procedure, so
that the stored procedure can act based on the parameter value(s) that is passed. They are created to
perform one or more Data Manipulation Language (DML) operations on Database. It can be modify
or access data in a database, but not tied to a specific object or database, which offers a number of
advantages.

53
Database Security:
Database security refers to the range of tools, controls, and measures designed to establish and
preserve database confidentiality, integrity, and availability. This article will focus primarily on
confidentiality since it’s the element that’s compromised in most data breaches. There are types of
data security methods in SQL server that are given below :-
 Data Backup and Recovery:
Backup is the process of creating a copy of data to protect against accidental or malicious deletion,
corruption, hardware failure, ransomware attacks, and other types of data loss. Data backups can be
created locally, offsite, or both. An offsite data backup is a key part of any business
continuity/disaster recovery plan.
Recovery refers to the process of restoring data and operations (e.g., returning a server to normal
working order following hardware failure). Products aimed at rapid recovery of data and operations
are typically referred to as business continuity and disaster recovery, or BCDR, solutions.
I. Scheduled backups
This is the most important features in backup software. It allows completely eliminating manual
backups with all compressing, transferring, filtering to the storage, and other. It takes a lot of efforts
and time that’s why most of the people do not back up their data (Anon., n.d.). In scheduled backup
there are lots of options such as backup start time, set name, daily schedule and so on. You can see
all the options in figure which is given below:

54
II. Backup database as SQL server dumps

The backup database statement is used in SQL Server to create a full back up of an existing SQL
database. Here you can see the backup of Library Management System:

55
 Authentication and authorization

Authentication is the act of validating that users are whom they claim to be. This is the first step in
any security process.
Complete an authentication process through:
 Passwords. Usernames and passwords are the most common authentication factors. If a user
enters the correct data, the system assumes the identity is valid and grants access.
 One-time pins. Grant access for only one session or transaction.
Authorization in a system security is the process of giving the user permission to access a specific
resource or function. This term is often used interchangeably with access control or client
privilege. Giving someone permission to download a particular file on a server or providing
individual users with administrative access to an application are good examples of authentication.

56
Evaluation of effectiveness of designed system against client requirements:

The library management system was designed with using C# as programming based on .NET
framework using Visual Studio as IDE. SQL server management studio was used as the database
management tool for storing the data of library management system. The effectiveness of the
designed system was evaluated comparing with the client requirements. Database Management. The
library management system is very easy and comfortable to use. Librarian can easily insert the data
into the system and also member can login to the system. According to the client requirements the
system was designed.

57
Prerequisite Specifications:
The library management system has many requirements and demands that are needed to be fulfilled.
After analyzing the requirements using various methods and procedures. The system had various
limitations and bugs which are needed to be overcome. Following are the requirements: 
 The entry of all Books
 The entry of all Members
 The entry of all Authors
 The entry of all Subjects
 The entry of all Fines
 The entry of all Book Category
 The entry of all Member Category
 The entry of all Assession Mapping
Every software has specific goals, requirements and serves particular purposes. Each goal and
purpose translate a process or several processes that the software aims to solve or to automate. To
deliver the right software product, we should define well the software from the beginning. System
requirement documents every operation and dictates how software should behave, it can be as
detailed as what a button should do and should be as complete and correct as possible. The purpose
of a specification document is to describe the behavior as well as the different functionalities of an
application or software in a specific environment. System requires to evaluate properly to verify all
the modules would work properly or not. All the modules contain in the library management system
such as dashboard, login, member and book etc. worked smoothly and properly. The new data
created successfully in the database you can see clearly from above figure. The library management
system fulfilled client requirement successfully. The system can have members, book detail,
feedback form and dashboard to communicate about available books and other query. As per the
requirements of college the system fulfilled as planned.
Benefits and Effectiveness of the system:
The benefits of using this system are: Database Management System.
 It helps to manage and monitor all the library operations efficiently.
 It reduces mistakes that always happen during manual method.
 We cannot able to access into the system without valid username and password.
 It saves time too. Measure of Performance There are three factors that are used to measure
the performance of a system:
I. Speed
Speed of any application works by specifying a goal for how long a specific web request should take.
The web application of library Management system is working normally as the requirements of
client.
II. Reliability
The software works without any failure or problem. This application does not create any downtime,
completely defect free, and performs correctly.
III. Security

58
This application is secure to use. The unauthorized parties cannot able access into the system. The
Data backup and recovery process are used in that system to backing up data in case of a data loss.
Conclusion:
In this task I have designed for a relational database management system to meet client requirements.
I have also analyzed how the design will optimize system performance. I have developed a fully
functional system which meets client and system requirements by using an open source language. I
have also tested the system functionality and performance. I have implemented effective features in
the solution to handle concurrency, security, user authorizations and data recovery. I have also
evaluated the effectiveness of the system design and development against client and system
requirements.
Part 3:
Create a lab report: Demonstrate the system administration and management tools available
on the chosen platform
 Demonstrate the tools available in the system to monitor and optimize system performance,
and examine the audit logs.
 Demonstrate the tools available in the system to manage security and authorizations. • Assess
the effectiveness of the system administration and management tools available on the
platform identifying any shortcomings of the tools.
 Assess any future improvements that may be required to ensure the continued effectiveness
of the database system.
Introduction:
The scenario is about the Cosmos International College which is a newly established educational
organization located in the heart of Mahendrapul, Pokhara which gives the courses related to
Management. There are limited number of students studying in this college. So, the records are
maintaining in a excel file. There is also facility of library and consists of large number of books.
There is too difficult to keep records of large number of books and students which has get which
books for their purpose of study. So, the college has decided to develop a web application to manage
its library. They should keep records of large number of books and their category, books which have
been issued and the books that needs to be returned. They should also provide dashboard for admin
which gives the overview of books category, total number of a available books, the total number of
books issued, the total penalty collected over the fiscal year. They should be also secure and effective
login system for the admin and the librarian with admin having full right to access the system and the
librarian being able to view stock, issue books and accept book returns.
In this part I am going demonstrate the tools available in the system to monitor and optimize system
performance, and also examine the audit logs. I will also demonstrate about the tools available in the
system to manage security and authorizations. I am going to assess the effectiveness of the system

59
administration and management tools available on the platform identifying any shortcomings of the
tools. I will describe about the future improvements that may be required to ensure the continued
effectiveness of the database system.
System monitoring and optimizing tools:
The system monitoring tools helps to know the state of your network and server health is incredibly
important for techs who want to optimize performance. Without insights into how your servers are
performing, you increase the odds of encountering pesky software bugs or potential bottlenecks.
That’s why it’s important to develop proactive server monitoring practices.
Monitoring servers can be a tedious or deal; applications must be checked for responsiveness,
storage can’t run above capacity, and web servers must be constantly protected from external threats.
Although some monitoring can be performed manually, human efforts are less efficient and, in many
cases, can’t match what proper tools can do. If you want to help ensure your server monitoring
provides granular insight into key metrics, it’s highly recommended you invest in professional server
monitoring software. The various tools are available in MS SQL server for monitoring the system
activities and optimizing performance which are listed below: -
 Error Log
The SQL Server error log contains user-defined events and certain system events you can use for
troubleshooting. When managing SQL Server there are so many different places to look for data.
These include the error logs, system event logs, profiler data, performance counter data, etc. Once
you have collected the data you then need to parse through and interpret the data you collected. One
of these areas where errors and other informational data is stored is the SQL Server error log. The
problem with the error log file is that there is so much data collected it is sometimes hard to
determine where the real errors lie. By default, all backups and integrity checks are logged in the
error log.
The steps for configuring and viewing the SQL Server Logs is shown with steps with figures are
given below: -
SN Steps Screenshots
1. In Object
Explorer,
expand the
instance of
SQL Server,
expand
Management,
right-click
SQL Server
Logs, and
then click
Configure.
2. In the
Configure
SQL Server
Error Logs

60
dialog box,
choose from
the following
options. a.
Log files
count b. Log
file size
3. When error
log is
configured,
expand the
Management
section Right
click SQL
Server Logs,
select View,
and then
choose SQL
Server Log
4. The Log File

Viewer
appears with a
list of logs for
we want to
view.
 Extended Events
Extended events is a lightweight performance monitoring system that enables users to collect data
needed to monitor and troubleshoot problems in SQL Server. See Extended events overview to learn

61
more about the extended events architecture. This article aims to help the SQL developer who is new
to extended events, and who wants create an event session in just a few minutes. By using extended
events, you can see details about the inner operations of the SQL system and your application. When
you create an extended event session, you tell the system:
 Which occurrences you are interested in.
 How you want the system to report the data to you.
1. In object
explorer,
expand the
instance of
SQL Server
2. Expand
Extended
Events
3. Right click
on Sessions
you can see
New Session
Wizard,
click on it.

62
4. This wizard
helps you
create
extended
event
session by
selecting the
events you
want to
capture
5. Set the
session
name from
set session
properties
6. In this step,
select the do
not use a
template

63
option and
click next.
7. Select the
events you
want to
capture
8. In capture
global
fields, it
contains the
fields to be
included
when we
monitor
activities

64
9. we can
apply filter.
10. The session

storage
allows you
to store the
events in a
file.
11. The
summary

65
will display
all the
options set
12. Here new
session
wizards
display
success
messages
 SQL Server Profiler

SQL Server Profiler is an interface to create and manage traces and analyze and replay trace results.
Events are saved in a trace file that can later be analyzed or used to replay a specific series of steps
when diagnosing a problem. It works by giving DBAs and developers a high-level view of the
operation of a system. Users create traces to capture data and monitor errors and other problems.
They then use the profiler to store, retrieve, and view the results of many traces graphically for
purposes of troubleshooting and repair. This function all happens on the client-side, meaning it uses
resources on the same machine it’s monitoring.
1. In the SQL
Server
Management
Studio Tools
menu, click
SQL Server
Profiler.
2. In Query
Editor, right
click and then
select Trace

66
Query in SQL
Server
Profiler and
click run.
3. In Activity
Monitor, click
the Processes
pane, right
click the
process that
you want to
profile, and
then click
Trace Process
in SQL Server
Profiler.
 Audit Log
Auditing an instance of the SQL Server Database Engine or an individual database involves tracking
and logging events that occur on the Database Engine. SQL Server audit lets you create server audits,
which can contain server audit specifications for server level events, and database audit
specifications for database level events. Audited events can be written to the event logs or to audit
files. There are several levels of auditing for SQL Server, depending on government or standards
requirements for your installation. SQL Server Audit provides the tools and processes you must have
to enable, store, and view audits on various server and database objects.

67
Effectiveness of Database Management Tools:

The world of data is constantly changing and evolving every second. This in turn has created a
completely new dimension of growth and challenges for companies around the globe. By accurately
recording data, updating and tracking them on an efficient and regular basis, companies can address
their challenges on one hand and make use of the immense potential offered by this sector on the
other hand. By collecting minute and updated data, companies are using the said information to
achieve their goals in a systematic way on one hand and empower their business in a strategic
manner on the other hand. Some of the activities conducted after collection of data includes creating
accounting reports, calculating sales estimates and creating invoices of customers. This data and its
insights is then made available to the management and employees of the organisation through
computerized database. One of the proven ways in which brands can manage the relationships
between the various database elements is through the use of database management systems, which is
today an integral part of functioning of companies and organizations around the world.
Modern database management systems are dependent on a programming language that is called
structured query language. This language is then used to access, update and delete data that are
present within its tables. The database systems also contain programs that include Microsoft’s SQL
server and the open source MySQL queries that enable outside programs to access its data through
SQL queries. For example, a web page can display information or data that includes product data and
description, photographs and prices. This information is easily available to the user easily, when the
web server software is connected to the relational database management system.
Advantages of database management tools:
The advantages of different database management tools that have been used for library management
system are given below: -

68
 Stored procedures
 It increases the performance of application.
 It reduces traffic between the application and database server.
 It is reusable and transparent to all applications that access the particular database.
 Transactions
 It maintains the database atomicity, consistency, integrity and durability transactions.
 It increases the flow of data.
 Triggers
 It compares before and after versions of data.
 It Roll back invalid modifications.
 It reads from other tables including those in other databases.
 It modifies other tables including those in other databases.
 It executes local and remote stored procedure.
 SQL Profiler
 It shows how a data interacts with clients.
 It can help zero in on trouble spots by allowing us to capture and replay key events.
 It lets users save trace data and compare it to newer data to spotlight new trouble spots.
 Database Backup and Recovery
 Individual File Restoration
 Efficiency
 It can be done at a datafile or tablespace level.
 It allows quick recovery to point-in-time.
Shortcoming of database management tools:
 Stored procedures
 Stored procedure code is not as robust as application code, particularly in the area of
looping. ii.
 Any data errors in handling Stored Procedures are not generated until runtime.
 Too much overhead is incurred from maintaining Stored Procedures that are not complex
enough.
 Transactions
 We want to keep transactions short, to begin them as late as possible and to end them as early
as possible. Otherwise concurrency hurts,
 we are getting more lock waiting and deadlocks
 Triggers
 It is hard to follow their logic as it they can be fired before or after the database insert/update
happens.
 It is easy to forget about triggers and if there is no documentation it will be difficult to figure
out for new developers for their existence.
 SQL Profiler
 It will increase the load on Server.
 It creates network latency.
 Database Backup and Recovery
 It changes since the most recent database or differential backup must be redone.
 It requires regular checking and proper maintenance.
 It consumes the more time.

69
The ‘Library Management System’ of Cosmos International College address all the information
queries and transaction queries. The various maintenance, security should be carried out the smooth
operation of system. These should be updated time to time to do good performance, to keep more
productive. This system helps to carried out the digitalization of library. It can handle all the
requirements in the library. It has capability to provide easy and effective storage of information of
member, students, fine, book etc. There are limited number of students studying in this college. So,
the records are maintaining in a excel file. There is also facility of library and consists of large
number of books. There is too difficult to keep records of large number of books and students which
has get which books for their purpose of study. So, the college has decided to develop a web
application to manage its library. They should keep records of large number of books and their
category, books which have been issued and the books that needs to be returned. They should also
provide dashboard for admin which gives the overview of books category, total number of a
available books, the total number of books issued, the total penalty collected over the fiscal year.
They should be also secure and effective login system for the admin and the librarian with admin
having full right to access the system and the librarian being able to view stock, issue books and
accept book returns.
A database is an integrated collection of data, usually so large that it has to be stored on secondary
storage devices such as disks or tapes. This data can be maintained as a collection of operating
system files, or stored in a DBMS (database management system). Database Management System
(DBMS) is a software for storing and retrieving users' data while considering appropriate security
measures. It consists of a group of programs which manipulate the database. The DBMS accepts the
request for data from an application and instructs the operating system to provide the specific data. In
large systems, a DBMS helps users and other third-party software to store and retrieve data.
 Performance
Performance means system throughput under a given workload for a specific timeframe.
Performance is validated by testing the scalability and the reliability of hardware, software and
network. It is an ongoing process and not an end result. Performance requirements undergo massive
changes as features and functionalities get added and eliminated to accommodate evolving business
requirements. The system is very easy to use for the effectiveness of the system. It is used to keep
records of member, book, fine, subject, book category and book issue returns etc. The system has
good interface which motivates to do online works in the library. The execution of system makes
easy way of payments of fine.
 Scalability
Scalability simply refers to the ability of an application or a system to handle a huge volume of
workload or expand in response to an increased demand for database access, processing, networking,
or system resources. Library management system software has scalable advantage because it is more
adaptable to the changing demands or needs of its members or users. It is scalable to records many
data and information about members, books and so on. And stored procedures increase scalability of
an application by isolating application processing on the server.
 High availability
High availability is when your apps remain available and accessible without any interruption and
serve their intended function seamlessly. High availability is achieved when your database cluster
continues to operate, for example, even if one or more servers are blown up, shut down, or simply

70
disengaged unexpectedly from the rest of the network. If any one of server goes down, whether due
to traffic overload or any other issues, the entire application or site could become unavailable. So the
library management system with high availability avoid this problem by eliminating single points of
failure, which prevents application from going down when one component fails.
 Security
Security of a computer system is a crucial task. It is a process of ensuring confidentiality and
integrity of the OS. A system is said to be secure if its resources are used and accessed as intended
under all the circumstances, but no system can guarantee absolute security from several of the
various malicious threats and unauthorized access. Similarly, in order to get access to the dashboard
of the system correct username and password provisions are available. User authentication policy is
made available and views are created in database software for protection. Various data validation and
security mechanism are used to maintain data integrity and consistency. The application security can
be further increased using more data validations. Encryption policy can be adopted to protect the
data. More views can be created in database to protect the sensitive data from other users. Strong
password can be deployed to prevent the unauthorized access. Similarly, scheduled backups can be
used to keep the data safe automatically.
Enhancement that can be done in the system:
There are various benefits provide by the Library Management System to the admins, members. But
still there can be improvements in future to improve reliability, security and scalability are listed
below: -
 There should be funding for operations, maintenance, and upgrades must be sustained over time.
 There should be improving data collection and entry in booking, offering services and contacting.
 The security system of the system can be strengthening for maintaining the privacy of members
as well as Library Management System.
 There should be enhancement of design which attracts more customers.
 The various payment methods should be made which make the members do payment with ease.
Conclusions:
In this task I have demonstrated the tools available in the system to monitor and optimize system
performance, with audit logs. I have also demonstrated the tools available in the system to manage
security and authorizations. I have also explained the effectiveness of the system administration and
management tools available on the platform identifying any shortcomings of the tools. I have also
mentioned the future improvements that may be required to ensure the continued effectiveness of the
database system.

71
Bibliography
Guru99, n.d.. [Online]
Available at: https://www.guru99.com/introduction-to-database-sql.html
Lucidchart, 2018. Lucidchart. [Online]
Available at: A database schema represents the logical configuration of all or part of a relational
database. It can exist both as a visual representation and as a set of formulas known as integrity
constraints that govern a database.
McMohan, M., 2020. [Online]
Available at: https://www.easytechjunkie.com/what-is-database-maintenance.htm
[Accessed 22 December 2020].

72
Paradigm, V., 2012. [Online]

Available at: https://www.visual-paradigm.com/tutorials/data-flow-diagram-dfd.jsp
Rajkumar, n.d. [Online]
Available at: https://www.softwaretestingmaterial.com/software-testing/
[Accessed December 2020].
singh, c., 2015. BegginerBooks. [Online]
Available at: https://beginnersbook.com/2015/04/relational-model-in-dbms/
Transaction, S., 2020. [Online]

Available at: https://www.w3resource.com/sql/controlling-transactions.php
[Accessed february 2020].
TutorialsPoint, n.d. [Online]
[Accessed 14 nov 2019].
slant, n.d. slant. [Online]
Available at: slant.com
study, n.d. study. [Online]
Available at: study.com
tutorialspoint, n.d. tutorialspoint. [Online]
Available at: www.tutorialspoint.com
w3schools, n.d. w3schools. [Online]
Available at: www.w3schools.com

73

DBMS Assignments

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DBMS Assignments

Uploaded by

Copyright:

Available Formats

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Presentation slides for Analyzing Different Types of Database Management System

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Relationships between Entities:

Shailendra Kumar Yadav (HND/Fourth Semester)

ER Diagram of Library Management System:

 It describes the static view of the system.

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Data Flow Diagram (DFD):

Data store: A collection of data needed by the business process. A

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Analyzation of design of relation database for optimization of system performance:

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Book Issue Returns

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Testing of system functionalities and performance:

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Implementation of different features for database maintenance and security:

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)

Shailendra Kumar Yadav (HND/Fourth Semester)