Bad Practice No. 1: Ignoring the Purpose of the Data
Bad Practice No. 2: Poor Normalization
Bad Practice No. 3: Redundancy
Bad Practice No. 4: Bad Referential Integrity (Constraints)
Bad Practice No. 5: Not Taking Advantage of DB Engine FeaturesNot knowing or ignoring these capabilities will take development to an extremely uncertain path and surely to bugs and future problems.
Bad Practice No. 6: Composite Primary Keys
Bad Practice No. 7: Poor Indexing
Bad Practice No. 8: Poor Naming Conventions
There are many database naming guidelines on the internet that will shine more light on this very important aspect of database design, but with these basic ones, you can at least get to a readable database. What is important here is not the size or the complexity of your naming guidelines but your consistency in following them!
This blog is listed under Data & Information Management Community
Share your perspective
Share your achievement or new finding or bring a new tech idea to life. Your IT community is waiting!