Database terminology Flashcards

(21 cards)

1
Q

Define an entity

A

A single object, person, event or thing e.g customers, appointments, products about which data is to be recorded. An entity is represented with one or more database tables.

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

Define an attribute

A

A specific type of data representing a particular characteristic of each data record. Also known as a field or column.

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

Define a relational database

A

A database that stores records in two or more tables. Records in one table can refer to records in another table to avoid duplicating data.

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

Define a flat file

A

A database with a single table.

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

Define a primary key

A

An attribute that uniquely identifies every row of the table. If there is no natural attribute for a primary key, one should be introduced. The primary key is automatically indexed and cannot be blank.

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

Define a composite primary key

A

Sometimes two or even more attributes are needed to uniquely define a record. These attributes form a composite key.

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

Define a foreign key

A

A primary key of one table which appears in another table. By doing this relationships between the tables are formed.

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

Define a secondary key

A

A field, other than the primary key, which is indexed.

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

Define an index

A

A list of keys (or keywords), each of which identifies a unique record. Indices make it faster to find specific records and to sort records by the index field (the field used to identify each record).

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

Define a relationship

A

A relationship exists between two tables when one table has a foreign key that references the primary key of the other table.

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

What are the 3 relationship types?

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

Define a record

A

A row in a database table which contains data about one instance of an entity.

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

Define data integrity

A

The overall accuracy and completeness of data

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

Define referential integrity

A

A foreign key must refer to an existing primary key. Referential integrity is violated when the primary key to which a foreign key refers no longer exists. A measure of the consistency of the data in a database.

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

Define a query

A

A request for data or information from a database table or combination of tables.

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

Define data redundancy

A

This occurs in database systems when the same piece of data exists in multiple places.

17
Q

Define normalisation

A

The process of structuring the data in a relational database according to formal rules, in order to avoid problems of data redundancy which leads to inconsistency and inaccuracy.

18
Q

Define a field

A

A part of a record that holds data of a specific type about one characteristic of the subject of the record.

19
Q

Define a table

A

A set of data items arranged using vertical columns (identifiable by name) and horizontal rows

20
Q

What are pros of flat file databases?

A
  • Easy to set up - no knowledge required
  • Easy to use in code
  • Easy to share, e.g. email attachments
21
Q

What are cons of flat file databases?

A
  • Duplication of data (data redundancy) which take more time to update
  • Take up more space so more storage is required.
  • Everyone can see everything (not good if some data is sensitive)
  • Inefficient – have to have all fields for every record
  • Can’t perform complex queries as easily