Re: SQL *Net more data from client - waiting too long
- From: Andrey Kriushin <Andrey.Kriushin@xxxxxxxx>
- To: niall.litchfield@xxxxxxxxx
- Date: Wed, 10 Jan 2007 19:53:36 +0300
I'm with you, Niall and other persons with similar view on the DBA role.
The difference is that I and my colleagues are not a production DBAs,
but rather an external consultants. Actually we are more close to local
DBAs. Definitely we are paid for "keeping things running". Most of the
clients see our role not only in providing qualified (well, at least
above the average) support for their business-critical databases/apps,
but also as a kind of "judges" particularly when the 3-rd party software
providers are involved.
Well, that's the only place thus far (a semi-political activities) where
I've found the OCM label quite useful :-)
--Andrey
Niall Litchfield wrote:
On 1/9/07, *Kerber, Andrew* <Andrew.Kerber@xxxxxxx
<mailto:Andrew.Kerber@xxxxxxx>> wrote:
It also means its not a problem w/ Oracle, it's a problem with the
application.
Absolutely not picking on Andrew here, since this and some of the
implications are a common view, but am I the only one to think that
the distinction is somewhat false. Technically a bad app is not my
problem as a DBA, but professionally and in reality I view it as my
problem to diagnose, report and offer solution with applications. In
other words I see application level design and performance problems as
part of my purview. What do others think?
Other related posts:
