You can read a lot about LOAD/UNLOAD operations in SAP HANA in the SAP Note 2127458 – FAQ: SAP HANA Loads and Unloads. A high number of loads/unloads could affect the performance of the system since the database have to bring the table/columns before the process using it can access it. For example, when the SAP HANA database runs low on memory, on MERGE/SHRINK situations or when the UNLOAD of the table was explicit. On the contrary, HANA unloads tables from memory in certain situations.
![my data.spdata could not be saved stock pro my data.spdata could not be saved stock pro](https://images-na.ssl-images-amazon.com/images/I/51qpoeehxFL._SX372_BO1,204,203,200_.jpg)
If it is a huge table (like tens or hundreds of GB) then OOM situations could appear.
![my data.spdata could not be saved stock pro my data.spdata could not be saved stock pro](https://caymaneco.org/yahoo_site_admin/assets/images/Bolsonaro.239114347_std.jpg)
For example, if I execute a SELECT * FROM TABLE and I have enough memory that table will be fully loaded into memory in case it wasn’t. This could happen because of explicit access, explicit load, index load/recreation after optimizing compression, etc. The SAP HANA database will load tables and columns into memory when those are required. It is also possible to enable the PRELOAD flag just for some columns of the table. Only those tables that have the PRELOAD flag enabled will be loaded into the memory. Not all the data is loaded into the memory at this moment. When you start your database the data is loaded into the physical memory. SAP HANA stores data on a persistence layer (data and logs). A spare system always brings down costs at the time of SAP migration.
#My data.spdata could not be saved stock pro archive
Therefore, one needs to create a plan to archive old, not often used data that is not critical to on-going real-time operations. Any data that is seldom used should be archived to have a good performance for SAP HANA. >Data supposed to grow will be a certain intrinsic value.
![my data.spdata could not be saved stock pro my data.spdata could not be saved stock pro](https://venturebeat.com/wp-content/uploads/2020/03/4.png)
>SAP Charges on HANA based on volume: The more data you’ve got to process, the more expensive it’s going to be. There are several reasons why this is a best practice to implement now: With the larger size of structured and unstructured data, the need to archive SAP data is very critical but not often discussed best practice. One such best practice is the archiving of SAP data before the migration. While building the business case for such migration, we need to most definitely consider implementing some proven best practices to bring down the overall cost of such migration. As data volumes and size is growing exponentially, customers/corporate ITs are now in various stages of considering migrating to SAP on HANA. SAP HANA (In fact Any DB which implies with SAP), SAP’s in-memory database system is extremely rich in features and has the capacity to process several terabytes of data without a sweat.