Re: DBAs and System Managers - War and Peace?

In article <44op6r$6ld$1_at_mhadf.production.compuserve.com> Paul Collins <76004.2053_at_CompuServe.COM> writes:
>From: Paul Collins <76004.2053_at_CompuServe.COM>
>Subject: Re: DBAs and System Managers - War and Peace?
>Date: 2 Oct 1995 13:24:43 GMT
 

>In my last two positions the Sys Admin reported to the DBA. In
>both cases though Oracle was the only thing running on the
>systems. In situations where the Sys Admin managed other boxes
>that had nothing to do with Oracle then They were indirect
>reports. The bottom line is if the machine runs Oracle then the
>DBA runs the machine not the Sys Admin. In reality I work very
>closely with my Sys Admins and we get along very well, but I am
>the one who makes the final decisions on all aspects of the
>system. I have complete system privilege and I give my Sys Admin
>DBA rights on the DB. I train them in important DB tasks and
>they keep me up to date on the OS. It really works out very
>well. I think most companies have problems because they give the
>Sys Admin a reporting structure that does not include the DBA.
>This encourages a rivalry that should not exist.
 

>--
>Paul Collins
>DBA
>DATASTORM Technologies

A problem that I am seeing now is that a lot of the companies in Canada are considering outsourceing. Sometimes the DBA stays in house and the Sys Adm is part of the outsource deal (I have this problem now at two of my clients). The outsource company is extremely stingy with root access. The disaster occurs when the Sys Adm people (who shall remain nameless) often aren't great at the job (this cuts costs for the outsource group. YES it is extremely short sighted, but then again that is the way money works in the short term).

So when Logical Vol Management is needed, (or any other obvious short commings are seen) there are real delays. I just see this situation getting worse.

Jeff
Toronto, Canada Received on Thu Oct 05 1995 - 00:00:00 CET