Start with the question
A table, dashboard or model is useful only when its grain, audience and decision are explicit.
Learn 100+ data terms across analytics, SQL, databases, statistics, data science, pipelines, warehouses and big-data architecture with clear explanations.
Good data work depends on shared definitions. A metric can be technically correct yet misleading if its grain, source or business meaning is unclear. This glossary connects database structure, analytical reasoning, statistics and modern data platforms so learners can move from vocabulary to trustworthy decisions.
A table, dashboard or model is useful only when its grain, audience and decision are explicit.
Missingness, duplication, lineage and freshness influence every result; documenting them is analytical work.
Warehouses, lakes and streaming platforms solve different combinations of history, scale, latency and governance.
See exactly where the concept appears in a structured specialisation.
Read the roadmap, comparison or project guide that gives it context.
Connect relevant terminology with the certification domain that assesses it.
A controlled experiment comparing two variants against a predefined outcome metric.
A database transaction that preserves atomicity, consistency, isolation and durability.
The calculation of summaries such as totals, averages or counts across groups of records.
A query designed to compare, group or summarise data for investigation and decision-making.
A query that trades exactness for faster answers on large datasets.
Processing a collected group of records together on a schedule or trigger.
Data whose scale, speed or variety requires distributed storage, processing or specialised architecture.
Tools and practices that turn organisational data into reports, dashboards and decision support.
The number of distinct values in a field or relationships associated with an entity.
A named field that stores one type or meaning of value across table rows.
A database that stores values by column to accelerate analytical scans and compression.
A named temporary result used to structure a larger SQL statement.
A measure of how strongly two variables move together, without by itself proving causation.
A structured visual display of metrics and patterns created for a defined audience and decision.
The practice of transforming data into metrics, patterns and recommendations that support decisions.
A searchable inventory describing available datasets, ownership, meaning, quality and access.
The detection and treatment of missing, duplicated, inconsistent or invalid data.
A documented agreement about a dataset's schema, semantics, quality and ownership.
A practitioner who builds reliable systems for collecting, transforming and serving data.
A labelled two-dimensional structure widely used for analysis in Python and related tools.
The degree to which available data reflects the latest required source updates.
Roles, policies and controls for data quality, security, access, retention and accountability.
A scalable repository that stores raw and processed data in multiple formats.
An architecture combining flexible data-lake storage with warehouse-style management and analytics.
A record of where data originated, how it changed and where it is used.
A curated subset of organisational data designed for a particular function or audience.
A decentralised data architecture that treats domains as accountable owners of interoperable data products.
A representation of entities, attributes, relationships and rules within a data system.
Monitoring that reveals the freshness, volume, quality and lineage of data systems.
The accountable person or function responsible for a data asset's meaning and governance.
A repeatable flow that collects, validates, transforms and delivers data between systems.
A reusable, owned data asset designed to serve a defined set of users and decisions.
The systematic examination of distributions, missingness, uniqueness and anomalies before analysis.
The degree to which data is accurate, complete, timely, consistent and fit for use.
Rules determining how long information is stored and when it is archived or deleted.
An interdisciplinary practice combining programming, statistics, domain understanding and modelling to learn from data.
The system, file, service or process from which data originates.
A reproducible operation that reshapes, cleans, combines or enriches data.
Checks confirming that data meets expected formats, ranges, relationships and business rules.
The deliberate use of charts and visual structure to communicate comparisons, patterns and uncertainty.
A governed repository optimised for integrated historical analysis and reporting.
An organised system for storing, retrieving and managing data with defined structures and controls.
The organisation of relational tables to reduce redundancy and update anomalies.
A collection of related observations or records used for analysis, training or evaluation.
A branching model that predicts an outcome through a sequence of feature-based rules.
The identification and controlled removal or consolidation of duplicate records.
Analysis that summarises what happened through metrics, comparisons and patterns.
A descriptive field used to group, filter or explain a measure.
A warehouse table containing descriptive attributes used to group or filter facts.
A database whose data or processing is coordinated across multiple machines or locations.
A database that stores records as flexible documents rather than fixed relational rows.
Extract, Load, Transform: loading source data before transforming it within the target platform.
Extract, Transform, Load: a data workflow that collects source data, reshapes it and writes it to a target system.
A continuous ordered flow of records describing actions or state changes.
Early investigation using summaries and visualisation to understand structure, quality and patterns.
A warehouse table containing measurable events linked to descriptive dimensions.
The creation or transformation of model inputs using domain and data understanding.
A field that references a key in another table to represent a relationship.
A join returning matched rows plus unmatched rows from both inputs.
The level of detail represented by one row, event or measurement.
A SQL operation that forms groups before calculating aggregate results.
A statistical procedure for evaluating evidence against a stated assumption.
The estimation or substitution of values where observations are missing.
A pipeline update that processes only records added or changed since the previous run.
A database structure that accelerates selected lookups while adding storage and write cost.
A join returning only rows whose join condition matches in both inputs.
A relational operation that combines rows from tables using matching keys or conditions.
A text format representing nested data through objects, arrays and primitive values.
A deliberately chosen metric used to monitor progress towards an important objective.
A join retaining every left-side row and matching right-side values where available.
A stored query result refreshed to improve repeated analytical access.
The arithmetic average calculated by dividing a sum by the number of observations.
The middle value of an ordered dataset, useful when extreme values distort the mean.
Information describing a dataset's structure, meaning, origin, ownership or operational characteristics.
A defined quantitative measure used to monitor behaviour, performance or outcomes.
An observation whose expected field is absent, unknown or not recorded.
A family of non-relational database approaches designed for varied structures or scaling patterns.
A database marker indicating an absent or unknown value, distinct from zero or empty text.
Systems and operations optimised for multidimensional analysis of large datasets.
Systems optimised for frequent, reliable operational reads and writes.
The use of timely data within recurring frontline workflows and decisions.
An observation unusually distant from the broader pattern and worthy of investigation.
A compressed columnar file format designed for efficient analytical storage and processing.
A logical division of data used to improve storage management and query performance.
A value below which a stated percentage of ordered observations falls.
A field or field combination that uniquely identifies a table row.
A description of possible values and their associated likelihoods.
A structured request to retrieve, combine, summarise or modify data in a database.
The process of reducing the resources or time required to execute a database query.
Statistical methods for estimating relationships between variables and a numerical outcome.
A database organising data into connected tables governed by keys and constraints.
A join retaining every right-side row and matching left-side values where available.
A subset of a population selected for analysis or estimation.
The defined structure, fields, relationships and constraints of stored data.
A warehouse technique for preserving or updating historical descriptive attributes.
Structured Query Language, used to define, retrieve, combine and manage relational data.
A measure of how widely observations vary around their mean.
A warehouse model with a central fact table connected to dimension tables.
A measure of how incompatible observed evidence is with a specified null hypothesis.
Data processed continuously or in near-real time as events arrive.
Data organised into consistent fields and records with a defined schema.
A generated identifier used instead of a natural business key.
A relational structure that organises records into rows and named columns.
Observations recorded in chronological order for trend, seasonality or forecasting analysis.
A logical unit of database work that succeeds or fails as a controlled whole.
Information such as text, images or audio without a fixed tabular schema.
The average squared distance of observations from their mean.
A SQL calculation across related rows that preserves individual row output.
Start with metric, dimension, granularity, aggregation, join, data quality, dashboard and statistical significance.
No. SQL can be learned through tables, filtering, grouping and joins. Statistics becomes increasingly valuable when you interpret variation, experiments and predictions.
A lake stores varied raw and processed data flexibly. A warehouse provides governed, integrated structures optimised for consistent analytics.
Use the glossary to clarify the language, then inspect the complete 30-hour syllabus and projects for your chosen technology.

Analyse business performance with SQL, dashboards and clear metrics.

Turn messy data into tested insight and predictive evidence.

Design relational databases and write production-minded SQL.

Design scalable batch, stream and lakehouse data workflows.