10 Times ( Oracle caching component )

[roadwarriorDBA]

Has anybody ever heard of it? I am told it was purchased by Oracle and that I should consider using it instead of a large pre-joined summary table after I put the nail in the coffin on using Materialized views for this project.

[padders]

Er... that would be "Times Ten" not "Ten Times".

Do I recall SlimDave posting a blog about testing this out or am I dreaming?

[slimdave]

Yes, but it's not got very far yet ...

So what were the reasons for rejecting the MV then?

[TimHall]

Mmmmmm. More layers, extra complexity, harder to support...

It sounds like a good idea to me. Where do I sign up?

I was under the impression that this purchase was the first step in improving the app server caching system.

Cheers

Tim...

[roadwarriorDBA]

Yes, but it's not got very far yet ...

So what were the reasons for rejecting the MV then?

Dave its reservation availability the problems with synching outweigh the gains. In fact we will leave out those aspects and just pre-join the other 20 tables and batch changes, then pre-join at night. There is nothing left for the mview to do we dont need query rewrite as we are always going against the rollup and we dont need auto synch.

[slimdave]

So you produce a precalculated result set every 24 hours or so then? And you actualy query against that during the day?