Fragmentation in an underlying Planning Essbase database that is caused by what two actions?
A.
Delete member from a sparse dimension.
B.
Delete member from a dense dimension.
C.
Renaming a member.
D.
Renaming an alias.
E.
Submitting data / deleting data frequently.
Explanation:
Fragmentation is unused disk space.
EssBase Database fragmentation is likely to occur with the following:
Read/write databases that users are constantly updating with data (E).
Databases that execute calculations around the clock
Databases that frequently update and recalculate dense members (B)
Data loads that are poorly designed
Databases that contain a significant number of Dynamic Calc and Store members
Databases that use an isolation level of uncommitted access with commit block set to zero