Eight tables. Size depends on the table and the time of day. I don't think
all tables get complete data turnover at this rate, but I've not had the
time to check with the Q continuum to verify. I know that the data in all
the tables is super volatile. We (i.e. me) got stuck with the chore of
coming up with an automated process for the indexes, the app is far from
being a "stabilized" app, so hard-coding stuff for each table is a bad idea,
so everyone agreed that any indexes in tablespaces X and Y get rebuilt. If
you don't want to get rebuilt, don't put it in tablespace X or Y. Does that
sound like something a sys admin might say? Is that what I used to do?
P.S. WHERE(!!) did you get your font? AAAAAUUUUGGGHHHHH!
-----Original Message-----
Curious me ... how big is the table that gets 'complete turnover of data in
15 minutes' ...??
Raj
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Stephen Lee
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
