Different entities that are being stored in the database will sometimes have similar attribute fields in common. By storing common attributes in a supertype table and unique attributes in a subtype table, you can streamline the structure of your relations
- [Narrator] When you start combining your field list…into table groupings,…you might start to identify tables…that share many characteristic fields,…but then have a subset of fields…that are specific to a particular business rule.…For instance, let's suppose…that the Two Trees Olive Oil Company…caters to two distinct types of customers.…Wholesale customers that resale our products,…and retails customers that purchase from us directly.…Both types of customers will have common fields,…such as a customer ID number, address fields,…and they would both be linked to an order history…through an invoices table.…
But each type of customer also has specific attributes…that are unique to their type of customer…that they represent.…Retail customers would have a first and last name,…whereas a whole sale customer would have a company name.…Further, you might have related information…that only applies to one type of customer.…The wholesale customers might have…multiple regional sales representatives.…Whereas the retail customer is their own point of contact.…
Adam Wilbert covers the basics of relational database design, regardless of whether you use Access, FileMaker, Open Office, or SQL Server. Learn how to prevent data anomalies, gather requirements to plan your design, and develop a conceptual data model—translating your ideas into components like tables, relationships, queries, and views. Plus, learn about logical design considerations that can help you construct a database that is easy to maintain.
- Identify the three rules of relations.
- Summarize the four stages of developing a relational database.
- Describe a strategy one might use to ensure a database remains flexible in terms of the questions a user can ask.
- Explain how to avoid scope creep.
- Recall the characteristics of a Lookup Table.
- Recognize situations in which denormalization would be beneficial.
- Understand the types of relationships modeled by junction tables.
- Define referential integrity.
Skill Level Beginner
1. Relational Database Basics
Relational structures3m 46s
2. Preventing Data Anomalies
3. Gathering Requirements
4. Developing the Conceptual Data Model
5. Normalizing Your Data
6. Logical Design Considerations
7. Developing the Physical Database
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.