You can translate the question and the replies:

Base view deployed even though table not present in database

Hello team, We are deploying a view created from A database from A environment to B environment. When deployed a view from A to B we found that the table was not present in the database B yet the view was deployed. we got to know that table was not present in database B after deployment. It will become tedious in future to check the tables in both the databases and deploy thousands of tables. Ideally Denodo should have checked whether the table exists(if not, do we have an explanation for this?).

1 Answer

Hi, By saying table, I am assuming that you mean the data source and/or base view that does not exist on the target system when you are trying to promote view without dependencies. If you are trying to import views through VQL scripts, then you should get an error in case any dependencies are not present in the target environment. Similarly, if you are trying to deploy such views through Solution Manager Admin Tool, you will see errors in the ‘Deployments’ tab under ‘Promotions’. Therefore, Denodo checks whether dependencies exist in the target system or not, before promoting the VQL. To ensure all dependencies are included, check the option which enables you to export all the related dependencies before code promotion. For more information, you can refer to the [Import/Export Scripts](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/cluster_architectures_server_backup/using_the_import_export_scripts_for_backup_and_or_replication/using_the_import_export_scripts_for_backup_and_or_replication) and [Promotions using Solution Manager](https://community.denodo.com/docs/html/browse/7.0/solution_manager/administration/promotions/promotions) documents. Hope this helps!
Denodo Team
27-03-2020 12:22:06 -0400
You must sign in to add an answer. If you do not have an account, you can register here