Exam 1-Chapter 3 Flashcards

1
Q

Relational Model

A

View data logically rather than physically

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

Table

A
  • Two-dimensional structure composed of rows and columns
  • Structural an data independence
  • Resembles a file conceptually
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Entity Set

A

Contains group of related entity occurrences

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

Key

A
  • One or more attributes that determine other attributes
  • A key’s role is based on determination (if you know the value of attribute A, you can look up or determine the value of attribute B)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Functional Dependence

A

Attribute B is functionally dependent on the attribute A if each value in column A determines one and only one value in column B

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

Composite Key

A

Composed of more than one attribute (Combination of LNAME, FNAME, INIT, and PHONE are likely to be unique)

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

Ful Functional Dependence

A

Attribute B is functionally dependent on a composite key A, but not on any subset of A

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

Key Attribute

A

Any attribute that is part of a key

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

Superkey

A

Any key that uniquely identifies each row. A superkey functionally determines all of the entity’s attributers (STU_NUM)

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

Candidate Key

A

A superkey without unnecessary attributes (a minimal superkey; STU_NUM, STU_LNAME is a superkey but not a candidate key, STU_NUM ins a candidate key)

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

Nulls

A

No data entry; not permitted in primary key; should be avoided in other attributes; can represent different meaning, such as an unknown attribute value, a known but missing attribute value, and a “not applicable” condition

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

Flags

A

Designers use flags to avoid nulls. Flags indicate absence of some value

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

Controlled Redundancy

A

Makes the relational database work. Tables within the database share common attribues

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

Rational Schema

A

A textual representation of the database tables

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

Foreign Key

A

An attribute whose values match primary key values in the related table

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

Referential Integrity

A

Foreign key contains a value that refers to an existing valid tuple (row) in another relation

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

Secondary Key

A

Key used strictly for data retrieval purposes

18
Q

Entity Integrity Rules Requirement

A

All primary key entries are unique, and no part of a primary key may be null

19
Q

Reference Integrity Rules Requirement

A

A foreign key may have either a null entry, as long as it is not a part of its table’s primary key, or an entry that matches the primary key value in a table to which it is related (every non-null foreign key value must reference an existing primary key value

20
Q

Relational Algebra

A

Defines theoretical way of manipulating table contents using relational operators. Use of relational algebra operators on existing relations produces new relations

21
Q

SELECT

A

SELECT all rows in a table that satisfy a given condition. Results in a horizontal subset of the table

22
Q

PROJECT

A

Yields all values for selected attributes. Results in a vertical subset of the table

23
Q

UNION

A

Combines all rows from two tables, excluding duplicate rows. The tables must be union-compatible (have the same degree (# of columns); columns must be of the same type; column domains (range of permissible values) must be compatible)

24
Q

INTERSECT

A

Yields only the rows that appear in both tables. The tables must be union-compatible.

25
Q

DIFFERENCE

A

Yields all rows in one table that are not found in the other table. Subtracts one table from the other. The tables must be union-compatible

26
Q

PRODUCT

A

Yields all possible rows from two tables. Also known as the Cartesian product

27
Q

JOIN

A

JOIN combines data from two or more tables. It is the real power behind the relational database. Tables are linked by a common attribute

28
Q

Natural Join

A

Links tables by selecting rows with common values in common attributes
A three stage process: 1) PRODUCT 2) SELECT 3) PROJECT

29
Q

Inner Join

A

A join that returns matched records from the tables being joined

30
Q

Outer Join

A

Inner join+ returns all the matched records from the tables being joined, plus it returns the unmatched records from one of the two tables

31
Q

Left Outer Join

A

Yields all rows from CUSTOMER table, including those that do not have matching value in the AGENT table

32
Q

Right Outer Join

A

Yields all rows from AGENT table, including those that do not have a matching value in the CUSTOMER table

33
Q

Data Dictionary

A

Provides detailed accounting of all tables found within the database; contains (at least) all the attribute names and characteristics for each table in the system; contains metadata

34
Q

System Catalog

A

Contains metadata; detailed system data dictionary that describes all objects within the database (data dictionary + other information, such as user authorizations and access privileges)

35
Q

1:M Relationship

A

Relational modeling ideal; should be the norm in any relational database design

36
Q

1:1 Relationship

A

Should be rare in any relational database design; one entity related to only one other entity, and vice versa

37
Q

M:N Relationship

A

Cannot be implemented as such in the relational model; an M:N relationship can be changed into two 1:M relationship

38
Q

Data Redundancy

A

Leads to data anomalies (sometimes, data redundancy is necessary

39
Q

Index

A

Orderly arrangement used to logically (an quickly) access rows in a table

40
Q

Index Key

A

Index’s reference point; points to data location identified by the key

41
Q

Unique Index

A

Index in which the index key can have only one pointer value (row) associated with it

42
Q

Composite Index

A

An index key can have multiple attributes