Database Final Vocabulary

Front 1

Characteristic or property of an entity/may also be called a fieldor column

Back 1

Attribute

Front 2

allows the structure of a database to be changed withoutthe programs that access the database having to change

Back 2

Dataindependence

Front 3

a structure that can store information about multiple types of entities,the attributes of these entities, and the relationships among the entities

Back 3

Database

Front 4

a program, or a collection of programs, through which users interactwith a database. DBMSs let you create forms and reports quickly and easily, aswell as obtain answers to questions about the data stored in a database

Back 4

Database managementsystem (DBMS)

Front 5

a person, place, object, event, or idea for which you want to store andprocess data.

Back 5

Entity

Front 6

group of related characters. An attribute orcharacteristic about something (column)

Back 6

Field

Front 7

a database has integrity if the data in it satisfiesall established integrity constraints

Back 7

Integrity

Front 8

a rule that must be followed by data in a database

Back 8

Integrityconstraint

Front 9

Collections of related attributes (rows)

Back 9

Record

Front 10

duplication of data, or the storing of the same data in more than oneplace.

Back 10

Redundancy

Front 11

How the entities are related to each other

Back 11

Relationship

Front 12

a two- dimensional table-style collection of data inwhich all entries are single-valued, each column has a distinct name, all thevalues in a column are values of the attribute that is identified by the columnname, the order of columns is immaterial, each row is distinct and he order ofrows is immaterial. also called a table.

Back 12

Relation

Front 13

a minimal collection of columns (attributes) in atable on which all columns are functionally dependent and that chosen as themain direct-access vehicle to individual rows

a. Attribute or attributes that uniquely identifies each row in a relation

b. Two rows cannot have the same primary key

c. Ensures each row is unique

d. Underlined

Back 13

Primary Key

Front 14

primary key consisting of more than one attribute

Back 14

Composite Key

Front 15

a characteristic or property of an entity; also calleda field or column.

Back 15

Attribute

Front 16

a collection of related fields; can be thought of as arow in a table

Back 16

Record

Front 17

the rule that no column (attribute) that is part of the primary key mayaccept null values.

Back 17

Entity Integrity

Front 18

the rule that if a table A contains a foreign key that matches theprimary key of table B, then the value of this foreign key must either matchthe value of the primary key for some row in table B or be null.

Back 18

Referential Integrity

Front 19

a data value meaning “unknown” or “not applicable.”

Back 19

Null value

Front 20

Column B is functionally dependent on column A (or on a collection ofcolumns) if a value for A determines a single value for B at any one time

Back 20

functional dependence

Front 21

a column in a table that determines at least one other column

Back 21

determinant

Front 22

a minimal collection of columns (attributes) in a table on which allcolumns are functionally dependent but that has not necessarily been chosen asthe primary key.

Back 22

candidate key

Front 23

a candidate key that was not chosen to be the primary key

Back 23

alternate key

Front 24

a minimal collection of columns (attributes) in a table on which allcolumns are functionally dependent and that is chosen as the main direct-accessvehicle to individual rows.

Back 24

primary key

Front 25

a column (attribute) or collection of columns in a table whose value isrequired either to match the value of a primary key in a table or to be null.

Back 25

foreign key

Front 26

a dependency that holds transitivity. Can occur only in a relation that has 3 ormore attributes (A -> B -> C)

Back 26

transitive dependency

Front 27

a dependency of a column on only a portion of the primary key.

Back 27

partial dependency

Front 28

the number of Instances of one entity that can or must be associatedwith each instance of another entity

Back 28

associative entity

Front 29

relationship between instances of two entity types-byfar most common type of relationship

Back 29

binary relationship

Front 30

the number of items that must be included in a relationship also calledmultiplicity.

Back 30

cardinality

Front 31

the processing of a transaction file that contains a group, or “batch,”of records to update a database or another file

Back 31

Batch Update/ Processing

Front 32

a situation in which two or more database users are each waiting to useresources that are held by the other(s); also called deadly embrace.

Back 32

Deadlock

Front 33

a DBMS’s denial of access by other users to data while the DBMSprocesses one user’s updates to the database

Back 33

Locking

Front 34

a set of steps completed by a DBMS to accomplish a single user task

Back 34

Transaction

Front 35

A security measure that converts the data in a database to a formatthat’s indecipherable to normal programs. The DBMS decrypts, or decodes, thedata to its original form for any legitimate user who accesses the database

Back 35

Encryption

Front 36

the conversion of a table that is in third normal form to a table thatis no longer in third normal form. Denormalizing introduces anomaly problemsbut can decrease the number of disk accesses required by certain types oftransactions, thus improving performance.

Back 36

Denormalization

Front 37

copies at different sites

Back 37

Data replication

Front 38

computers connected to a network and used by users to access data (frontend processor or machine)

Back 38

Client

Front 39

computer providing data to clients (back end processor or machine)

Back 39

Server

Front 40

Server performs database functions. Clients perform presentationfunctions

Back 40

Client/Server System

Two-tier architecture

Front 41

Clients perform presentationfunctions. Database server performs database functions. Applicationservers perform business functions and interface between clients and databaseserver.

Back 41

Client/Server System:

Three-tier architecture

Front 42

the ability of a computer system to continue to function well asutilization of the system increases

Back 42

Scalability

Front 43

limited scope, data selected from Enterprise Data Warehouse (EDW)

Back 43

Data Mart

Front 44

the uncovering of new knowledge, patterns, trends, and rules from thedata stored in a data warehouse

Back 44

Data Mining