15 January,2016 by Jack Vamvas
Survival in the DBA world is following good practises but just as importantly it is about identifying bad practises. Bad practises can also be called antipatterns. An antipatterns is a standardised fix to a common problem that may lead to a counterproductive outcome.
There is a well known book – AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis – where this term was first coined. The authors highlighted two criteria required to satisfy a fix as an antipattern
There are hundreds of examples in all fields. You may have heard of cart before the horse, scope creep, stovepipe system, blind faith, accidental complexity,busy waiting, hard coding. There are plenty more concepts used which represent this idea of antipattern.
Keeping an eagle eye and having processes in place to identify these SQL Antipatterns, can yield some serious improvements in database server systems and supporting systems management processes.
I’ve started a series called SQL Antipattern. I’ll be posting SQL Antipatterns sightings.