The Database Architect	Back

Modern data warehouses consist of various different types of platforms, for various reasons, and if the architecture remains consistent, scalability, efficiency, cost of ownership and many other design-induced problems are either eliminated or vastly reduced. The architect’s experience and skills are crucial during all phases of the project, especially in the beginning when the skilled architect can already visualize the database’s design concept, refining and adapting the concept and capabilities as requirements are resolved. Having the architect on board from the beginning assures continuity and a design that is in accord with the business requirements lowering the cost of development and ownership. The final outcome risks being compromised, escalating costs and frustrations later if the architect does not have the opportunity to shape the initial concept designs. The benefits of a well designed database positively impact all the systems that interface with it. The development team relies heavily on the specifications flowing from the architectural designs and clear, concise and intuitive documentation and charts are key to reducing mistakes and misunderstanding. For instance, our logical schemas show column-specific relationships providing a more intuitive and clearer picture of the database structure. As primary mentor of the design concepts and fundamentals, the architect remains involved throughout the development and implementation phases.