• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 2. Database Design > Midchapter Review

Midchapter Review

We'll look at the problems of table creation in much more depth in a little while. Right now, let's quickly review what you've done. You first created a mission statement for the Classic TV database. You followed up by developing mission objectives—what you want the database to accomplish. You used those mission objectives to come up with a list of data needs. From those data needs, you developed a preliminary list of columns you could use to store data.

None of these steps is peculiar to relational databases. Creating a mission statement and defining mission objectives aren't bad ideas for any information project—indeed, for achieving any goal. Even when you use a simple spreadsheet to store data, you still have to decide what columns you need and what data to put in them. And my diagnosis of the problems of “one table fits all” could just as easily be used to launch a discussion of the benefits of database models besides relational databases.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint