Re: venting my spleen

Tom Hoffmann wrote:

> On Mon, 01 Jul 2002 12:47:28 -0400, Daniel Morgan wrote:
>
> > Sybrand Bakker wrote:
> >
> >> On Sat, 29 Jun 2002 19:36:51 +0100, "Paul Brewer"
> >> <paul_at_paul.brewers.org.uk> wrote:
> >>
> >> >"Tom Barnes" <barnest_at_san.rr.com> wrote in message
> >> >news:ae6b6116.0206261659.49fb18b1_at_posting.google.com...
> >> >> Part of the problem seems to be the lack of communication between
> >> >> the DBAs and the developers. I recommend that you don't separate
> >> >> your people into two camps of "DBAs" and "developers". You'll need
> >> >> to work together constantly!
> >> >
> >> >Sorry, but I disagree with sentence 2. The responsibilities,
> >> >accountabilities and skillsets differ, so IMHO, in other than the
> >> >smallest shop, there should be a demarcation line. But I agree
> >> >entirely with sentences 1 and 3; developers and DBAs do need to work
> >> >together cooperatively to build, deploy and maintain successful
> >> >applications, and given a set of intelligent, mature adults I see no
> >> >reason why this should present any problem.
> >> >
> >> >Regards,
> >> >Paul
> >> >
> >> >
> >> >
> >> Most organisations I have been consulting for have *Chinese Walls*
> >> between dba's and developers, with developers looking down on DBAs
> >>
> >> Regards
> >>
> >> Sybrand Bakker, Senior Oracle DBA
> >>
> >> To reply remove -verwijderdit from my e-mail address
> >
> > And visa versa. DBAs refusing even the most reasonable developer
> > requests such as granting SELECT on some v$ objects.
> >
> > The problem comes from both camps. And ultimately should be laid at the
> > feet of management that doesn't understand that there is no such
> > (singular) position as DBA.
> >
> > The solution, in my view, is to separate production DBAs from
> > developerment DBAs. Production DBAs should rule as gods over their
> > databases and keep developers, testers, hackers, and everyone else out
> > ... especially including management types.
>
> I've never had the opportunity to work in an organization large enough to
> have the luxury of production vs development DBAs, though I like the
> concept.

It makes a huge difference in how things work. In my opinion "DBA" really stands for three very different positions.

1. Database Architect
2. Development Lead Developer
3. Production Database Administrator

And the three positions require entirely different skill sets, entirely different responsibilities, and entirely different mind-sets.

Organizations that try the 'one set of rules for all' approach are the equivalent of those that try to make every problem a nail and apply a hammer to it.

Daniel Morgan Received on Tue Jul 02 2002 - 11:14:57 CDT