Re: Yes, this is probably a stupid question but...

From: Pat <>
Date: Sun, 13 Apr 2008 12:54:45 -0700 (PDT)
Message-ID: <>

On Apr 13, 11:20 am, hpuxrac <> wrote:
> On Apr 12, 5:55 pm, Pat <> wrote:
> Another option to consider is looking at is using/creating a
> materialized view to support the count query.
> Going down the posts in the other part of this thread, if you force
> the count query to use a hash join, this might help the queries that
> return a high count ( 200k ) but could ( possibly severely ) impact
> the queries that ( running now with a nested loop ) return a small
> count.

I'm going to show my ignorance here, but would a materialized view help if there's a lot of transactional volume on the table e.g. if there are, say, 500 or so updates per hour across that table? Wouldn't I need to refresh the view every few seconds to keep it current? Or is this the part I'm missing? Received on Sun Apr 13 2008 - 14:54:45 CDT

Original text of this message