Isn't this pattern well-served by Data Virtualization? Basically, the virtualized views exposed by the Data Virtualization layer are the JIT tables that Stakeholders demand. Thoughts?
Could try the Kimball lifecycle approach and try to model a business process? Then you have data that can be used for more than one report. And who needs conceptual, logical, physical model? With dimensional modeling, they are pretty much the same thing. I don’t need E/R either. Relational modeling is good enough for me.
Isn't this pattern well-served by Data Virtualization? Basically, the virtualized views exposed by the Data Virtualization layer are the JIT tables that Stakeholders demand. Thoughts?
Could try the Kimball lifecycle approach and try to model a business process? Then you have data that can be used for more than one report. And who needs conceptual, logical, physical model? With dimensional modeling, they are pretty much the same thing. I don’t need E/R either. Relational modeling is good enough for me.