RE: SQL *Net more data from client

From: Powell, Mark D <mark.powell_at_eds.com>
Date: Tue, 9 Jan 2007 14:28:59 -0500
Message-ID: <D1DC33E67722D54A93F05F702C99E2A95E45BF@usahm208.amer.corp.eds.com>

Problems with the application are often the DBA's problem since a poorly designed/written/implemented application can impact the entire database work load. This in turn makes it the DBA's problem. A DBA needs to point out bad practice or code where he or she sees it to protect the database as much as possible. Sometimes no "fix" is going to be forthcoming. Sometimes you might get one down the road. And once or twice in your lifetime you might even get a immediate positive response. Maybe, but I agree with Niall, you need to take responsibility for trying to make things better.

Mark D Powell -- Phone (313) 592-5148

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Niall Litchfield

	Sent: Tuesday, January 09, 2007 1:55 PM
	To: Kerber, Andrew
	Cc: dd.yakkali_at_gmail.com; oracle-l_at_freelists.org
	Subject: Re: SQL *Net more data from client - waiting too long
	
	
	On 1/9/07, Kerber, Andrew <Andrew.Kerber_at_umb.com> 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?

	-- 
	Niall Litchfield
	Oracle DBA
	http://www.orawin.info

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Jan 09 2007 - 13:28:59 CST

RE: SQL *Net more data from client - waiting too long