Primary keys are one of the core components of a relational database. They’re used to ensure that each record in a table is uniquely identifiable. They're also used to link related tables together.
- [Narrator] One of the most important restrictions…that are placed on our data tables is that…every row or record must be uniquely identifiable.…There has to be one piece of information that you can use…to identify exactly one record with absolutely no ambiguity.…This particular field is called the table's primary key…and it's the value that we use when it comes time…to link our related data tables together.…Let's suppose that one of our customers has an issue…with a product that he ordered.…We can go to our orders table and look up the information…about that transaction, but how do we find it?…The customer first gives us their name,…which will show us all of the transactions…that they've completed with us,…and hopefully that's a bunch.…
This is good to know and it gets us close,…but it doesn't find us a specific transaction.…They could tell us the date they placed the order,…but again, that would also return all of the other…orders placed on the same date,…and not identify their own order specifically.…This is why we have something like an invoice number column.…
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.