11). How do we resolve attribute roles?
By creating explicit table alias for the same or enabling the Automatic Attribute Role recognition.
12). What are statistics tables and how do you configure the project statistics?
Statistics tables contain data on the Microstrategy system’s usage and performance, and are populated by all projects that are configured to log statistics.
To configure:-
Set up the Enterprise Manager.
Define the statistics and enterprise warehouse database.
Create the statistics database instance
Go the project configuration wizard of the project
Select statistics and define the what you want to log
13). What is the Command Manager?
Microstrategy Command Manager lets you perform various administrative and application development tasks by using text commands that can be saved as scripts.
Like for example: – server management, user management, security, database management.
14). Difference between project merge and object manager?
1). Object Manager can move just a few objects or just the objects in a few folders. Project Merge moves all the objects in a project.
2). Object Manager must locate the dependents of the copied objects and then determine their differences before performing the copy operation. Project Merge does not do a dependency search, since all the objects in the project are to be copied.
3). Project Merge can be run from the command prompt in Microsoft Windows.
15). How conflicts occur and what the ways to resolve them?
When copying objects across projects with Object Manager, if an object with the same ID as the source object exists anywhere in the destination project, a conflict occurs. There are various ways to resolve depending upon the conditions like use existing, replace, keep both, use newer, use older, update in same path, update in new path and merge privileges.
16). How many types the microstrategy license can be bought?
Two types: – named users or cpu license.
17). What are report caches and how many types are there?
A report cache is a result set from an executed report that is stored on Microstrategy Intelligence Server. 4 types: matching caches, history caches, matching-history caches and xml caches.
18). While establishing relationship between attributes how do you decide which attribute qualifies as child and which one as parent?
While establishing the relationship between attributes one can either look from business hierarchy point of view and the attribute higher in the hierarchy becomes parent of the attribute lower in the hierarchy. Parent and Child follow a one-to-many relationship. Example Time hierarchy Year > Month > Date. Here Year would be parent of Month and Date and Month parent of Date.
We can also identify Parent-Child relationship from database design point of view. Here in a table the Primary Key uniquely identifies the other columns in the table and hence qualifies as child of all the other attributes from the table, in the same ways as a child in real world identifies his father (at least the biological one).
19). What is a joint child?
A joint child is Microstrategy way of handling Composite Keys. Composite keys are constituted of two or more columns which together act as unique identifier. To handle this case in Microstrategy we make this set of columns, constituting composite keys, as joint child.
20). What is a logical size of a table and what does it depend on?
Logical size is Microstrategy way of generating the best suitable/optimized SQL to fetch the required data.
Microstrategy follows an algorithm to calculate the logical size of a table, which depends on the no of attributes and facts based on the table and also the position of those attributes in the system hierarchy.
By creating explicit table alias for the same or enabling the Automatic Attribute Role recognition.
12). What are statistics tables and how do you configure the project statistics?
Statistics tables contain data on the Microstrategy system’s usage and performance, and are populated by all projects that are configured to log statistics.
To configure:-
Set up the Enterprise Manager.
Define the statistics and enterprise warehouse database.
Create the statistics database instance
Go the project configuration wizard of the project
Select statistics and define the what you want to log
13). What is the Command Manager?
Microstrategy Command Manager lets you perform various administrative and application development tasks by using text commands that can be saved as scripts.
Like for example: – server management, user management, security, database management.
14). Difference between project merge and object manager?
1). Object Manager can move just a few objects or just the objects in a few folders. Project Merge moves all the objects in a project.
2). Object Manager must locate the dependents of the copied objects and then determine their differences before performing the copy operation. Project Merge does not do a dependency search, since all the objects in the project are to be copied.
3). Project Merge can be run from the command prompt in Microsoft Windows.
15). How conflicts occur and what the ways to resolve them?
When copying objects across projects with Object Manager, if an object with the same ID as the source object exists anywhere in the destination project, a conflict occurs. There are various ways to resolve depending upon the conditions like use existing, replace, keep both, use newer, use older, update in same path, update in new path and merge privileges.
16). How many types the microstrategy license can be bought?
Two types: – named users or cpu license.
17). What are report caches and how many types are there?
A report cache is a result set from an executed report that is stored on Microstrategy Intelligence Server. 4 types: matching caches, history caches, matching-history caches and xml caches.
18). While establishing relationship between attributes how do you decide which attribute qualifies as child and which one as parent?
While establishing the relationship between attributes one can either look from business hierarchy point of view and the attribute higher in the hierarchy becomes parent of the attribute lower in the hierarchy. Parent and Child follow a one-to-many relationship. Example Time hierarchy Year > Month > Date. Here Year would be parent of Month and Date and Month parent of Date.
We can also identify Parent-Child relationship from database design point of view. Here in a table the Primary Key uniquely identifies the other columns in the table and hence qualifies as child of all the other attributes from the table, in the same ways as a child in real world identifies his father (at least the biological one).
19). What is a joint child?
A joint child is Microstrategy way of handling Composite Keys. Composite keys are constituted of two or more columns which together act as unique identifier. To handle this case in Microstrategy we make this set of columns, constituting composite keys, as joint child.
20). What is a logical size of a table and what does it depend on?
Logical size is Microstrategy way of generating the best suitable/optimized SQL to fetch the required data.
Microstrategy follows an algorithm to calculate the logical size of a table, which depends on the no of attributes and facts based on the table and also the position of those attributes in the system hierarchy.
0 comments:
Post a Comment