Tables in SAP HANA are automatically compressed to enable you to store huge amounts ofdata within very little space.Further data footprint reductions are achieved because we removed huge numbers of tablesthat are not needed, as well as unnecessary indexes.We can go further and reduce the in-memory data footprint by implementing data agingstrategies. SAP HANA can split data across an in-memory tier (we call this HOT storage) and a disk-based tier (we call this WARM storage). All processing and database services are held in common. This means a developer does not need to know where the data is physically located, as this is handled internally by SAP HANA. The benefit of this is that data that is used less frequently can be moved automatically from HOT to WARM storage, so you are not filling memory with data that is less useful. However, this data is still available whenever it is needed.Compression from HANA, simplification of app redesign, and data aging using tiering adds up to less replication, less network load, and earlier restart over failover.