• Personally, I think the blame lies mostly with the DBAs. Ten to Fifteen years ago, when all the modern development paradigms were starting to shake out, when object oriented programming was really getting to its feet, DBAs acted like a bunch of over-protective jerks. Yeah, we had reason to be. You want to ensure that the database is online, accurate, and, if possible, fast. So we stood in the way of developers and tried to dictate what they do, slowed them down, threw up road blocks. But the developers still needed to respond to the business and move things fast. So, they bypassed us at every opportunity.

    Now, I sit in developers conferences, because I try to go to those to present, as a DBA, and listen to how we're no longer needed, dinosaurs on our way out, etc. But, I hear how they hit problems with their tools, aren't sure how to solve some of them, are concerned about downtime, etc. In short, all stuff DBAs could contribute to if we could get re-invited to the table.

    At this point, both sides are to blame for not recognizing that it's not code or data that's important, it's the business.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning