
Originally Posted by
TheAJ
I think you mean going through normal database design procedures of normalization and to eliminate multi-valued dependencies(0NF/UNF to 1NF), partial dependencies (1NF to 2NF), and transitive dependencies (2NF to 3NF/Final).
Technically, this is just a way to draft a database design, and to get rid of inconsistent and redundant data - but soley does not mean it will improve performance. The typcial relational database (in this case, MySQL, and most likely you are using their default engine "InnoDB") will automatically optimize the query for best performance.
I quickly scanned through that database design (the link you posted) and you guys are on the right track. A strong, relational and consistent database is the first step. Ofcourse though, you won't be able to finish the whole design at first, as you'll have to add/delete/modify it as you progress with your server
Good luck!