Replace SIFT tables with materialised views

well there's a thing - I see indexed views will replace sift tables in the next version of Navision.

the usual impact of indexed views is that the data is materialised, but as they will replace physical tables that factor doesn't come into play. You're confusing the use of indexed views for tuning - if you call the view in std edition directly then it will be referenced - to explain my comment it has been a long established fact that to create extra clustered indexes on a table you can create an indexed view, or views, in enterprise edition the query against the base table will use the indexed view instead of the table - the downside was you duplicated data to get your performance gain - using indexed views to replace the SIFT tables is slightly different.
Getting rid of all those triggers will likely give a 10 - 20 % performance boost out of the box. SQL DBA's know that the easiest way to destroy performance is to put triggers on tables - especially large ones which encroach upon the mem to leave area. Now if they'd just get rid of the cursors !!!