Why dimension tables are loaded first

But if we are doing full load, everything will come irrespective of any change. Have Login? Your Name. Email Address Re-type Email Address. Choose a Password. New Account? Email Address. Password Forgot? Log in. Go to Login. Tomorrow if 10k rows coming from source then update as usual but what about 1m rows loaded with only surrogate keys and other columns will nulls? Inferred dimension is a late arriving dimension. While you are loading the fact tables in EDW, you should always load first dimensions with surrogate keys.

Don't bother about the other data as you have source id and corresponding surrogate key is present in your dimension. Lets use simple example : 10 employees are registered with New NPS account diff account types. Based on your requirement the logic should change, you can update ref keys in fact tables or make flag as deleted or update the primary key surrogate key in dimension table based on source key.

You are telling about null data in few columns and then update them based on some column in the next run. Error: You don't have JavaScript enabled. Dim tables should have information about the person name, address, gender etc , Any table holding transaction data will be a fact table.

And in above example the table holding monthly data should be called as fact and not dim. Fact table has foreign keys referencing the primary key of dimension. Logically Foreign key is a subset of primary or unique key. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account?

Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. We'll send a magic link to your inbox.