Leveraging table partitioning

Loading even very large fact tables is not a problem if you can perform incremental loads. However, this means that data in the source should never be updated or deleted; data should only be inserted. This is rarely the case with LOB applications. In addition, even if you have the possibility of performing an incremental load, you should have a parameterized Extract- Transform-Load (ETL) procedure in place so you can reload portions of data loaded already in earlier loads. There is always the possibility that something might go wrong in the source system, which means that you will have to reload historical data. This reloading will require you to delete part of the data from your DW.

Deleting large portions of ...

Get SQL Server 2017 Developer's Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.