Forum Discussion

rks's avatar
rks
Resolver II
4 years ago
Solved

Skip Partitions during Processing

Hi all,

 

I have a use case with some historical data that never updates. My idea was to throw all this into a partition of a history-dimension and tag this partition (maybe with certain external tools) as "don't process during table refresh". I am aware of the fact that I can create scripts or manually refresh certain partitions. But in this case it would be easier just to implement this information into the model.bim, rather than to create certain processing strategies.

 

Thank you all and best regards,

Konstantin

  • rks I'm missing too much information to be very specific here. If you could provide more information I could be more specific. Let's say you have a single table with all of your historical and current data in it. Pick a point in time and create a query that pulls the historical information. Load. Disable refresh. Create a second query that pulls the current information. Setup incremental refresh on this query. Append the two queries. Hide the historical table in the data model. You could do something like that for example but, again, I don't even know what your source systems are or what you are truly trying to accomplish.

4 Replies

  • Greg_Deckler's avatar
    Greg_Deckler
    Community Champion

    rks If you have a separate query for this then you can simply right-click the query and uncheck "Include in report refresh".

    • rks's avatar
      rks
      Resolver II

      Hi Greg_Deckler , thanks for the answer. If I am not mistaked this is on the table level but not on the partition level. By default all partitions of a table are being processes. Is this flag also available on a partition level?

      • Greg_Deckler's avatar
        Greg_Deckler
        Community Champion

        rks I'm missing too much information to be very specific here. If you could provide more information I could be more specific. Let's say you have a single table with all of your historical and current data in it. Pick a point in time and create a query that pulls the historical information. Load. Disable refresh. Create a second query that pulls the current information. Setup incremental refresh on this query. Append the two queries. Hide the historical table in the data model. You could do something like that for example but, again, I don't even know what your source systems are or what you are truly trying to accomplish.