Skip to Content
0
Former Member
Oct 28, 2012 at 04:22 PM

Attribute View Best Practice Questions

48 Views

Hey,

Some random Attribute View questions I wanted to ask which is considered best practice. Please explain your answers for better understanding:

1) Is it better to:

a) Have as many related tables in one attribute view to make it very organized. I prefer this method as it is better to test data and seems more organized.

or

b) Try to split up Attribute Views if possible into more views and join all of them at the Analytic View level (better for performance because they will run in parallel?)

^Which practice is better (please explain) and is it not a big deal to use either approach?

2) If there is a transaction table (ex. AFVC) that I need, but I don't need any measures from this table, just attributes. Is it better to:

a) Use the transaction table at the Attribute level

or

b) Use the transaction table at the Analytic Level and create a dummy measure?

^The above scenario gets interesting if there is another transaction table which will be used to get measures. If option b is used then there has to be 2 analytic views created.

3) Related questions:

a) What's the difference between 'calculated attribute' and 'calculated column'?

b) What is the benefit of using one over the other?

c) Any performance benefit for using either?