Back to marketplace

10. Fundamentals of Databases

No description yet. This curated deck is ready for daily study.

Total cards: 11•Content version: v4•Public deck•Updated: 8/1/2026

Card preview (11)

#1
Front (Question)

What is a Relational Database?

Back (Answer)

A Relational Database is a Database which stores information in Relations/Tables. Each Relation will consist of Records/Rows and Attributes/Columns.

#2
Front (Question)

What is SQL?

Back (Answer)

SQL is Structured Query Language, a language for communicating with Relational Databases.

#3
Front (Question)

What is a Primary Key?

Back (Answer)

A Primary Key is a unique identifier for each Record in a Relation.

#4
Front (Question)

What is a Foreign Key?

Back (Answer)

A Foreign Key is an identifier for a Record in another Relation.

#5
Front (Question)

What is a Composite Key?

Back (Answer)

A Composite Key is a Key (Primary or Foreign) which consists of multiple Attrributes.

#6
Front (Question)

What is First Normal Form?

Back (Answer)

A Relation is in First Normal Form if it has no repeating Attribute or group of Attributes.

#7
Front (Question)

What is Second Normal Form?

Back (Answer)

A Relation is in Second Normal Form if it is in First Normal Form and there are no Partial Key Dependencies. A Partial Key Dependency is when an Attribute is dependent upon only part of a Composite Key.

#8
Front (Question)

What is Third Normal Form?

Back (Answer)

A Relation is in Third Normal Form if it is in Second Normal Form and there are no Non-Key Dependencies. A Non-Key Dependency is when an Attribute is dependent upon another Attribute which is not part of the Primary Key.

#9
Front (Question)

Why do we Normalise Databases?

Back (Answer)

Normalisation removes repetition/redundancy in a Database which has the following benefits: • Easier to update, as each value is only stored in one place. Repeating data can lead to an inconsistent Database. • Quicker to search, as we have smaller Relations with fewer Attributes. • Splitting data over multiple tables places constraints on how the the Database can be manipulated. These constraints may enforce Referential Integrity.

#10
Front (Question)

Why do Databases implement Record Locks?

Back (Answer)

Record Locks prevent multiple users from changing the same Record in a Relation at the same time which can lead to inconsistent results or corrupt data.

#11
Front (Question)

What is DeadLock?

Back (Answer)

DeadLock is when cyclical dependency appears between the Record Locks that users have created whilst interacting with a Database. For example user A may have locked Table 1 whilst waiting for user B to unlock Table 2, whilst user B is waiting for Table 1 to be unlocked to continue.