Database System Concepts and Architecture Flashcards

1
Q

A collection of concepts that can be used to describe the structure of the database.

A

Data Model

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

Categories of Data Model

A
  1. Conceptual (or High-level) Data Models
  2. Representational (or Implementation) Data Models
  3. Physical (or Low-level) Data Models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Provide concepts that are close to the way many users perceive data

Use concepts such as entities, attributes, and relationships

A

Conceptual Data Models

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

Provide concepts that may be easily understood by end users but are not too far removed from the way data is organized in computer storage

Used most frequently in traditional commercial DBMSs

Include relational, network, and hierarchical data models

A

Representational Data Models

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

Representational Data Models are also known as __________________ since they represent data by using record structures

A

record-based data models

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

Provide concepts that describe the details of how data is stored on the computer storage media

Describe how data is stored as files in the computer by representing information such as record formats, record orderings, and access paths

A

Physical Data Models

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

Description of the database

A

Schema (or Database Schema)

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

Specified during database design and is not expected to change frequently

A

Schema

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

When schema changes, it is called?

A

Schema Evolution

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

a displayed schema

A

Schema Diagram

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

Description of the schema constructs and constraints

Stored in database catalog (or database dictionary)

A

Meta-data

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

Data in the database at a particular moment in time

A

Database State

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

Database State is also called as

A

database snapshot, current set of occurrences / instances

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

When database is defined (schema specified) but no data

A

Empty State

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

When database is first loaded / populated with data

A

Initial State

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

Database state NOW

A

Current State

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

State that satisfies the structure and constraints specified in the
schema; DBMS must ensure this

A

Valid State

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

Three-Schema Architecture

A

External level
Conceptual Level
Internal Level

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

Describes the physical storage structure of the database

Uses physical data model

A

Internal Schema

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

Helps visualize and achieve the database system approach’s characteristics of having a self-describing nature, data independent and capable of multiple user views.

A

Three-Schema Architecture

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

Describes the structure of the whole database for a community of users

Typically uses representational data model to describe it

A

Conceptual Schema

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

Describes the part of the database that a particular user group is interested in

Typically uses representational data model to describe it

A

User View (or External Schema)

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

Process of transforming requests and results between levels

A

Mapping

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

Capacity to change the schema at one level of a database system without having to change the schema at the next higher level

A

Data Independence

25
Two types of Data Independence
Logical and Physical
26
Capacity to change the conceptual schema without having to change external schemas or application programs
Logical Data Independence
27
Capacity to change the internal schema without having to change the conceptual schema
Physical Data Independence
28
Language used by DBAs and Database Designers to define (and/or modify) the description of the database
Data Definition Language (DDL)
29
Language (or set of operations) used by database users to manipulate the database (i.e., retrieval, insertion, deletion, modification)
Data Manipulation Language (DML)
30
Specifies database access control which grant or revoke privilege to or from users
Data Control Language (DCL)
31
Language that allows database users to manipulate processing of transactions
Transaction Control Language (TCL)
32
DBMS Languages
Data Definition Language (DDL) Data Manipulation Language (DML) Data Control Language (DCL) Transaction Control Language (TCL)
33
DBMS Interfaces
* Command-line Interface * Menu-based interfaces for Web Clients or Browsing * Apps for Mobile Devices * Forms-based Interfaces * Graphical User Interfaces * Natural Language Interfaces * Keyword-based Database Search * Speech Input and Output * Interfaces for Parametric Users * Interfaces for DBAs
34
Processes schema definitions specified in the DDL and stores/updates the meta-data in the database system catalog.
DDL Compiler
35
Includes information such as names/data types of data items, storage details of files, constraints as well as information needed by other modules
Database System Catalog (Data Dictionary)
36
Parses and validates queries for correctness of syntax and file/data element names Compiles queries into internal form
Query Compiler
37
Concerned with rearrangement/reorder of operation, elimination of redundancies, and use of efficient search algorithms prior to execution
Query Optimizer
38
Consults the DB system catalog then generate executable code that performs the necessary operation(s) in an optimal way
Query Optimizer
39
Extracts DML commands from application programs
Precompiler
40
Compiles extracted DML commands into object code which will later be linked with the rest and turned into compiled transaction(s)
DML Compiler
41
Executes privileged commands, executable query plans, and compiled transactions
Runtime Database Processor
42
Refers to DB system catalog and may update statistics
Runtime Database Processor
43
Works with Stored Data Manager and performs other tasks such as buffer management
Runtime Database Processor
44
Controls access to DBMS information stored on disk
Stored Data Manager
45
Uses basic operating system services for carrying low-level input/output (read/write) operations between disk and memory
Stored Data Manager
46
Subsystems working with the Runtime Database Processor for the purpose of transaction management
Concurrency Control and Backup & Recovery
47
Database System Utilities
Loading Backup Database storage reorganization Performance monitoring
48
Add data (in bulk) into the database; Maybe from files or from another database
Loading
49
Create backup copy (or copies) of database onto mass storage medium (tape, slower/cheaper disk); Capability to do incremental backups
Backup
50
Reorganize database files into different file organizations and/or create new access paths to improve performance
Database storage reorganization
51
Monitors DB usage and provide statistics to the DBA; Helps in making decisions on whether changes are needed to improve performance
Performance Monitoring
52
Database Application Architecture developed to deal with computing environments with large number of devices and/or software connected via a network
Centralized (Client-/server)
53
Two-Tier vs Three-Tier Client/Server
**Two-Tier** are much used in earlier generations and the *application resides at the client machine*, where as **Three-tier** is used in modern database applications, where the *client machine is merely for frontend* and does not contain any direct database calls. Front end communicates with application server where business logic is embedded (instead of multiple clients)
54
Classification of DBMS (Based on Data Model)
* Relational * Object * NO SQL/Big Data Systems * Document-Based * Graph-Based * Column-Based * Key-Value * XML * Legacy * Hierarchical * Network
55
Classification of DBMS (Based on Number of Users)
**Single-user:** Supports only one user at a time; Mostly used with PCs **Multiuser:** Supports concurrent multiple users; Majority of DBMSs are in this classification
56
Classification of DBMS (Based on Number of Sites)
**Centralized:** Data is stored at a single computer site **Distributed:** Database and DBMS distributed over many sites connected by a computer network
57
Two Types of Distributed DBMS
**Homogeneous DDBMS:** Use the same DBMS software at all sites **Heterogeneous DDBMS**: Can use different DBMS software at each site
58
Classification of DBMS (Based on Cost)
* **Open-Source (Free):** Supported by third-party vendors with additional services * **Paid:** Different kinds of licensing scheme