Using the various types of verification in ADWB

I have noticed in the dropdown menu for verification that there are two options ‘Read & Write Verification’ and ‘Forward Engineering Verification’.

What is the difference between these two options and how are they beneficial in term of building a data warehouse?

Astera DWBuilder has two built-in verification options to help users correct their models during design time: ‘Verify for Read and Write Deployment’ and ‘Verify for Forward Engineering’.

The default verification is set to ‘Verify for Read and Write Deployment’. This type checks whether or not the model is ready for deployment. It compares the database and the data model to see whether or not they are in sync. Any differences, for example, the data type (as shown in the screenshot below) are detected by this verification.

The ‘Verify for Forward Engineering’, on the other hand, checks whether the changes made to the model after it was reverse engineered are ready to be reflected onto the database. This verification option also checks whether the rules for database are violated. For example, indexes with the same name defined for a particular entity will give the error as shown in the below screenshot.

Any errors detected in either type of verification need to be fixed before you can deploy the model.