Chapter 3 Flashcards
<p>Define relational database</p>
<p>enables logical representation of the data and its relationships
</p>
<p>what facilitates the creation of data relationships based on a logical construct?</p>
<p>Relation</p>
<p>Define table</p>
<p>two-dimensional structure composed of rows and columns</p>
<p>define key</p>
<p>one or more attributes that determine other attribute</p>
<p>What is the key's role based on?</p>
<p>determination</p>
<p>define functional dependence</p>
<p>attribute B is functionally dependent on A if all rows in table agree in value for A also agree in value for B</p>
<p>define primary key</p>
<p>Attribute or combination of attributes that uniquely identifies any given row
</p>
<p>composite key</p>
<p>Composed of more than one attribute
| </p>
<p>super key</p>
<p>Any key that uniquely identified each row
| </p>
<p>candidate key</p>
<p>A super key without unnecessary attributes
| </p>
<p>Entity integrity key</p>
<p>Each row (entity instance) in the table has its own unique identity
</p>
<p>Nulls</p>
<p>No data entry, Not permitted in primary key, &amp; should be avoided in other attributes.
</p>
<p>Foreign Key</p>
<p>An attribute whose values match primary key values in the related table
</p>
<p>referential integrity</p>
<p>FK contains a “VALID” value that refers to an existing valid tuple (row) in another relation</p>
<p>T/F, many RDBM's do not enforce integrity rules automatically</p>
<p>F</p>
<p>inner join</p>
<p>only returns matched records from the tables that are being joined</p>
<p>natural join</p>
<p>links tables by selecting rows with common values in common attributes</p>
<p>Outer join</p>
<p>matched pairs are retained and any unmatched values in other table are left null</p>
<p>Data dictionary</p>
<p>Provides detailed accounting of all tables found within the user/designer-created database
Contains (at least) all the attribute names and characteristics for each table in the system
Contains metadata: data about data
</p>
<p>system catalog</p>
<p>Contains metadata
Detailed system data dictionary that describes all objects within the database
</p>
<p>homonym</p>
<p>Indicates the use of the same name to label different attributes
</p>
<p>synonym</p>
<p>Indicates the use of different names to describe the same attribute
</p>
<p>1:M</p>
<p>Relational modeling ideal
Should be the norm in any relational database design
</p>
<p>1:1</p>
<p>Should be rare in any relational database design
| </p>
<p>M:N relationships
| </p>
<p>Cannot be implemented as such in the relational model
Can be changed into 1:M relationships
</p>
<p>What does data redundancy lead to?</p>
<p>data anomalies</p>
<p>what functions do foreign keys play?</p>
<p>Control data redundancies by using common attributes shared by tables
Crucial to exercising data redundancy control
</p>
<p>Indexes</p>
<p>Orderly arrangement to logically access rows in a table
| </p>
<p>Index key</p>
<p>Index’s reference point
Points to data location identified by the key
</p>
<p>unique index</p>
<p>Index in which the index key can have only one pointer value (row) associated with it
</p>
<p>t/f, each index is associated with only one table</p>
<p>T</p>
<p>define entity</p>
<p>an entity is a single person, place, or thing about which data can be stored.</p>
<p>degrees</p>
<p>number of entities in a relationship</p>
<p>unary relationship</p>
<p>A unary relationship is when both participants in the relationship are the same entity.</p>
<p>binary relationship</p>
<p> two entities participate and is the most common relationship degree.</p>
<p>cardinality</p>
<p>refers to the uniqueness of data values contained in a particular column (attribute) of a database table.</p>
<p>attribute</p>
<p>may describe a component of the database, such as a table or a field, or may be used itself as another term for a field.</p>
<p>associative entity</p>
<p>associates the instances of more or more entity types and contains attributes that are specific to the relationship between those entity instances.</p>
<p>an entity is also called a blank</p>
<p>object</p>
<p>an object of interest to the end user</p>
<p>entity</p>
<p>characteristics of entities</p>
<p>attributes</p>
<p>attribute that must have value</p>
<p>required attribute
| </p>
<p>required attribute</p>
<p>attribute that must have value</p>
<p>attribute that does not require a value</p>
<p>optional attribute</p>
<p>optional attribute</p>
<p>attribute that does not require a value</p>
<p>attribute that does not require a value</p>
<p>optional attribute</p>
<p>set of possible values for a given attribute</p>
<p>domain</p>
<p>domain</p>
<p>set of possible attributes for a given domain</p>
<p>one or more attributes that uniquely identify each entity instance</p>
<p>identifiers (primary keys)</p>
<p>primary key composed of more than one attribute</p>
<p>composite key</p>
<p>an attribute that can be further subdivided to yield additional attributes</p>
<p>composite attribute</p>
<p>an attribute that cannot be subdivided</p>
<p>simple attribute</p>
<p>Address is an example of a what?</p>
<p>composite attribute</p>
<p>age is an example of what</p>
<p>simple attribute</p>
<p>attribute whose value is calculated from other attributes</p>
<p>derived attribute</p>
<p>entities that participate in a relationship</p>
<p>participants</p>
<p>describes relationship classification</p>
<p>connectivity</p>
<p>expresses the minimum and maximum number of entity occurrence associated with one occurrence of the related entity</p>
<p>cardinality</p>
<p>crows feet are a form of </p>
<p>cardinality</p>
<p>can exist in the database only when it is associated with another related entity occurence</p>
<p>existence dependent</p>
<p>an entity that can exist apart from all of its related entities</p>
<p>existence independent</p>
<p>existence independent is also referred to as </p>
<p>strong entity or regular entity</p>
<p>exists if the primary key of the related entity does not contain a primary component of the parent entity</p>
<p>weak relationship</p>
<p>when the primary key of the related entity contains a primary key component of the parent entity</p>
<p>strong relationship</p>
<p>number of entities or participants associated with a relationship</p>
<p>relationship degree</p>
<p>when an association is maintained within a single entity</p>
<p>unary</p>
<p>two entities are associated </p>
<p>binary</p>
<p>three entities are associated</p>
<p>ternary</p>
<p>an entity that cannot be uniquely identified by its attributes alone</p>
<p>weak entity</p>
<p>a bridge table is also called</p>
<p>associative entity</p>
<p>a joint table is also referred to as</p>
<p>associative entity or bridge table</p>
<p>An entity which has its own key attribute is a regular entity.</p>
<p>regular entity or strong entity</p>
<p>An entity which depends on other entity for its existence and doesn't have any key attribute of its own</p>
<p>weak entity</p>
<p>In a parent/child relationship, a parent is considered as a strong entity and the child is what kind of entity</p>
<p>weak entity</p>
<p>the age of a student is considered what kind of attribute?</p>
<p>single value attribute</p>
<p>the telephone number of an employee is considered what kind of attribute?</p>
<p>multi-valued attribute</p>
<p>An employee works for an organization. Here "works for" is a what?</p>
<p>relationship</p>
<p>define data</p>
<p>raw facts</p>