U

4 Messages

 • 

1.1K Points

Saturday, April 20th, 2024 2:18 AM

Moving Physical Data Dictionary Domain (which has Schema under it) to a Sub-community - Will this have an impact on the current integration

Hi. I'm new to Collibra and I'm helping our organization improve its current platform.

Our current Data structure is:

Top Community 

     >Community

          >Physical Data Dictionary (Domain) > Schema (Asset).

We would like to add a Sub Communities to segment the different databases that we have and more the domains which contains the schema under it to show the hierarchy similar to our database setup. It will be like this:

Top Community

    > Community

          > Sub-Community 1

               >Physical Data Dictionary (Domain) > Schema (Asset)

           > Sub-Community 2

              >Physical Data Dictionary (Domain) > Schema (Asset)

Will this affect any integration and sync configuration we have currently set up?

14 Messages

 • 

705 Points

11 days ago

I moved it couple of time and it work perfectly. When synchronizing the schemas if we select the default schema rule then it will create a physical data dictionary under the domain where you create database asset, and I moved it under different domain and I also tried to refresh after moving it and it worked for me.

4 Messages

 • 

1.1K Points

@lhakpa_sherpa​ Hi. Thanks for the reply. Another question tho, when synchronizing schema, is it best practice to use default rule or should I change it to target domain if I already set up a specific domain prior?

24 Messages

 • 

955 Points

Generally it should be fine ... it only cares about domain-id and asset-id, not where 'stuff' lives

Loading...