Its the same when you modify normal index. When you save a table with modified SIFT definition corresponding SIFT view is dropped and recreated, along with clustered index on it.
Same happens when you import a fob with table defnition having different SIFT index structure than existing table.
In NAV 2015 / 2016 update occurs when you synchronise changes with tenant databases.
Later on SQL internally keeps clustered index on SIFT view updated. This is happenning as a part of any insert/modify/update operation which touches any record included in the view.
Comments
Same happens when you import a fob with table defnition having different SIFT index structure than existing table.
In NAV 2015 / 2016 update occurs when you synchronise changes with tenant databases.
Later on SQL internally keeps clustered index on SIFT view updated. This is happenning as a part of any insert/modify/update operation which touches any record included in the view.
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03