That's what happens when you have 10 times as many developers as DBAs and the DEVELOPERS are the ones writing all stored procedures and creating/modifying tables and databases without DBA consultation or interaction.
Yes, you read that correctly. Welcome to my hell.
I feel your pain. I can tell you though at my shop one of the first things I convinced my manager of is that we do not just hit F5 on any SQL code coming into our QA environment. We review all incoming SQL code for standards and performance metrics and if ANY developer code fails that review, then that code is returned to development for retooling. Period. There are no exceptions to this rule and we got managment buy in on it as well. Without management buy-in its useless. The code does not rollout unless the DBA group bless it, period. Some see this as a bottleneck, sure, but let a developer lock up an important production database with a badly coded stored procedure and the phones start lighting up, then managment sees the light real fast. 😀
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"