database - When should use 3NF design in data warehouse field -


i have 1 confusion 3nf design , dimensional design in data warehouse field.

i don't want cause quarrel between inmon , kimball's idea, dimensional design causes less time query , easy understand, don't know when normalized design should used, give me detail example using normalized design better denormalized one?

in understanding, data warehouse built query, should order more read write, more query insert, i'd know when should use normalized model, lot.

i creating data-warehouse should have denormalized schema. optimise selects, allows better reporting using bi, cubes, star schemas etc. warehouses reporting puposes need better performance selects on inserts/updates. needs able store historic data on dimensions such time.

you normalize data model , use 3nf when working operational database. has updates, inserts, deletes , selects. not want have duplicate data stored make data consistancy difficult maintain.


Comments

Popular posts from this blog

Android layout hidden on keyboard show -

google app engine - 403 Forbidden POST - Flask WTForms -

c - Why would PK11_GenerateRandom() return an error -8023? -