ABSTRACT
Determining the type of database to be deployed for a project is a combination of access requirements and preference. In an effort to make an informed decision on which to deploy, the application engineer should be familiar with the types of databases as well as the pros/cons of each. In this entry we will consider two general types of databases and explore some of their applications and key points in the decision cycle when faced with a project.
A "flat file" database allows the user to specify data attributes (columns, datatypes, etc) for one table at a time, storing those attributes independantly of an application. dBase III and Paradox were good examples of this kind of database in the CP/M and MS-DOS environments, and the original FileMaker was a good Mac O/S example.
A relational database takes this "flat file" approach several logical steps further, allowing the user to specify information about multiple tables and the relationships between those tables, and often allowing much more declarative control over what rules the data in those tables must obey (constraints).
TABLE OF CONTENTS
TITLE PAGE
CERTIFICATION
ACKNOWLEDGEMENT
DEDICATION
ABSTRACT
TABLE OF CONTENTS
CHAPTER ONE
1.0 INTRODUCTION
1.1BACKGROUND OF STUDY
1.3PURPOSE OF STUDY
1.4IMPORTANCE OF STUDY
1.5DEFINITION OF TERMS
1.6ASSUMPTION OF STUDY
DATA TRANSFER OPERATIONS OF THE FLAT FILE DATABASE SYSTEM
CHAPTER TWO
LITRATURE REVIEW
2.1 THE CONCEPT OF RELATIONAL DATABASE SYSTEM
CHAPTER THREE
3.0 FLAT FILE DATABASE SYSTEM VS RELATIONAL DATABASE SYSTEM
3.1 FLAT FILE DATABASE
3.2 RELATIONAL DATABASE
3.3 SELECTING A DATABASE: FLAT FILE VS. RELATIONAL
CHAPTER FOUR
4.0 COMPARING THE TWO DATABASE TYPES
4.1 ADVANTAGES OF A DATABASE
4.2 ADVANTAGES OF THE FLAT FILE DATABASE SYSTEM
CHAPTER FIVE
5.0 CONCLUSION AND REFERENCES
5.1 CONCLUSION
5.1LIMITATION OF STUDY
5.3 REFERENCES
Subscribe to access this work and thousands more