AN 324 UKY

studied byStudied by 0 people
0.0(0)
Get a hint
Hint

Data

1 / 109

encourage image

There's no tags or description

Looks like no one added any tags here yet for you.

110 Terms

1

Data

Facts that are recorded and can be accessed

New cards
2

information

refers to the data that is accessed by a user for some particular purpose

New cards
3

knowledge

the application of experience to information

New cards
4

Metadata

data that describes the structure and the properties of the data

New cards
5

database

structured collection of related data stored on a computer medium

New cards
6

Database Metadata

represents the structure of the database; ex) data types, data descriptions, names of data structures

New cards
7

Database Management System (DBMS)

used for creation of databases; insertion, storage, retrieval, update, and deletion of the data in the database

New cards
8

database system

computer-based system whose purpose is to enable an efficient interaction between the users and the information captured in a database

New cards
9

Front-end applications

provide a mechanism for easy interaction between the users and the DBMS

New cards
10

End-users (business-users)

users using a database system to support their tasks and processes

New cards
11

indirect interactions

end-user communicating with the database through front-end applications

New cards
12

direct interaction

end-user communicating with the database directly through DBMS

New cards
13

database analyst

involved in the requirements collection, definition, and visualization stage

New cards
14

database designers

involved in the database modeling stage

New cards
15

database developers

in charge of implementing the database model as a functioning database using the DBMS software

New cards
16

Front-end application analysts

in charge of collecting and defining requirements for front-end applications

New cards
17

Front-end applications developers

in charge of creating the front-end applications

New cards
18

Database Administrator (DBA)

perform the tasks related to the maintenance and administration of a database system

New cards
19

Database end users

use a database system to support their work or life related tasks and processes

New cards
20

operational information (transactional information)

the information collected and used in support of day to day operational needs in business and other organizations

New cards
21

operational database

collects and presents operational information in support of daily operational procedures and processes

New cards
22

Analytical Information

the information collected and used in support of analytical tasks

New cards
23

analytical database

collects and presents analytical information in support of analytical tasks

New cards
24

entities

constructs that represent what the database keeps track of; represent various real world notions such as people, places, objects, events, items, and other concepts

New cards
25

attribute

depiction of a characteristic of an entity; represents the details that will be recorded for each entity instance

New cards
26

Unique Attribute

attribute whose value is different for each entity instance; every regular entity must have at least one unique attribute

New cards
27

Cardinality constraint

depict how many instances of one entity can be associated with instances of another entity

New cards
28

composite attribute

attribute that is composed of several attributes (attribute in parenthesis)

New cards
29

Composite Unique Attribute

attribute that is composed of several attributes and whose value is different for each entity instance (Underlined composite attribute)

New cards
30

Multiple unique attributes (candidate keys)

when an entity has more than one unique attribute each unique attribute is also called a candidate key

New cards
31

multivalued attribute

attribute for which instances of an entity can have multiple values for the same attribute (double circle around attribute)

New cards
32

derived attribute

attribute whose values are calculated and not permanently stored in a database (Dotted circle around attribute)

New cards
33

optional attribute

attribute that is allowed to not have a value

New cards
34

degree of relationship

reflects how many entities are involved in the relationship

New cards
35

binary relationship

relationship between 2 entities (Degree 2)

New cards
36

unary relationship

occurs when an entity is involved in a relationship with itself (Degree 1)

New cards
37

weak entity

an entity that does not have a unique attribute of its own (double boxed)

New cards
38

owner entity

entity whose unique attribute provides a mechanism for identifying instances of a weak entity

New cards
39

Identifying relationship

relationship between a weak entity and its owner entity in which each instance of a weak entity is associated with exactly one instance of an owner entity (double line around relationship)

New cards
40

Partial Key

attribute of a weak entity that combined with the unique attribute of the owner entity uniquely identifies the weak entity's instances

New cards
41

Associative Entity

construct used as an alternative way of depicting M:N relationships

New cards
42

relational database model

logical database model that represents a database as a collection of related tables

New cards
43

relation

table in a relational database

New cards
44

relational database

collection of related relations within which each relation has a unique name

New cards
45

Primary Key

column (or a set of columns) whose value is unique for each row

New cards
46

composite primary key

a primary key that is composed of multiple columns

New cards
47

Entity Integrity Constraint

in a relational table, no primary key column can have null values

New cards
48

Foreign Key

column in a relation that refers to a primary key column in another (referred) relation

New cards
49

referential integrity constraint

in each row of a relation containing a foreign key, the value of the foreign key either matches one of the values in the primary key column of the referred relation or the value of the foreign key is null

New cards
50

Granularity of the table

Describes what is depicted by one row in the table

New cards
51

relational database constraints

rules that a relational database has to satisfy in order to be valid (implicit and user-defined constraints)

New cards
52

Update operation

collective term for insert, delete and modify operations

New cards
53

update anomaly

anomalies in relations that contain redundant data, caused by update operations

New cards
54

insertion anomaly

occurs when inserting data about one real-world entity requires inserting data about another real-world entity

New cards
55

Deletion Anomaly

occurs when deletion of data about a real-world entity forces deletion of data about another real-world entity

New cards
56

Modification Anomaly

occurs when, in order to modify one real-world value, the same modification has to be made multiple times

New cards
57

Functional Dependency

occurs when the value of one (or more) columns in each record of a relation uniquely determines the value of another column in that same record of the relation (ex: A->B; ClientID->ClientName)

New cards
58

Trivial Functional Dependency

occurs when an attribute (or a set of attributes) functionally determines itself or its subset

New cards
59

augmented functional dependency

functional dependency that contains an existing functional dependency

New cards
60

Partial functional dependency

occurs when a column of a relation is functionally dependent on a component of a composite primary key

