I have to agree with Rich on this. At my employer, I own the databases. ( Oracle *and* SQL Server) If they break, guess who is responsible? The exception is 3rd party software that I have little control over. Even then, I can fix some of their coding mistakes through judicious use of database features. ( indexes on FK, constraints, MV/query rewrite to avoid FTS, etc.) Jared On 8/29/05, Jesse, Rich <Rich.Jesse@xxxxxxxxxxxxxxxxx> wrote: > > So if your devs want the DBA role in your production DBs, you give it to > them??? > If devs hurt the production DB bad enough, *I* have to fix it thru DB > recovery. How then is it not the my job to force rules and restrictions? > Granted, there is some leeway of grandfathered schemas/objects/code, but > that comes from a lack of ROI (e.g. to remove a "potentially dangerous" > priv from a schema like "DELETE ANY TABLE", there's no way I can ask the > department to spend 6 months rewriting apps while our backlog grows for no > discernable benefit to the company). But to blanketly say that it's not the > DBA's job to enforce rules and restrictions is a lack of accountability at > best. > My $.02, > Rich > > -----Original Message----- > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Marquez, Chris > *Sent:* Monday, August 29, 2005 10:28 AM > *To:* oracle-l@xxxxxxxxxxxxx > *Subject:* RE: Are you angry DBA? > [snip] > It is my database to support, backup, and make available and avoid > personal mistakes while doing so. > It is NOT my database to force rules and restrictions. > It is NOT my database to block all bad code from and stop all data loss > from. > People *will* "hurt" the database...I just need to be ready to fix what is > within my control. > Anybody feel differently? > Chris Marquez > Oracle DBA > > -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist