Building relationships between tables allows the database to pull associated data from the individual tables. Cardinality denotes the maximum number of records from each table that will be involved in a relationship, and optionality defines the minimum nu
- [Tutor] Now that our fields are organized by subject,…we should have a good understanding…of all the tables that will need to be created…in the database in order to satisfy our mission objectives.…Additional tables will be required…by the DBMS to operate efficiently,…but we'll identify those more thoroughly…in the next chapter.…The next stage is to begin hooking our tables together…in a series of relationships.…To do this, we'll evaluate each of our tables…against every other table,…and ask if there's an association between the entities.…In making this determination,…it's often helpful to try and verbalize the relationship.…
For instance, when comparing the Employees table…to an Invoice table,…you might say that the employee assists with an invoice,…or that an invoice is created by an employee.…If you were to compare the Invoices…with the Line Items table,…you might realize that invoice is made up of line items,…or that a line item appears on an invoice.…These types of sentences often come directly…from their requirements gathering phase…
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.