New cards
61

Full key functional dependency

occurs when a primary key functionally determines the column of a relation and no separate component of the primary key partially determines the same column

New cards
62

transitive functional dependency

occurs when nonkey columns functionally determine other nonkey columns of a relation

New cards
63

Normalization

process used to improve the design of relational databases

New cards
64

normal form

term representing a set of particular conditions (whose purpose is reducing data redundancy) that a table has to satisfy

New cards
65

First Normal Form (1NF)

a table is in 1NF if each row is unique and no column in any row contains multiple values

New cards
66

Second Normal Form (2NF)

a table is in 2NF if it is in 1NF and if it does not contain partial functional dependencies

New cards
67

Third Normal Form (3NF)

a table is in 3NF if it is in 2NF and it does not contain transitive functional dependencies

New cards
68

Denormalization

reversing the effect of normalization by joining normalized relations into a relation that is not normalized, in order to improve query performance

New cards
69

Data Definition Language (DDL)

Used to create and modify the structure of the database• Example commands:CREATE, ALTER, DROP

New cards
70

Data Manipulation Language (DML)

• Used to insert, modify, delete and retrieve data • Example commands: INSERT INTO, UPDATE, DELETE, SELECT

New cards
71

Data Control Language (DCL)

Used for data access control

New cards
72

Transaction Control Language (TCL)

Used for managing database transactions

New cards
73

CREATE TABLE

Used for creating and connecting relational tables

New cards
74

DROP TABLE

Used to remove a table from the database

New cards
75

INSERT INTO

Used to populate the created relations with data

New cards
76

SELECT

used for the retrieval of data from the database relations

New cards
77

WHERE

Where condition determines which rows should be retrieved and consequently which rows shouldn't be retrieved

New cards
78

DISTINCT

can be used in conjunction with the SELECT statement; eliminates duplicate values from a query result

New cards
79

ORDER BY

Used to sort the results of the query by one or more columns (or expressions)

New cards
80

LIKE

used for retrieval of records whose values partially match a certain criteria

New cards
81

Aggregate functions

For calculating and summarizing values in queries, SQL provides the following aggregate functions:
COUNT
SUM
AVG
MIN
MAX

New cards
82

GROUP BY

Enables summarizations across the groups of related data within tables

New cards
83

HAVING

determines which groups will be displayed in the result of a query and consequently which groups will not be displayed in the result of the query

New cards
84

nested query

a query that is used within another query (aka inner query)

New cards
85

IN

used for comparison of a value with a set of values

New cards
86

JOIN

facilitates the querying of multiple tables

New cards
87

Alias

An alternative name that can be used anywhere within a query instead of the full relation name

New cards
88

ALTER TABLE

Used to change the structure of the relation, once the relation is already created

New cards
89

UPDATE

used to modify the data stored in database relations

New cards
90

DELETE

used to delete the data stored in database relations

New cards
91

VIEW

mechanism in SQL that allows the structure of a query to be saved in the RDBMS (aka virtual table, it allows people to work on the query without altering the actual data)

New cards
92

Set Operators

Used to combine the results of two (or more) SELECT statements that are union compatible; columns are union compatible if they contain the same number of columns, and if the data types of the columns in one set match the data types of the columns in the other set

New cards
93

UNION

Used to combine the union compatible results of two SELECT statements by listing all rows from the result of the first SELECT statement and all rows from the result of the other SELECT statement

New cards
94

INTERSECT

Used to combine the results of two SELECT statements that are union compatible by listing every row that appears in the result of both of the SELECT statements

New cards
95

MINUS (EXCEPT)

Used to combine the results of two SELECT statements that are union compatible by listing every row from the result of the first SELECT statement that does not appear in the result of the other SELECT statement

New cards
96

Self-JOIN

A join statement that includes a relation that contains a foreign key referring to itself, and joins a relation with itself in a query

New cards
97

INNER JOIN

regular join; Joins records from two tables where the value of a specified column in a record in one table matches the value of a specified column in another (or same) table

New cards
98

OUTER JOIN

Variation of the JOIN operation that supplements the results with the records from one relation that have no match in the other relation

New cards
99

IS NULL

used in queries that contain comparisons with an empty value in a column of a record

New cards
100

EXISTS

In queries where the inner query (nested query) uses columns from the relations listed in the SELECT part of the outer query, the inner query is referred to as a correlated subquery; In such cases, the EXISTS operator can be used to check if the result of the inner correlated query is empty

New cards

Explore top notes

note Note
studied byStudied by 36 people
... ago
5.0(1)
note Note
studied byStudied by 12 people
... ago
5.0(1)
note Note
studied byStudied by 9 people
... ago
5.0(1)
note Note
studied byStudied by 18 people
... ago
5.0(2)
note Note
studied byStudied by 57 people
... ago
5.0(1)
note Note
studied byStudied by 19 people
... ago
5.0(3)
note Note
studied byStudied by 19 people
... ago
5.0(2)
note Note
studied byStudied by 136 people
... ago
5.0(2)

Explore top flashcards

flashcards Flashcard (51)
studied byStudied by 13 people
... ago
5.0(1)
flashcards Flashcard (27)
studied byStudied by 32 people
... ago
5.0(2)
flashcards Flashcard (51)
studied byStudied by 45 people
... ago
4.5(6)
flashcards Flashcard (70)
studied byStudied by 5 people
... ago
5.0(1)
flashcards Flashcard (32)
studied byStudied by 13 people
... ago
5.0(1)
flashcards Flashcard (20)
studied byStudied by 7 people
... ago
5.0(1)
flashcards Flashcard (38)
studied byStudied by 11 people
... ago
5.0(1)
flashcards Flashcard (20)
studied byStudied by 94 people
... ago
5.0(2)
robot