Database Systems Chapter 4

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/15

flashcard set

Earn XP

Description and Tags

CS 4210 Module 4- Database Design using Normalization

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

16 Terms

1
New cards

How to assess table structure

-determine multivalued dependencies, functional dependencies, candidate keys, primary keys, foreign keys, ref integrity constraints

-count number of columns and rows (i think this is the first step)

2
New cards

If the database is updatable, we want it normalized in

BCNF. If the database is read only we may not use BCNF

3
New cards

Updateable Databases

operationa databases of a company, modification anomalies and inconsistencies are priority

4
New cards

Advantages of Normalization

no mod anomalies, no duplicate data, data integrity, paster queries

5
New cards

Disadvantages of Normalization

more complicated SQL

extra DBMS work = slower applications

6
New cards

when not to use BCNF

zip codes

7
New cards

Read-Only database

nonoperational database using data extracted from operational databases in data warehouses. For querying, reporting, and data mining. Used in BI Systems and data warehouses

8
New cards

Denormalization

joining of the data in normalized tables prior to the storing. Used on previously normalized tables to increase performance

9
New cards

How is Denormalization different from unnormalized tables

The benefits of denormalized tables are only realized on data otherwise normalized. Denormalizing improves read performance at the expense of write performance

10
New cards

Is denormalization good for read only tables

no, processing speed is more important

11
New cards

customized tables

read only db designed with many copies of the same data with each copy customized for specific applications

12
New cards

normalization vs DB Normalization

organizing data w tables vs make relational DB without redundancies

13
New cards

common design problems; multivalue, multicolumn problem

occurs when multiple values of an attribute are stored in more than one column

solution: use separate table to store them

14
New cards

common design problems; inconsistent values

same data, slightly different forms (different coding, spelling, etc)

to check this: ref integrity check

SQL GROUP BY clause

15
New cards

common design problems; missing values

missing or null value hasnt been provided. ie value might be null because not appropriate, appropriate but unknown, appropriate and known, but never entered.

how to check:

SQL IS NULL operatorcommon design problems;

16
New cards

common design problems; general purpose remarks column

columns with ‘comments’ or ‘notes’

important data in a verbose way