MicroStrategy Interview Q&A Guide
MicroStrategy Interview Q&A Guide
The database repository where definitions of all MicroStrategy objects are stored.
Metadata could be hosted on most databases. In simple words, Metadata could be
considered as the heart of MicroStrategy environment.
What are the tasks that you can perform with the MicroStrategy Architect?
Initially populate the metadata with project definition and parameters, schema
objects and create schema objects
In 2 tier architecture, the MicroStrategy Desktop itself queries against the Data
warehouse and the Metadata with out the Intermediate tier of the Intelligence server.
No it is not reflected. Following are the methods by which we can reflect it in 3 tier.
Update the schema in 2-tier and reload the project from the Project Monitor.
There are no restrictions on the names for the columns used in the expressions of a
given attribute form. Heterogeneous mapping allows the engine to perform joins on
unlike column names. If the user defines more than one expression for a given form,
Page 1 of 47
MicroStrategy Interview Question and Answers
heterogeneous mapping will automatically take place when tables and column
names require it.
For example, because different source systems store Date information in various
contexts, a data warehouse may have multiple columns in different tables which all
represent the concept of 'Date'. The ID form of the attribute 'Date' may contain two
expressions. The DATE_ID column occurs in the LU_DATE table as well as in two
other tables. The elements in these columns correspond to elements in the
ORDER_DATE column in the order_detail and ORDER_FACT tables.
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).
Page 2 of 47
MicroStrategy Interview Question and Answers
Schema Objects: The building block of BI. Schema objects are directly mapped to a
column or columns in the database. Attributes, Facts, Functions & Operators,
Hierarchies, Partition Mappings, Tables & Transformations
Public Objects: Objects that generate analytical data and are built on other schema
objects or public objects. Also called as application objects. Ex: Consolidation,
Custom Groups, Drill Maps, Reports, Documents, Filters, Prompts, Metrics,
Templates and Searches
Types of Attributes
Simple
Implicit Attributes
An implicit attribute is a virtual or constant attribute that does not physically exist in
the database because it is created at the application level. The implicit attribute has
its own expression.
Derived Attributes
Page 3 of 47
MicroStrategy Interview Question and Answers
A derived attribute has its value determined by an expression which combines two or
more columns in a database to create a new column.
An implicit attribute is a virtual or constant attribute that does not physically exist in
the database because it is created at the application level. The implicit attribute has
its own expression.
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 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).
It is preferable to use separate attributes that are related hierarchically (that is,
parent-child relationships) for the following reasons:
Page 4 of 47
MicroStrategy Interview Question and Answers
Page 5 of 47
MicroStrategy Interview Question and Answers
When the attribute must be used as an aggregation level (metric dimensionality). For
example, customer and state: if a user wishes to calculate sales totals by the states
in which customers live, state should be a separate attribute as a parent (or
grandparent, and so on) of customer.
System hierarchy: It contains all the project attributes and its available browse paths
and is based on relation between attributes.
User defined Hierarchy: Custom grouping of attributes and define their browse paths.
Facts
You can use level extensions to change a fact level, which is a set of attributes that
represent the lowest level of detail at which the fact exists in the warehouse.
Level extensions define how facts can be extended, lowered, or disallowed to other
facts across the schema.
When facts exist at a higher level than the report display level, you must specify how
the Engine degrades the data to the lower level. When you lower the level at which a
fact is reported, you are using degradation.
Types of facts
Simple facts
A simple fact is made up of one or more fact expressions. With a simple fact
definition, you can define a fact as a column, constant, or simple expression.
Implicit facts
An implicit fact is a virtual or constant fact that does not physically exist in the
database because it is created at the application level.
Page 6 of 47
MicroStrategy Interview Question and Answers
Derived facts
A derived fact has its value determined by an expression that combines two or more
columns in a database to create a new column.
Metrics
Simple : Simple metrics combine aggregate operators with fact columns or attributes.
Derived
Use a simple expression as a base formula to facilitate the creation of more complex
metrics.
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).
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.
Page 7 of 47
MicroStrategy Interview Question and Answers
The formula defines the data to be used and the calculations to be performed on the
data. The outermost formula must be a group function.
The level, or dimensionality, determines the level at which to perform the metric
calculation. For example, you can choose to calculate at the month level or year
level.
The transformation applies offset values, such as “four months ago,” to the selected
attributes. This is also an optional component.
Rollup metric values that occurs when an attribute is moved from the report grid to
the report objects.
For Eg: The report grid has Quarter and Customer City, Revenue. If we remove
Quarter into the report objects then revenue should automatically roll up to Customer
City.
How to ensure that a particular fact table will be chosen for a metric
The MSTR operates in such a way that the incoming queries and data retrievals are
done from the table which has the least logical size. Thus if we prefer a specific table
Page 8 of 47
MicroStrategy Interview Question and Answers
to be the center of activity then we should try to reduce the logical size of that
specific table so that it becomes considerably lesser than the other tables.
In MicroStrategy, how can you direct the sql generated to use a specific table?
Assuming you have OLAP licence, the easiest way to direct to a particular table is to
create a dummy fact on the table, include the fact in metric and put the metric in
report objects.
What is Metric Formula Join Type? How it is different with Metric Join Type?
Metric Formula Join Type is 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.
Filters
What is filter?
In the MicroStrategy when the same filter conditions must be applied to multiple
passes, the same where clause appears in each of those passes. This redundant
where clause can be expensive if the filter conditions are complicated and thus
involve many tables and joins. Ideally, an intermediate table populated with entries
could be created to satisfy the complicated filter conditions so that the rest of the
SQL statements can use that intermediate table. In that case, the where clause
would be executed only once instead of multiple times and SQL performance would
be improved. In this case to populate the temporary table we can use report as a
filter
View Filters: View Filters are the conditions that come into play before a specific
result is presented to the user. Thus the view filters are not part of the SQL
statements like report definitions, rather they are the filters applied after the
execution of the SQL statements, after the data is retrieved from the data
warehouse.
Page 9 of 47
MicroStrategy Interview Question and Answers
Report filters: report filters are the conditions that accompany the report generating
SQL statements. The report definitions have the filters as part of their definition.
View Filters: View Filters are the conditions that come into play before a specific
result is presented to the user. Thus the view filters are not part of the SQL
statements like report definitions, rather they are the filters applied after the
execution of the SQL statements, after the data is retrieved from the data
warehouse.
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.
When we use the absolute filtering in definition of level metric whatever data we
obtain from the filter is going to be reported as such and 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.
Enables to create filters with attribute pairs as well as triplets, quadruplets and so on.
Security filter is used to apply security at the database data level. Whenever a users
associated with security filter runs a report, a WHERE clause is always included in
the report sql with the condition defined in the Security Filter.
Page 10 of 47
MicroStrategy Interview Question and Answers
Page 11 of 47
MicroStrategy Interview Question and Answers
Prompts
What is prompt?
2. Level: Level prompts enable you to specify the level of aggregation calculation
of a metric
b. Qualify on an attribute
d. Qualify on a metric
Level prompts enable you to specify the level of aggregation calculation of a metric
Report
Page 12 of 47
MicroStrategy Interview Question and Answers
Two metric and one attribute – How will the SQL look if the metrics are from
same tables and are from different tables?
If the two metrics are sourced from the same table then only one pass will come.
If they are sourced from different fact tables then a pass will be generated for each
metric and in the final pass the data will be aggregated,
Difference between drill map and drill path. What is drill to template?
Drill maps allow you to create fully customized drill paths that are available to your
users while drilling on a report. By default, the paths available are based on the
system Hierarchy of the project. You can create custom drill maps that can override
these defaults.
Difference between Consolidation and Custom Groups. How will they affect
SQL ? Which is more expensive operation.
Custom Groups are handled at the database end whereas 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.
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.
Page by enables to select and display subsets of report results as separate pages.
Outline mode enables indented grouping of related attributes This is useful when we
want to display the same report at different levels quickly.
Caching can be enabled/disabled at project or report level. However the report level
setting will override the project level setting.
Using Project Configuration we can enable the caching else in report – using caching
options we can enable or disable the caching.
Templates can also be used for caching. Using a common template for developing
common reports will help to fetch report data faster.
Page 13 of 47
MicroStrategy Interview Question and Answers
2. Background
3. Image
4. Text
Adhoc reports run in real time based on the input parameters provided by the user at
the run time. In Microstrategy, adhoc reports are created using Prompts.
In static reports, users won't be provide any input parameters. These reports are
usually schedule to run overnight and ready to view immediately in the mornings
using cache.
Tables
1. Warehouse catalog
2. Architect
When you add a physical table from the data warehouse into the project, MSTR
creates a corresponding logical table in the metadata. Physical table stores the
actual data whereas the logical data stores information about their corresponding
physical tables including column names, data type and schema objects associated
with the column names.
Page 14 of 47
MicroStrategy Interview Question and Answers
There are two views - the physical view and the logical view in the table editor. The
logical view shows the attributes and facts mapped whereas the physical view
shows the columns and corresponding data types.
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
Other Questions
Architect
Object Manager
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.
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.
Project Merge can be run from the command prompt in Microsoft Windows.
The portion of the interface that allows users to retrieve the results of previously
executed or scheduled reports.
Page 15 of 47
MicroStrategy Interview Question and Answers
When there are changes made to the objects in the data warehouse, the existing
caches may be configured so that they are no longer valid when hitting certain
warehouse tables. Any further report execution will no longer hit the cache.
In the case of a Matching cache, invalidating it will automatically result in deleting it.
When a cache is updated, the current cache lifetime is used to determine the cache
expiration date based on the last update time of the cache. This means that
changing the Report cache duration setting does not affect the expiration date of the
already existing caches. It only affects the new caches that are being or will be
processed.
Cache deletion is a process that deletes the cache from memory as well as disk.
Report caches are automatically deleted by MicroStrategy Intelligence Server if
cache invalidation and History Lists are performed and maintained properly.
Page 16 of 47
MicroStrategy Interview Question and Answers
In the case of a History cache, deleting it does not automatically delete the
associated History List messages that reference it. After deleting a History cache,
when a message that references it is retrieved, the following occurs:
MicroStrategy Web users see an error message, "Execution results not available.
Would you like to re-execute?"
MicroStrategy Desktop users do not see the above error message because
MicroStrategy Desktop automatically resubmits the report for execution.
On the other hand, a History cache is automatically deleted when all the History List
messages that reference it are deleted (when its History List reference count
reaches 0).
In the case of a Matching-History cache, when all the History List messages that
reference it are deleted, it is simply converted to a Matching cache, while losing its
History component.
Cache Purging is a process whereby all report caches can be deleted in bulk, even
the one references by History List messages.
Applying Security filters to the user. This provides row level security
When New Tables are added to the schema using warehouse catalog.
When you update the structure of existing tables in the warehouse catalog.
VLDB stands for Verly Large Data Base Properties. This is MicroStrategy way of
handling database specific preferences while generating the report SQL. There are
number of them. A few common one are for Attribute or Metric join types, cross join
check, type of intermediate table, etc.
Page 17 of 47
MicroStrategy Interview Question and Answers
Page 18 of 47
MicroStrategy Interview Question and Answers
At which levels you can set the VLDB properties? Which level has the highest
precedence?
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.
Putting user specific restrictions at the database end and using user
specific connection mapping. This is for column level security.
Applying Security filters to the user. This provides row level security.
Object Level
Folder Level
Row Level
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.
The command manger is the one through which you can manage the applications,
user accesses, security and databases of the MicroStrategy. The command
manager allows us to save the text commands that can be executed as scripts. Thus
it can help in automation of the entire management process.
What are the nulls on MicroStrategy report and how to mask them.
1)If in this question we want to deal with null in MSTR report than we have some
display property in report data option which we can change according to the
replacement of null values.
Page 19 of 47
MicroStrategy Interview Question and Answers
2) if we want to deal with sql geration of report than there is an option of VLDB
property according to you requirement you can deal with sql query of report
Servers in MSTR
Web Server: MicroStrategy web server responds to the requests from browsers.
Web server interacts with the I-server to extract the necessary information. Can be
installed on most of the major web servers and supports most popular browsers.
Contact MicroStrategy for certified products.
Roles in MSTR
Administrator: By default, the role/person will have full access to the environment.
In other words this role has full access to all the type of objects mentioned above.
Pass through functions are used to utilize various special functions that specific to
databases. Some of the passthrough functions available are Apply simple and Apply
comparison.
Page 20 of 47
MicroStrategy Interview Question and Answers
For example, a fact table in the data warehouse may have two columns: Sales and
Years. If a report is run with Sales for the Year = 1999, the query engine will need to
search through the entire table for all the years, including 1999, to return the data.
To improve efficiency, Partition Base Tables (PBT) can be created to have Sales for
particular years. Assuming that there are 10 years worth of data in the database, 10
different partition base tables need to be created:
A Warehouse Partition Mapping Table (PMT) will then need to be created and will
have:
Year PBTName
1991 PBT1
1992 PBT2
...
2000 PBT10
The above PMT is going to tell the engine which table to grab the data from for a
particular year. This means that when the report is run for Sales for 1997, then the
query engine will first go to the Partition Mapping Table and then find the correct
PBT corresponding to the year 1997.
Metadata Partition Mapping Tables map the attribute elements to its corresponding
PBT and performs the same function as the PMT.
Page 21 of 47
MicroStrategy Interview Question and Answers
4. A data slice can be defined. The data slice will be the attribute (i.e., Year) to
join from this metadata PMT to the PBT.
By doing this, the equivalent of a PMT in the warehouse has been created, but in the
metadata. In theory, both the warehouse and metadata partition mapping tables are
accomplishing the same task
Based on these two categories, the following types of report caches are displayed in
the Cache Monitor:
1. Matching caches
2. History caches
3. Matching-History caches
4. XML caches
Matching caches
When a report is run in a MicroStrategy 8.x project, with report caching enabled, the
Intelligence Server determines for each report request whether it can be served by
an already existing cache. If there is no match, it then runs the report on the
database and creates a new cache. The type column for this cache on the cache
monitor will be 'Matching.'
Matching-History caches
When a report is sent to history directly instead of being executed, the type column
in the cache monitor will be 'Matching, History.' Matching-History cache is a
Matching cache with at least one History List message referencing it. It is actually
one cache with two logical parts: Matching and History.
History caches
The following two circumstances result in the Type column displaying only 'History':
Page 22 of 47
MicroStrategy Interview Question and Answers
also invalidate cache by right clicking the cache entry in cache monitor and
choosing 'Invalidate Cache'.
XML Caches
When a report is executed from Web, an XML cache for this report is created in XML
format. It is available for reuse on Web later on. It is possible that the XML cache is
created at the same time as its corresponding normal report cache. Although just a
different format of the same report cache, the XML cache is maintained as a distinct
cache and thus counts towards the maximum number of caches as an independent
unit. It is automatically removed when the associated report or History cache is
removed.
Types of Caches
1. Element Cache
When is it created?
2. Browsing a prompt
3. In Filter Editor
When is it created?
Page 23 of 47
MicroStrategy Interview Question and Answers
3. Drilling in Documents
5. Intelligent Cubes
Default Ordering
1. Subtotal
2. Compound Metrics
3. Consolidation
4. Metric Limit
1. Compound Metrics
Page 24 of 47
MicroStrategy Interview Question and Answers
2. Consolidation
3. Metric Limit
4. Subtotal
Governing: Intermediate Row Limit, Maximum SQL/MDX size, result set row limit
Joins
Attribute to join when key from neither side can be supported by the other side
Possible Values: - Join common key on both sides, Join common attributes
(reduced) on both sides
Base Table Join for Template: Controls how fact tables are joined, for a report
containing metrics from different fact tables, or for a compound metric which has the
base metrics coming from different fact tables. Controls whether temporary tables
will be created for each metric or if fact tables will be directly joined.
Downward Outer Join Option: Controls how joins are performed when joining metrics
which are calculated at different levels.
Full Outer Join Support: Controls the property which informs the Engine if a full outer
join is supported by the Target database.
Preserve All Final Pass Result Elements: Controls how final pass result elements are
joined to Lookup/Relationship tables
Preserve all Lookup Table Elements: Provides users the option to control if all lookup
table elements should be included in the final results.
Metrics
Metric Join Type: Controls the type of join that is used to join a metric's data with
other metric data on a report.
Null Check
Page 25 of 47
MicroStrategy Interview Question and Answers
Query Optimizations
- Level 0: No optimization.
WHERE clause driving table: Controls which table the Engine should use to
apply the filter (WHERE clause). By default Fact Table is used
Intelligent Cubes
Types of Cubes
Intelligent Cubes: Rather than returning data from the data warehouse for a single
report, you can return sets of data from your data warehouse and save them directly
to Intelligence Server memory. These sets of data can be shared as a single in-
memory copy, to be used by many different reports created by multiple users.
Activities on Cubes
1. Dynamic Aggregation
2. Derived Metrics
3. Derived Elements
Advantages of Cubes
1. Fast Performance
Page 26 of 47
MicroStrategy Interview Question and Answers
3. Drilling
4. Data Sharing
If none of the OLAP features are used then it is a standard report, once any feature
is added like view filter, derived metrics then its converted to a OLAP report. A
Standard report can be converted to OLAP but not vice versa.
1. In PIC, Full access to re execute data against the warehouse but in IC , in order
to re-execute against the warehouse , we have to drill on the data.
2. PIC is linked to a single report whereas multiple reports can access a IC.
3. Both view and report filters can be used in PIC but only view filters can be used
in IC
4. In IC, prompts can be used only on objects included in IC but in PIC it can be
applied even on objects not in the prompt.
6. Consolidations and Custom Groups cannot be used in reports using IC but this
can be achieved by using derived elements
2. OLAP Service Features: View Filters and Derived metrics cannot be used
From the Folder List, expand Administration, then expand System Monitors, then
expand Caches, and select Intelligent Cubes. The Intelligent Cube Monitor is
displayed. Right-click an Intelligent Cube and select Delete. Unpublish only deletes
data in the cube but not the cube itself.
Page 27 of 47
MicroStrategy Interview Question and Answers
When does the report fails due to the unavailability of Intelligent Cubes?
4. Cube is offline
Eg: East Coast: Groups the Mid-Atlantic, Northeast, and Southeast attribute
elements. West Coast: Groups the Northwest and Southwest attribute elements
For Eg: Southern Regions: Returns attribute elements whose name begins with
South.
Northern Regions: Returns attribute elements whose name begins with North.
All other derived elements: Collects all attribute elements that are not included in
derived elements and includes them as individual attribute elements by default
What is a document?
Page 28 of 47
MicroStrategy Interview Question and Answers
Flash View
HTML View
Design View
What is a dataset?
A dataset is a MicroStrategy report that defines the data that the Intelligence Server
should retrieve from your data warehouse or from a cache that is available to the
document.
What is a hyperlink?
A hyperlink connects text or an image in a document to a web page (the target of the
hyperlink). When the document is open in PDF View, as shown below, the cursor
changes to a hand when you hover the cursor over text that contains a hyperlink.
If the data is grouped by page, drop-down lists are displayed at the top of the screen,
What is a layout?
What is a dashboard?
A dashboard is commonly only one page long, is intended to be viewed online, and
usually provides interactive features that let analysts change how they view the
dashboard’s data. By being only one page long, a dashboard makes it easy to view
the whole document at one time and see all the information. A dashboard allows
interactivity from users, so each user can change how they see the data, within the
limits of what the dashboard allows them. You must view a dashboard in Flash View
in MicroStrategy Web to be able to interact with its widgets, selectors, and panel
stacks
Page 29 of 47
MicroStrategy Interview Question and Answers
•Cannot manipulate any objects on the document, as you can in any of the other
display modes.
Interactive Mode
•Use selectors to flip through the panels in a panel stack or display different attribute
elements or metrics in a grid or graph report displayed on the document.
•Add totals.
•Cannot format the layout and positioning of objects or the entire document.
Flash Mode
Access and interact with features provided by Flash, such as widgets. Widgets are
interactive Flash-only graphs, such as gauges and time series slides, that
dynamically update when you select a new set of data.
•Use selectors to flip through the panels in a panel stack or display different attribute
elements or metrics in a grid or graph report displayed on the report.
•Cannot manipulate or format grid or graph reports, except to sort and pivot objects
on them.
•If a graph report uses a graph type that is not supported in Flash, the graph is not
displayed
Page 30 of 47
MicroStrategy Interview Question and Answers
Page 31 of 47
MicroStrategy Interview Question and Answers
Controls are the objects that display the data, images, and shapes in a document;
they are the objects shown in the document’s Layout area as you design the
document.
1. Text Fields
2. HTML container
3. Line or Rectangle
4. Image
5. Grid/Graph
7. Selector, which allows users to interact with the document, by flipping through the
panels in a panel stack or by displaying different attributes or metrics in a Grid/Graph
Static text: This text does not change and is commonly used for labels or
descriptions. Examples in the sample document are the words “Employee” and
“Revenue”. For directions to add static text, see Adding static text to a document
Page 32 of 47
MicroStrategy Interview Question and Answers
Data field
What are the different types of metrics that can be created within a document?
Summary metrics.
Choose Excel-compatible colors for objects as well as grid and graph formatting.
MicroStrategy Desktop's basic set of 40 colors matches the Excel colors. Color
from the Advanced Color Picker will be matched by Microsoft Excel with more or less
accuracy.
Lines and rectangles are not supported when exporting to Microsoft Excel. As a
workaround, use a text field border to create a line or a rectangle.
A line graph within a Report Services document changes color when exported to
excel. [Fixed in 9.3]
When exporting Report Services documents with objects that are overlapped,
unexpected behaviour is seen as Microsoft Excel does not support this feature and
priority might be given to one of the overlapped objects.
Word-wrapping specified for multi-word object names does not take effect in PDF or
Excel.
Custom line in a graph report is not carried over when exporting to Microsoft Excel
as a Live Chart [Not sure if its fixed now]
The secondary axis on a dual axis graph report is not displayed when exporting the
report to Excel format with the option "Export graphs as live Excel charts".
Hence don't export a graph report as live chart in Excel format when exporting it.
Page 33 of 47
MicroStrategy Interview Question and Answers
Banding does not display correctly when exporting reports to Excel 2007 and above
from MicroStrategy 9.2.1 Desktop and Web. Change the excel options such that you
can export to older versions.
Prompt details are not fully displayed when exporting to Microsoft Excel 2007 from
MicroStrategy Web [Link] the excel options such that you can export to older
versions.
Metric values will still appear despite column width set to 0 when exported to Excel
2007 in MicroStrategy version 9.2.1. Use excel 2003 to workaround.
Stacked Bar graph becomes Clustered Bar graph when exporting a Report Services
document to Excel in MicroStrategy Web 9.2.1.
A Report Services document that includes attributes which use the date or date time
datatype. When the document is exported to Microsoft Excel, the attributes are
recognized as plain text instead of dates, thereby inhibiting the use of certain pivot
functions in Microsoft Excel native to the date format.
Page 34 of 47
MicroStrategy Interview Question and Answers
How does MicroStrategy Object Manager determine if two projects are related?
MicroStrategy Object Manager compares the Schema ID's of the two projects.
Duplicated projects have different Project ID's, but their Schema ID's are the same.
What happens if a user tries to move objects between two unrelated projects?
If a user tries to perform cross-project operations between two unrelated projects,
MicroStrategy Object Manager will not permit the operation and will display the
following error:
Objects cannot be copied across the projects because these two projects, "Project
name of the source" and "Project name of the destination", have not been created
from the same source. For more information see Chapter 4: Managing Your
Applications, in the System Administration Guide.
What is the Conflict Resolution Window?
The Conflict Resolution window provides the user with a means to decide how to
handle object conflicts between the source project and the destination project. In
addition, the Conflict Resolution window displays the object name in the original
project, the object name in the destination project and the type of conflict. Users may
also specify a new name for the object depending on the action chosen.
How does MicroStrategy Object Manager determine if two objects in different
projects are the same?
To determine if two objects are the same, MicroStrategy Object Manager compares
their Object ID's. If these ID's are the same, MicroStrategy Object Manager then
compares the Version ID's. If the Version ID's are the same, the Conflict Resolution
grid lists the conflict as 'Exists Identically.' If the Version ID's are different, the
Conflict Resolution grid lists the conflict as 'Exists Differently.'
How can the user determine the Object ID of an object?
To view the Object ID of an object, right-mouse click on the object and select
'Properties.' The Object ID and Version ID are listed on the 'General' tab.
Why does MicroStrategy Object Manager search for object dependencies?
MicroStrategy Object Manager makes a list of all object dependencies before
copying an object to prevent metadata inconsistency. The time required for
dependency checking varies based on a customer's metadata size and schema
complexity. For large metadata and complex schemas, gathering all the
dependencies may take a long time.
Can schema objects be copied across projects with MicroStrategy Object
Manager?
Yes, schema objects can be copied across projects using MicroStrategy Object
Manager. MicroStrategy Object Manager moves objects seamlessly between similar
Page 35 of 47
MicroStrategy Interview Question and Answers
Page 36 of 47
MicroStrategy Interview Question and Answers
Page 37 of 47
MicroStrategy Interview Question and Answers
Page 38 of 47
MicroStrategy Interview Question and Answers
General Questions:
1. Describe your previous experience and the projects you worked on.
2. Describe your expertise, your strengths and your weaknesses.
3. What databases have you worked on?
4. What is the database size that you dealed with? What is the max size of the
database that you worked on?
5. Comfort level on SQL
6. How to tune a report SQL.
7. Troubling shooting an issue.
8. How to you handle the migration process
9. What is the documentation process that you prefer or followed in the past.
10. Any experience interacting with Business Users?
11. Any experience in gathering requirements?
12. Do you have experience training end users.
13. When a users reports an issue and complains about the performance, how
would you handle this, explain in detail.
14. Common User issues that you have experienced?
15. What versions of MicroStrategy have you worked on? What do you like in the
latest version?
16. Tell me one of your favourite feature of MicroStrategy and why do you like it.
17. What is your current team size.
18. If you have multiple architects working on same projects, how do you make
sure that both of them are not modifying the schema at a time.
19. How many users did you support?
20. Describe your experience with NC. List some common issues.
Administration & Narrowcast
1. What is metadata?
2. Explain 2-tier and 3-tier Architecture in MSTR.
3. What is ScanMD and MD Doctor?
4. What is clustering and types of clustering?
5. How did you achieve or document schema object version control at your
previous clients?
6. What are different modes you can run I-Server?
Page 39 of 47
MicroStrategy Interview Question and Answers
7. How can you make sure that I-Server would be running even if the application
mode has crashed and how to get back the instance?
8. What are various authentication modes?
9. What will you do when I-Server crashes?
10. Where is Administrator’s password stored? Is it encrypted? How will you reset
password of all users?
11. What will you do if your Administrator has forgotten password or the account
is locked?
12. How can you monitor the error received while running I-Server and report?
13. What are the features available for MSTR Intelligence Server?
14. When you wanted to compare two projects in MSTR. What are the tools
available and what would you use?
15. What is the use of command manager?
16. Types of caches and where are they stored?
17. Where and how are the report caches saved? When are they used?
18. On what operating systems can MicroStrategy run?
19. Have you done any customizations of the tool, if so please describe.
20. What types of services have you built in Narrowcast.
21. What is the difference between PPE (Personalized Page Execution) and PRE
(Personalized Report Execution)?
Architect and Report Development
1. What are Factless facts?
2. Difference between Star schema and Snowflake schema. And what is best
suited for MicroStrategy
3. What is the difference between view and materialized view?
4. What are OLAP Services. Define couple of them.
5. What’s fact table, dimension table and relate table?
6. Should you have DATE as ID attribute form?
7. What is compound key?
8. What is a relationship table?
9. How will you resolve double counting in M-M relationship between two
attributes?
10. What is the difference between RSD document and HTML document?
Page 40 of 47
MicroStrategy Interview Question and Answers
11. Have you worked on flash dashboards? Explain few feature of flash?
12. What are Transformations? Are there any transformations implemented in
your project? Explain an example from your project.
13. Explain Level Metrics. How it is used in your project?
14. Explain Fact Degradation.
15. Difference between View Filter and Report Filter.
16. Explain custom groups and consolidations and the difference between them.
17. Explain few VLDB properties that you have used in the past and the reason
behind them.
18. What is a role attribute?
19. What are different null which can occur in a report and how do you mask
them?
20. Talk about best practices in creating dashboards and reports
Database Related
1. What is a surrogate key? Difference between a primary key and a surrogate
key.
2. Why do we use a staging area?
3. Why do we use dimensional modeling in DW? Why not Relational?
4. What are conformed dimensions?
Page 41 of 47
MicroStrategy Interview Question and Answers
Page 42 of 47
MicroStrategy Interview Question and Answers
8) Mention what types of testing can be carried out over the Microstrategy
reports?
Microstrategy can carry out test like
– Naming convention tests
– Total calculations test
– SQL query validations
– Attribute and metric positions in the report
– Drilling options tests
– Prompts related verifications
– Security filter tests
– Formatting/export functionality tests
– Threshold testing
9) Explain what is Microstrategy Narrowcast server?
Microstrategy Narrowcast Server is a software product which monitors and delivers
individualized information to users through e-mails, web portals and wireless devices
like pagers, PDAs, and phones. Users determine what information they want, when
and how they want to receive it, through an easy to use web page.
10) Explain what are the advantages of dataset compared to file-set?
File set consists of total tables and information while data-set consists of attributes,
metrics of a particular report only.
Page 43 of 47
MicroStrategy Interview Question and Answers
19) Explain how you can create the intelligent cubes in Microstrategy?
– Intelligent cubes can be made in Microstrategy in the public folder or a particular
user folder
Page 44 of 47
MicroStrategy Interview Question and Answers
– We can make a report and point the report to a cube or right click in a folder and
select the cube option to make a -new cube
– Once the cube is created, select the report objects which is required and save the
cube
– Once the cube is stored and ran to check, one can create multiple reports out of a
cube
– You can also add new attributes and metrics, whenever necessary, and those will
be readily available when you run the reports next time
20) Explain how you can optimize a report in Microstrategy?
VLDB properties enable you to customize the SQL that Microstrategy produces, and
determine how data is processed by the Analytical engine.
21) How long does it take to get Microstrategy Desktop up and running?
Microstrategy Desktop installs in minutes and automatically presents a list of
available Microstrategy Intelligence Servers. Within an hour, the installation and
setup are completed.
22) How does Microstrategy Desktop integrate with the rest of the
Microstrategy platform?
Microstrategy Desktop is the intuitive client-server interface used by business
analysts and application developers. Microstrategy Desktop interacts with the
Intelligence Server to build metrics, create and format reports, and retrieve timely,
accurate information to the desktop to enhance the decision-making process.
23) What security is provided with Microstrategy Desktop?
Microstrategy Desktop provides a host of security options to ensure that data is kept
confidential and private. To facilitate easy deployment and minimal maintenance,
Microstrategy Desktop integrates with Windows NT and 2000 security and with
Novell directory. As a result, users who have logged into these systems will not need
to log on again.
Learn more about Microstrategy Advanced Interview Questions in this blog post.
Page 45 of 47
MicroStrategy Interview Question and Answers
26) Can users join data across SAP BW Info Cubes and Query Cubes?
Yes. Users can use Microstrategy Desktop to create reports that access SAP data
and join data across SAP BW Info Cubes and Query Cubes as well as access
multiple instances of SAP BW at once.
27) Can Microstrategy Desktop join data across heterogeneous data
sources?
Yes. Microstrategy 8 extends the Microstrategy data modeling flexibility to include
integrated views of data across heterogeneous data stores. By mapping conforming
dimensions from different sources, Microstrategy Desktop can automatically join data
from multiple different sources in the same report document. Data can come from
any source accessible by Microstrategy 8, including the data warehouse, data marts,
SAP BW, and any number of operational system databases
28) Does Microstrategy provide predictive modeling capabilities commonly
available in data mining tools?
Yes. Microstrategy 8 can calculate four of the primary data mining functions including
neural network algorithms, clustering algorithms, regression algorithms, and tree
algorithms.
29) Can Microstrategy incorporate best-of-breed data mining insight into
mainstream business reports and analysis?
Yes. Microstrategy 8 has extended its analytic engine with “Data Mining Services”
capability that allows reports and analyses to include predictive capabilities in every
Microstrategy report or analysis. Microstrategy 8 includes the new ability to import
data mining models directly from best-of-breed data mining products from vendors
like IBM, Teradata, SAS, and SPSS using the new PMML or predictive modelling
mark-up language standard.[/sociallocker]
30) What is Microstrategy Narrowcast Server?
Microstrategy Narrowcast Server is a software product that monitors and delivers
individualized information to users via email, web portals, and wireless devices such
as PDAs, pagers, and phones. Through a easy-to-use web page, users specify what
information they want, when and how they want to receive it.
31) Can I access Intelligent Cubes without OLAP Services?
Yes, with the appropriate version of Microstrategy Web or Desktop, certain functions
leverage the Intelligent Cubes. These functions include: report formatting down to
cell level, column aliasing, drilling, pivoting, page-by, adding metric thresholds,
adding subtotals, ranking and sorting. Please see the Web and Desktop version
comparisons to determine exactly which Web or Desktop version includes the
desired functionality.
32) Is OLAP Services sold as a separate product?
Page 46 of 47
MicroStrategy Interview Question and Answers
Yes, OLAP Services is sold as a separate product that is installed with Microstrategy
Intelligence Server. It is licensed either on a per-user or per-CPU basis.
For Indepth understanding of MicroStrategy click on
MicroStrategy Desktop
MicroStrategy Architect
MicroStrategy Reporting
DataWarehousing fundamentals
Page 47 of 47
The many-to-many relationships in MicroStrategy are resolved by introducing an intersection entity that forms two one-to-many relationships. This involves creating a new entity, such as EMPLOYEE_TASK, which links each EMPLOYEE to multiple TASKs while individually associating each TASK with multiple EMPLOYEEs . This approach reduces data redundancy, avoids double-counting, and enhances database performance .
Logical Views in MicroStrategy are created by defining SQL within the MicroStrategy environment rather than relying on pre-existing database catalog tables . This allows for greater flexibility and customization as logical views can structure data specifically for reporting needs without altering the database schema, offering advantages in scenarios where direct database alterations are infeasible .
In MicroStrategy, Custom Groups are processed at the database level, whereas Consolidations are processed by the Analytical Engine. This distinction makes Consolidations generally more resource-intensive because they require additional processing after data retrieval .
Prompts in MicroStrategy provide dynamic interaction by allowing users to modify a report's content at run-time. They enable reports to satisfy a range of requirements by letting users select criteria or objects dynamically, enhancing flexibility and reducing the number of static reports needed . This capability lets users personalize reports without needing to alter report definitions .
MicroStrategy handles cache invalidation by rendering the cache unusable, nullifying its eligibility in the matching process, and eventually deleting it if it is a Matching cache . When a report definition or template changes, the related report cache is marked as invalid. Cache expiration is similar, terminating the useful life of the cache according to the 'Report cache duration' setting. Both processes affect how caches are managed, ensuring outdated or irrelevant caches are not used to fulfill report requests . These actions help control cache growth and maintain report accuracy.
Attribute roles in MicroStrategy are resolved by creating separate table aliases or enabling automatic role recognition, ensuring attributes are referenced correctly in various contexts . This addresses challenges of ambiguity and improper attribute mapping, which can lead to inaccurate data reporting if not handled correctly.
MicroStrategy ensures effective use of Intelligent Cubes by automatically generating them upon running new reports, thus eliminating the need for users to specify which cube to connect to. These cubes provide speedy access to queried data, improving performance for subsequent queries without requiring repetitive data warehouse access . Unlike traditional querying, multiple users can leverage the same cube, which optimizes resource utilization and reduces processing time .
XML caches in MicroStrategy are created when a report is executed from the Web, storing the report in an XML format. Unlike standard caches, these XML formats are distinct and maintained separately, contributing to the cache count. Thus, they provide a reusable report format specifically for Web executions, ensuring consistency and performance optimization in subsequent Web-based report runs .
Security Filters in MicroStrategy apply data-level security by adding a WHERE clause to the report's SQL queries. Whenever a user associated with a Security Filter runs a report, this filter ensures only authorized data is retrieved, thus maintaining confidentiality and compliance with data access protocols .
Metadata Partition Mapping in MicroStrategy maps attribute elements to their corresponding Partition Mapping Tables (PBTs). By doing this, the retrieval process knows precisely which table corresponds to the desired year, optimizing data extraction by linking metadata mappings to warehouse mappings . This process enhances efficiency and accuracy in data reports by directing queries to appropriate partitions based on metadata .