ASO (Aggregate Storage Option) – Used for

  • If we have large number of dimensions (generally more than 10)
  • Most of the dimensions are sparse
  • We cannot write back in ASO. I heard recently that ASO will also have the write back capability.

BSO (Block Storage Option)-

  • Dimensions are less and dense (recommended values for no of dim are between 4 and 8).
  • We can write back hence much suited for planning applications.

Financial applications are generally dense structures and normal analytical cubes are sparse. Here we also need to understand what these dense and sparse members are. When the intersections or cells of two dimensions mostly contain a value it is dense. Say for example we have two dimensions period(Month or quarter) and region and we are calculation the sales amount. Generally maximum regions(countries, cities) will have some sales value for a particular month or quarter. Hence we can say that our period dimensions would be dense. But now instead of period, consider another dimension product. Now there are some products which are sold in only some particular regions hence for them there will be no values in other regions or will have very low percentage of data values hence the structure will become sparse.

To automate the process of creating dimensions with thousands of members.

1. Generation references
2. level references
3. Parent-Child references.

We cannot define that as Generation 1 is not valid.

Yes, we can do that but it is recommended to use separate rule file for each dimension.

UDA represents the class of the members. Aliases are just another names of the members. both are different and has different usage.

Yes. You can query a member for its UDA in a calculation script.

Absolutely no impact as UDA’s does not require additional storage space.

Attribute dimensions provides more flexibility than UDA’s. Attribute calculations dimensions which include five members with the default names sum, count, min, max and avg are automatically created for the attribute dimensions and are calculated dynamically.

1. UDA’s- No Impact as they do not perform any inherent calculations.
2. Attribute dim- No Impact as they perform only dynamic calculations.

UDA’s values are never displayed in the reports and hence do not impact report performance.

They highly impact the report performance as the attributes are calculated dynamically when referenced in the report. For very large number of att dim displayed in the report, the performance could drastically reduce.

Essbase is an file based database where the data is stored in PAG files of 2 GB each and grows sequentially.

Yes. But only one database per application is recommended.

No. Because we define ASO or BSO option while creating the application and not database. Hence if the application is ASO, the databases it contains will be that type only.

To communicate between Essbase and Microsoft office tools.

Integration services and in version 11, we have Essbase studio.

Yes. We can manage our server resources by starting only the applications which receive heavy user traffic. When an application is started, all associated databases are brought to the memory.

Yes. We can have multiple instances of an Essbase server on a single machine and there will be different sets of windows services for all these instances.

It prevents members from being consolidate across any dimension.

Lower level members and associated data remains in relational database where as upper level members and associated data resides in Essbase database.

In the process it calculates more blocks than is necessary. Sometimes it is necessary to perform top-down calculation to get the correct calculation results.

If we have a single processor, we will use serial calculation but if we have multiple processors we can break the task into threads and make them run on different processors.

Analytic services (or Essbase Services) locks the block and all other blocks which contain the Childs of that block while calculating this block is block locking system.

The statement should be just opposite. As dynamic calc members are calculated when requested, the retrieval time should increase.

Answer

They are specific objects like files, cell notes or URL’s associated with specific data cells of Essbase database. You can link multiple objects to a single data cell. These linked objects are stored in the server. These LRO’s can be exported or imported with the database for backup and migration activities.

There will be no impact on the database as the UDA’s doesn’t store data in the database.

Three types of partitions are there.
1. Transparent partition: A form of shared partition that provides the ability to access and manipulate remote data transparently as though it is part of your local database. The remote data is retrieved from the data source each time you request it. Any updates made to the data are written back to the data source and become immediately accessible to both local data target users and transparent data source users
2. Replicated Partition:
3. Linked Partition:

In the process it calculates more blocks than is necessary. Sometimes it is necessary to perform top-down calculation to get the correct calculation results.

If we have a single processor, we will use serial calculation but if we have multiple processors we can break the task into threads and make them run on different processors.

UDA’s values are never displayed in the reports and hence do not impact report performance.

Analytic services (or Essbase Services) locks the block and all other blocks which contain the Childs of that block while calculating this block is block locking system.

1. Login attempts allowed before username is disabled.
2. Number of inactive days before username is disabled.
3. Number of days before user must change password.

Yes. But only one database per application is recommended.
Depend on which database that you are going to create. For Example: If you are creating ASO then we can’t create more that 1 db per application. If you are creating BSO then you can create more than 1 db per application

Essbase is an file based database where the data is stored in PAG files of 2 GB each and grows sequentially.

The statement should be just opposite. As dynamic calc members are calculated when requested, the retrieval time should increase.

To communicate between Essbase and Microsoft office tools.

Yes. We can have multiple instances of an Essbase server on a single machine and there will be different sets of windows services for all these instances.

Start the change

Register to become an Instructor

Please login to fill in this form.

  • Your name
  • Your email
  • Your phone number
  • Your message

I’m a Copywriter in a Digital Agency, I was searching for courses that’ll help me broaden my skill set. Before signing up for Rob’s.