Level 17 Level 19
55 words 0 ignored
Ready to learn Ready to review
Check the boxes below to ignore/unignore words, then click save at the bottom. Ignored words will never appear in any learning session.
First Normal Form
Normalisation of a database following rules of having no repeating attributes or groups of attributes
1NF Rule: each row must be ...
1NF Rule: each field must have a unique ...
1NF Rule: no columns can have similar or ...
broken down further
1NF Rule: each data item should not be able to be ...
Second Normal Form
Normalisation of a database so that it is in First Normal Form and contains no partial dependencies
when an attribute in a table depends on only one part of the primary key
Second Normal Form only applies to tables which have a ...
Third Normal Form
Normalisation of a database so that it is in Second Normal Form and contains no 'non-key dependencies'
when an attribute in a table depends on another attribute in the table which is not (part of) the primary key
data that appears in more than one database table (which can reduce data integrity)
Advantage of Database Normalisation: it is easier to maintain and ...
Advantage of Database Normalisation: it removes the possibility of having redundant data, helping prevent inefficiencies and ...
does not exist
Advantage of Database Normalisation: it is impossible to use details in one table for another entity that ...
sorting and searching
Advantage of Database Normalisation: it produces smaller tables, allowing for faster ...
Advantage of Database Normalisation: as data is only stored once in the database, normalised databases save ...
Advantage of Database Normalisation: it helps to prevent the ... of records
structured query language
a declarative language used for querying and updating tables in a relational database
SQL: extracts the data in the requested fields of a specified table
SQL: declares the table(s) to get data from
SQL: specifies the search criteria
SQL: declares the field that the results should be sorted on
SQL: condition to check whether the field doesn't contain a value
BETWEEN ... AND
SQL: condition to specify a range including the two values that define the limits
SQL: condition that the value must be within a set of values
SQL: condition to find values that are similar to the one specified
SQL: combines rows from multiple tables based on a common field between them
SQL: specifies the common field that tables should be joined by
SQL: wildcard, representing a string of any length
SQL: wildcard, representing a single character
SQL: returns the number of records that meet the criteria
SQL: used with count and will return the number of records for every value that appears
SQL: creates a table with the specified name and fields that are defined within ()
SQL: allows the specified table to be modified
SQL: adds a column to the table when used with the ALTER TABLE statement
SQL: deletes a column from the table when used with the ALTER TABLE statement
SQL: allows changes to be made to a column when used with the ALTER TABLE statement
SQL: creates a column that is a foreign key when creating a table
SQL: used with the FOREIGN KEY statement to specify what table and field the foreign key links to
SQL: used to create a new record in a database table
SQL: used with the INSERT INTO statement to specify what values should be in the record
SQL: modifies the values of a record in the database
SQL: used with the UPDATE statement to set the values of columns
SQL: deletes a record from a database
a single logical operation on data in a database
a transaction must be processed in its entirety or not at all (ie. it is not possible to only process part of a transaction in event of the database crashing)
a transaction cannot violate any validation rules for maintaining the integrity of the database (such as the defined referential integrity rules)
the execution of concurrent transactions should have the same result regardless of the order that they are processed
once a transaction has been committed, it must remain committed
technique of preventing simultaneous access to objects in a database from causing updates to be lost or data inconsistencies
when two users are trying to access two records and lock them in such an order that neither can proceed with the transaction
technique to ensure that transactions don't overlap in time and cannot lead to updates being lost
technique to ensure that the transaction which began first, will be applied first before the other
technique that orders transactions in terms of their dependencies on each other
technique of having additional hardware / measures in place to prevent the loss of data in the event of a power failure or other disaster