Avoiding sync tables - help on design

[#1]

Hi How can i avoid the sync table for the following 4 tables:

• Balance (Actual)
• BBALNCE (Budget)
• Account codes
• Cost Centres

Both Actual + Budget tables should both be linked to the account codes + cost centres. Both Actual + Budget tables also have similar fields such as type / period / year.

Regards, Jason

[#2 · Accepted solution]

If combination of the fields is correct for unique identification for the tables, it's not necessary remove the synthetic key.

Take a look at this post: http://community.qlik.com/forums/t/31028.aspx

[boorgura]

Having a Link key would be a solution to avoid the Synthetic key.

the link key can either be a concatenated or a hash of the common attributes.

The rest of the fields need to be qualified or renamed uniquely.

You can qualify them using "qualify *;" statement.

Let me know I you got it or need further clarification.

[johnw]

OK, this looks like a pretty classic problem of matching up budgets to actuals. Now, I THOUGHT I remembered there being some reason that you do NOT want to link budgets to actuals on a compound key (synthetic or otherwise) like this. But I'm looking at a simple example that works that way, synthetic key and all, and it SEEMS to be behaving. And I can't remember or think of why it wouldn't behave.

And that's the real question, I think. Is your application behaving properly? Is it allowing you to compare budgets to actuals in the way that you want? If so, then there is probably no reason to remove the synthetic key.