Re: Accessing 2 tables with 1 name

Brian, I am curious why you felt you needed to this since, with full transactional support built into the Oracle database engine, refreshing data by a process need not be seen by other reading processes, until it commits its new information.

But perhaps I am missing something; perhaps that would have been too much load on Oracle's rollback segments, and you had insufficient storage and physical hardware to make sufficient use of this Oracle feature? I'm not sure, just curious, that's all.

Phil

"Brian Peasland" <oracle_dba_at_remove_spam.peasland.com> wrote in message news:3F033B89.B6995D40_at_remove_spam.peasland.com...
> We did this exact thing before Materialized Views came into existence.
> We would preaggregate data into a table to aid in searching. We would
> have two such tables to perform a "refresh" operation on one while the
> application read from the other. The synonym pointed to the correct
> table and was moved to the new table after the refresh was complete.
>
> HTH,
> Brian
>
> Mark Perrault wrote:
> >
> > Thanks for the advice.
> >
> > The reason I have 2 identical tables is that I load 1 while using the
> > other and then simply update the State table to "point" to the new
> > data.
> >
> > After some testing, I've chosen to use synonyms to solve my problem.
> >
> > Now I load the "inactive" table, update the State table, and then
> > execute a stored procedure that creates a public synonym to the new
> > active table.
> >
> > Thanks again for the advice.
> >
> > Mark
>
> --
> ===================================================================
>
> Brian Peasland
> oracle_dba_at_remove_spam.peasland.com
>
> Remove the "remove_spam." from the email address to email me.
>
>
> "I can give it to you cheap, quick, and good. Now pick two out of
> the three"
Received on Fri Jul 04 2003 - 13:41:14 CDT