Internationalization - Translation details for particular language object (Metadata query)

-

select a.object_id,a.object_name,b.translation from dbo.DSSMDOBJINFO a join
dbo.DSSMDOBJTRNS b
on a.object_id =b.object_id
where b.project_id='Project_id'
and b.Locale =16778249
and a.project_id ='Project_id'


you can use the query to get path from object id to get the path information along with this.

Comments

  1. Bowman7712 April 2012 at 06:49

    I am working with MSTR too.
    Thank you for sharing.
    I have to open a blog for my notes I suppose ;)

    ReplyDelete
  2. kumar23 July 2012 at 22:14

    Thanks for your information, which made me to join Microstrategy online training @ www.monstercourses.com

    ReplyDelete
  3. laxmicynixit18 October 2022 at 09:44

    nice information thanks for sharing..!
    micro strategy certification training

    ReplyDelete

Post a Comment

Popular posts from this blog

Intelligent cubes in Microstrategy

-
Intelligent Cubes: Topics: Intelligent cubes Intelligent cubes Vs Cache Manage and Monitoring cubes Cube Size and Memory usage Accessing Intelligent cubes Dynamic sourcing Intelligent cube & Security filters Intelligent cubes & Multi-tenant Architecture Intelligent cubes & Level Metrics Intelligent cube is an OLAP feature introduced in Microstrategy 9 version.  Intelligent cube is a pre aggregated set of data stored in intelligent server memory and it will give very quick access to the data without hitting the data warehouse. It is very simple to create an intelligent cube, it is same like a report creation. When we create and publish intelligent cube, it stores all the data in intelligent server memory as well as a copy in file system (secondary storage area -Hard disk). Whenever it reboots, it loads the data to memory from the file ·           Stores data in intelligent server memory and in disk We have two ways to access th
Read more

Useful Metadata Queries - Microstrategy

-
Object ID in MSTR 9.2: Object id in MSTR 9.2 metadata tables has been stored as Unique identifier. So we cannot use Metadata object id in MSTR Desktop and vice versa. But we have a built in functions to convert this. MSTR Metadata Object ID to Desktop Object ID: dbo.fn_UniqueidentifierToCharMsTR () MSTR Desktop Object ID to MSTR Metadata Object ID dbo.fn_CharToUniqueidentifier() Metadata query to get user and group details Excluding Everyone group: select GROUPNAME . object_name [Customer_group] , USERNAME . object_name [User_name] from dbo . DSSMDOBJINFO GROUPNAME       join             ( select object_name , OBJDEPN . depn_objid from dbo . DSSMDOBJINFO b                     join                     ( select distinct Object_id , depn_objid from dbo . DSSMDOBJDEPN                      where object_id in ( select object_id from dbo . DSSMDUSRACCT where isgroup = 0 )                      and depn_obji
Read more

Microstrategy OLAP - Dynamic Aggregation

-
Dynamic Aggregation: When you create a report, MSTR SQL engine writes a SQL in a report level and calculates all the metric values added in the report. After report creation and execution, you have two different options in all objects added in the report. a) Remove from report b) Remove from grid  - Dynamic aggregation Remove From Report: Right Click on any attribute and give "Remove from report" then MSTR SQL engine will rewrite the SQL in the new level and calculate all the values Remove from Grid: Right Click on any attribute and give "Remove from grid" (Still that object present in the report object and only removed from the grid) - In this case, No changes in the SQL. MSTR Analytical engine will calculate all metric aggregation based on the new level in the grid  - This is called DYNAMIC AGGREGATION   In simple terms, MSTR analytical engine dynamically aggregates and calculates all metric values when you remove any attribute from the grid How
Read more