• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/16

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

16 Cards in this Set

  • Front
  • Back
Data Dictionary
Info regarding the structure of the database. For each element there is a record in the data dictionary describing that element. Inputs include new or deleted data elements or changes in names, descriptions, or uses of existing elements. Outputs Include reports useful to programmers in which new systems are designed and implemented, systems are documented, and audit trails are created.
Data Definition Language
Build the data dictionary. Initialize or create the database. Describe the logical Views. Specify Limitation or constraints on security.
Data Manipulation Language
Updating portions of the database. Inserting portions of the database. Deleting portions of the database.
Data Query Language
Retrieving records, Sorting records, Ordering records, or Presenting subsets.
Primary Key
Primary key is the database attribute, or combination of attributes, that uniquely identifies a specific row in a table. The primary key cannot be null. Every column in a row must be single valued. All non-key attributes in a table should describe a characteristic of the object identified by the primary key.
Foreign Key
Foreign Key is a attribute in a table that is a primary key in another table. Foreign keys are used to link attributes. A foreign key must either be null or correspond to the value of a primary key in another table. Every column in a row must be single valued. All non-key attributes in a table should describe a characteristic of the object identified by the primary key.
Normalization
Way to design a well-structured relational database. Starts with the assumption that everything is initially stored in one large table & follows set of rules to decompose the table. Objective is to produce a set of tables in third-normal form.
Semantic data modeling
Way to design a well-structured relational database. Database designer uses knowledge of business processes and information needs to draw a graphical picture of what should be included in the database. The resulting graphic is used to create a set of relational tables that are in third-normal form.
Update Anomoly
Problem that arises when attributes that aren't characteristics of the primary key are stored in that table, then the data item is stored in many different rows.
Insert Anomaly
Problem that arises when attributes that aren't characteristics of the primary key of a relation are stored in the table.
Delete Anomaly
Problem that arises when attributes that aren't characteristics of the primary key are stored in a table, so that deleting a row from the table may result in the loss of all information about those attributes that are not characteristics of the primary key.
Logical view of data
How the user or programmer conceptually organizes and understands that data.
Physical view of data
How and where the data are physically arranged and stored.
Files versus Databases
A set of related records, such as all customer records, forms a file. A set of interrelated, centrally coordinated files forms a database.
Database management system
The interface between the database and the various application programs. The database, the DBMS, and the application programs that access the database through the DBMS are referred to as the database system.
Database Administrator
Responsible for the database.