Introduction

Database design refers to the process of formulating a detailed data representation of a database. However, this process of data modeling has all the required physical and logical design choices, and physical data storage parameters, which are required for generating a design in a data definition language, which is then used to make a database. This paper pays high attention to the analysis of potential problems that result from a poor database design.

There are numerous problems that are associated with poor database design. First, poor database design results in missing documentation for database during production, which make it impossible to contemplate the impact of change (Howard, 2015). This makes database developers, business analysts, architects scramble to getting on the same page and are left to their own imagination of interpreting the usage and meaning of the data. In addition, poor database design results in little or no normalization. Most database developer tries to enhance the flexibility of a database by designing one table for storing all data. Though this one table approach may enhance the accessibility of data, poor design may result in the repetition of values stored in the table, numerous nulls for columns, and sometimes a unique code would be required for handling the database (Howard, 2015).

Consecutively, poor database design leads to improper storage of reference data. For example, this reference data may either be embedded in the application code or stored in numerous places. Moreover, poor design may result in a database that does not use domains and naming standards, which are the two chief features that are incorporated in database modeling practices (Howard, 2015).

Conclusion

It is, therefore, evident that poor database design can have a wide range of problems. To avoid most of these problems, competent database developers or architects should be called upon during the modeling practice.

References

Howard J., (2015). Deadly Sins of Database Design. Retrieved from, http://edn.embarcadero.com/article/40466