• Deletes and updates should be avoided.

    Use partitions for your fact tables and apply partition switching instead of deleting data.

    Then you can consider creating a clustered columnstore index cos I think with the amount of rows added and deleted, you will have large deltastore if you do it directly on the table.

    If you are partition switching, you won't need to rebuild the entire table everytime you have a dataload.

    Catch-all queries done right [/url]
    Gail Shaw's Performance Blog[/url]