Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1017757
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T10:45:12+00:00 2026-05-16T10:45:12+00:00

Is there a pattern that can handle recurring dimension in data warehouse? I’ve got

  • 0

Is there a pattern that can handle recurring dimension in data warehouse? I’ve got recurring company subjects structure. Sales fact can be assigned at every level. Example

 Company A                  <- sales facts here
    Company A subcompany    <- sales facts here
         Department A1      <- sales facts here
         Department A2      <- sales facts here
 Company B                  <- sales facts here
 Company C                  <- sales facts here
    Company C department    <- sales facts here

While displaying sales fact sum for Company A I want it to be sum of sales of whole tree.

In my relational database I have a parent-child recurring structure. I can’t (or don’t know how) create this kind of structure in data warehouse, as dimensions levels must be defined.

I thought about 3 levels of hierarchy, but some companies doesn’t have departments at all.

I’m using InfiniDB and trying to configure Mondrian and JPalo

  • 1 1 Answer
  • 3 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T10:45:12+00:00Added an answer on May 16, 2026 at 10:45 am

    Simply de-normalize this into the dimDepartment table

    dimDepartment          Example Data
    ----------------       -------------
    DepartmentKey            1234
    DepartmentBusinessKey    a_b_a1
    Department               A1
    SubCompany               B
    Company                  A
    

    So for whole company A:

    select
        sum(Amount) as TotalSale
      , sum(Taxes)  as TotalTax
    from factSale      as f
    join dimDepartment as d on d.DepartmentKey = f.DepartmentKey
    where Company = 'A' 
    

    for sub-company B of the company A

    where Company    = 'A'
      and SubCompany = 'B'
    

    for department A1, sub-company B, company A

    where Company    = 'A'
      and SubCompany = 'B'
      and Department = 'A1'
    

    If a company does not have sub-companies, simply use ‘none' or 'main' as a default sub-company name.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Is there a browser or plugin that can handle multiple cookie sessions on a
Are there any patterns or best practices that can be used to simplify changing
Are there any known design principles, best-practices and design patterns that one can follow
Is there a pattern that I could apply to refactor this code? The only
Is there any order or pattern that action parameters in an MVC controller follow.
Is there a multiple instances pattern in F# somewhere? Consider that I'm working on
Observer pattern: There are 2 variants of it. Where Subjects informs all the observers
Are there pattern recognition algorithms where I can specify the weight of matching or
Is there a pattern that I may use for calling the required initialization and
Are there any mnemonics or patterns that make memorizing emacs key combos easier?

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.