See my comment above on multidimensional axes for presentation vs primary key components of a relation. More interestingly, SQL has a hard time with the contex

See my comment above on multidimensional axes for presentation vs primary key components of a relation. More interestingly, SQL has a hard time with the contextual calculations (actuals come from this table and are aggregated, forecasts come from those 12 tables and are computed by the following formula series, now apply that logic across N variables for actual and forecast) and a really painful time defining computed rows (like fields in some rows being ratios of the same field in other rows). That's what the modeling tools like Anaplan, Tidemark and some others excel at.