week9 after reading “geekgirls.com/databases”

ubiquitous [jubkwts]

adj existing, found or seeming to be found everywhere at the same time; omnipresent

ubiquitously adverb

After reading “Databases from scratch I: Introduction“

This website contains a lot of information about database, and this is the first page introduction section.

It was interesting to read, I had to remember what I did in 70s, and 80s. My first computer experience was in 1994. Even that period, I had to taste lotus, which absolutely unnecessary class for an ordinary house wife. But that class was the most important class in my whole life.

That class make gave me a lot of confidence in playing computer. That time most ordinary people believed that computer is something like a monster, something we had to afraid of.

It is interesting that ubiquitous is used by writer. I knew that this word is using in networking area. After reading explain, I understood.

It was a great reading, I had this database related subject when I studied in UWS in 2002. I remember that I was not difficult because I had a little bit of knowledge about Access. Anyway, this article reminds me all those terms and what I did for that particular subject. And I know database planning is not so easy to do, yet I have a great confidence in database stupidly

This the summary from that article.

A summary of the design process

Although your ultimate design will depend on the complexity of your data, each time you design a database, make sure you do the following:

• Break composite fields down into constituent parts. Example: Name becomes lastname and firstname.
• Create a key field which uniquely identifies each record. You may need to create an ID field (with a lookup table that shows you the values for each ID) or use a composite key.
• Eliminate repeating groups of fields. Example: If your table contains fields Location 1, Location 2, Location 3 containing similar data, it’s a sure warning sign.
• Eliminate record modification problems (such as redundant or inconsistent data) and record deletion and addition problems by ensuring each non-key field depends on the entire key. To do this, create a separate table for any information that is used in multiple records, and then use a key to link these tables to one another.