Ross McMicken (3/27/2013)
kevaburg (3/20/2013)
My train of thought is that although from my side it is far more work and attention to detail, I can reduce the amount of damage that a single developer (that incidentally still insist on developing on production databases) can do to the entire instance.If I had a developer who insisted on using production for development, my management would get an ultimatum - him or me, with an explanation of the hazards associated with developer access to production. Doing development on a production database is stupid to the extreme, and possibly illegal if your company is subject to US SOX regulations. I can't think of a reason to ever allow a developer anything other than read access to production data.
Believe me, I am with you all the way except the part that reads him or me! Jobs are hard enough to find! We have this Problem with both the SQL Server and Oracle Environments but additionally, our department head (only one down from the CEO) is also from a development Background. He has determined that they shuold have this ability, as stupid as it is.
The only Thing I have really been able to do is Audit who does what and when. Even that he wanted turned off due to certain restrictions we have here in Europe but to that end my Ultimatum was that auditing would be used or their accounts would be locked and I would have to account for my Actions. That is something in this case I would be happy to do.