Re: Different 'priorities' when doing selects

"Jan Gelbrich" <j_gelbrich_at_westfalen-blatt.de> wrote in message news:bodkll$1ceg8g$1_at_ID-152732.news.uni-berlin.de...
> "Joe Smith" <nospam_at_nospam.com> schrieb im Newsbeitrag
> news:bodh2v$ekk$1_at_news-reader3.wanadoo.fr...
> > Hi,
> >
> > I'm using Oracle 9i. My program is doing "heavy" calculations on some
> > tables A,B, C, which require a lot of I/O, and afterwards, inserts a
value
> > in a table D.
> > It's vital to have a decent response time when accessing this table, and
> > now, when I'm in the middle of one of these calculations, I may wait for
> > more than one minute to show this D table which has no more than one
> hundred
> > elements.
> >
> > Is there any way to give a higher priority to the selections in the
table
> D?
> >
> > Thx!
> >
>
> Hi, Joe,
>
> Unfortunately You do provide almost no info to help You.
> I have no clue what You want to do.
> But from scratch I would say, based on the few infos provided,
> when You make selects as a first step to show A,B,C,D,
> why do You not simply show D first ?
> Or is it the "heavy calculations" that take so much time ?
>
> So much from my crystal ball 8}
> Jan

I'll explain it a little more :)

The tables A,B,C saves raw data, which is periodically processed (say, every hour). The calculations done (counts, joins, "correlations", etc), produce a small set of results, which is stored in the D table. This final table may be accessed for viewing the results, and I would like the select operations in this results table to be of a higher priority, so the "user experience" is better. The results being calculated may take longer to be produced, but the current results should be returned as fast as possible.

I'm a poor programmer :p who must face this beast (Oracle), so I thought that perhaps there was a way to do what I had in mind. I have somewhat optimized the SQL, but I was wondering if it was possible to apply this "priority" principle.

Thanks again. Received on Thu Nov 06 2003 - 09:32:04 CST