"Egruno" <egruno_at_dk.snt.com> wrote in message news:<3c67b144$0$247$d40e179e_at_nntp02.dk.telia.net>...
> Check this scenario.
> I have access to our CTI system i am not allowed to mess around with it, i
> created a table to be able to cache for the CTI system data so that i could
> change the data etc.
> The problem(?) is that i have to update the "cachetable" very frequently do
> be uptodate, how is this done with out making dups? there are no primaykeys.
>
> Best regards.
> Emil Gruno.
Emil, I think you might consider using a materialized view of the base
table set to update with every commit OR you could place an insert
trigger on the table and capture every insert. But with either method
you are duplicating the data and will consume space.
Received on Mon Feb 11 2002 - 08:31:13 CST
