A good database design is, therefore, one that:
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.
* Provides the database management system (e.g. ACCESS) with the information it requires to join the information in the tables together as needed.
In our lab exercise we have used a small database with the data of Products and Suppliers. We organizes data in two-dimensional tables with rows and columns called relations. Each table contains data about an entity and its attributes. The data is stored in tables made up of columns (product name, product category, selling price) and each column must be of a single data type. Those collection values is called a row from the table. Each table also contains a key filed to uniquely identifies instances of that unique record. (e.g. product name:classic 109, coolest 100)
We have data in a same file and join the information together.
* Accommodates your data processing and reporting needs. The database management system for creating, storing, organizing, and accessing data from a database. We use tables to data storage, selecting and viewing records, data input and display (Two display method:"Inventory Status by Product Category"& "Inventory Status by Supplier Name")
We used the MS ACCESS Report Wizard to easily design a customized report even without any technical background.
回覆刪除Each table in our sample database also focuses only on a single subject. For example, you won't see any supplier-related information in the Product table. To find out the address of a supplier for a product, you can look it up in the Supplier table according to the supplier ID in the product record.