Title CaMEO/Career Mobility of Europe’s Older Workforce: Improving and extending the employability of an ageing workforce in Europe through enhancing mobility
Project Number 539099LLP-1-2013-1-UK-LEONARDO-LNW
Product Matching Database
Title Matching Database
Product Type website
Database normalisation is the final step of the database design process, through which the fields, tables and relational database is organised to minimize the dependency and redundancy as much as possible. The objective of this task is to isolate data so that additions, deletions, and modifications of a field can be made in just one table and then propagated through the rest of the database via the defined relationships.
The steps that will be followed are:
1. Free the database of modification anomalies
When an attempt is made to modify (update, insert into, or delete from) a table, undesired side-effects may follow. Not all tables can suffer from these side-effects; rather, the side-effects can only arise in tables that have not been sufficiently normalised.
2. Minimise redesign when extending the database structure
When a fully normalized database structure is extended to allow it to accommodate new types of data, the pre-existing aspects of the database structure can remain largely or entirely unchanged.
3. Avoid bias towards any particular pattern of querying
Normalised tables are suitable for general-purpose querying. This means any queries against these tables, including future queries whose details cannot be anticipated, are supported. In contrast, tables that are not normalized lend themselves to some types of queries, but not others.
Once the above steps have been finalized, then the Database will be installed on a server.
Area of application
Product Languages English