data base systems study text
Page 1
This paper is intended to equip the candidate with the knowledge, skills and attitude that will enable
him/her to administer and manage databases
A candidate who passes this paper should be able to:
Write structured query language (SQL) statements to manipulate data in databases
Develop a database application
Handle transactions and concurrency controls
Administer databases
Integrate databases and other applications
Manage database integrity issues
1. Introduction to databases
 Files, records, files and databases
 History of database systems
 Traditional file systems versus the database approach
 Characteristics, importance and limitations of database systems
 Database components and architecture
2. File organisation techniques
 Storage structures and blocking
 Unordered files
 Sequential files
 Indexing
3. Database models
 The role of data modeling
 The hierarchical model
 The relational model
 The object-oriented model
 The object-relational model
4. Database development life cycle
 Data and user requirements specification
 Stages of database development
 Conceptual, logical and physical database design
 Writing database requirements specifications
5. Relational database model
 Relational database concepts and properties
 E-R database design
Page 2
Database design anomalies
Relational algebra
Creating database design
implementing database design in mysql /oracle /DB2
6. Structured query language (SQL)
 Data definition language
 Data manipulation language
 Structure of SQL statements
 Data control
 in-built functions
 Writing SQL statements
 Using SQL functions
7. Transaction management and concurrency control
 Transaction management
 Properties of a transaction
 Serialisability and concurrency control
 Lock-based and timestamp-based protocols
 Types of failures
 Database recovery concepts and mechanisms
8. Database administration
 Database users
 Data administration
 Functions and roles of database administrators
 Monitoring database performance
9. Database security and integrity
 Security and integrity concepts
 Social, ethical and legal database issues
 Threats to database security and integrity
 Managing threats
 Establishing data backup procedure
10. Distributed database systems
 Introduction of concepts
 Distribution methods - fragmentation and replication
 Concurrency control mechanisms in distributed systems
 Two-tier database architecture
 Three-tier database architecture
11. Data warehousing and data mining
 Overview of data warehousing
 Characteristics of a data warehouse
 Components of a data warehouse
Page 3
Types of data warehouses
Elements of a data warehouse
Over view of data mining
Techniques of data mining
12. Integrating databases to other applications
 Importance of integrating databases to other applications
 Integrating databases to other applications (visual, C++, Java, C# among others)
 Developing web enabled database applications
13. Emerging issues and trends
Data hierarchy
Data Hierarchy refers to the systematic organization of data, often in a hierarchical form. Data
organization involves fields, records, files and so on.
A data field holds a single fact or attribute of an entity. Consider a date field, e.g. "September 19,
2004". This can be treated as a single date field (e.g. birthdate), or 3 fields, namely, month, day
of month and year.
A record is a collection of related fields. An Employee record may contain a name field(s),
address fields, birthdate field and so on.
A file is a collection of related records. If there are 100 employees, then each employee would
have a record (e.g. called Employee Personal Details record) and the collection of 100 such
records would constitute a file (in this case, called Employee Personal Details file).
Files are integrated into a database. This is done using a Database Management System. If there
are other facets of employee data that we wish to capture, then other files such as Employee
Training History file and Employee Work History file could be created as well.
History of Database Systems
Early Manual System
Data was stored as paper records.
Lot of man power involved.
Lot of time was wasted e.g. when searching
Therefore inefficient
Revolution began
1950s and early 1960s:
Page 4
Data processing using magnetic tapes for storage
Tapes provide only sequential access
Punched cards for input
Late 1960s and 1970s:
Hard disks allow direct access to data
Data stored in files
File based systems
Adequate for small applications
Separation and isolation of data
Each program maintains its own set of data.
Users of one program may be unaware of potentially useful data held by other programs
Duplication of data
Same data is held by different locations.
Wasted space and potentially different values and/or different formats for the same item.
Data dependence
File structure is defined in the program code.
Incompatible file formats
Programs are written in different languages, and so cannot easily access each other‘s
Fixed Queries/Proliferation of application programs
Programs are written to satisfy particular functions.
Any new requirement needs a new program.
Database Approach
Arose because:
Definition of data was embedded in application programs, rather than being stored separately and
No control over access and manipulation of data beyond that imposed by application programs.
The database and Database Management System (DBMS).
Database Management Systems (DBMS)
Object-oriented Object-relational
1960‘s Hierarchical Network
CMDB Mobile
Hierarchical Model
Well suited for data which are in someway related Hierarchically begin with a strictly defined
tree of data nodes Each node can contain some identifying data, plus a set of subnodes of a
specific child type
Page 5
Page 6
Network Model
 Supported more complex relations
 Physical file pointers were used tomodel the relations between files
 Relations had to be decide in advance
 Most suitable for large databases with well-defined queries and well-defined applications.
Relational Model (1970’s)
E.F. Codd introduced the relational model in 1970
Provides a conceptually simple model for data as relations (Typically considered
―tables) withal data visible.
DB2 from IBM is the first DBMS product based on the relational model
Other DBMS based on the relational model were developed in the late 1980s
today, DB2, Oracle, and SQL Serve rare the most prominent commercial
DBMS products based on the relational model
Object Oriented Data Model (1990’s)
Goal of OODBMS is to store object-oriented programming objects in a database without
having to transform them into relational format.
Extend the entity-relationship data model by including encapsulation, methods and
object identity
Object-relational models
Extend the relational data model by including object orientation and constructs to deal
with added data types.
Allow attributes of tuples to have complex types, including non-atomic values such as
nested relations.
Preserve relational foundations, in particular the declarative access to data, while
extending modeling power.
Modern Database Management Systems
DBMS are large complex pieces of software designed specifically for the efficient
management of data.
Oracle (Oracle Corporation)
Ingres (Computer Associates)
SQL Server (Microsoft Corporation)
Access (Microsoft Corporation)
And many more…s
Page 7
This is a SAMPLE (Few pages have been extracted from the
complete notes:-It’s meant to show you the topics covered in the full
notes and as per the course outline.
Download more at our websites:
To get the complete notes either in softcopy form or in
Hardcopy (printed & Binded) form, contact us on:
Call/text/whatsApp +254
[email protected]
[email protected]
[email protected]
Get news and updates by liking our page on facebook and
follow us on Twitter
Sample/preview is NOT FOR SALE
Page 8
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF