1.3.2 - Databases Flashcards

You may prefer our related Brainscape-certified flashcards:
1
Q

What is a Database?

A

A structured and persistent store of data for ease of processing; allowing for data to be:
- Retrieved quickly
- Updated easily
- Filtered for different views

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

What are Records

A
  • Records are made up of fields
  • Example: Person could be represented as record with fields as name, age and address
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Describe a Flat-File Database

A
  • A simple data structure table that is easy to maintain as only a limited amount of data is stored.
  • They are of limited use because they may have redundant data which can waste space and leave inconsistent data.
  • No specialist knowledge is needed to operate.
  • They are harder to update and the data format is difficult to change.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Describe a Relational database

A
  • Based on tables whose records are linked by certain fields (relation)
  • Each table has data on one entity
  • Each table has a relationship to other tables using primary and foreign keys
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Benefits of a Relational Database over a Flat File Database

A
  • Relational data allows for less redundancy of data (less repeated data)
  • Relational databases improve the consistency of data
  • Relational databases allow for complex queries and/or searches to be performed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Redundancy

A
  • Redundant data is data that is repeated in a database
  • A single table file is inefficient as it is full of redundant data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Primary Key

A
  • A field that is a unique identifier for every record in that table
  • Example - ID numbers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is Concatenated Primary Key?

A

When more than one field is added together to form a unique primary key for a table.

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

Foreign Key

A
  • Primary key in one table used as an attribute (foreign key) in another
  • Provides a link between tables
  • Represents many-to-one relationship
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Secondary Key

A

An attribute that is indexed and allows a group of records to be searched for quickly; usually more memorable than PK

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

Different types of Entity Relationship Modelling (ERM)

A
  • One to one
  • One to many
  • Many to Many
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

One to one relationship

A
  • When one entity is linked to another entity
  • Makes no sense to put in separate tables
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

One to many relationship

A
  • When one entity is linked to several entities
  • Used in most well designed RDBs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Many to many relationship

A
  • When several entities are linked to several other entities
  • Problematic; will lead to data redundancy
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Database management

A

Handled by the database management system (DBMS) such as:
- MySQL
- Oracle
- Bigtable

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

Methods of Capturing Data

A
  • Paper-Based Forms - Manual data input involving a human reading and typing the information into a system
  • Optical Mark/Character Recognition (OCR/OMR) - Automatically reads text/marks by interpreting the shape of the letters; better for printed text and used for Road Cameras and Multiple Choice Tests
  • Chip and Pin/QR Codes
17
Q

Methods of Exchanging Data

A
  • XML and JSON - Human-readable, open formats for structuring data
  • CSV (Comma Separated Value file) - Stores each record on a separate line and each field is separated by a comma
18
Q

What is Normalisation?

A

The process of arranging data in tables, and setting their relationships to move them through normal forms.

19
Q

What is Indexing?

A

The process of creating a database index, which is a data structure that improves the speed of data retrieval operations on a dataset table at the cost of additional writes and storage space to maintain the index data structure.

20
Q

What is Normal Forms?

A

A way of structuring the data in a relational database according to formal rules, in order to avoid problems of efficiency and security in accessing and maintaining the data.

21
Q

What is 0NF?

A

A table with no normalisation. All data and all fields in one table.

22
Q

What is 1NF?

A
  • No Repeating fields; all fields must be unique
  • Data must be atomic
  • Database has a primary Key
23
Q

What is 2NF?

A

Data must be in 1NF and any partial dependencies must be removed

24
Q

What is 3NF?

A

Data must be in 2NF and any transitive dependencies must be removed

25
Q

SQL

A

Structured Query Language: The language and syntax used to write and run database queries.

26
Q

What is Referential Integrity?

A

Refers to the accuracy of and consistency of data across a database
Conditions for Referential Integrity:
- If a record is removed, all references to it are removed
- A foreign key value must have a corresponding Primary key value in another table.

27
Q

What is Transaction Processing?

A

Information processing that is divided into individual, indivisible operations, called transactions. Each transaction must succeed or fail as a complete unit, and it can never be only partially complete.

28
Q

What is ACID, and what do the terms stand for?

A

ACID: Atomicity, Consistency, Isolation, Durability.

A set of properties that guarantee that database transactions are processed reliably. In the context of databases, a single logical operation on the data is called a transaction.

29
Q

Atomicity

A

A transaction must be processed in its entirety or not at all

30
Q

Consistency

A

Any changes in the database must retain the overall state of the database

31
Q

Isolation

A

Each transaction shouldn’t affect or overwrite other transactions concurrently being processed

32
Q

Durability

A

Once a change has been made to a database, committed data/transactions must not be lost in case of power / system failure

33
Q

What is Record Locking?

A

Allows one user to access record level data at any one time so data that is being used elsewhere cannot be modified