What you're describing can be done to great success with the right type of requirements. Say you're building an information warehouse for OLAP style work. Total

What you're describing can be done to great success with the right type of requirements. Say you're building an information warehouse for OLAP style work. Totally makes sens to pyt all the heavy stuff in the DB because the data model is going to be pretty rigid and it's the sort of asset to get enough attention from the business to be supported correctly with a full staff. On the other hand, defnining everything in code and using the db as a dumb store that's fractionally better than using files is a pretty good strategy when you may be handing over support to a team that won't be giving full time attention to the app. It also handles those key person risks etc by keeping thigns in one area of the app code.