I feel like enabling SQL SELECT statements to access hierarchies is a common feature, so option D seems likely, but I can't recall if it’s specifically related to shared hierarchies.
I’m a bit confused about the difference between star join and no star join in this context. I might lean towards option A and D, but I’m not entirely sure.
I'm a bit confused on the difference between a CUBE with and without a star join. I'll need to make sure I understand that before I can confidently answer this question.
Okay, I've got this. Shared hierarchies can be used to provide reusable hierarchies for drilldown in a CUBE with a star join, and they can also be used to access hierarchies created in external schemas.
Hmm, this one seems tricky. I'll need to carefully read through the options and think about how shared hierarchies could be used for drilldown and accessing data from external sources.
I think the key here is understanding what shared hierarchies are and how they can be used in a CUBE. I'll need to review my notes on CUBE structures and hierarchy management.
Hmm, I think C is also a valid answer. Shared hierarchies can be used for drilldown even without a star join, right? Although I'm not sure if that's as common as the other use cases.
A and B seem like the correct answers here. Shared hierarchies are definitely useful for reusable drilldown in cubes, and accessing external schemas is a great feature.
Salley
2 months agoVan
2 months agoTeddy
2 months agoMaryln
3 months agoDomingo
3 months agoJerilyn
3 months agoMollie
4 months agoJuan
4 months agoMaryann
4 months agoAntione
4 months agoClarinda
4 months agoGilberto
5 months agoClarence
5 months agoShawna
5 months agoEura
2 months agoSue
2 months agoDortha
3 months agoCatalina
3 months agoGeraldo
7 months agoLouis
5 months agoSherell
5 months agoAvery
7 months ago