1.Q:What is the meaning of the two options from Essbase regarding storage and what separates them?
A: a)The Aggregate Storage Option or ASO:1. Used for more than ten dimensions 2. The majority of the dimensions will be sparse 3. It is impossible to write back in ASO. In the next versions we should be able to write back.
b)The Block Storage Option or BSO:1.Less dimensions and more dense dimensions
2.The write back quality is present, good for application planning. The commercial programs are usually dense, the analytical cubes-sparse. We must comprehend the meaning of the sparse and dense members. Dense means that the cells of two dimensions have intersections that include a value, let’s have this example of two dimensions like period (Month) and region(City, Country)and we have to calculate how much sales are. Usually the biggest regions will get a specific value for a month. We can talk about the dimension period as being dense. Let’s take another dimension, for example-products. The same, some of the products are being sold in a specific region, they will not have any value in other region and they will become sparse. The question that has to asked is what meaning has naming them sparse or dense? Is it any real difference? The answer can be found only by doing good research.
2.Q: Is it possible to construct dimensions straight from the data sorce and not to use the rule files?
A: No, it isn’t.
3.Q: In general why do we have to use rules files?
A: For making dimensions containing thousands of members in an automated way.
4.Q: What are the first 3 ways of constructing dimensions?
A: a)the level references.
b)the Parent/Child references.
5.Q: Can we define in the generation build method generation 1?
A: No we can’t , because it’s not a valid operation.
6.Q:Can we construct a dimension in which we have added Generation 2, then Generation 4 and the following will be Generation 3 but not now, it will be added later?
A: We can’t do it in this way, if 2 and 4 are already applied we must aply Generation 3 as well.
7.Q: With the aid of a single build rule file can we make at least 2 dimensions?
A: yes, but a different rule file should be used for every dimension.
8.Q: What is the meaning of user defined attributes or UDA and what is the difference between them and Aliases?
A: The user defined attributes are referring to the members classes while the aliases are only different ways to name memebres, they are totally separate and have totally separate usages.
9.Q: Is it possible to query a member for UDA in calculating scripts?
A: Yes, we can query members for UDA in calculating scripts.
10.Q: What impact has UDA on the size of a database?
A: Because UDA’s are not needing any space in addition, they don’t have any impact on the size of a database.
11.Q:What separates Attribute dimensions from UDA’s?
A: Attribute dimensions are different from UDA’s because of their improved flexibility. The calculation with the attribute calculations dimensions with five members named: sum, min, max, count and avg is made automatically and dunamicaly.
12.Q:What impact have UDA’s and Attribute dimensions on the performance of batch calculations?
A: The UDA’s don’t have any impact because they don’t make inherent calculations and the Attribute dimensions the same have no impact because they just make dynamic calculations.
13.Q: In what way can we show UDA’s in the reports and what impact have they on the performance of the reports?
A: We can’t show UDA’s in the reports so there is no performance change.
14.Q: What impact do Attribute dimensions have on the performance of reports?
A: The impact of the Attribute dimensions on the performance of the reports is very high due to the dynamic calculation made referencing the reports. If the number of attribute dimensions shown in the reports is high, this will have a negative impact on performance.
15.Q: In the data loading period, what is the result if both the selection and the rejection criterias are implemented?
A: The result will be the rejection of the record.
16.Q:In what way is data storage made in the database of ESSbase?
A: In Essbase (a database based on files)the data storage is made in 2GB PAG files that have a sequential way of growing.
17.Q:Is it possible to keep several databases in only one application?
A: It is possible but the generic recommendation is to use a single database per application.
18.Q: Is it possible to include a BSO and an ASO database, both in only one application and why?
A: The answer is no because BSO and ASO are defined at the making of the application (not the database). The database included by the application will be only ASO if the application is ASO.
19.Q: What file extensions are used for rule file, calc script or outline?
A: The extensions are: .RUL, .CSC and .OTL.
20.Q: What purpose do provider services have?
A:They have the purpose of communication of the Essbase with the office tools of Microsoft.
21.Q: How can we create rule file, load data or metaoutline in a different way?
A: We can make it using Integration services and the ESSbase studio from the version 11.
22.Q: Is it possible to begin and end an application at the individual level and can this enhance the performance?
A: Yes, it is. We can begin only those applications that have high traffic, in this way we can save server resources, the memory will be filled with databases at the beginning of the application.
23.Q: If we already made an application in Unicode mode , can we modify it later to become non-unicode?
A: The answer will be no.