Databases 101 for BAs

Summary

A basic mental model of tables, rows and relationships — enough to understand why 'just add one field' isn't always trivial, and to write requirements that account for data structure realistically.

• 1Sketch a simple database schema (e.g. customers, orders) for a system you're documenting requirements for.
• 2Learn the difference between a relational and non-relational database at a high level.
• 3Understand why changing an existing field's type can be a risky change, not a quick fix.