Deleting unused Facts in MicroStrategy

I was searching a technote for a friend about distinct not apearing in the SQL (not something to do True Key, sadly) with the and landed up with this interesting technote which I’m going to implment for my current project sometime. We can’t use Object Manager to find this even though there is specific feature to do it as Tables are considered (logically) dependent on Facts. [Can anyone from MicroStrategy explain why is that? It should be other way round.]

Luckily it is simple but you need to have Select access on Metadata. Just run following query against your metadata database and your would get the list of afacts not used by any metric. Also, your would need to run it for each project your have. :(

SELECT object_id,
       object_name
FROM   dssmdobjinfo
WHERE  object_type = 13
       AND project_id = <Project ID> 
       AND object_id NOT IN (SELECT DISTINCT depn_objid AS object_id
                             FROM   dssmdobjdepn
                             WHERE  project_id =??
                                    AND depnobj_type = 13
                                    AND object_type = 4)
ORDER  BY object_id ASC

Disclaimer: Running a unmanaged SQL query against Metadata is not guranteed by MicroStrategy, Inc.


Notice: compact(): Undefined variable: limits in /home1/microoat/public_html/blog/wp-includes/class-wp-comment-query.php on line 821

Notice: compact(): Undefined variable: groupby in /home1/microoat/public_html/blog/wp-includes/class-wp-comment-query.php on line 821

Notice: compact(): Undefined variable: groupby in /home1/microoat/public_html/blog/wp-includes/class-wp-comment-query.php on line 821

Warning: count(): Parameter must be an array or an object that implements Countable in /home1/microoat/public_html/blog/wp-includes/class-wp-comment-query.php on line 399

3 thoughts on “Deleting unused Facts in MicroStrategy

  1. Hello Ashish,

    I need some help with my dashboard. Am new to microstrategy and this is my first project. Can you please help me out.

     
    I created the dashboard with same look and feel with metrics placed in the text boxes.
     
    Now he wants three drop down selectors
     
    Region     District  (Driven by Region)      Store  (Driven by District)
     
    Should i directly place these selectors on document header and select Target as the grids in doument objects or Metrics in the dasboard. and select source as these resp. attributes.  ( I tried it but when i execute the document, drop down boxes are not populating the elements).
     
    I tried using Panels , selected panels as Selector targets, but nuthing seems to work.
     
    Am just stuck, i tried everything. Please suggest me.
     
    I tried even grouping by these 3 attributes.   initially it selects all for three attributes and displayes about 16 documents for each region. As per the requirement it should display total for all regions( That is what i am thinking).
     
    Please help me
     

    Thanks,
    Swetha

  2. If dropdowns are not populating the element,s most probably the data is not populated in warehouse.

    Can you create 3 different reports containing these 3 attributes. If these reports doe not show any data upon execution, there is no sufficient data in your WH. Need not worry. You output would look fine once your move this dashboard into production environment.

  3. want Distinct Customer Count by Period.
     
    this is for a dashboard. and we have last 12 PEriods(months) like below and is constructed using consolidation.
     
    MAT(Prd1+prd2+prd3) and prd 1 prd 2  and prd 3 till prd 12.in the columns(consolidation)
     we have this consilidation on the columns and metrics on the rows.
    we have below metrics in the rows.
    Sales$
    Transcount
    Customer count
     

    Issue: the issue here is for sales $ its ok to sum the $ for last 3 periods for MAT.but for Customer count we want to have a distinct count of all the customers for the 3 periods not jus for individual periods and sum it up as this would be doubling becas a customer would have shopped in all 3 periods and we would be counting as 3 customers but in real life it was jus one customer. we are using distinct count of the customers and its ok when its run for one period its only issue when we use it in cosolidation for MAT(which is prd1+prd2+prd3).
     
    If any one has any Idea or workaround to get this sorted that would be great.

Comments are closed.