We all had the unfortunate experience of seeing how computers can, at times, make life's journey abit more difficult. This is especially true in knowledge centric workplaces. Describe an example of a very poorly implemented database that you've encountered (or read about) that illustrates the potential for really messing things up. Include, in your description, an analysis of what might have caused the problems and potential solutions to them. Be sure to provide supporting evidence and citations from the literature

 

Answer:

An example of such a database is a small company that has grown but no proper modifications were made in the database of that company .The problems caused due to improper management and their respective solutions are given in the explanation section.

Step-by-step explanation

One such example of a very poorly implemented database is where we Avoid or Neglect the Importance of Data.

Usually a huge amount of data is kept to be consumed later, and the objective is always to keep it and use it in the most proficient manner. To accomplish this the database designer must know about data presentation, how it is going to be gained and at what rate and lastly how it will be utilized.

Example: - A small company was using a database design without complete knowledge. Handling small set of data was achievable for the company.But when the amount of data increased it created problem for the company. Therefore it could not handle huge amounts of data and this lead to many problems. The data volume or size is not the only main angle to consider regarding poor implementation, but the data also influences the level of normalization & the usage of the entire framework.

Also, the major problem toward the failure of any database is the improper use of normalization. Generally, while creating a database the companies use the concept of 1NF because of its simplicity without taking into consideration which normal form is actually required that has disastrous effects on the system like there are more than one entries corresponding to one primary key ,every attribute is not dependent on the primary key and so on. The companies should be clear with the basic functionality that what is the required normal form.It is found that in general cases database should at least be normalized to third normal form or 3NF.

 What caused the problem in this case :

•  Ignoring the concept of Normalization  
• Poor data collection techniques, and
•  Not maintaining a proper database where the data can be used for further use

Potential solutions to the factors regarding the poor implementation of database are listed below: -

Normalization of Database.

The database must posses a desired normal form.

It is recommended that databases should be standardized to the third normal form (3NF), as the format will best speak to entities(entries), and the execution will be best adjusted whilet inserting, updating and erasing records

Know the purpose of Data kept in Database

By knowing the reason for the data framework, it can help in creating the leads in the decision regarding the choice of the database engine, the record size and frame, and the database engine administration approaches.

Think about the possible volume of the database

If you are making a system that emphasizes the current project, the expected volume of data or information could be estimated by viewing the volume of information in the old framework. This information could be utilized when making a model plan a for new framework or system.