Path: news.easynews.com!easynews!feed.news.qwest.net!news.uswest.net.POSTED!not-for-mail
From: "Joe Smith" <jsmith@imaphost.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Re: Tuning Nightmare -  Advice Needed
References: <15e9c449e88b29dc01b5ad4bda120e52.36240@mygate.mailgate.org>
Lines: 10
Message-ID: <%HMR7.815$Nt5.89271@news.uswest.net>
Date: Wed, 12 Dec 2001 17:44:27 GMT
NNTP-Posting-Host: 63.148.99.230
X-Trace: news.uswest.net 1008179067 63.148.99.230 (Wed, 12 Dec 2001 11:44:27 CST)
NNTP-Posting-Date: Wed, 12 Dec 2001 11:44:27 CST
Xref: easynews comp.databases.oracle.server:127967
X-Received-Date: Wed, 12 Dec 2001 10:44:30 MST (news.easynews.com)

> 
> Mabey you could add a table that breaks up accounts into sizes and select what
> type of query you run by the size of account.  It could be a table something
> like:
> ACCOUNT_ID  NUMBER
> SIZE        VARCHAR2 Check ('SMALL','MED','BIG')
> The web servers could suck the rows from this table into a cache and determine
> which type of query to send to the DB by the size of the account (BIG gets the
> query with use_hash and small gets the query with use_nl or vice versa).  This
> should allow you more control than histograms and literals.