Personal training advice

Live online training for international teams.For businesses
Find my course
Databases

Relational data modelling

Database design training: model relational data, define keys, normalise up to third normal form and plan queries with performance in mind.

In this database design training you learn to model relational data cleanly, and it is aimed at developers, analysts and administrators with first SQL knowledge. You derive an entity-relationship model from requirements, define primary and foreign keys, normalise up to third normal form and plan queries and indexes. PostgreSQL serves as the example system, and the concepts apply to relational databases in general. We agree scope and examples with you when you enquire.

IntermediateDE / ENBusiness training · Live online

What you’ll take away.

  • Translate requirements into an entity-relationship model with entities, attributes and cardinalities
  • Define primary, foreign and unique keys and further constraints appropriately
  • Normalise tables up to third normal form and justify deliberate denormalisation
  • Model many-to-many relationships with junction tables and define delete behaviour
  • Plan typical queries with JOINs and indexes and check them with EXPLAIN
Herstellerneutral

Your training in detail

Who is it for?
Software developers, data analysts, database administrators and consultants who design data models or review existing ones.
Prerequisites
Basic SQL knowledge (SELECT, WHERE, simple JOIN). Knowledge of a specific database system is not required.
Format & planning
Suggested format: 2 days live online or on site, split into modules. Scope depends on prior knowledge.

Agenda: from understanding to application

Our independently developed agenda proposal. Focus areas, lab environment and scope are agreed before booking.

  1. From requirement to ER model with entities, relationships, cardinalities and notation.

  2. Keys and data types: natural versus surrogate primary keys, foreign keys, unique and NOT NULL.

  3. Normalisation from first to third normal form, including insert, update and delete anomalies.

  4. Implementing relationships: one-to-many, many-to-many with junction table, ON DELETE and CHECK constraints.

  5. Planning queries with join types, aggregation, subqueries and views.

  6. Performance: B-tree indexes, EXPLAIN ANALYZE, deliberate denormalisation and schema changes through migrations.

PRACTICE & TRANSFER

Suggested exercise: You model a course booking system with participants, courses, sessions and bookings, create the schema in PostgreSQL and check three typical queries with EXPLAIN.

Exams, licences & credentials

There is no single vendor-neutral exam for database design. Database vendors offer their own certifications. Attending alone awards no vendor certificate. Exam fees and licences are only included if the offer confirms them.

Vendor references & review date

Sources checked on 2026-11-03. These sources describe the technology or external exam requirements. They do not imply a partnership with NextNowa.

Your learning content

These objectives describe the training topic. The specific syllabus, duration, dates, trainer and price are agreed before booking.

Individual offer: Availability and delivery are confirmed on enquiry.

Frequently asked questions

Up to which normal form should I normalise?

In practice, third normal form is usually enough. It avoids redundancy and update anomalies. Higher normal forms are rarely needed. For reporting or performance requirements you denormalise selectively, but should do so deliberately and with documentation. In the training you work through the stages on an example.

Primary key: natural key or surrogate ID?

Natural keys such as tax numbers change or are not as unique as expected. Surrogate IDs are stable and compact but do not replace uniqueness of the business data, for which you add unique constraints. The choice depends on data stability and requirements.

Is relational design enough, or do I need NoSQL?

For structured business data with relationships and consistency needs, a relational model is usually the solid choice. NoSQL can fit very flexible structures or extreme scale. Many systems use both. Mastering good relational design remains a useful foundation in either case.

Does Relational data modelling include a certificate?

There is no single vendor-neutral exam for database design. Database vendors offer their own certifications. Attending alone awards no vendor certificate. Exam fees and licences are only included if the offer confirms them.

KEEP LEARNING

Related topics in this field

View all topics

Guides

NextNowa Guide

Your training guide

What would you like to learn next?

Ask about courses, learning paths or advice. I will help you find your next step.

Automated guidance using reviewed information. No booking or funding confirmation. Please avoid sensitive data.