Assignment 1 CMP556

Database Management Systems

Harish Chander Kunta
10000127895
Virginia International University

Dr. Nathan A. Minami

Database Management Systems
May 10, 2015

Assignment 1 CMP556
1. The 4 main actions involved in database are:
Defining a database
Characterizing a database incorporates information sorts, structures and limitations of the
information that need to be put away in the database.
Constructing the database
Developing the database incorporates the procedure of putting away the information on
the same stockpiling medium that is under the control of DBMS.
Manipulating a database
Controlling the database incorporates capacities, for example, questioning the database to
recover particular information, redesigning the database to reflect changes in the miniworld, and
producing reports from the information.
Sharing a database
Offering the database which helps different clients to get to the databases in the
meantime.
2. Responsibilities of the DBA and the database designers are:
The main responsibility of the DBA are all as follows

Keeping up all databases needed for advancement, testing, preparing and

generation utilization
Establishment and arrangement of DBMS server programming and related items.
Redesigning and fixing/hot-altering of DBMS server programming and related

items.
Move database to another server.

Assignment 1 CMP556

Assess DBMS highlights and DBMS related items.

Create and keep up solid reinforcement and recuperation arrangements and

techniques.
Deal with the Database outline and usage.

3. Differences between database schema and database state:

When we characterize another database, we determine its database diagram just to the DBMS
and we get the introductory condition of the database when the database is initially stacked with
the starting information.
Each time an upgrade operation is connected to the database, we get another database state.
The DBMS is incompletely in charge of guaranteeing that each condition of the database fulfills
the structure and limitations determined in the outline.

4. Differences between procedural and non-procedural DMLS:

Procedural DML

1.
The client determines what information is obliged and how to get it. This implies that the
client must express all the information access operations that are to be utilized by calling suitable
strategies to get the data needed.

1.
Procedural DML recovers a record, forms it and, taking into account the outcomes
acquired by this preparing, recovers another record would be handled et cetera. This procedure of
recoveries proceeds until the information asked for from the recovery has been accumulated

2.

Procedural DML'S are abnormal state programming dialect

Non-procedural DML

Assignment 1 CMP556
Non-procedural DML's permit the obliged information to be indicated in a solitary
recovery or overhaul proclamation. The client indicates what information is needed without
determining how it is to be gotten.

The DBMS makes an interpretation of a DML explanation into one or more strategies
that control the obliged arrangements of records which liberates the client from needing to know
how information structures and calculations that are obliged to recover and potentially change
the information.

Non-procedural are definitive dialect and simple to incline and utilization

5. What is the difference between the two-tier and three-tier client/server architectures?

Two-Tier Architecture:

The two-level is in view of Client Server building design. The two-level structural
planning is similar to customer server application. The immediate correspondence happens in the
middle of customer and server. There is no middle in the middle of customer and server. In view
of tight coupling a 2 layered application will run speedier.

The Two-level construction modeling is separated into two sections:

1) Client Application (Client Tier)

2) Database (Data Tier)
On customer application side the code is composed for sparing the information in the SQL server
database. Customer sends the solicitation to server and it handle the appeal & send back with
information. The primary issue of two level building design is the server can't react different
solicitation same time, thus it cause an information respectability issue.
Simple to keep up and change is bit simple
Correspondence is speedier

Assignment 1 CMP556
Three-Tier Architecture:

Three-level construction modeling normally contain a presentation level, a business or

information access level, and an information level. Three layers in the three level construction
modeling are as per the following:
1) Client layer
2) Business layer
3) Data layer
1) Client layer:
It is additionally called as Presentation layer which contains UI some piece of our application.
This layer is utilized for the configuration reason where information is exhibited to the client or
data is taken from the client. For instance planning enlistment structure which contains content
box, name, catch and so forth.

2) Business layer:
In this layer all business rationale composed like acceptance of information, estimations,
information insertion and so forth. This goes about as an interface between Client layer and Data
Access Layer. This layer is additionally called the delegate layer serves to make correspondence
quicker in the middle of customer and information layer.

3) Data layer:
In this layer real database is comes in the photo. Information Access Layer contains systems to
associate with database and to perform addition, redesign, erase, get information from database
in view of our data information.

Preferences
Elite, lightweight relentless articles
Adaptability Each level can scale evenly
Execution Because the Presentation level can reserve appeals, system usage is minimized, and
the heap is lessened on the Application and Data levels.
High level of adaptability in organization stage and arrangement

Assignment 1 CMP556
Better Re-utilization
Enhance Data Integrity
Enhanced Security Client is not immediate access to database.
Simple to keep up and adjustment is bit simple, won't influence different modules