Re: Time and Expenses

Probably one fact table. It depends on how do you want to implement
Expenses. They dont have Hours attached to them so you would have to put 0
as a value for Hours. If 0 hours is not a problem, dont see why you wouldnt
go with one fact.

If, however, there are different attributes attached to those two objects
(lets call them Payment and Expenses) then you should probably go with two
facts.


MC


"Scott" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3C1B54BC-B0E4-4A91-AFDC-85A861296A19@xxxxxxxxxxxxxxxx
> We're building a data warehouse to report on consulting revenue
> (HoursWorked*BillRate) and Expenses. We need to do things like determine
> Gross Profit (GP) based on a consultant's loaded rate and by subtracting
> the
> non-reimbursable expenses and costs from the revenue. Should this be one
> fact table for both Hours and Expenses or two fact tables, one for Hours
> and
> one for Expenses? Is there a best practice? They seem like different
> data
> to me. I'm a relational database administrator learning the ropes of
> dimensional modeling and data warehousing. Using SQL Server 2005 SSIS,
> SSAS
> and SSRS. Thanks.


.

Loading