On Tue, 06 Nov 2007, damorgan_at_psoug.org wrote:
> Galen Boyer wrote:
>> On Tue, 06 Nov 2007, damorgan_at_psoug.org wrote:
>>> Hasta wrote:
>>>> In article <1194284665.769857_at_bubbleator.drizzle.com>,
>>>> damorgan_at_psoug.org says...
>>>>> Hasta wrote:
>>>>>> In article <1194206398.972648_at_bubbleator.drizzle.com>,
>>>>>> damorgan_at_psoug.org says...
>>>>>>> My point was that while the developers here seemed more than
>>>>>>> willing to point fingers at incompetent DBAs from my experience
>>>>>>> the developers are equally guilty of not keeping their skills
>>>>>>> current. Not more so ... equally so.
>>>>>> Well, honnestly, I haven't seen a lot of developpers in this
>>>>>> group claiming that dbas are generally incompetent.
>>>>>>
>>>>>> I have seen them claiming that a dba is unlikely to find the
>>>>>> root cause of an application problem alone, for reasons that
>>>>>> are very understandable and unrelated to his/her competency.
>>>>> You are dissembling. Identifying root causes on a production
>>>>> server is a core competency of the DBA job in the vast majority of
>>>>> organizations.
>>>> A good dba can certainly find one cause in the causal chain.
>>>> However, he does not know the specifications of the components
>>>> of the system. Without a specification, he cannot identify with
>>>> certaincy the root component that is misbehaving.
>>> Then he or she is incompetent and should be trained or replaced.
>> So, while this replacement is considered, how is the problem to
>> be
>> figured out?
>
> If you can't figure out how to get a qualified DBA in one hour
> contact me. I can get you one in that much time during normal
> business hours.
The management that does the hiring does not know Daniel Morgan. They
have a problem they want solved. What exactly are they supposed to do
again?
--
Galen Boyer
Received on Sat Nov 10 2007 - 12:04:02 CST
