Blog Journal entry 4

Meesha Carey- Module 4

Seven Deadly Sins of Database Design. By Jason Tiret: How to avoid the worst problems in database design (2015). Retrieved from http://edn.embarcadero.com/article/40466

Why was this article, blog, post, or multimedia chosen?

This article was chosen because it discusses issues with database design which is what is addressed in module 4.

What makes it interesting, appropriate, or reputable?

The article is appropriate because some of its contents were addressed in our access assignment, and it’s applicability to health care practice is evident.  

Is it an opinion? Case study? Research study? Product review?

The article is based on the views of Jason Tiret, the director of project management for modeling and design solutions for Embarcadero. Embarcadero is a provider of multi-platform database tools and developer software.  

What was the need, problem, issue or trend addressed in the article, blog, post, or multimedia?

The issue addressed in the article is how to avoid the worst problems in database design. The author states that several factors may be responsible for a poor database design. He states that the problem could be a lack of experience, a shortage of the necessary skills, strict timelines as well as insufficient resources. The author also states that poor database design can lead to poor performance, inability to make changes to accommodate new features and low quality data that can become very costly.

What was the solution for which technology had an answer?

The author’s solution to the problems discussed above is to address some simple data modeling and design fundamentals which is listed and discussed in great detail. The 7 sins and solutions are discussed below:

1.      Poor or missing documentation for database in production. - Solution is to place the document into a centralized repository.

2.      Little or no normalization- Solution is to apply normalization which will add flexibility to a design while reducing redundant data.

3.      Not treating the data model like a living, breathing organism- Solution is to practice the “design then build” model and as changes occur in the future, those changes need to be applies back to the model.

4.      Improper storage of reference data- Solution is to store reference values in the data model if possible and to have it defined in one place and used in other places.  

5.      Not using foreign keys or check constraints- Solution is to utilize check constraints and to validate the data in the database. This will help handle errors and increase data quality.

6.      Not using domains and naming standards- Solution is to always utilize naming standards because having a set of standards ensures consistency across systems and promotes readability of models and codes.

7.      Not choosing primary keys- Solution is always identify a primary key, and make sure to get it right the first time because changing it down the line can be a huge undertaking.

What implications might this have in healthcare delivery?

The implication in healthcare delivery is having a better understanding of data design in order to design projects for organizations that can save them time and money in the future.

What did you learn from it that might have application for your practice?

I learned several things from this article that can be applied to my practice. Reading through the author’s 7 deadly sins of database design, I’ve learned that it is important to capture as much information as possible for the database and that it is important to properly store the data. I’ve also learned the importance of having check constraints as well as properly choosing primary keys. After completing the access assignment and reading this article, I have gotten a better understanding of database principles.