by Willen L
In this article, the author states that people that work with anything related to databases are often asked by their organization to take on the job of data modeling even though it does not specify it on their job description. With that said, he gives us some basic data modeling concepts everyone working with databases should know. He states that data modeling begins with understanding the requirements and to use this knowledge as a blueprint to build a physical database. He states that it is important to understand and build a well-designed data model in order to increase value to the organization by minimizing redundancy, maximize data integrity, increase stability, enhanced data sharing, consistency, more timely access to data, and better usability. Without a good data model you will run the risk of missing some important data that can be a disadvantage for the business. He states that it is important to think of “what” is of interest instead of “how”. He leaves off with 3 basic tips that everyone should know. First think conceptual – focus on business issues and terms. Second, think structure, how something is done is not as important as processes being done to. Last, think relational, the way things are related to one another.
I think this article was helpful for me because it has been stated that if we get a job working with databases, usually the databases are already build and we start from there and there is no need for building the database from ground up but in this article it states that in the real world it is often not the case as people are asked to do tasks that are outside of their job descriptions. I also find it helpful because it helps me understand the “big picture” of how data modeling is and how important it is to the organization.
Mullins, C. (2002 November). Data Modeling Concepts Every DBA Should Know. Craigsmullins. Retrieved January 14, 2012, from http://www.craigsmullins.com/dbta_015.htm