Table-internal sync without a Primary Key and index at rule creation

KVM

What happens when a Table-internal sync rule is created when the table does not have a primary key (join columns indicator is red) at rule creation but a primary key is added during masking with a command rule? 

PlantBasedSQL

Hi @KVM thank you for your post!

When you say "What happens...?" are you expecting or wanting something to happen specifically?

When the join column shows as red this is just a warning that because you're using an un-indexed join column performance of the rule will be poor(er), however if you add a PK using a command rule and then refresh Data Maskers understanding of the indexes during the run, the Table-Internal rule will run as designed and it should perform well.

So effectively... it just works is my answer

I hope this helps, if you have any other questions or concerns about this please let me know - happy to help out further! Thanks and kind regards!