Data retention or archiving strategy
Date: Sun, 26 Nov 2023 10:34:06 +0530
Message-ID: <CAEzWdqeLCTu4Q8d9nr7L9_1+ifspt=avJjdaFgNHLvq+8Z_AVA_at_mail.gmail.com>
Hello Listers,
We have a requirement to selectively set the retention period of the application data. And the data should be in a queryable state.
As because in normal database backup where the backup gets stored compressed in the cheap storage like tape etc for a certain retention period as per business requirement, they are not in an immediate queryable state.
In case we need those data, they(those backups) have to be first moved and restored to a database servers and then they will be in a state to be queried back and that takes a lot of time normally. Also we may need to just query data from few selected table but not all. So the requirement is to store the selective data in a queryable state and that to also in cheap storage.
So the firm is using a cheap storage called neptune and asking us to move the selective data to that location. So teams suggesting to have the selective data from multiple databases first moves to a JSON-->Clob format and that to a AQ which calls the API to move that to the neptune storage which is always queryable.
However, I want to check with the experts here if this is the right strategy or if any other option for catering such requirements exists?
Regards
Yudhi
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Nov 26 2023 - 06:04:06 CET