Domain separation and IDR
-
- UpdatedJan 30, 2025
- 1 minute read
- Yokohama
- Instance Data Replication
Instance Data Replication (IDR) functions at the data level, which means it does not explicitly support domain separation.
For a typical use case, data moves from a producer instance to a consumer instance and back without regard to which domain the instance is in. You can use IDR to filter data, enabling you to segregate specific data between instances. If you must go beyond the IDR record-level filtering capability, you can use business rules to convert data from one domain to another. For more information, see Before Query business rules.
Related Content
- Data privacy in Instance Data Replication
The ability of replication sets to host multiple remote consumers in Instance Data Replication (IDR) means that there are potential data privacy issues to consider.
- Adapter descriptions for Instance Data Replication
Adapters modify the producer data before inserting the data on consumer instances in Instance Data Replication (IDR).
- Excluded tables in Instance Data Replication
You can't replicate certain tables in Instance Data Replication (IDR). Child tables of tables in the exclusion list are also excluded.
- Instance Data Replication properties
These system properties control the behavior of the Instance Data Replication (IDR) application.
- Instance Data Replication roles
Instance Data Replication (IDR) is installed with these roles.