...
The data model includes three tables:
| Table | Description |
|---|---|
ValidationRun | This table shows the status of runs. It will have one row for each time the validation engine is started. This should evolve into a community standard. |
ValidationResults | This table has all of the validation results. This is the data that would be consumed by the SIS via the API. This table has a foreign key that ties it back to the validation run. This table should also evolve into a community standard. |
ValidationRules | This is a table that has the SQL that produces validation results. This is what drives the T-SQL validation engine, and should serve as a starting point and example. This would NOT evolve into a community standard - different organizations could implement this functionality in their preferred technology. |
Processing Logic
The prototype includes a stored procedure, RunValidationRules, that will iterate through all of the rules in the ValidationRule table for a given ValidationRuleSet and populate the results into the API tables. When called with a ValidationRuleSet it does:
...