Importance Data Modeling

by Claudia J
The article that I read about talked about that in order for us to be good in working with databases it is important to acquire knowledge in security management, data integration and data recovery in the case of a disaster. Designing a good database doesn’t consist only in linking tables together; it requires lots of skills combined to be able to pull off a complete database structure that will run optimally. Many companies tend to fail when trying to design a good database because developing a good database model requires lots of time to create a well-model design and most of the companies don’t count with the necessary time to allocate to the data modeling phase.

Nowadays companies have opted in building database structure in the development phase and doing the coding along. Instead of taking the project into separate phases to avoid time constraints and other functionalities issues in the future. Merging and doing all the phases of a database design at once causes delays, poor database performance and money overspendings. The article gives insight on how important it is to have good code and structure practices when developing a database because it can affect the performance response of the database overall.

In order to succeed, we need to invest good amount of time in the physical design and implement good data modeling techniques which will help in the future when there is a need to manipulate the existing database to add, delete or modified functionalities in a table. I thought this article was good because it recap the importance of learning well how to do the relational database in order to design good databases. We are learning ER modeling and how to connect databases logically so by reading the importance of it and how not knowing how to do initial procedures right at the beginning of the database design could affect a project makes us being more aware in class on the things presented in each chapter. It really takes a lot in making a database and maintaining it efficient.

Robin, Schumacher. (2012) Why Data Modeling?. Retrieved Oct 14, 2012, from

2 thoughts on “Importance Data Modeling

  • October 14, 2012 at 11:17 pm

    Designing the database during the development phase can save a lot of time but lead to more problems in the future. Also, sometimes it depends on the project as the teacher talked about in class. If its something small, then maybe it might work- but having a data model prior to creating a system is a good idea because it acts as a road map.

  • October 15, 2012 at 12:14 am

    I can see why some companies that develop their own databases, especially at a large scale would be tempted to speed through the planning and designing phases. This however, as you mentioned, can and may times will cause problems especially in the long run in the event of scaling up would be necessary. I have seen many, or at least larger companies, outsource the development of their databases to companies in which database development is their expertise. I am not sure how common this is, and how much effort the company in need of the database has to put into the project, however this seems to be an easier but more costly approach.

Comments are closed.