Explore topic-wise InterviewSolutions in .

Compound metrics are the ones that are derived by some specific expression INVOLVING the DIFFERENT simple metrics. Eg, Total( profit/units Sold). Smart metrics is when the compound METRIC is CALCULATED with the help of subtotal calculations for every element inside the compound metric. For the above example the smart metric computation can be Total(profit)/Total(Sold).

Compound metrics are the ones that are derived by some specific expression involving the different simple metrics. Eg, Total( profit/units Sold). Smart metrics is when the compound metric is calculated with the help of subtotal calculations for every element inside the compound metric. For the above example the smart metric computation can be Total(profit)/Total(Sold).

The COGNOS has the two METADATA repository based database, while the microstrategy is based on single metadata repository. The Cognos has only a web based reporting tool, while the microstrategy can be operated as a webbased and a DESKTOP tool. Cognos has a cube dataset which has to be refreshed to get latest repository values before reporting. The microstrategy has no cube dataset and we get the latest data from the data warehouse automatically available. The Cognos reporting can be CONSIDERABLY slow in performance than the microstrategy reporting.

The Cognos has the two metadata repository based database, while the microstrategy is based on single metadata repository. The Cognos has only a web based reporting tool, while the microstrategy can be operated as a webbased and a desktop tool. Cognos has a cube dataset which has to be refreshed to get latest repository values before reporting. The microstrategy has no cube dataset and we get the latest data from the data warehouse automatically available. The Cognos reporting can be considerably slow in performance than the microstrategy reporting.

Trimming of the SQL REFERS to the clean up and OPTIMIZATIONS that are applied to the query at the MSTR level using VLDB settings. The main thing that is achieved by the trimming is the removal of the unwanted cross joins and the other COMPLEX operations

Trimming of the SQL refers to the clean up and optimizations that are applied to the query at the MSTR level using VLDB settings. The main thing that is achieved by the trimming is the removal of the unwanted cross joins and the other complex operations

There are many aspects of the REPORT that can be PUT into testing depending upon the type of report.

• Naming convention tests.
• Total calculations test.
• SQL query validations.
• Attribute and metric positions in report.
• Drilling OPTIONS Tests.
• Prompts related verifications.
• SECURITY FILTER tests.
• Formatting/export functionality tests.
• Threshold testing

There are many aspects of the report that can be put into testing depending upon the type of report.

When we USE the absolute filtering in definition of level METRIC whatever data we obtain from the filter is GOINGTO be reported as such and the the report filter will be overridden by the absolute filter settings. The STANDARD filtering the report filter interacts with the metric filter in the normal way and what we obtain will be FORMATTED according to the report filter settings

When we use the absolute filtering in definition of level metric whatever data we obtain from the filter is goingto be reported as such and the the report filter will be overridden by the absolute filter settings. The standard filtering the report filter interacts with the metric filter in the normal way and what we obtain will be formatted according to the report filter settings

Department table: Department_ID, Department_Name, STATE (Note: Department ID is Unique here and more than one department can belong to one State) Employee Table: Employee_ID, Employee_Name, Department_ID (Note: Employee ID is unique here and more than one Employee can belong to one department, but one employee does not belong to more than one department)

Following should be the query

SELECT DEPT.department_id,
Max(dept.department_name),
COUNT(emp.employee_id)
FROM department dept JOIN employee emp
ON dept.department_id = emp.department_id
WHERE dept.state = “new YORK”
GROUP BY dept.department_id
HAVING Count(emp.employee_id) > 50

Department table: Department_ID, Department_Name, State (Note: Department ID is Unique here and more than one department can belong to one State) Employee Table: Employee_ID, Employee_Name, Department_ID (Note: Employee ID is unique here and more than one Employee can belong to one department, but one employee does not belong to more than one department)

Following should be the query

SELECT dept.department_id,
Max(dept.department_name),
Count(emp.employee_id)
FROM department dept JOIN employee emp
ON dept.department_id = emp.department_id
WHERE dept.state = “new york”
GROUP BY dept.department_id
HAVING Count(emp.employee_id) > 50

Pass-through FUNCTIONS are MICROSTRATEGY way of generating DATABASE specific SQL construct which otherwise are not possible. These are called pass-through functions because Microstrategy does not check the actual SQL construct and DUMPS it as is on the database. Example include ApplySimple, ApplyComparison, ETC.

Pass-through functions are Microstrategy way of generating database specific SQL construct which otherwise are not possible. These are called pass-through functions because Microstrategy does not check the actual SQL construct and dumps it as is on the database. Example include ApplySimple, ApplyComparison, etc.

In Microstrategy security can be incorporated using a mix of any of the following WAYS:
1. Putting USER specific restrictions at the database end and using user specific connection mapping. This is for column level security.
2. Applying folder and object level security to restrict ACCESS to CERTAIN set of reports/objects
3. Applying Security filters to the user. This provides row level security.

In Microstrategy security can be incorporated using a mix of any of the following ways:
1. Putting user specific restrictions at the database end and using user specific connection mapping. This is for column level security.
2. Applying folder and object level security to restrict access to certain set of reports/objects
3. Applying Security filters to the user. This provides row level security.

VLDB Properties can be SET at VARIOUS levels like Report, Template, Metric, Project, Database INSTANCE and DBMS level. Out of this Report level has the highest priority. It overrides all other levels.

VLDB Properties can be set at various levels like Report, Template, Metric, Project, Database Instance and DBMS level. Out of this Report level has the highest priority. It overrides all other levels.

Custom GROUPS are handled at the database end where as CONSOLIDATIONS are handled at the Analytical Engine end. As a result the Consolidations are not an overhead for the database as there is a SINGLE pass in the query. On the other hand Custom Groups are an overhead on the database as they fire a separate SQL pass for EVERY Custom group ELEMENT.

