September 2013
Intermediate to advanced
350 pages
9h 38m
English
When designing a database, it often makes sense to divide data between two or more tables. For example, if we are maintaining a database of patient records, we would probably want at least four tables: one for the patient’s personal information (such as name and date of birth), a second to keep track of appointments, a third for information about the doctors who are treating the patient, and a fourth for information about the hospitals or clinics those doctors work at.

We could store all of this in one table, but then a lot of information would be needlessly duplicated:
If we divide information between tables, ...
Read now
Unlock full access