You do not need a relationship between the two tables. Relevant is to use a deterministic algorithm. Using a wrapper (as contained in UTILITY) you can extend an existing algorithm with for example a prefix/suffix or with a preserve range : as a result ...

Hi Tio: I think the below example will give more info . As i said in my earlier there is no relation between the so called master and child and no user who can access both the schemas. each schema has their own individual users who are owners of their ...

I reached out to customer success to identify who is managing your account. If there is an active engagement I will try to reach out directly and arrange a session. As stated earlier the UTILITY plugin can do what you are looking for. I assume the ID_value ...

Thank you Tino. But there are couple of constraints in our scenario. There is no single user who has access to both the schemas. so we have to use one user one schema and second there is no FK between the master and child. The client is treating them ...

As far as I know you cannot automatically handle cross-schema constraints. You need a connector, ruleset and job per schema. What you can do is use pre-scripts to drop the PK/FK constraint in both schemas, then mask them using the same deterministic uniqueness ...

we have a requirement from a client where we need to mask tables from 2 schemas. parent is in one schema and child is in another. both schema belong to same database. both schemas have different users having access ONLY to their schemas. user of child ...