How to create a perfect fact table ?

  • Hi, all. I'm developing a data warehousing system using Analysis Service. Everyday I transfer data from OLTP system to Analysis Service. But I never able to build a fact table for my data. There is always something's wrong with my data. What's wrong ????

  • I have a little experience of this, but will need some more info: what error messages are being returned? Are the dimension tables being populated ok? Is the schema changing? etc.

    Paul Ibison

    Paul.Ibison@btinternet.com


    Paul Ibison
    Paul.Ibison@replicationanswers.com

  • Hi Hendra,

    As Paul said, to specifically respond to your problem, we do need more information. However, there are general books on the subject if you are looking for a high level approach. A classic is Ralph Kimball's The Data Warehouse Toolkit : Practical Techniques for Building Dimensional Data Warehouses. I'm not pushing Amazon.com (never bought anything from there, myself), but this page should give you an idea about the book itself because it does have some sample pages linked:

    http://www.amazon.com/exec/obidos/ASIN/0471153370/qid=1006975278/sr=8-2/ref=sr_8_3_2/002-3484430-9595208

    K. Brian Kelley

    bk@warpdrivedesign.org

    http://www.sqlservercentral.com/columnists/bkelley/

    K. Brian Kelley
    @kbriankelley

  • Pls post some more information and we will try to help.

    Steve Jones

    steve@dkranch.net

  • A common problem loading fact tables into an OLAP Services cube is failure to rebuild dimensions prior to the data load. There are occassions where the OLAP dimensions do not get rebuilt properly, causing the facts and the dimensions to be out of synch in the cubes. Be sure to process your dimensions before processing the cubes and this might help resolve some of your problems. Also, be sure you are imposing referential integrity on your star schema to avoid the same problem in the relational source tables.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply