Currently, I have a projects table that stores all of our company's projects. It has a primary key (INT IDENTITY). Now one would think that each project would be ONE project, but that is not the case. In my situation, we one project with the possibility of multiple sub-projects. For example, in my business (construction) we'll have a project to build an office building. A project number is assigned, and then there are additional projects set up, much like phases. Using the office example, there could be a project set up for pre-construction, another one for concrete/foundation, and so on. The project numbering goes something like this: master job: 1000, sub-jobs: 1000.01, 1000.02, and so on. I think that the best way forward is to create a derived table (dimension) for the master job. Doing so would provide me with a clearly defined relationship. Any input would be most appreciated.
asked Jan 12 at 01:33 PM in Default