"Relational databases organize data into tables, where each table contains lists of rows and columns similar to a spreadsheet. Each table strictly contains information about one kind of object only."
"In a simple database, you might have only one table. For most databases you will need more than one. For example, you might have a table that stores information about products, another table that stores information about orders, and another table with information about customers. In a relational database, we do not mix information about two different objects (e.g. orders and customers) in a single table."
"There are two basic principles behind relational database design. The first principle is that duplicate information (also called redundant data) is bad, because it wastes space and increases the likelihood of errors and inconsistencies. The second principle is that the correctness and completeness of information is important. If your database contains incorrect information, any reports that pull information from the database will also contain incorrect information. As a result, any decisions you make that are based on those reports will then be misinformed."
"A good database design is, therefore, one that:
* Divides your information into subject-based tables to reduce redundant data.
* Provides the database management system (e.g. ACCESS) with the information it requires to join the information in the tables together as needed.
* Helps support and ensure the accuracy and integrity of your information.
* Accommodates your data processing and reporting needs."
(Reference: http://office.microsoft.com/en-us/access/HA012242471033.aspx?pid=CH100645691033#Good)
Think of the small database we used in our lab exercise - Products and Suppliers. Briefly describe how this database observes any two of the four design principles outlined above.
No comments:
Post a Comment