Ais 4

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

Database management system (DBMS)

Back 2

Manages and controls the data. 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 (DBA)

Back 4

Responsible for coordinating, controlling, and managing the database

Front 5

Data warehouse

Back 5

One or more very lage databases containing both detailed and summarized data for a number of years that is used for *analysis* (not transaction processing)

Front 6

Business intelligence

Back 6

Analyzing large amounts of data for strategic decision

Front 7

Online analytical processing (OLAP)

Back 7

Using queries to investigate hypothesized relationships among data

Front 8

Data mining

Back 8

Sophisticated statistical analysis, including AI techniques such as neural networks, to discover unhypothesized relationships in the data

Front 9

Scrubbing the data

Back 9

Verifying the accuracy of data

Front 10

Data integration

Back 10

One advantage of a DBS. Master files are combined into large "pools" of data that many application programs access

Front 11

Data sharing

Back 11

Another advantage of a DBS. All data under one system can be shared among authorized users

Front 12

Minimal data redundancy and data inconsistencies

Back 12

Another advantage of a DBS. Data items are stored only once

Front 13

Data independence

Back 13

Another advantage of a DBS. The [data] and the [programs that use them] are independent of each other, so that each can be changed without changing the other. Facilitates programming and simplifies data management

Front 14

Cross-functional analysis

Back 14

Another advantage of a DBS. Relationships can be explicitly defined and used in the preparation of management reports (ie, the association between selling costs and promotional campaigns)

Front 15

Record layout

Back 15

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

Front 16

Database approach

Back 16

Provides two separate views of the data: the physical view and the logical view

Front 17

Logical view

Back 17

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

Front 18

Physical view

Back 18

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

Front 19

Schema

Back 19

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 20

Conceptual level schema

Back 20

Overall concept. Entire database. The organization-wide view of the entire database. Lists all data elements and the relationships among them

Front 21

External-level schema

Back 21

An individual user's view of portions of a database

Front 22

Subschema

Back 22

An external-level schema is called a subschema

Front 23

Internal-level schema

Back 23

A low-level view of the DB. Describes how the data are stored and accessed, including record layouts, definitions, addresses, and indexes

Front 24

Data dictionary

Back 24

Defines each data element in the database. Contains information about the structure of the DB. For each data element stored in the DB, there is a record in the dictionary describing it.

Front 25

Data definition language

Back 25

Builds the data dictionary, creates the database, describes logical views for each user, and specifies record or field security constraints

Front 26

Data manipulation language (DML)

Back 26

Changes database content, including data element creations, updates, insertions, and deletions

Front 27

Data query language (DQL)

Back 27

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

Front 28

Report writer

Back 28

Simplifies report creation. Users specify the data elements they want printed, and the report writer searches the DB, extracts the data elements, and prints them in the user-specified format

Front 29

Data model (logical data model)

Back 29

Abstract representation of database contents

Front 30

Relational data model

Back 30

Represents conceptual- and external-level schemas as if data are stored in two-dimensional tables

Front 31

Tuple (rhymes with couple)

Back 31

A row in a table

Front 32

Primary key

Back 32

The database attribute, or combination of attributes, that uniquely identifies a specific row in a table (a tuple)

Front 33

Foreign key

Back 33

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

Front 34

Update anomaly

Back 34

Occurs when data values are not updated correctly. When the address is updated in one location and not the others, an update anomaly occurs, and data inconsistencies result

Front 35

Insert anomaly

Back 35

Inability to add records to a database because attributes of one entity are stored in the record of a different entity. Solution: create two separate tables for each of the two entities, then link the two tables

Front 36

Delete anomaly

Back 36

Occurs when deleting a row has unintended consequences. Deleting a row loses all information about that entity. Again: have a sales table, and a customer table, then link the two

Front 37

Relational database

Back 37

A database using the relational data model

Front 38

Every column in a row must be single valued

Back 38

In a relational DB, there can only be one value per cell

Front 39

Primary keys cannot be null

Back 39

A primary key cannot uniquely identify a row in a table if it is null (blank)

Front 40

Entity integrity rule

Back 40

A nonnull primary key ensures that every row in a table represents something and that it can be identified

Front 41

Foreign keys, if not null, must have values that correspond to the value of a primary key in another table

Back 41

Foreign keys link rows in one table to rows in another table

Front 42

Referential integrity rule

Back 42

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. This is to ensure database consistency

Front 43

Normalization

Back 43

Following relational database creation rules to design a relational database that is free from delete, insert, and update anomalies. It's one way to design a DB by assuming that everything is initially stored in one large table

Front 44

Third normal form (3NF)

Back 44

Decompose the initial large table into a set (many, multiple) of tables. Free of update, insert, and delete anomalies

Front 45

Semantic data modeling

Back 45

The designer uses knowledge of business processes and information needs to create a diagram that shows what to include in the database. This diagram is then used to create a set of relational tables that are already in 3NF