Databases for Data Analyticss
Databases, for an analyst, means understanding how data is organised so that queries return trustworthy answers. It covers tables, keys, relationships, normalisation and star schemas with fact and dimension tables. Knowing the model tells you the grain of a table, why joins can multiply rows, and where to find the right column, which supports the SQL stage of the Data Analytics path.
Stage: SQL · Part of the Data Analytics roadmap · Last reviewed 19 November 2026
What to learn in Databases
- Identify primary and foreign keys from an entity relationship diagram
- State the grain of a table before aggregating it
- Explain why joining to a many-side table can inflate totals
- Describe a star schema with a fact table and dimension tables
- Tell normalised transactional tables from denormalised reporting tables
Databases interview questions
A revenue total doubles after joining orders to order items. What happened?
Orders have one row each but items have many, so order-level revenue repeats once per item and then gets summed. Aggregate at one grain first, or sum item-level amounts instead. Always compare row counts before and after a join.
What are fact and dimension tables in a star schema?
A fact table holds measurable events at a stated grain, such as one row per sale with amounts and foreign keys. Dimension tables hold descriptive attributes such as customer, product and date, used to filter and group. Analytical queries join the fact table to its dimensions.
Where Databases fits in the Data Analytics roadmap
Databases belongs to the SQL stage (beginner level), which takes about 8 hours. The analyst's main tool.
Other units in this stage
Back to the full Data Analytics roadmap