Our organization makes extensive use of validation attribute rules to ensure data integrity and that all attributes in our data adheres to our core business logic. Our workflow is to evaluate rules just before we reconcile and post to default. We also have a custom reconcile and post tool that checks the validation status of the features modified in the version and ensures that all features have been validated and have no errors. To ensure we validate all our data properly, our workflow when we evaluate rules is to validate the full extent of the data, but only features that have been modified in this version.
Through the capture of various Database logfiles, we have determined that the evaluate rules tool will start by creating selection sets of the features it needs to validate - BUT, the tool creates selection sets of all features modified in this version, when in reality, it would be so much faster to create selection sets of all features modified in this version that have a validation attribute rule.
Currently, the tool is creating selections on about 4000 features that don't even have a validation attribute rule present. There is nothing to evaluate against these features so why create selection sets for them? This is extremely inefficient and slows the tool down significantly.
Could you please consider enhancing the Evaluate Rules tool so that it only creates selection sets against features that have a validation rule present?
