In order to check automatically if there are differences between the base views in Denodo and the tables in the underlying databases, I use the GET\_SOURCE\_CHANGES and GET\_VIEWS procedures in Denodo.
The GET\_SOURCE\_CHANGES procedure returns information about differences between Denodo views and the associated table in the underlying data source. I can use the GET\_VIEWS procedure in conjunction with the GET\_SOURCE\_CHANGES procedure to execute the procedure on all of my views. For more information about these stored procedures, you can reference the [GET\_SOURCE\_CHANGES](https://community.denodo.com/docs/html/browse/latest/vdp/vql/stored_procedures/predefined_stored_procedures/get_source_changes#get-source-changes) and [GET\_VIEWS](https://community.denodo.com/docs/html/browse/latest/vdp/vql/stored_procedures/predefined_stored_procedures/get_views#get-views) sections of the Virtual DataPort VQL Guide.
If I am worried about changes occurring regularly in the underlying data sources in my scenario, I usually configure a Scheduler job to routinely run my GET\_SOURCE\_CHANGES and GET\_VIEWS query. In the Scheduler job, I filter out results where the modification column is an empty string and do not export results when no columns are returned. Then, I can configure a mail handler to send me an email every time a file is exported, which means that a change was detected in the underlying data source.
I hope this helps!