We currently have the following SQL Schema:Projects   Budgets       BudgetTabs            BudgetSections                BudgetTasks                   BudgetTaskDetails                   BudgetUnitsThe data held in these tables is used to specify how much a project will cost to complete. The problem I foresee is that whenever we need to get the total value of a project we have a query with a minimum 6 joins (there maybe more if including some other project information). As our db is a multi-tenant the these tables are likely to contain hundred of thousands of rows.We've been wondering whether this information would be better stored in a document db such as MongoDB, which would also enable us to move some of the calculations out of SQL and into our code.
Looking for advice for the following MS SQL Schema
database design;sql server;nosql;relational database;scheme