Exam 1 Flashcards

(44 cards)

1
Q

Data

A

Raw facts that need to be processed and could be simple: numbers text

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Information

A

Data that has been processed, organized and presented in a useful way

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Traditional db

A

Data elements or fields are text or numbers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Modern db

A

Fields can be images, videos, and sounds

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Entity

A

Name things, people or objects that it represents

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

DBMS

A

DataBase Management System

Makes it easier to: define a database, construct it, maintain and manipulate it, and give access to a variety of users/applications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Record

A

Another name for the row of a table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Database Catalog

A

A file containing all definitions and constraints of data and database, such as definition of each table, each column data type and its value constraint.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Virtual data

A

Data not explicitly stored in database, such as GPA

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Data normalization

A

Removing redundancy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Correct database state

A

DBMS provides recovery functionality that, on a system crash, will go back to the last persistent state

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

End user

A

Those who use databases on a daily basis and for their job. The db application is for them. Examples: bank tellers, cashiers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Database Administrators

A

Defining users, setting access levels

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Data Abstraction

A

Removing unnecessary details and highlighting essential features to understand data better, for the purpose of developing a database application.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Database Schema

A

it is the description of a database, you specify it in database design phase and it does not change much after that.

Stored as metadata in catalog file in DBMS and includes structure of the db and all constraints that keep the database valid.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Schema Diagram

A

Representing the database schema description as a diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Database state/snapshot

A

Data in a database at a particular moment in time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Three-Schema Architecture

A

Introduced in 1978 to support data independence between user applications and the physical database.

External level: End-user views; what ordinary staff see

Conceptual level: Represents database in terms of tables, attributes, data types, relationships and constraints

Internal level: Uses a physical data model to describe details of storing/retrieving data in disk level

o In internal level; a sequence of numbers (bytes) is read from disks.
o In conceptual level; that is in terms of table(s) of grades, student_info, course_info, etc.
o In external level; you see a nicely formatted human readable form containing all your courses and grades.

19
Q

Data Independence

A

The capacity to change database schema in one level without having to change the higher level schemas

20
Q

Data Definition Language

A

Used by the DBA to specify the conceptual schema of a database; also used to define internal and external schemas.

21
Q

Data Manipulation Language

A

Used to specify database retrievals, updates, and can be embedded in a programming language like Java or C#. (JDBC/OBDC)
DMLs can be high level or low level

22
Q

Data Dictionary

A

A file similar to the catalog file and has all catalog file information. It is for humans and it could include comments and descriptions as well

23
Q

Client-Server Architecture

A

Client: User machine which provides the user interface and local processing

Server: A strong machine having hardware and software to provide different services to clients

24
Q

Categories of DBMS

A

Centralized - Everything is included into one machine; both DBMS software and GUI applications

Client-server architecture - Server machine has the DBMS software, and clients have web access or form based software

25
Parametric users
End users with a few defined commands to interact with DBMS, such as bank tellers
26
Privileged commands
Commands such as altering tables, changing data types, defining users, etc. that just DBAs have privilee to run
27
Canned Transactions
Pre-programmed and fully tested transactions for non-IT personnel, these transactions cannot harm the system
28
Runtime database processor
Runs transactions on a stored database, and gets information such as data types and constraints from catalog files to do so
29
Stored data manager
It manages buffers, read/write on disks and moving data to RAM
30
DBMS Classifications
- Based on data models: o Relational, Object-oriented, key-value storage (NOSQL). - Other classification: o Centralized vs. client-server based. o Single user vs. multi user
31
Attribute Types
Simple - Hold one value Composite - Composed of several simple attributes (Name) Multivalued attributes - Hold multiple values
32
Derived Attribute
An attribute that doesn't need to be stored in a db, but you can retrieve it via query and based on other stored attributes. Shown by dotted circle Example: GPA
33
Weak Entity
Has no key attribute of its own. Owner entity type: weak entity instances are identified by being related to a strong entity instance, that strong entity type is called owner entity type (or parent entity type). Identifying relationship: the relationship which relates a weak entity type to its owner is called this! partial key: an attribute of a weak entity type which uniquely identifies an instance, among instances of the same owner entity. o In ER, it is underlined with a dashed line. A weak entity type always has a total participation constraint (existence dependency) with respect to its identifying relationship. o A weak entity cannot be identified without an owner entity.
34
Relational Model
A data model which represents all data in terms of tuples, and groups tuples as relations. Majority of DBMS software is based on the relational model. Table row = record = tuple Relation can be represented as a table
35
Key of a Relation
An attribute that can identify a row uniquely. Also just known as a key
36
Schema of a Relation
Denoted by R(A1, A2...) where R is the name of the relation, A1 and A2 are attributes. Example: CUSTOMER(Cust-id, Cust-name)
37
Tuple
An ordered set of values, each derived from an appropriate domain.
38
Inherent/Implicit Constraints
Based on the data model itself. Example: RM doesn't allow a list as a value for an attribute
39
Schema-based or Explicit Constraints
Beyond the expressive power of the model and must be specified and enforced by the application programs
40
Constraints
Conditions that must be held on all valid relation states. Three types: Key constraints Entity integrity constraints Referential integrity constraints Domain constraint
41
Key Constraints
Superkey of R such that no two tuples in any valid relation state will have the same value
42
Entity Integrity
Primary key attributes cannot have null values in any tuple, since they're used as identifiers.
43
Referential Integrity
A tuple in the relationship reference no longer exists or can no longer be accessed
44
Semantic Constraints
Based on application semantics and cannot be expressed by the model. Example: "the maximum number of hours per employee for all projects he or she works on is 56 hours per week"