cancel
Showing results for 
Search instead for 
Did you mean: 

Attribute View Best Practice Questions

Former Member
0 Kudos

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?

Accepted Solutions (0)

Answers (2)

Answers (2)

rama_shankar3
Active Contributor
0 Kudos

Mic:

I recommend the below modelling approach:

  1) Group tables as master data and transction data. The attribute views will be master data tables and transaction data will be typically analytical views.

  2) The analytical views in addition will include business logic that needs to be applied for reporting purpose to link transaction data with master data

  3) As needed, based on comple requirements - you will have to design calculation views 

Hope this helps.

Regards,

Rama

henrique_pinto
Active Contributor
0 Kudos

It depends on your model.

For example, you can only use attributes from one table in the AT to join with the AN.

It won't let you join the fact table with key attributes coming from different tables in your AT.