MySQL Database Design. Ten Common Database Design Mistakes. No list of mistakes is ever going to be exhaustive.
People (myself included) do a lot of really stupid things, at times, in the name of “getting it done.” This list simply reflects the database design mistakes that are currently on my mind, or in some cases, constantly on my mind. I have done this topic two times before. Database Design Project. The Wet Paint design school was opened in 2001 in Edmonton, Alberta and it offers art instruction as well as web design courses for the general public.
Most of the courses are offered online with some seminars available on request in locations within Edmonton. Wet Paint does not have any actual offices and all of its activities take place over the internet and by computer. Practical database design, Part 2. In the first half of this article, I began to discuss some general best practices that I have found to be particularly helpful.
Again, none of it is specific to any one vendor's product and everything should, therefore, be applicable, regardless of which database implementation is being used. In this concluding article, I'll attempt to give an approachable introduction to the topic of database normalization and to the five Normal Forms. I'll also discuss other possible uses for a database in a project, such as a repository for configurational or logging data, for example. Normalization No discussion of relational database (DB) design is complete without a section on normalization.