MGS351 Exam 2 review XCM C Flashcards

1
Q

Relational Databases

A

-Stores data in the form of related tables

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Relational Design

A

-Based on normalization and can be accomplished by using ERD’s

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Benefits of Relational Databases and designs

A

(1) Making sure the data is good.
Example: Adding, Deleting, and updating records
(2) Powerful to use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Principles of Design Relational Databases

A

(1) you must become a business expert
(2) knowing that Poor Relational Databases design lead to system failure
(3) Having a Proper design because this accurately reflects the organizations business rules
(4) Relational database is both an art and science (Cost-benefit)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Entity Relationship Diagrams (ERD)

A

-Its a Diagramming tool to design a database (Blueprint)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

If the ERD is designed properly then…?

A
  • The ERD will accurately reflect the the business rules of the organization.
  • Visual illustration of the organizations business rules
  • corrections are harder than adding on
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

1:1

A

One to one

(1) Relationships merge into one table.
(2) Then one entity becomes an attribute for the other
- Example: The entities is “A single student” to a “single Id card”
- then it would be a a single “STUDENT” with an attribute of an ID card

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

1:N

A

One to Many

  • all relationships must be simplified to this!
    (1) make a primary key in the “One Entity” and make it the Foreign key for the “Many Entity”
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

N:M

A

Many to Many

  • Needs to be simplified to 1-N
    (1) Add an intersection table between the two tables
    (2) flip the lines so that the many faces the intersection table
    (3) Include the Primary keys from both tables into the intersection table as foreign keys.
    (4) make a name for the intersection table
    (5) add relevant Attributes(fields) to the table if necessary
    (6) make a primary key or auto-number in the intersection table
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Entities

A
  • The rectangular shape
  • Attributes stored in here (data)
  • Correspond to Database tables
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Lines

A

Relationships between one another

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Attributes

A
  • These are fields
  • Descriptive value associated with an entity
  • Corresponds to database fields in a table
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Key Attributes

A
  • Correspond to Primary keys

- Uniquely identifies an entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What concept should be factored into relationships

A

-Time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Database Normalization

A

The way Database design is taught in classrooms

  • Learning process on how to use relationships
  • Number of rules to the relationship model which would simplify relationships
    • Avoid common database problems
    • Make the data as tightly bound as possible
    • Store the minimum amount of data
  • First, second, and third normal form
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Un-normalized vs. Normalized

A

Goal: The fields in a table depend on the key, the whole key, nothing but the key*

17
Q

Database normalization steps: 1NF

A

Remove repeating groups

18
Q

Database normalization step: 2NF

A

Remove fields that depend only on the key field.

-Applies to concatenate fields

19
Q

Database normalization step: 3NF

A

Remove fields that depend only on other fields