Help in declaring grain and identifying dimensions

Facts with different grain from different sources but related

Hi, I have a situation which I am trying to resolve but not able to Technologies Using : SQL Server and Analytics Services (SSAS) Background I have a flat file which is from the enterprise peoplesoft system and has the followings GL Account,

Mixed grain issues

I am in the process of modelling a typical sales invoice. The header contains the usual suspects...Invoice Date, Customer Number, Tax Amount, Total Amount. The detail is also unremarkable...Product Number, Qty Ordered, Qty Shipped, Total Amount. In

Monster Dimensions

My customer list is huge (about 70 millionish). We currently have a 60 million row dimension (CUSTOMER) that holds most of our existing customers, and this existing large DIM is currently performing fine for us. Now my clients want to type 2 two

Textual values in dimension tables

With much interest I am reading "The Data Warehouse Toolkit", and I stumble upon a design thing that I have done differently in my Data Warehouse design (this is described in the book on page 42). It describes about the dimension table that it

Dynamic dimensions

What is the best way to handle dimensions that change depending on user parameters? For example, lets say you want "Months Since Inception" to be a dimension, because you want to bucket by it (i.e. 0 to 50 Months, 51 to 100 Months, etc.) but

Sparse dimensions, how to handle?

I've purchased the book "The Microsoft Data Warehouse Toolkit" and have reviewed it in order to build out a data warehouse solution I am currently designing. I am stuck in a spot that I don't seem to find any examples of , or am not abl

How to manage Conformed dimensions

Hi, If I'm implementing data mart by data mart, I build a dimension for the first data mart. After a few months, I realize I can use that dimension for the second data mart as a conformed dimension. But it needs additional columns. How do you manage this

Flexiblity To Add Attributes To A Dimension And Not Process The Whole Cube/s

Hello, We are in the process of designing a DW for Games and have run into a business problem : Business users want to add attributes to a dimension and decide its level in the hierarchy on the fly. The new attributes should be availabe in reports

Supplier Dimension to include Customers & Employees

We are in the process of finalising Dimensions /Facts to be used in Datawarehouse. Already finalised separate dimensions (eg Customer,Supplier,Employee) to handle requirements of Sales,Purchace and Human resourses. During designing Accounts Payable Fact

Cube Processing for Dimension Schema changes

Hi, I had a general question about how cube processing works. If my dimension schema changes (an addition of a property), will I have to do a full reprocess of all cube partitions for which that dimension was member of? Or do I only need to

KPI Goals and Percentages as Dimensions or Store as Facts?

We are using PPS Monitoring for our Dashboards and we are creating our KPIs within PPS and SSAS. Our client would like to create a dimension with these KPI goals and percentages for each goal per department and measures or add to the fact table. Now

Linking or Merging Similar dimensions from Different Source Systems

We've got a situation with the DW we're building where we have 2 seperate systems that we are wanting to bring the data together for cross analysis 1) The first system is the main operational system ie a contact management application that records

fact table as a dimension

Hi I'm presently modeling a data mart and I would like to use a fact table as a dimension for another fact table. Is it something doable and efficient or is there a better way to do that? if yes should i just create a surrogate key and link both