sql server - Building Budget Into a Database -

sql server - Building Budget Into a Database -

i building budget sql server database, in order maintain track of items via either web app, or desktop app. question when keeping budget on 5 years improve practice have line items in 1 table descriptions, , years in another, 60 columns each month 5 years, or have 1 table each year , given line items. querying purposes seems easier way, referential integrity seems other way better. insight great

essentially trying utilize is, compare , reporting on 5 years of assumptions vs, actual results on time

60 columns 5 years breaks normalization rules. way lies madness....

i can see categories transcend years (e.g. "income taxes", "housing", "food").

i can see transactions categories roll years grouping timestamps.

i can see predictions , actual values referring categories.

i don't see of in either of proposed designs.

sql-server database-design referential-integrity