why do we need multiple SQL for each measure?

building semantic layer
1

Hello Everyone,

I need some clarification on the “multiple SQL for each measure” option in the universe. what scenario’s require selecting this option, I was informed that selecting this option hinders performance

Can I expect correct results unselecting this option ,where measure comes from more than one fact tables?

Thanks,

bouser4 :us: (BOB member since 2007-03-23)

2

That option is used when you have the need to query measures from multiple fact tables; it will create a SELECT for the measures in each fact table. It was discussed here. It also is used to help solve Fan Traps, but in that case all measures must have SQL aggregate functions applied (it won’t work if the SELECT doesn’t generate a GROUP BY).

charlie :us: (BOB member since 2002-08-20)