What are the two possible effects on the database when the data storage property of a parent member in the sparse Entity dimension is set to Dynamic Calc?

What are the two possible effects on the database when the data storage property of a
parent member in the sparse Entity dimension is set to Dynamic Calc?

What are the two possible effects on the database when the data storage property of a
parent member in the sparse Entity dimension is set to Dynamic Calc?

A.
Data cannot be input to the parent in target versions.

B.
Essbase data block size decrease*.

C.
The member is not available for process management.

D.
Retrieval performance could be slower when referencing the parent entity member.



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Astral

Astral

Answer should be A and D.

Data Block size depends on stored members in dense dimensions. Hence B can’t be true.

In target Versions, data is entered at parent level and since parent is dynamic Calc, value can’t be inputed at parent level.