![sap hana studio how to delete an index sap hana studio how to delete an index](https://community.esri.com/legacyfs/online/420890_pastedImage_5.png)
If it is a huge table (like tens or hundred of GB) then OOM situations could appear. For example, if I execute a SELECT * FROM TABLE and I have enough memory that table will be fully load into memory in case it wasn’t. This could happen because explicit access, explicit load, index load/recreation after optimize 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.
![sap hana studio how to delete an index sap hana studio how to delete an index](https://cloud.google.com/solutions/sap/docs/images/hana-studio-scaleout-landscape.png)
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. If you are reading this you probably know that SAP HANA stores data on a persistence layer (data and logs). Most of them are really easy to follow and it won’t take you a lot of time.
Sap hana studio how to delete an index series#
The main idea with this post series is to give you a list of best practices and recommendations that you can follow so you will avoid issues and problems in the future. It seems that there are some basic best practices that nobody follows… Maybe because they are not known by most of the SAP Basis Admins or because people is lazy, who knows. The idea popped up in my mind a few weeks ago when I was checking a SAP HANA databases from several of my customers.
![sap hana studio how to delete an index sap hana studio how to delete an index](https://blogs.sap.com/wp-content/uploads/2014/12/reptask0_604898.png)
I decided to start a series of post related to SAP HANA Best Practices.