locked
What causes additional filter criteria to be added to the source query during a partition process RRS feed

  • Question

  • Hi

    This is probably a simple question but I've never really come across this before.

    I have a partition fetching off an *oracle* fact table.  When running a partition process, the query changes from:

    select 
     col1
    ,col2
    ,col3
    ,col4
    from fact

    to

    select 
     "table"."table_aggo_0"
    ,"table"."table_aggo_1"
    ,"table"."table_aggo_2"
    ,"table"."table_aggo_3"
    ,"table"."table_agg0_4"
    from ( select 1 "table_aggo_0",
                  "col1" "table_aggo_1",
                  "col2" "table_aggo_2",
                  "col3" "table_aggo_3",
                  "col4" "table_aggo_4"
            from (select col1,col2,col3,col4
                  from fact) "fact") "table", 
                                     "dim1",
                                     "dim2"
    where (   ("dim1"."col" = "table".col1)
          AND ("dim2"."col" = "table".col2)   )

    The major problem is, is that it is applying some join logic in the query that is generates.  Therefore, on rare occassions, it filters out data rather than failing to join to the dimenion during process

    Anyone got any ideas (mainly what causes this filter logic to happen)...??

    Cheers

    David


    Cheers David

    Tuesday, March 20, 2012 7:11 PM

Answers

  •  Have you checked that you are connecting to the key of the dimension? Also check the processing settings of the dimension, especially around the convert to unknown behavior.

    There might also be something around the uniqueness of the attributes in the dimension.

    • Marked as answer by Challen Fu Wednesday, March 28, 2012 8:17 AM
    Wednesday, March 21, 2012 11:12 AM

All replies

  • have taken a look at my dimension setup and can't see a noticable difference between one dimension that has been added to the where clause by ssas and a dimension that hasn't??

    Cheers David

    Wednesday, March 21, 2012 10:58 AM
  •  Have you checked that you are connecting to the key of the dimension? Also check the processing settings of the dimension, especially around the convert to unknown behavior.

    There might also be something around the uniqueness of the attributes in the dimension.

    • Marked as answer by Challen Fu Wednesday, March 28, 2012 8:17 AM
    Wednesday, March 21, 2012 11:12 AM