Database Set 1

Front 1

A collection of logically coherent data with some inherent meaning designed and built for some specific pupose, but not just random information (aka "My Documents" folder= bad, Phonebook = good)

Back 1

Database

Front 2

Pieces of data are connected to each other in a rational, logical manner. Attribute of database.

Back 2

Logically coherent

Front 3

The data as a whole can be described (e.g "a collection of customers"). Attribute of database.

Back 3

Inherent Meaning

Front 4

The data was organized with a particular audience in mind. Attribute of database.

Back 4

Specific Purpose

Front 5

A general purpose software system that enables defining, constructing, manipulating and sharing of databases.

Back 5

DBMS: Database Management System

Front 6

Description of what data in the database means.

Back 6

Meta-data

Front 7

Type of file processing where each application developer comes up with his own file format for each specific application. There may be some sharing formats but data is generally locked to an application.

Back 7

Traditional file processing

Front 8

Type of file processing where there is a single repository of data. It is defined once and can be used by multiple applications and users.

Back 8

Database Approach

Front 9

Name the four characteristics of the database approach to file processing.

Back 9

1) Self-describing
2) Separation of programs and data
3) Multiple views of the data
4) Sharing of data (multiple users/applications)

Front 10

(Characteristic) Every database system contains a description of the database structure. (e.g. Meta-data)

Back 10

Self-describing

Front 11

(Characteristic) The use off meta-data to advertise what's available to applications and users. Also known as DATA ABSTRACTION: DBMS acts as intermediary between the data model and the physical data stored on disk. Improved on the traditional file approach where data definition was encoded in the application programs.

Back 11

Separation of programs and data

Front 12

(Characteristic) Allows data subsets to be visible based on need (e.g. Looking at your shopping cart on Amazon vs warehouse worker viewing list of items to ship out). Provides ability to restrict level of access to data (known as view)

Back 12

Multiple views of data

Front 13

(Characteristic) The database approach allows multiple users to share data simlutaneously.

Back 13

Sharing of Data

Front 14

Transactions from database are ACID, which stands for:

Back 14

Atomic, Consistent, Isolated, and Durable.

Front 15

Idea that transactions from database are "all or nothing".

Back 15

Atomic

Front 16

Idea that transaction from database must not put the database in a state that violates its constraints.

Back 16

Consistent

Front 17

Idea that transaction occurs as they happened by themselves.

Back 17

Isolated

Front 18

Idea that completed transactions can survive system failure.

Back 18

Durable

Front 19

Most users of a database fall into this category, use canned screens and reports to do their job.

Back 19

Typical ("naive") users

Front 20

These users need a better understanding of the database and they write their own reports - often for one-off jobs.

Back 20

Sophisticated ("power") users

Front 21

These DB users determine what software the users need and write it for them.

Back 21

Systems Analysts and Software Engineers

Front 22

This DB user administers access rights, monitors the database for performance, etc.

Back 22

DBA, Database Administrator

Front 23

These DB users Design the layout of the database, often overlap with DBAs and System Analysts depending on the organization.

Back 23

Database Designers.

Front 24

(Term/Concept) This idea keeps the data serparate from how it is stored in the system. Data actually stored in files as with any other computer system. DB approach provides a way of letting the user interact with the data without caring about how it is stored.

Back 24

Data Abstraction

Front 25

(Term/Concept) This helps to illustrate the database structure including: data types, relationships between data records, constraints on data records.

Back 25

Data Model

Front 26

This model type shows how the users perceive the data (via entities: real-world concepts like student), Attributes (property of entity like GPA), and Relationship or association between entities (students are enrolled in sections)

Back 26

High-level model

Front 27

This model simply shows how the data is stored in the computer.

Back 27

Low-level model

Front 28

This data model is like a cross between the low and high level data models. It is still a way to organize data so users can understand it but also shows how data is physically stored. Relational data models fall into this category and are widely used.

Back 28

Representational model

Front 29

Part of the data model that is essentially a description the DB.

Back 29

Database Schema

Front 30

Part of the Three Schema Architecture that shows the physical storage of the database.

Back 30

Internal Level

Front 31

Part of the Three Schema Architecture that hides details of physical storage, describes; entities, relationships, constraints, etc; and is usually the level where the DB is actually designed and implemented.

Back 31

Conceptual Level

Front 32

Part of the Three Schema Architecture that the user views. It describes parts of database a use is interested in and hides the rest (different user, different view)

Back 32

External Level

Front 33

Type of data Independence where one changes the conceptual schema without changing the external schemas or application programs. Examples include expanding or reducing the DB and Changing the constraints.

Back 33

Logical Data Independence

Front 34

Type of data Independence where one changes the physical storage of data without changing the conceptual storage of the data without changing the conceptual schema.

Back 34

Physical Data Independence

Front 35

(DBMS Language) Defines both Schemas

Back 35

Data Definition Language (DDL)

Front 36

(DBMS Language) Specifies the internal schema

Back 36

Storage Definition Language (SDL)

Front 37

(DBMS Language) Specifies user views/mappings to conceptual schema

Back 37

View Definition Language (VDL)

Front 38

(DBMS Language) This allows for retrieval insertion, deletion, and modification.

Back 38

Data Manipulation Language (DML)

Front 39

(DBMS Language) DML type that can be used on its own to specify complex database operations concisely. Set-at-a-time or set-oriented

Back 39

High-level or nonprocedural DML

Front 40

(DBMS Language) DML type that must be embedded in a general purpose programming language. Record-at-a-time.

Back 40

Low-level or Procedural