After a database has been constructed and put into service, it can become extremely difficult to make changes to table structures. Poorly planned schemas and unplanned query types can cripple a databases performance or cause significant problems. Moreover, correcting these types of problems can require downtime and/or complex data migrations to a new schema. Performing these tasks without errors or customer impact is a challenge unto itself. Fortunately, there are many tools and techniques available to avoid these types of problems. One of them is modeling your data using an Entity-Relationship diagram.

Write 2 to 3 paragraphs answering the question: Should every database be modeled using an Entity-Relationship diagram (or similar technique) prior to implementation? Provide at least one argument supporting your stance. If your answer is no, be sure to give an example to support your statements.