https://community.qlik.com/t5/Data-Movement-Streaming/Adding-a-new-table-to-Landing-Task-forces-full-recreation-of-all/m-p/2551049#M3675 <P>Hi everyone,</P><P>We are currently migrating to Qlik Cloud Capacity and building our data pipelines using Data Integration. Our source is Oracle, connected via Data Movement Gateway version 2025.11.23.</P><P>Every time we add a new table to an existing Landing task, the entire pipeline seems to recreate all QVDs from scratch — not just the newly added table. This takes over 2 hours, during which our end users cannot access any of the dashboards that depend on those QVDs.</P><P><BR />We are aware that since the September 2024 update, only the affected/changed tables should be dropped and recreated after a metadata change, not all tables. Given that we are on gateway version 2025.11.23, we expected this behavior to be in place.</P><P>Some quastions:&nbsp;<BR />- Is using "Recreate tables" after adding a new table the wrong approach? Should we just use "Run" or "Reload tables" instead?<BR />- Is there a way to add a new table to an existing Landing task without triggering a full reload of all existing tables and downstream QVDs?<BR />- Has anyone experienced this and found a reliable workaround?</P><P>Any guidance would be greatly appreciated. Thanks in advance!</P> Wed, 10 Jun 2026 13:34:28 GMT MigueldelCampo 2026-06-10T13:34:28Z https://community.qlik.com/t5/Data-Movement-Streaming/Adding-a-new-table-to-Landing-Task-forces-full-recreation-of-all/m-p/2551049#M3675 <P>Hi everyone,</P><P>We are currently migrating to Qlik Cloud Capacity and building our data pipelines using Data Integration. Our source is Oracle, connected via Data Movement Gateway version 2025.11.23.</P><P>Every time we add a new table to an existing Landing task, the entire pipeline seems to recreate all QVDs from scratch — not just the newly added table. This takes over 2 hours, during which our end users cannot access any of the dashboards that depend on those QVDs.</P><P><BR />We are aware that since the September 2024 update, only the affected/changed tables should be dropped and recreated after a metadata change, not all tables. Given that we are on gateway version 2025.11.23, we expected this behavior to be in place.</P><P>Some quastions:&nbsp;<BR />- Is using "Recreate tables" after adding a new table the wrong approach? Should we just use "Run" or "Reload tables" instead?<BR />- Is there a way to add a new table to an existing Landing task without triggering a full reload of all existing tables and downstream QVDs?<BR />- Has anyone experienced this and found a reliable workaround?</P><P>Any guidance would be greatly appreciated. Thanks in advance!</P> Wed, 10 Jun 2026 13:34:28 GMT https://community.qlik.com/t5/Data-Movement-Streaming/Adding-a-new-table-to-Landing-Task-forces-full-recreation-of-all/m-p/2551049#M3675 MigueldelCampo 2026-06-10T13:34:28Z