This is pretty simple to describe:
Table A & B both have a date field. I need a query/procedure which will do:
SELECT A.date, { max(B.date) where B.date < A.date}
Example:
A.date.... B.date
======.... ======
10/10/2006 01/01/1999
01/04/2007 12/12/2006
Result: A.date | Max B.date < A.date...
That is all very useful (I have bridging tables elsewhere to consider) but I think I phrased my question badly. The manager of a project is definitely dimensional data not fact data. What I meant to ask is if it is normal for there to be relationships between different dimensions. In this case...
OK, so I want to keep my DW schemas as simlpe as possible. But say I have my project dimension. A project has a person as owner/leader. I could just merge person fields into project table, but person is also a dimension. Is it considered bad for there to be relationships between dimensions? How...
That makes sense, great.
Taking it a bit further, what if you have the concept of a task having several phases? I think again a phase would come under the dimension category. So with a task you might have "not started"/"in progress"/"complete" phases, with all kinds of other information...
Imagine you want to load to a DW something like the number of minutes spent by a person on a project. The obvious interpretation is that the measurable fact is the number of minutes, and the person and the project should be the dimensions.
But what if you also need to load the projects into the...
Hi there. I'm new here so if my questions are already answered please let me know.
Anyway, two questions about loading data into a DW from the operational process databases:
1)Do we normally update the DW each time the operational DBs are modified? i.e when a sale is made would the DW be...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.