Before taking the new repository online, it's required to check the validity of the repository. There's a tool named Consistency Check Manager that is used to validate this repository.
Whenever you want to save your repository, it's going to ask you if you want to check global consistency or not.
We can also trigger this from the File menu.
The Consistency Check Manager tool is going to check the validity of the repository. For example, if the business model is still marked as
Disabled, it may tell you that the business model is consistent.
We have to be sure about the validity, otherwise when we try to upload it to the server, it's going to generate errors and we won't be able to start the BI server service. If you see a message as shown in the following screenshot, it means the repository is consistent.
We can easily simulate an error by deleting the entire subject area from the Presentation layer, starting the Consistency Check Manager tool and seeing the result. It'll give an error about the missing subject area. In this case, the rule that applies is that every business model should be mapped to at least one subject area. Otherwise that business model is not consistent.
The last step before loading the repository to the BI server is to check the server for consistency. Checking the consistency is a step that cannot be skipped. It's always recommended. It's going to check for missing or broken references. So, in every change, we'll have to start the Consistency Check Manager tool and see whether there's any inconsistency or not. If you don't check it and try to load the new repository to the BI server and if it's in an inconsistent state, the BI server is going to generate an error and will not start up.