Study Notes For DB Design and Management Exam 1
Study Notes For DB Design and Management Exam 1
Table of Contents
Glossary Table 1
Summary Chap 1 12
Glossary Table
data—Raw facts; that is, facts that have not yet been processed to reveal their meaning
to the end user.
data management—A process that focuses on data collection, storage and retrieval.
Common data management functions include addition, deletion, modification and
listing.
metadata—Data about data; that is, data concerning data characteristics and
relationships. See data dictionary.
query—A question or task asked by an end user of a database in the form of SQL
code.
data warehouse database—A database that focuses primarily on the storage of data
used to generate information required to make tactical or strategic decisions.
database design—The process that yields the description of the database structure.
The database design process determines the database components. Database design
is the second phase of the database life cycle.
redundant data—Duplicated data that are stored in more than one location.
logical design—A stage in the design phase that matches the conceptual design to
the requirements of the selected DBMS an is, therefore, software-dependent. It is used
to translate the conceptual design into the internal model for a selected database
management system, such as DB2, SQL Server, Oracle, IMS, Informix, Access, and
Ingress.
data processing (DP) specialist—A now obsolete position formed in the conversion
from manual filing systems to computer filing systems; once filled by an employee who
created and programmed the necessary file structures, wrote the software that
managed the data in those structures, and designed the application programs that
produced reports from the file data.
data processing (DP) manager—A DP specialist who evolved into the department
supervisor. Roles include: managing the technical and human resources, supervising
the senior programmers, program troubleshooting.
physical data format—The way in which the computer ―sees‖ the data.
data redundancy—A condition that exists when the data environment contains
redundant—unnecessarily duplicated— data.
data inconsistency—A condition in which different versions of the same data yield
different (inconsistent) results.
data integrity—A condition in which given data always yield the same result. Data
integrity is mandatory in any database.
data anomaly—A data abnormality that exists when inconsistent changes to the
database have been made. Example: An employee moves, but the address change
is only corrected in one file and not across all files in the database.
data dictionary—A DBMS component that stores metadata – data about data.
Thus, the data dictionary contains the data definition as well as its characteristics
and relationships. A data dictionary may also include data that are external to the
DBMS. See also active data dictionary and passive data dictionary.
query language—A nonprocedural language that lets the user specify what i s to be
done without specifying how i t is to be done. An example of a query language is
SQL.
Redundant data are often the source of difficult to trace information errors.
A poorly designed database tends to generate errors that are likely to lead to BAD
decisions and BAD decisions can lead to the failure of an organization.
Although the file systems method of organizing and managing data was a definite
improvement over a manual system many problems and limitations became evident
in this approach.
3rd Generation Languages require the programmer to specify both WHAT must be
done and HOW it is to be done. Examples of this are COBOL, BASIC and
FORTRAN.
4th Generation Languages require the programmer to specify both WHAT must be
done WITHOUT specifying HOW it is to be done. Examples of this are SQL.
Programming in a 3GL can be a time consuming, high skilled activity. This is
because programmers must be familiar the physical file structure that is how and
where the files are stored in the computer.
The need to write 3GL Programs to produce even the simplest reports makes AD
HOC Queries impossible!!
DB Specialists and Managers are often harried and having numerous requests for
reports means reports often take weeks and months.
Another problem with 3GL programming is that as the number of files in the system
expands the System Administration becomes very difficult. Each file must have it’s
own file management system composed of programs that allow the user to do:
A change in any file’s structure requires the modification of all programs using that
file. Such modifications are required because the file system exhibits Structural
Dependency that is access to a file is dependent on its structure.
3. People – This component includes all users of the DB System. There are 5 types
of users in a DB System:
o Systems Administrator (SYSADM)—The person responsible for
coordinating the activities of the data processing function. The systems
administrator also manages the use of database software in a data
processing (DP) department; solicits and evaluates database designs,
coordinates the development of applications based on the data resource,
and assigns the right to manage the database(s) to selected individuals.
The systems administrator also coordinates the activities of all database
administrators (DBAs) in a multidatabase operation.
o Database Administrator (DBA)—Person responsible for the planning,
organization, control and monitoring of the centralized and shared
corporate database. The DBA is the general manager of the database-
administration department.
o Systems Analysts and Programmers – Design and implement the
applications programs. They design and create the data entry screens,
reports and procedures through which end users access data.
o End User – People who use the application programs to run the
organizations daily operations.
4. Procedures – They are the instructions and rules that govern the design and use
of the DB Systems.
5. DATA – The word DATA covers the collection of facts stored in the DB.
DB levels of system complexity are dedicated by the organizations activities and the
environment within which those activities take place.
DBMS Functions:
1. Data Dictionary Management – The DBMS stores the definitions of the data
elements and their relationships (metadata) in the Data Dictionary.
2. Data Storage Management – The DBMS creates and manages the complex
structures required for data storage.
3. Data Transformation and Presentation – The DBMS transforms the entered
data to conform to the data structures that are required to store the data. It
relieves is of the chore of distinguishing between Logical and Physical format.
Data Independence—A condition that exists when data access is unaffected by
changes in the physical data storage characteristics. The DBMS formats the
physically retrieved data to make it conform to the users logical expectations.
4. Security Management – The DBMS creates a security system that enforces user
security and data privacy within the DB. Security rules determine which users
can access the DB, which data items each user may access and which data
operations (read, add, modify, delete...) the user may perform.
5. Multi-User Access Control – The DBMS creates the complex structures that
allow multiple users access to the data. In order to provide data integrity and data
consistency the DBMS uses sophisticated algorithms to ensure that multiple
users can access the DB concurrently without compromising the integrity of the
DB.
6. Backup and Recovery Management – The DBMS provides backup and data
recovery procedures to ensure data safety and integrity. Current DBMS systems
provide special utilities that allow the DBA to perform routine and special backup
and restore operations.
7. Data Integrity Management – The DBMS promotes and enforces integrity rules
to eliminate data integrity problems. Thus minimizing data redundancy and
maximizing data consistency. The Data Relationships stored in the Data
Dictionary are used to enforce data integrity.
8. Database Access Languages and Application Programming Interfaces – the
DBMS provides data access through a query language.
o A query Language is a Non Procedural Language (4GL) o The
DBMS query language contains two components:
▪ Data Definition Language (DDL)—The language that allows
a database administrator to define the database structure,
schema, and subschema.
▪ Data Manipulation Language (DML)—The language (set of
commands) that allows the end user to manipulate the data in
the database (Select, Insert, Update, Delete). o The DBMS
also provides data access to programmers via Procedural
Languages (3GL) ex: COBAL, C, PASCAL, VB...
The DBMS allows chores to be done and performed without the tedious and time
consuming programming required in the File Management System.
The availability of a DBMS makes it possible to tackle far more sophisticated uses of
the DATA resources, if the DB is designed to make use of that available power.
Summary Chap 1