Let's imagine basis on which the day data every day is flooded. Thus if the data the certain period is there can be a week, month, year they do not participate in current processes in any way. Certainly, all of them are equally stored - for history, "just in case", etc.
And now we present that we want for UAT/SIT/DEV to catch copies . Certainly "the old" data there is not necessary to us - they only take a place, extend process , etc. How to organize data storage and to take only "the actual" data?
Well, for example, the most simple decision which comes to mind - for each table on to create its copy ARCH_ the table in other , to organize automatic process of data migration in ARCH_ labels, and at to specify to pass this .
The decision for certain works, but is too labor-consuming and is ugly.
Other method: we store in other only partitions. Then copies of tables are not necessary, but I did not try and I do not know - whether the basis if at to pass opens UAT, and there are tables at which there are these partitions in it . Or all will be normal?
But for certain there are any other methods which to me simply do not come to mind - experience shows that many people can have set of judgements.