To keep response times down where the users like it. Despite
the best efforts of the DBA and ABAP groups, many of
SAP's queries end up doing FTSs, and an FTS on our largest
table (40+GB) takes too long for the users.
SAP's archiving strategy actually does not remove the data
from user accessibility. Archived data is stored in a large
flat file of proprietary design, and can be stored on slow
JBoD or DVD storage. Users understand that access to data=20
that's over two or three years old (depends on the data)
will be slow, and they can accept that. Everything else
is now! now! now!
Cheers,
Mike
-----Original Message-----
From: Jared.Still_at_radisys.com
Sent: Thursday, August 26, 2004 10:10 AM
To: oracle-l_at_freelists.org
Subject: RE: LiveReorg vs Oracle's online reorg capabilities
It helps us!
=20
We use LiveReorg on our SAP system. We have an active archival/delete
process that purges older data. By reorging we recover space that
we can redeploy, and index reorgs regain space and speed.
=20
Which brings up another question: Why are you archiving data?=20
We use LiveReorg on our SAP system. We have an active archival/delete
process that purges older data. By reorging we recover space that
we can redeploy, and index reorgs regain space and speed.
=20
Jared
Please see the official ORACLE-L FAQ: http://www.orafaq.com
To unsubscribe send email to: oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
