Exceptions and irregularities need to be accommodated in an automated system; they cannot be manually dealt with as they arise. During the interview process, pay special attention to areas that might have extraneous occurrences and make a plan for them.
- [Instructor] In the real world,…collecting data is a messy endeavor.…There will always be those exceptional cases…and outliers that'll pop up.…In a paper or a spreadsheet-based system,…often these cases are just dealt with…in an offhand or irregular manner when they occur.…But in a database they need to be accommodated…as if they were business as usual.…The primary way that you'll identify…these exceptional cases is through the interviews.…When asked about a checkout process,…an interviewee might say something like,…"We need to collect the customer's first…"and last name and their credit card number.…
"Oh, unless it's a wholesale customer.…"Then we need the business name…"and a purchase order number."…This brief explanation indicates several data items…that might be exceptions or irregularities.…We now know that we need to store separate…customer name and business name items.…We also learned that the database…should be collecting both a credit card data item…and a separate purchase order data item.…It also might be useful to store…
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.