Skip to main content
To homepage To homepage
Solved

Execution jobs and Supernatural Keys

Did this topic help you find an answer to your question?
Show first post

30 replies

daniel
TimeXtender Xpert
Forum|alt.badge.img+7
  • daniel
  • TimeXtender Xpert
  • 188 replies
  • Answer
  • August 2, 2024

Dear @aftabp ,

Great that I worked for you. but please be advised that thurning on the ‘ only read from store’ in the dimension table is not the best practice on doing this. 
The way to do this is set the fact tables to ‘Only read from the store’ and have this option deselected in the dimension. The Dimensions are always the ‘master’ table in these cases. If you have multiple fact tables than both fact tables should be ‘ Only read from the store’.

The only time you might want to consider deselecting the fact table from ‘ Only read from store’ is when you know you have early arriving facts.

Hope this helps

= Daniel

A
Problem Solver
Forum|alt.badge.img
  • aftabp
  • Author
  • Problem Solver
  • 112 replies
  • August 2, 2024

@daniel 
Thank you for pointing out. 
It is infact checked on FACT table and not DIM.

I am still unsure why it has stopped working suddenly. It has worked fine all the time

A
Problem Solver
Forum|alt.badge.img
  • aftabp
  • Author
  • Problem Solver
  • 112 replies
  • August 8, 2024

@rory.smith and @Christian Hauggaard 

I have a follow up question before i go ahead and make changes in PROD.

I have guarded (on deploy and execution) the table in ODX because its has 9.6 million static rows from a retired source.

Would it have any effect on the SNKs if i also guard (on deploy and execute) the table in DSA?

The table is futher used in MDW together with two other tables. All have the same SNKs but FACT_TABLE_B and FACT_TABLE_C are not guarded becasue the source is updated daily.

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • 651 replies
  • August 8, 2024

Hi,

if the supernatural key fields in the guarded table are correctly populated and you never need to regenerate the keystore, you could guard that table. Note that as you are using incremental load on the fact table, you should ensure that any lookups into the table from other tables will require those tables to be type 1 historical to prevent issues when records in those tables are deleted. This also goes for the fact tables you will continue to load.

Any changes to the supernatural key setup, or hash settings or similar will require you to unguard and reload the table to avoid the wrong key values being used.

A
1 person likes this
  • A
    aftabp
A
Problem Solver
Forum|alt.badge.img
  • aftabp
  • Author
  • Problem Solver
  • 112 replies
  • August 8, 2024

@rory.smith 

As for now the SNK are correctly populated. I have tested and varified. 

Since the table i am refering to is static i am considering changing it from incremental to non-incremantal, since it will not get any new data.  There are some look-up columns from other tables that are also static and are non-incremental. 

 

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings