There’s more to it than meets the eye and the purpose it serves depends what mood I’m in …
1) Reminds me of the worst aspects of some DBAs I still come across. I’ll be able to point them to this from now on so that they can see how things must seem from the poor developer’s perspective.
2) Reminds me of my own “DBA moments” and why we sometimes react like that e.g – “When working on a project that requires new tables and schemas wait until the day of release to production before bringing the DBA into the loop. When he scoffs at your table design tell the VP who wants the project done that the DBA is not being a “Team Player”.”
3) Made me laugh! e.g. ” Q: On what day did God create DBAs?
A: The day before all his access got revoked.”
Well, it cheered me up anyway and I had the good grace to send it round the team to see if we could recognise anyone ;0)
Cheers,
Doug
I liked the “How to make your DBA angry” part. Those make me angry except 7. and 9. These two do not make me angry, especially i prefer putting the business logic in stored packages, but not procedures 🙂
7. Put all your business logic in your sproc
9. Tell the DBA, “I need to make a new table.”
I agree. They aren’t all things that would make you angry, but I’m sure we could add a few more that would!
Cheers,
Doug