To age data in the solidDB® frontend, you use SQL statements to first set the data capture mode to a state where deletes are not propagated to the backend, and then delete the rows with the obsolete or unnecessary data. After you have deleted the data, you can change the data capture mode in the solidDB® server to allow propagation of data normally.
Before you begin
To use data aging, you need to have your Universal Cache environoment up and running.
It is assumed that there are no subscriptions from the backend to the frontend, or, the subscriptions and table mappings are designed in such a way that there is no risk of returning aged data from the backend to the frontend.
Procedure
1 Set the data capture mode to DELETE CAPTURE NONE.
To enable data aging for the session, issue the following command:
SET DELETE CAPTURE NONE
To enable data aging for the next transaction, issue the following command:
SET TRANSACTION DELETE CAPTURE NONE
2 Drop (delete) the rows with the obsolete data.
3 Disable data aging by setting the data capture mode to DELETE CAPTURE CHANGES.
To disable data aging for the session, issue the following command:
SET DELETE CAPTURE CHANGES
If you used the SET TRANSACTION DELETE CAPTURE NONE statement, the mode is changed back to DELETE CAPTURE CHANGES after you have committed your transaction.