Appendix 5.6 Flashcards

1
Q

5.6 What is a relational database?

A

A relational database is a collection of interrelated two-dimensional tables, consisting of rows and columns.

+ [RD is NOT one big table—usually called a flat file.]
+ [Flat file? A file that contains all of the records and attributes. The design of a flat file entails far too much data redundancy.]
+ [A RD is usually designed with a number of related tables.]

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

5.6 What do a relational database’s rows and columns represent.

A

Each row represents a record, and each column (or field) represents an attribute (or characteristic) of that record.

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

5.6 What is a primary key, secondary and foreign key?

A

Every record in the database must contain at least one field that uniquely identifies that record so that it can be retrieved, updated, and sorted.

  • This identifier field, or group of fields, is called the primary key. In some cases, locating a particular record requires the use of secondary keys.
  • A secondary key is another field that has some identifying information, but typically does not uniquely identify the record.
  • A foreign key is a field (or group of fields) in one table that matches the primary key value in a row of another table. A foreign key is used to establish and enforce a link between two tables.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

5.6 What is a data model?

A

Data model is a diagram that represents the entities in the database and their relationships.

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

5.6 What is an entity?

A

Entity is a person, place, thing, or event about which an organization maintains information.

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

5.6 What are the disadvantages of relational databases?

A

Large-scale databases can be composed of many interrelated tables.
Result: the overall design can be complex, leading to slow search and access times.

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

5.6 What are the two types of query languages?

A
  1. Structured Query Language (SQL)
  2. Query by Example (QBE)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

5.6 Describe SQL.

A

Structured query language (SQL) is the most popular query language used for interacting with a database. SQL allows people to perform complicated searches by using relatively simple statements or key words.

Typical key words are SELECT (to choose a desired attribute), FROM (to specify the table or tables to be used), and WHERE (to specify conditions to apply in the query).

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

5.6 Describe QBE.

A

In Query By Example, the user fills out a grid or template—also known as a form—to construct a sample or a description of the data desired.

Users can construct a query quickly and easily by using drag-and-drop features in a DBMS such as Microsoft Access.

Conducting queries in this manner is simpler than keying in SQL commands.

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

5.6 What is entity relationship modeling?

A

The process of designing a database by organizing data entities to be used and by then identifying the relationships among them.

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

5.6 What is an entity in ERM (entity relationship modeling)?

A
  • Definable thing or concept within a system, such as a person/role (e.g. Student), object (e.g. Invoice), concept (e.g. Profile) or event (e.g. Transaction)
  • In ER diagram, the term “entity” is often used instead of “table”, but they are the same.
  • When determining entities, think of them as nouns
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

5.6 What are entity attributes in ERM?

A

Also known as a column, an attribute is a property or characteristic of the entity that holds it.

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

5.6 What are relationships in ERM?

A

Relationships illustrate an association between entities.

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

5.6 What are business rules in ERM? Hint: PPP

A

Business rules are precise descriptions of policies, procedures, or principles in any organization that stores and uses data to generate information.

To properly identify entities, attributes, and relationships, database designers first identify the business rules for the particular data model.

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

5.6 What is the degree of a relationship in ERM?

A

The degree of a relationship indicates the number of entities associated with a relationship.

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

5.6 What is a binary relationship in ERM?

A

A binary relationship exists when two entities are associated.

17
Q

5.6 Entity relationships may be classified as…

A
  • one-to-one
  • one-to-many
  • many-to-many
18
Q

5.6 What is cardinality?

A

Cardinality is indicator of business rules.

Cardinality refers to the maximum number of times an instance of one entity can be associated with an instance in the related entity.

Cardinality can be mandatory single, optional single, mandatory many, or optional many.

19
Q

5.6 What is data normalization?

A

Normalization is a method for analyzing and reducing a relational database to its most streamlined form to ensure minimum redundancy, maximum data integrity (accuracy, inconsistency), and optimal processing performance.

Data normalization is a methodology for organizing attributes into tables so that redundancy among the non-key attributes is eliminated.

Basically, we structure data before we work with it (ex.: we make sure each student has a unique student ID, not multiple)

20
Q

5.6 What are the five steps of normalization?

A

The first step in normalization is to determine the functional dependencies among the attributes. Then, compose the first normal form, the second normal form, and finally the third normal form. At the end, the join process produces an order amongst third normal form tables.

21
Q

5.6 What are functional dependencies?

A

Functional dependencies are a means of expressing that the value of one particular attribute is associated with a specific single value of another attribute.

22
Q

5.6 What is a null value?

A

Several attributes of each record have null values. A null value is an attribute with no data in it.

23
Q

5.6 What is the first normal form in normalization?

A

In the first normal form, the attributes under consideration are listed in one table and primary keys have been established.

This data file contains repeating groups and describes multiple entities. That is, this relation has data redundancy, a lack of data integrity, and the flat file would be difficult to use due to repeating groups. When data repeats itself, it is called repeating groups.

24
Q

5.6 What is the second normal form in normalization?

A

In the second normal form, we break the table into smaller tables to eliminate some of its data redundancy.

Second normal form does not allow partial functional dependencies. That is, in a table in second normal form, every non-key attribute must be functionally dependent on the entire primary key of that table.

However, the second normal form has not eliminated all the data redundancy.

25
Q

5.6 What is the third normal form in normalization?

A

In the third normal form, non-key attributes are not allowed to define other non-key attributes. That is, the third normal form does not allow transitive dependencies in which one non-key attribute is functionally dependent on another.

Third normal form structure has these important points:

  • It is completely free of data redundancy.
  • All foreign keys appear where needed to link related tables.
26
Q

5.6 What is the join operation?

A

The join operation combines records from two or more tables in a database to obtain information that is located in different tables.