Only add/alter indexes on related tables instead of drop-create tables

When adding or modifying lookups it triggers a change of indexes on the related table if automatic indexes are enabled. If a table is not a history/incremental table it will drop it and recreate the table with the new indexes. It would be better if it would only drop and recreate the index instead of dropping and therefore emptying the table.

Also, it would be good to know when deploying changed tables that a checkmark for the deployment of a valid table is only to modify indexes and nothing else.


Please sign in to leave a comment.