I'm actually on holiday next week so won't be able to see response, but I was just wondering if anyone had tried comparing the performance of a physical SIFT tables vs a materialised view - I figure the maintenence overhead would be much lower.
Just a thought.
0
Comments
The problem with materialized views is that some data can be potentially out-of-date.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Indexed views can be created and used in any SQL edition but only Enterprise will consider them in query plans. With the other editions they must be explicitly called.
Developer must decide on the trade-off between updating the indexed view each time the underlying data is changed vs. producing the view on the fly (normal view)
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
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 !!!
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Ah, ok, my misunderstanding - I understood it that they (MS) are changing plan to replace SIFT by indexed views... 8)
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.