Normalization

Question 1

Process of applying a series of techniques and rules to a database in order to reduce data redundancy

Answer 1

Normalization

Question 2

Process of decomposing relations with anomalies to produce smaller, well-structured relations

Answer 2

Normalization

Question 3

Normalization techniques which involves splitting a relation into two or more

Answer 3

Projection

Question 4

Series of rules

Answer 4

Normal form

Question 5

any multivalued attribute have been removed

Answer 5

First Normal Form

Question 6

Main Goals of Normalization

Answer 6

• Minimize data redundancy, thereby avoiding anomalies and conserving storage space
• Simplify the enforcement of referential integrity constraints
• Make it easier to maintain data (insert, update, delete)
• Provide a better design that is an improved representation of the real world and a stronger basis for future growth

Question 7

Any multivalued Attribute have been removed, so there is a single value (possibly null) at the intersection of each row and column of the table

Answer 7

First Normal Form (1NF)

Question 8

Any functional dependencies have been removed

Answer 8

Second Normal Form (2NF)

Question 9

Any transitive dependencies have been remove

Answer 9

Third Normal Form (3NF)

Question 10

Constraints between two attributes or two sets of attributes

Answer 10

Functional Dependencies

Question 11

For any relation of R, attribute B is functionally dependent on attribute A if, for every valid instance A, that the value of A uniquely determines the value of B

Answer 11

Functional Dependencies

Question 12

Attribute on the left-hand side of the arrow in a functional dependency

Answer 12

Determinants

Question 13

SSN, VIN, ISBN are

Answer 13

Determinants

Question 14

Attribute, or combination of attributes, that uniquely identifies a row in a relation

Answer 14

Candidate Keys

Question 15

This property implies that each nonkey attribute is functionally dependent on that key

Answer 15

Unique identification

Question 16

No attribute in the key can be deleted without destroying the property of unique identification

Answer 16

Non-redundancy

Question 17

A relation that has a primary key and in which there are no repeating groups

Answer 17

First Normal Form

Question 18

if new product is ordered for order 1007 of existing customer, customer data must be re-entered, causing duplication

Anomalies

Answer 18

Insertion

Question 19

if we delete the Dining Table from Order 1006, we lose information concerning this item’s finish and price

Anomalies

Answer 19

Deletion

Question 20

changing the price of product ID 4 requires update in several records

Anomalies

Answer 20

Update

Question 21

The primary key consist of only one attribute (such as attribute Product_ID in the PRODUCT relation). By definition, there cannot be a partial dependency in such a relation

Answer 21

Second Normal Form

Question 22

No nonkey attributes exist in the relation (thus all of the attributes in the relation are components of the primary key). There are no functional dependencies in such a relation

Answer 22

Second Normal Form

Question 23

Evey nonkey attribute is functionally dependent on the full set of primary key attributes (such as the attribute Order_Quantity in the ORDER_LINE relation)

Answer 23

Second Normal Form

Question 24

A relation that is in second normal form and has no
transitive dependencies present

Answer 24

Third Normal Form

Question 25

A functional dependency between two (or more) nonkey attributes

Answer 25

Transitive Dependency

Question 26

a situation in which a non-key attribute of a table depends on only a part of the primary key.

Answer 26

Partial Dependency

Question 27

consists of one or more columns whose data contained within are used to uniquely identify each row in the table.

Answer 27

primary key

Question 28

is a set of one or more columns in a table that refers to the primary key in another table.

Answer 28

foreign key