I am stuck on this as a matter of best practice and maybe feasability (My SQL Server knowledge is still mostly conceptual).
In the database there are often used queries that take a while to execute which makes me think that an indexed view is appropriate. However one of the tables involded sees a lot of bulk transactions. Is this problematic for perfomance with writing to both the table and the indexed view?
In looking at other posts, it seem like indexed views may bomb on aggregate functions (i.e. sum). Is that true?
In the database there are often used queries that take a while to execute which makes me think that an indexed view is appropriate. However one of the tables involded sees a lot of bulk transactions. Is this problematic for perfomance with writing to both the table and the indexed view?
In looking at other posts, it seem like indexed views may bomb on aggregate functions (i.e. sum). Is that true?