Custom Groups are handled at the database end where as Consolidations are handled at the Analytical Engine end. As a result the Consolidations are not an overhead for the database as there is a single pass in the query. On the other hand Custom Groups are an overhead on the database as they fire a separate SQL pass for every Custom group element.

LEVEL metrics are ADVANCED metrics which are set to be evaluated at a specified ATTRIBUTE level. These are required when in the same report you need to roll up a METRIC at two different LEVELS side by side. Example is comparison of “Revenue from a Region” to “Revenue from a Country”. Here Region and Country are the two different levels.

Level metrics are advanced metrics which are set to be evaluated at a specified attribute level. These are required when in the same report you need to roll up a metric at two different levels side by side. Example is comparison of “Revenue from a Region” to “Revenue from a Country”. Here Region and Country are the two different levels.

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. The logical size does not depend on the actual data (no of ROWS) in the database. If the candidate answers this than his concept is wrong

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. The logical size does not depend on the actual data (no of rows) in the database. If the candidate answers this than his concept is wrong

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

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

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.

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.

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.

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.

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.

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.

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:-
1. Set up the Enterprise Manager.
2. DEFINE the statistics and enterprise warehouse database.
3. Create the statistics database instance
4. Go the project configuration wizard of the project
5. Select statistics and define the what you WANT to log

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:-
1. Set up the Enterprise Manager.
2. Define the statistics and enterprise warehouse database.
3. Create the statistics database instance
4. Go the project configuration wizard of the project
5. Select statistics and define the what you want to log

By CREATING explicit table ALIAS for the same or ENABLING the Automatic Attribute Role recognition.

By creating explicit table alias for the same or enabling the Automatic Attribute Role recognition.

A user defines two attributes that have the same definition but play different roles in the business MODEL. In this example, attribute Origin Airport and Destination Airport are defined USING the same LOOKUP Table and Column (Airport_ID). Both attributes share the same forms, or information about them (Description, LOCATION, etc.). In the fact table, however, a SEPARATE column exists for each of their roles (Origin_Airport_ID and Destination_Airport_ID).

A user defines two attributes that have the same definition but play different roles in the business model. In this example, attribute Origin Airport and Destination Airport are defined using the same Lookup Table and Column (Airport_ID). Both attributes share the same forms, or information about them (Description, Location, etc.). In the fact table, however, a separate column exists for each of their roles (Origin_Airport_ID and Destination_Airport_ID).

This is basically used for COMPOUND METRICS and determines how the different tables used in metric formula are joined. WHEREAS the Metric Join Type determines how the metrics are joined to other metrics.

This is basically used for Compound Metrics and determines how the different tables used in metric formula are joined. Whereas the Metric Join Type determines how the metrics are joined to other metrics.

A report limit specifies a set of CRITERIA used to restrict the data returned in the report data set after the report metrics are calculated. Report FILTER APPLIES the where condition to the QUERY sent to WAREHOUSE to extract the results.

A report limit specifies a set of criteria used to restrict the data returned in the report data set after the report metrics are calculated. Report Filter applies the where condition to the query sent to warehouse to extract the results.

Reports>Project>DATABASE INSTANCE>DBMS

Reports>Project>Database Instance>DBMS

VLDB properties allow you to CUSTOMIZE the SQL that MICROSTRATEGY generates, and DETERMINE how DATA is processed by the Analytical Engine.

VLDB properties allow you to customize the SQL that MicroStrategy generates, and determine how data is processed by the Analytical Engine.

A custom group is a set of SPECIAL filters that can be placed on a template. It is made up of an ordered collection of elements CALLED custom group elements. CONSOLIDATIONS are USED to specify the data you want to view in your report. They ALLOW you to group attribute elements in new ways without changing the metadata and warehouse definitions.

A custom group is a set of special filters that can be placed on a template. It is made up of an ordered collection of elements called custom group elements. Consolidations are used to specify the data you want to view in your report. They allow you to group attribute elements in new ways without changing the metadata and warehouse definitions.

Standard filtering allows the report filter to affect the metric. ABSOLUTE filtering RAISES the report filter to the level of the TARGET, so all subcategories in the CATEGORIES included on the report are added together. Ignore filtering disregards filtering criteria based on the ATTRIBUTE in the target and its related attributes (both parents and children).

Standard filtering allows the report filter to affect the metric. Absolute filtering raises the report filter to the level of the target, so all subcategories in the categories included on the report are added together. Ignore filtering disregards filtering criteria based on the attribute in the target and its related attributes (both parents and children).

By EDITING the projectsources.xml, NEW PROJECT SOURCES can be ADDED.

By editing the projectsources.xml, new project sources can be added.

Logical Views allows application ARCHITECTS to create any desired view using MicroStrategy, without DBA involvement. Once these Logical views are created, they are available to the report designer in a way similar to any other table. This allows developers to model attributes and FACTS WHOSE expressions SPAN multiple TABLES.

Logical Views allows application architects to create any desired view using MicroStrategy, without DBA involvement. Once these Logical views are created, they are available to the report designer in a way similar to any other table. This allows developers to model attributes and facts whose expressions span multiple tables.

An object PROMPT allows you to SELECT which MicroStrategy objects to INCLUDE in a REPORT, such as attributes, metrics, custom groups and so on. Object prompts can either determine the definition of the report TEMPLATE or the report filter.

An object prompt allows you to select which MicroStrategy objects to include in a report, such as attributes, metrics, custom groups and so on. Object prompts can either determine the definition of the report template or the report filter.

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.

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.

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.

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.

Two types: – NAMED USERS or cpu license.

Two types: – named users or cpu license.