From owner-freebsd-database@FreeBSD.ORG Thu Sep 18 05:46:20 2003 Return-Path: Delivered-To: freebsd-database@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D23B816A4B3; Thu, 18 Sep 2003 05:46:20 -0700 (PDT) Received: from mta8.adelphia.net (mta8.adelphia.net [68.168.78.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A64343FBF; Thu, 18 Sep 2003 05:46:19 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([24.53.179.151]) by mta8.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20030918124620.BUCO14799.mta8.adelphia.net@potentialtech.com>; Thu, 18 Sep 2003 08:46:20 -0400 Message-ID: <3F69A91A.60100@potentialtech.com> Date: Thu, 18 Sep 2003 08:46:18 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Supote Leelasupphakorn References: <20030918110851.55151.qmail@web40611.mail.yahoo.com> In-Reply-To: <20030918110851.55151.qmail@web40611.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-database@freebsd.org cc: freebsd-questions@freebsd.org cc: FreeBSD-Chat@FreeBSD.org Subject: Re: How DBA solved overload problem ? X-BeenThere: freebsd-database@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Database use and development under FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 12:46:21 -0000 Supote Leelasupphakorn wrote: > To all, > > As a newly DBA, I really don't know how I deal with > this problem. My problem is not so long ago, my database > server seem to overloaded. It take me a time to find > the cause of problem. I realize that some program don't > queried wiht inappropriated SQL statement. I mean they're > not efficient one. > > AS DBA how do you solved this problem? You're hitting up against, what I feel is one of the most common and most difficult to solve problems out there. The best solution is to fix the SQL statements. Unfortunately, it's quite possible that you won't be able to fix the application that's causing the problem, becuase it's closed-source and written by someone else. At that point, you're up against the frustrating chore of convincing the application designer to fix their lousy code, which is often impossible. In the end, it seems that most people end up buying faster, more expensive hardware to make up for lousy application design. It's a damn shame, but that's what seems to happen a lot. -- Bill Moran Potential Technologies http://www.potentialtech.com