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 7547447
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T09:27:19+00:00 2026-05-30T09:27:19+00:00

When reading a book for business objects, I came across the term- fact table

  • 0

When reading a book for business objects, I came across the term- fact table and dimension table. Is this the standard thing for all the database that they all have fact table and dimension table or is it just for business object design? I am looking for an explanation which differentiates between two and how they are related.

Edited:

Why cannot a query just get the required data from the fact table? What happens if all the information are stored in one fact table alone? What advantages we get by creating a separate fact and dimension table and joining it?

Sorry for too many questions at a time but I would like to know about the inter-relations and whys.

  • 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-30T09:27:20+00:00Added an answer on May 30, 2026 at 9:27 am

    Dimension and Fact are key terms in OLAP database design.

    • Fact table contains data that can be aggregate.
    • Measures are aggregated data expressions (e. Sum of costs, Count of calls, …)
    • Dimension contains data that is use to generate groups and filters.
    • Fact table without dimension data is useless. A sample: “the sum of orders is 1M” is not information but “the sum of orders from 2005 to 2009” it is.

    They are a lot of BI tools that work with these concepts (e.g. Microsft SSAS, Tableau Software) and languages (e. MDX).

    Some times is not easy to know if a data is a measure or a dimension. For example, we are analyzing revenue, both scenarios are possibles:

    • 3 measures: net profit , overheads , interest
    • 1 measure: profit and 1 dimension: profit type (with 3 elements: net, overhead, interest )

    The BI analyst is who determines what is the best design for each solution.

    EDITED due to the question also being edited:

    An OLAP solution usually has a semantic layer. This layer provides to the OLAP tool information about: which elements are fact data, which elements are dimension data and the table relationships. Unlike OLTP systems, it is not required that an OLAP database is properly normalized. For this reason, you can take dimension data from several tables including fact tables. A dimension that takes data from a fact table is named Fact Dimension or Degenerate dimension.

    They are a lot of concepts that you should keep in mind when designing OLAP databases: “STAR Schema”, “SNOWFLAKE Schema”, “Surrogate keys”, “parent-child hierarchies”, …

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

Sidebar

Related Questions

While reading a book, i came across this statement: The methods of an object
I was reading the book Expert C# 2005 Business Objects . The book describes
I was reading a book and came across a program to read entries from
I am reading EJB 3 in Action and I came across this sentence In
While reading a book about JavaScript I stumbled across an example: var names =
I'm reading this book on C# and .NET and I'm learning a bunch of
I'm reading a book Crafting Rails Applications by Jose Valim and have come across
I am reading a book which mentions this If the compiler knows every use
I am reading book called C++ coding standard By Herb Sutter, Andrei Alexandrescu and
I was reading this book about WCF services. What it said was to create

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.