A Consistency Check ensures that the repository is in a fit state to process any queries passed through.
A "Consistency Check" is a feature of the Administration Tool that checks whether a repository has met certain requirements, such as the following:
- All logical columns are mapped directly or indirectly to one or more physical columns.
- All logical dimension tables have a logical key.
- All logical tables have a logical join relationship to another logical table.
- There are at least two logical tables in the business model: a logical fact table and a logical dimension table. Both can map to the same physical table.
- There are no circular logical join relationships.
- A subject area exists for the business model.
You can check consistency for the entire repository or for a single object:
For the entire repository: select File > Check Global Consistency. or Tools > Show Consistency Checker.
For an individual repository object: select the object, right-click and select Check Consistency. You can select multiple objects and check their consistency.
When you check in changes to a repository you are also prompted to Check Consistency before saving, this however is for the entire repository. A large repository can take some time to complete a check.
It is good practise to keep checking consistency in the local area you are working and making changes. You may even notice that the consistency checker has reported no errors but has 'fixed' some inner workings. It may be worth digging in to what is actually being adjusted automatically to suit what the consistency checker expects. If anyone knows please drop me a line.
It is good practise to keep checking consistency in the local area you are working and making changes. You may even notice that the consistency checker has reported no errors but has 'fixed' some inner workings. It may be worth digging in to what is actually being adjusted automatically to suit what the consistency checker expects. If anyone knows please drop me a line.
