Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Data Warehousing / November 2005

Tip: Looking for answers? Try searching our database.

Time and Expenses

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Scott - 29 Nov 2005 23:43 GMT
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.
MC - 30 Nov 2005 06:57 GMT
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

> We're building a data warehouse to report on consulting revenue
> (HoursWorked*BillRate) and Expenses.  We need to do things like determine
[quoted text clipped - 9 lines]
> SSAS
> and SSRS.  Thanks.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.