Acct 321 (C.4) Relational Databases

Front 1

Database

Back 1

A set of interrelated, centrally coordinated data files that are stored with as little data redundancy as possible.

Front 2

Data Base Management System (DBMS)

Back 2

The program that manages and controls the data and the interfaces between the data and the application programs that use the data stored in the database.

Front 3

Database System

Back 3

The database, the DBMS, and the application programs that access the database through the DBMS.

Front 4

Database Administrator

Back 4

The person responsible for coordinating, controlling, and managing the database.

Front 5

Data Warehouse

Back 5

Very large databases containing detailed and summarized data for a number of years that are used for analysis rather than transaction processing.

Front 6

Business Intelligence

Back 6

Analyzing large amounts of data for strategic decision making.

Front 7

Online Analytical Processing (OLAP)

Back 7

Using queries to investigate hypothesized relationships among data.

Front 8

Data Mining

Back 8

Using sophisticated statistical analysis to "discover" unhypothesized relationships in the data.

Front 9

Record Layout

Back 9

Document that shows the items stored in a file, including the order and length of the data fields and the type of data stored.

Front 10

Logical View

Back 10

How people conceptually organize, view, and understand the relationships among data items.

Front 11

Physical View

Back 11

The way data are physically arranged and stored in the computer system.

Front 12

Schema

Back 12

A description of the data elements in a database, the relationships among them, and the logical model used to organize and describe the data.

Front 13

Conceptual-Level Schema

Back 13

The organization-wide view of the entire database that lists all data elements and the relationships between them.

Front 14

External-Level Schema

Back 14

An individual users's view of portions of a database; also called a subschema.

Front 15

Subschema

Back 15

A subset of the schema; the way the user defines the data and the data relationships.

Front 16

Internal-Level Schema

Back 16

A low-level view of the entire database describing how the data are actually stored and accessed.

Front 17

Data Dictionary

Back 17

Information about the structure of the database, including a description of each data element.

Front 18

Data Definition Language (DDL)

Back 18

DBMS language that builds the data dictionary, creates the database, describes logical views, and specifies record or field security constraints.

Front 19

Data Manipulation Language (DML)

Back 19

DBMS language that changes database content, including data element creations, updates, insertions, and deletions.

Front 20

Data Query Language (DQL)

Back 20

High-level, English-like, DBMS language that contains powerful, easy-to-use commands that enable users to retrieve, sort, order, and display data.

Front 21

Report Writer

Back 21

DBMS language that simplifies report creation.

Front 22

Data Model

Back 22

An abstract representation of database contents.

Front 23

Relational Data Model

Back 23

A two-dimensional table representation of data; each row represents a unique entity (record) and each column is a field where record attributes are stored.

Front 24

Tuple

Back 24

A row in a table that contains data about a specific item in a database table.

Front 25

Primary Key

Back 25

Database attribute, or combination attributes, that uniquely identifies each row in a table.

Front 26

Foreign Key

Back 26

An attribute in a table that is also a primary key in another table; used to link the two tables.

Front 27

Update Anomaly

Back 27

Improper database organization where a non-primary key item is stored multiple times; updating the item in one location and not the others causes data inconsistencies.

Front 28

Insert Anomoly

Back 28

Improper database organization that results in the inability to add records to a database.

Front 29

Delete Anomaly

Back 29

Improper organization of a database that results in the loss of all information about an entity when a row is deleted.

Front 30

Relational Database

Back 30

A database built using the relational data model.

Front 31

Entity Integrity Rule

Back 31

A non-null primary key ensures that every row in a table represents something and that it can be identified.

Front 32

Referential Integrity Rule

Back 32

Foreign keys which link rows in one table to rows in another table must have values that correspond to the value of a primary key in another table.

Front 33

Normalization

Back 33

Following relational database creation rules to design a relational database that is free from delete, insert, and update anomalies.

Front 34

Semantic Data Modeling

Back 34

Using knowledge of business processes and information needs to create a diagram that shows what to include in a fully normalized database (in 3NF)