• Michael Valentine Jones (5/7/2009)


    The most common and worst mistake is failing to develop a normalized data model that fits the real world data.

    Most developers seem to just throw tables together with little thought about how it actually models the real world data. Once a bad table "design" is in place, the application is doomed to an endless series of hacks to work around the design problems.

    You can fix bad indexes and poorly written stored procedures, but a bad table design is with you forever.

    Thats exactly the issue I face daily - hastily built databases that are data stores for websites which haven't been designed.

    Extendeded functionality leads to extra tables being added without any review of impact on the database.

    Also LINQ gets thrown in and it all goes down hill with the devs then having no idea how to navigate through the data.

    But hey they employ me to bail them out so its all good in a way 😉

    Hiding under a desk from SSIS Implemenation Work :crazy: