Unit 1

Question 1

Two tier client

Answer 1

client directly connects to the server for information.

Question 2

N tier client

Answer 2

divides application into physical tiers and logical layers; includes 3 or more separate tiers.

Question 3

Thin client

Answer 3

The process happens on the server(s).

Question 4

Thick (Fat) client

Answer 4

The process happens locally for the client.

Question 5

DB Evolution Timeline

Answer 5

1. flat files hierarchical structure
2. Relational DB
3. Object-oriented DB (DEAD)
4. DB for Social Media
5. Big Data, NOSQL DB (Cloud Computing)
6. Data Warehouses

Question 6

Operational Data

Answer 6

Raw ERP data.

Question 7

Informational Data

Answer 7

on-time performance reports.

Question 8

Analytical Data

Answer 8

optimization, modeling, and simulation to support business decisions.

Question 9

IaaS

Answer 9

Infrastructure as a service.

Question 10

PaaS

Answer 10

Platform as a service.

Question 11

SaaS

Answer 11

Software as a service.

Question 12

Data

Answer 12

Something captured and stored; not information.

Question 13

Information

Answer 13

Data processed for insight; the next step after data.

Question 14

Char

Answer 14

Stores characters. If data entry doesn’t meet limit, will attach spaces on the end of the string of characters.

Question 15

Varchar

Answer 15

Stores a string. If data entry doesn’t meet limit, WILL NOT attach spaces on the end.

Question 16

Nchar, Nvarchar

Answer 16

More storage capacity per character than char and varchar. Can contain special characters. Unicode; two bytes per character.

Question 17

Enumerated Data Type

Answer 17

Has a list of possible values that are user-defined.

Question 18

Metadata

Answer 18

data about data. It defines the structure and properties of a table.

Question 19

Data Dictionary

Answer 19

metadata of metadata. Information containing all the column titles and table titles of all tables in a DB.

Question 20

Crows Foot Notation

Answer 20

ERD method relating tables to other tables with constraints and cardinality.

Question 21

Chens Notation

Answer 21

The other ERD method.

Question 22

Cardinalities

Answer 22

one: one, one: many, many: many

Question 23

Constraints

Answer 23

atleast one (dash), atleast zero (hole)

Question 24

Entity

Answer 24

Table.

Question 25

Instance

Answer 25

A single row.

Question 26

Programming variable notations

Answer 26

camelCase, PascalCase, underscore_delimited

Question 27

Identifier Attribute

Answer 27

Reflects a unique instance and therefore each value is unique; does not contain null values. Bolded.

Question 28

Multivariate Attribute

Answer 28

a single entity containing multiple values combined. Ex: {phoneNum} or {emailAddress}.

Question 29

Composite Attribute

Answer 29

a single entity containing multiple simple attributes. Ex: Address(Street, City, Zip).

Question 30

Derived Attribute

Answer 30

can be calculated from other values. Sometimes not stored until the data is final. Ex: [birthday].

Question 31

Relationship Degree

Answer 31

Unary, Binary, Ternary

Question 32

Associative/Bridge Entity

Answer 32

Bridges a many-to-many relationships. Usually has a composite or surrogate identifier.

Question 33

Super/subtype entities

Answer 33

"IsA" relationship, usually has a discriminator attribute, subtype entities inherit the relationships and attributes of the supertype entities.

Question 34

Discriminator Attribute

Answer 34

attribute that categorizes instances in the supertype entity that break down to subtype entities.

Question 35

Does the discriminator need to recognize all possible types of subtypes from the supertype entity?

Answer 35

No. However a good discriminator will.

Question 36

Does every instance in the supertype needs to break down to subtype?

Answer 36

No.

Question 37

Partial Completeness

Answer 37

Every instance in the supertype entity is not sorted into a subtype entity. Some types of instances are not recognized and carried over into a subtype entity.

Question 38

Total Completeness

Answer 38

Every instance in the supertype entity is sorted into a subtype entity.

Question 39

Can a ternary entity be classified as associative if only two of the entities that are related to it are related via one-to-many-many-to-one.

Answer 39

Yes.

Question 40

DBDLC: Conceptual Design

Answer 40

Data Modeling; ERDs

Question 41

DBDLC: Logical Design

Answer 41

Normalization; relational modeling

Question 42

DBDLC: Physical Design

Answer 42

DB creation with SQL

Question 43

Who made RD model of shared data banks in 1970

Answer 43

Edgar Ted Cod