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

  • SEARCH
  • Home
  • 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 6090665
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T12:14:23+00:00 2026-05-23T12:14:23+00:00

I am working on building a data mart for reporting purpose. I am new

  • 0

I am working on building a data mart for reporting purpose.
I am new to this field and looking for help.

I have a fact table and two dimension tables.
The fact table has only 3 fields, its primary key and foreign key references to two dimension tables.
The two dimension tables have data related to 1)phonenumbers and 2)extension numbers.
(I cannot combine these dimension tables because they have different information)

As you see my fact table does not have any quantitative columns.

I want to generate a report that displays phonenumbers and corresponding extensions.

I can get this information by performing a join on the two dimension tables.

So my question is do I have to use fact table for the report? i.e Should I first get the key from phonenumber table, perform join on fact table, get extension key and perform join on extension table?

OR

Simply join the two dimension tables to generate the report because it is possible in this case?

Do we have to involve the fact table?

Thanks for reading.

Any help is appreciated.

  • 1 1 Answer
  • 0 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-23T12:14:23+00:00Added an answer on May 23, 2026 at 12:14 pm

    do I have to use fact table for the report? i.e Should I first get the key from phonenumber table, perform join on fact table, get extension key and perform join on extension table?

    Often, this is necessary.

    Simply join the two dimension tables to generate the report because it is possible in this case?

    Sometimes, this works, also.

    Do we have to involve the fact table?

    Depends on the relationships.

    If you have a “hierarchy” of dimensional information, then the two dimensions could be directly related. In this case, the fact table doesn’t tie them together. The fact ties to the detailed dimension; the detailed dimension ties to the summary. This is rare.

    Dimensions change.

    If you have two or more Slowly Changing Dimensions, then your dimensions may include lots of “previous” relationship information.

    Fact 1: Phone xxx-xxx-xxxx, Extension yyyy
    Fact 2: Phone xxx-xxx-xxxx, Extension zzzz
    

    Then, another load applies an SCD rule to modify zzzz to aaaa, as of 7/1/11 You may have the old dimension values available, as well as the new dimension values, with an applicable date range.

    Now, the fact (and the date range) are required to define which copy of the dimension value you’re going to get.

    Fact 2: Phone xxx-xxx-xxxx, Extension zzzz, from beginning to before 7/1/11.
    Fact 2: Phone xxx-xxx-xxxx, Extension aaaa, from 7/1/11 to end.
    

    So, you may need the fact, dimensions and time to sort out the relationships.

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

Sidebar

Related Questions

I'm working on a new data type for an Umbraco site and have been
I'm working on building a development tool that is written in JavaScript. This will
I'm currently working on building a java web app. I've been looking to use
I'm working on building a tree structure in MySQL and have been experimenting with
I'm building a Spring MVC app with Spring 3.0.3. I have data binding of
I am currently working on building a classifier using c5.0. I have a dataset
I'm working on building a MySQL database that will have many related tables. I
Let's say you're building something simple, like a data entry/CRUD form for working on
I am working on a data warehousing project, and therefore, I have been implementing
I'm working on building a custom module in Orchard CMS, and I have the

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.