What is a surrogate key?
A surrogate key is an artificial, system-generated identifier, typically an auto-incrementing number or UUID, used as a table's primary key instead of meaningful business data. It stays stable even when business attributes change, which makes it ideal for reliably linking tables, especially in data warehouses.
A surrogate key has no business meaning, it exists purely to identify a row. It contrasts with a natural key, which is real-world data used as an identifier (like an email or ISBN).
Surrogate keys are favoured because they are:
- Stable they never change, even if business values do.
- Simple a single integer is efficient to index and join.
- Decoupled from messy or changeable real-world identifiers.
They are especially common in dimensional warehouses, where surrogate keys link fact tables to dimensions and support slowly changing dimensions (each historical version of a dimension row gets its own surrogate key).
For analysis, surrogate keys are efficient but unreadable, a fact row referencing 'customer_key 48213' means nothing to a person. iDBQuery bridges that gap: it uses surrogate keys to join tables correctly, but its semantic layer maps them back to the meaningful attributes, so you ask 'sales by customer name' and it resolves the surrogate joins for you behind the scenes. You never handle the raw keys; you get a readable, cited answer. And when data spans systems using different key schemes, iDBQuery's federation still relates the records so cross-source questions work.
Updated 2026-06-22