Introduction To Database
Introduction To Database
Chapter 1
It is a computerized record keeping system, which stores related data in an organized way. The
overall purpose of a database system is to store information and to allow users to add, delete,
retrieve, search, query and update that information upon request. The information concerned can
be anything that is deemed to be of significance to the individual or organization the system is
intended to serve. That is, needed to assist in the general process of running the business of that
individual or organization.
A database system is basically a computerized record keeping system. Users of the database can
perform a variety of operations. Such as:
Adding new data to empty file
Adding new data to existing file
Retrieving data from existing file
Modifying data to existing file
Deleting data from existing file
Searching for target information
Data handling approaches
Data management passes through the different levels of development along with the
development in technology and services. These levels could be best described by categorizing
the levels into three levels or types of development/approach. Even though there is an advantage
and a problem overcome at each new data handling approach/level, all methods or approaches of
data handling are in use to some extent. The major three approaches/levels are discussed as
follows:
1. Manual Approach
In the manual data handling approach, data storage and retrieval follows the primitive and
traditional way of data/information handling where cards and paper are used for the purpose.
Typing the data on paper and put in a file cabinet. The data storage and retrieval will be
performed using human labour. This approach Works well if the number of items to be stored is
small.
The organization of the database becomes necessary when the data is voluminous. Otherwise,
managing data will be very difficult.
E.g. A Manufacturing Company with product data
A Bank with account data
A Hospital with patients
A University with Students
A government with planning data
The advantages of a database approach over the traditional and paper-based methods of record
keeping will include the following:
Compactness: no need for possibly voluminous paper files.
Speed: the machine can retrieve and change data faster than a human can. In particular, ad hoc,
spur-of-the-moment queries
(“Do we have more red screws than blue ones?”) can be answered quickly without any need for
time consuming manual or visual searches.
Accuracy: timely, accurate and up-to-date information is available on demand at any time.
The foregoing benefits apply with even more force in a multi-user environment where the
database is likely to be much larger and much more complex than in the single user case. In a
multi-user environment the database system provides the enterprise with centralized control of its
data. The centralized approach has the following advantages:
Data can be shared: two or more users can access and use same data instead of storing data in
redundant manner for each user.
Redundancy can be reduced: In non database or non centralized systems each application or
department keeps its own private files. The files may hold common data elements that exist as
part of the enterprises data. This will lead to considerable redundancy in stored data, with
resultant waste in storage space. For example, a personnel application and an education records
application might both own a file that includes department information for employees. Note that,
this is not to say we should eliminate all redundancies. Sometimes there are sound reasons for
maintaining several copies of the same data.
Inconsistency can (to some extent) avoided: If there are a number of files which store similar
data elements among other sorts of data then when a change is made to a particular data (among
the common ones) this change need to be done throughout the system where there is such data
stored. This is not, often, the case. Some of the data might be updated and others left as they are
which results in inconsistent information about the same phenomena.
Standards can be enforced: Standardizing data representation is particularly desirable as an aid
to data interchange or migration of data between systems. Likewise, data naming and
documentation standards are also very desirable as they facilitate data sharing and
understandability.
Security restrictions can be applied: Since the data is stored in one place/area all accesses to
the data can be regulated by the system through some defined rules built into the system. The
system ensures that the only means of access to the database is through proper channels.
Different rules can be established for each type of access (retrieve, insert, delete, etc.) to each of
information to the database.
Integrity can be maintained The problem of integrity is the problem of ensuring the data in the
database is accurate. Inconsistency between two entries that represent the same “fact” is an
example of lack of integrity. It is more serious in a multi-user environment where one user may
enter bad data and other users may go on working on the updated data as if it were a correct one.
Conflicting requirements can be balanced: knowing the overall requirements of the enterprise
the Database Administrator (DBA) can structure the system so as to provide an overall service
that is best for the enterprise. For example, a representation can be chosen for the data in storage
that gives fast access for the most important applications (possibly at the cost of poorer
performance for certain other applications).
Transaction support can be provided: basic demands of any transaction support systems are
implanted in a full scale DBMS.
Improved decision support: the database will provide information useful for decision making.
Less labour: unlike the other data handling methods, data maintenance will not demand much
resource.
Centralized information control: since relevant data in the organization will be stored at one
repository, it can be controlled and managed at the central level
structure of the database?. These and similar issues might be concerned with the way the data
stored in the system.
Hardware: This portion of the system consists of secondary storage media (disks, tapes and
optical media) that are used to hold the stored data and associated device controllers (hard disk
controller, etc.); and the processor(s) and associated main memory that are used to support the
execution of the database system software.
Software: This is the software, Database Management System (DBMS) that is responsible for
the overall management of communications between the user and the database. It is found
between the data and the users, which, in other words, means the data is entirely covered or
shielded by the DBMS software. The DBMS provides facilities for operating on the database.
This is the most important software component in the overall system that allows the user to
interact with the data.
Users and Designers of Database: As people are one of the components in DBS environment,
there are group of roles played by different stakeholders of the designing and operation of a
database system.
1. Data Base Administrator (DBA)
Responsible to oversee, control and manage the database resources (the database itself,
the DBMS and other related software)
Authorizing access to the database
Coordinating and monitoring the use of the database
Responsible for determining and acquiring hardware and software resources
Accountable for problems like poor security, poor performance of the system
Involves in all steps of database development
We can have further classifications of this role in big organizations having huge
amount of data and user requirement.
Data Administrator (DA): is responsible on management of data resources.
Involves in database planning, development, maintenance of standards policies
and procedures at the conceptual and logical design phases.
We have two distinctions of database designers, one involving in the logical and conceptual
design and another involving in physical design.
Application programmers who are responsible for writing application programs that use
the database using some programming language such as COBOL, Pascal, or a
programming language built-in to the DBMS.
4. End-users: These are those people who are engaged on processing different types of
operations on the database system. Users are workers, whose job requires accessing the
database frequently for various purpose. There are different group of users in this
category.
Naïve Users:
Sizable proportion of users
Unaware of the DBMS
Only access the database based on their access level and demand
Use standard and pre-specified types of queries.
Sophisticated Users
Are users familiar with the structure of the Database and facilities of the
DBMS.
Have complex requirements
Have higher level queries
Are most of the time engineers, scientists, business analysts, etc
Casual Users
Users who access the database occasionally.
Need different information from the database each time.
Generally, End users are those that interact with the system from online workstations or
terminals that use an application program developed by application programmers or those that
query the system through an interface provided by the DBMS.
These users can be again classified as “Actors on the Scene” and “Workers Behind the Scene”.
Actors On the Scene:
Data Administrator
Database Administrator
Database Designer
End Users
Workers Behind the Scene
DBMS designers and implementers: who design and implement different DBMS
software.
Tool Developers: experts who develop software packages that facilitates database
system designing and use. Prototype, simulation, code generator developers could be an
example. Independent software vendors could also be categorized in this group.
Operators and Maintenance Personnel: system administrators who are responsible for
actually running and maintaining the hardware and software of the database system and
the information technology facilities.