Physical Database Structure

by David H
The article that I read this week is about building a best fit data warehouse. This article talks about the structure of data warehouse and why physical database design is crucial. Data warehouse structure has four crucial models. There are symmetric multi-processing (SMP), cluster, massively parallel processing (MPP), and grid. The goal of these models is to process a large amount of data. As an architect, they need to come up with solution on how to measure disk space, processing power, and network bandwidth. In business, the requirement of database express on Business Intelligence workload. The dimension of time and data volume is the most challenging of structure. Basically, what data warehouse does is to serve the users who were performing a lot of tasks.  During that time, all of transaction database need to send operational report in real time. The physical design of data warehouse focuses on three terms. There are Operational Business Intelligence, Enterprise Business Intelligence, and Historical Business Intelligence. The characteristic of Business Intelligence workloads include data volume, number of users, type of query, frequency and timing of access, and latency requirement. These characteristics are very important of physical design that influence in data warehouse.

This article relates to class because it mentions on how the physical designs of database affect to data warehouse. I have learned that the characteristic of Business Intelligence workload is very important to database structure. However, it was little complicated but as long as we follow step by step of physical design, we will be fine.  I think we should spend more time on physical database design topic. We need to have deep understanding about this in order to build database.



O’Brien, J. (2008). Building a best-fit data warehouse: Why understanding physical database structures matters. Business Intelligence Journal, 13(1), 51-62.

5 thoughts on “Physical Database Structure”

  1. I never really thought about the physical side of database systems. It does pose a challenge for the database architect to consider all the different aspects of a specific system and take them all into consideration to formulate the best efficient database system. Reading all of the different sides of databases gives me a better understanding on how database systems work, and how many aspects go into making the best system possible.

  2. Physical database structuring…..this is definitely a more technical aspect of database systems that holds my interest, particularly due to my fondness for, well, technical work. I’m sure analyzing business opportunities in terms of how, where, and when to start one’s database and with what tools can be a challenging task. Planning such a system is one thing, but purchasing and organizing the means for creating it is quite another. Of course, having to do so for a successful organization with a sizable budget for such matters can certainly prove to be a bit of fun, no?

  3. It seems like a lot of planning is required to build a data warehouse. There’s so many things that needs to be taken into consideration so that the design of the data warehouse can be useful to the user. This definitely sounds like a challenge for the architects.

  4. When i think about physical structuring, it think of it as a simple step. I never though it would require this much of thoughts and planning in to it. But its a good thing that some much design and planning go into this step because data warehouse is very important in hosting so much data

  5. wow!! great article I must say, I actually talked about physical data structured in my article as well. I think the important part is to follow the necessary steps and procedure to build a data warehouse.

Comments are closed.