This can be acheived by decreasing the logical size of the
desire table in a such a way that it should be less than
other tables. AS Microstrategy will look the tale having
the least logical size and will make a join with that table.
Logical view is just a table(logical table) but it is
create in deskop by writing our own SQL as per Our
requirement based on the physical tabes what we import from
our database.Once if it is create itacts as a physicaltable
as other phisical tables.
we can use alias name of that table and change the logical
size of that alias table dnt modifies main table and use the
you can do so by ODBC test tool one of the component of
microstrategy through wich u can update delete or even alter
the table specification as per your need
developer should know follow things:
i)how to create public objects(metrics,filters...ect)
ii)how to create shema objects(attributes,facts)
iii)how to trouble shoot reports/dashboards
Besides these if a candidate how to write and execute system
test case is well and good :)
VLDB properties allow you to customize the SQL that
MicroStrategy generates, and determine how data is
processed by the Analytical Engine.
Eg: if you want to display top 5, 10 or 15 ranks.
1.Create a value prompt which will prompt the user to enter
the value( to display top n rankers)
2. create a filter to calculate rank and in value field
just drag and drop the prompt created above.
Prompt will be tagged to the filter and user will be
prompted during execution. Depending on the input provided
by the user top n rankers will be displayed
You can do it without using value prompt with below steps.
Create a filter on day attribute qualified on ID operator >
and set value to resolve dynamically today - last 10 days.
Standard filtering allows the report filter to affect the
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).
For performance tuning there some areas where you need to look and work accordingly.
1) is there sufficient space so that MSTR can create temporary tables.
2)proper filtering condition.
3)proper joining between required tables.
4) VLDB property
5)optimization (manual, logical and global)
its better if go go in the same order....