Explore topic-wise InterviewSolutions in .

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.

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.

If you WANT to grant access to all DIMENSIONS then you wouldn’t USE a filter. Just grant read access for the database to the user and/or GROUP. The only reason you WOULD use a filter is if you wanted to restrict access.

If you want to grant access to all dimensions then you wouldn’t use a filter. Just grant read access for the database to the user and/or group. The only reason you would use a filter is if you wanted to restrict access.

It PREVENTS MEMBERS from being CONSOLIDATE ACROSS any DIMENSION.

It prevents members from being consolidate across any dimension.

ABSOLUTELY no impact as UDA’s do not REQUIRE additional storage SPACE.

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

A DATA block CONTAINING cells that have been changed since the LAST calculation. UPPER level BLOCKS are marked as dirty if their child blocks are dirty (that is, have been updated)

A data block containing cells that have been changed since the last calculation. Upper level blocks are marked as dirty if their child blocks are dirty (that is, have been updated)

Essbase MACROS that we WRITE with Essbase calculator functions and special MACRO functions. Custom-defined macros use an internal Essbase macro language that enables you to COMBINE calculation function and operate on multiple input parameters.

Essbase macros that we write with Essbase calculator functions and special macro functions. Custom-defined macros use an internal Essbase macro language that enables you to combine calculation function and operate on multiple input parameters.

Yes.we have MULTIPLE meta outlines BASED on one OLAP model in Integration services.

Yes.we have multiple meta outlines based on one OLAP model in Integration services.

The STATEMENT should be just opposite. As dynamic calc MEMBERS are calculated when REQUESTED, the retrieval TIME should increase.

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

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.

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.

It PREVENTS MEMBERS from being CONSOLIDATE ACROSS any DIMENSION.

It prevents members from being consolidate across any dimension.

USING (~) EXCLUDE from CONSOLIDATION OPERATOR.

Using (~) exclude from consolidation operator.

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.

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.

HYPERION Administrative services console provides a MIGRATION utility to do this but only the application, database OBJECTS are migrated and no data is TRANSFERRED.

Hyperion Administrative services console provides a migration utility to do this but only the application, database objects are migrated and no data is transferred.

 No.We cannot CHANGE to nonunicode MODE.

 No.We cannot change to nonunicode mode.

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 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.

INTEGRATION SERVICES and in VERSION 11, we have Essbase studio.

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

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.

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.

The RECORD will be REJECTED.

The record will be rejected.

UDA's values are NEVER displayed in the reports and hence do not impact REPORT PERFORMANCE.

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

Yes. You can query a MEMBER for its UDA in a CALCULATION SCRIPT.

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

UDA REPRESENTS the CLASS of the MEMBERS. Aliases are just another names of the members. both are DIFFERENT and has different usage.

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

YES, we can do that but it is RECOMMENDED to USE separate rule file for each DIMENSION.

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

We cannot DEFINE that as GENERATION 1 is not VALID. 

We cannot define that as Generation 1 is not valid. 

To automate the process of CREATING DIMENSIONS with THOUSANDS of MEMBERS.

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

No. we cannot build dimensions directly from DATA sources WITHOUT using rule FILES.

No. we cannot build dimensions directly from data sources without using rule files.

 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.

 ASO (Aggregate Storage Option) ­ Used for

BSO (Block Storage Option)­