Re: A 'snapshot' of table data

Stephen Bell wrote:

> Hello all,
>
> I have a requirement to be able to present an image of a table's data at
> a specific point in time..this point in time would be determined by the
> user...i.e. after they complete certain procedural requirements, they
> would "freeze" the table (from their perspective)..the actual table
> would still be open for transactions but we would need a snapshot of the
> table at the point in time it was requested.
>
> There could be several times when the user might do this while
> interacting with the application so I don't want an indefinite number of
> table copies floating around...the real table and it's copies would
> reside on the same server so the issue seems different from using oracle
> snapshots..would temporary tables be the way to go?
>
> I hope I explained this with some clarity....let me know if
> not....thanks in advance for any ideas.
> Steve

The answer to your question is contained within your Subject line. Use a snapshot, also known as a materialized view, and give the end-users the ability to refresh it.

Daniel A. Morgan Received on Fri May 25 2001 - 01:41:25 CDT