Abhinav, one common pattern is to use VDBs from VDBs.
You will create your first VDB as a full copy, and use the hook to remove the older data. From there, you create VDBs from that VDB for all your teams, to rapidly provide them with their own copy and you don't have to do the hook again.
You can leverage this same pattern to inject synthetic test data, compress, encrypt, mask, or even upgrade the DB. Basically you want to do all the work once to create your non-prod copy, and then distribute it many times.
You can even begin to create a new "first VDB" (some call this the Gold Copy) while users continue to use copies of the old one. That way, if the transformations from prod to Gold take a while, you can do that in the background while users work. Simply refresh the Gold copy and transform it while the downstream VDBs continue as normal. Note that you'll need additional disk space for that model, since your users will be leveraging the old blocks until they refresh.
------------------------------
Ranzo Taylor
Technical Services Director
Delphix
------------------------------
Original Message:
Sent: 04-16-2020 04:22:28 AM
From: Abhinav Chandra
Subject: VDB provision with limited data
Hi,
Could you please help me in provisioning a VDB with only limited data. To explain further lets suppose we have a dSource with data from last 1 year and daily new data are flowing in. Now i want to provision a VDB with only data that has been inserted from last 2 months. I do not want to have data in the VDB older than 2 months. How it can be achieved?
One method is using hook, run a script to purge old data before provision? Is there any other way??
------------------------------
Abhinav Chandra
Team Leader
Accenture
------------------------------