It is also possible to compress a table in SAP HANA system manually by executing the following SQL statement.UPDATE "table_name" WITH PARAMETERS ('OPTIMIZE_COMPRESSION' = 'YES')This results in deciding whether a compression is required or an existing compression can be optimized. In this scenario, HANA system uses most suitable compression algorithm.When you run the above SQL command, compression status remains the same. You can also force the database to reevaluate compression using the following SQL status UPDATE "AA_HANA11"."SHOP_FACTS" WITH PARAMETERS ('OPTIMIZE_COMPRESSION' = 'FORCE')

To check the Compression ratio for a table, you can navigate to Table Definition. Go to Runtime Information.To see Compression Ratio, go to Columns tab. You can see the compression ratio in the Main Size Compression Ratio [%] column.

In SAP HANA, you can create a Graphical Calculation view or SQL script based view. The graphical view is easy to develop and you don’t require to be an expert in SQL scripting.When you create a Calculation View, we get an option which type of view we want to create. It is recommended that you should prefer to Graphical Calculation views as you can easily achieve parallel processing and other performance benefits associated with HANA.To create a Calculation view- SQL Script or Graphical view, you have to go to a package and right click → New → Calculation ViewSelect Type ... Read More

In SAP HANA, there are various methods and algorithms that you can use to store data in Column based structure- Dictionary Compressed, Run Length Compressed and many more.In Dictionary Compressed, cells are stored in form of numbers in tables and numeral cells are always performance optimized as compared to characters.In Run length compressed, it saves the multiplier with cell value in numerical format and multiplier shows repetitive value in the table.Compression is calculated using Compression factor. Compression factor refers to the ratio of the uncompressed data size to the compressed data size in SAP HANA.In SAP HANA, Compression is performed ... Read More

You have the following Operators that can be used to define restrictions

Yes, you can define Analytic Privilege for multiple views in a single object. When you add multiple HANA views, you can find all Attributes: Select attributes to assign analytic privileges.

Yes, when an Analytic Privilege is defined you have an option of using it for a specific time period. You have an option of defining Privilege validity where you can pass validity details.You can also opt for SQL Editor or Dynamic where you can pass different validity conditions. When you use SQL option you can pass a SQL query and it will be set as per SQL queryFor Dynamic option, you can pass Stored Procedure to define validity.

The following table explains few points about the use of row vs column store tablesTo know more about row and column store tables, refer the below link: SAP HANA is optimized for column storage.https://help.sap.com/doc/6b94445c94ae495c83a19646e7c3fd56/2.0.00/en-US/bd2e9b88bb571014b5b7a628fca2a132.html

Analytic Privilege is created inside packages under Content tab.Analytic Privileges are only applied to attributes in an Information View. We cannot add measures to restrict access to Analytic privileges.Analytic Privileges are used to control read access to SAP HANA Information views. You can also hide an information from the specific time period.

SAP HANA Modeler Views can only be created on the top of Column based tables. Storing data in Column tables is not a new thing. Earlier it was assumed that storing data in Columnar based structure takes more memory size and not performance Optimized.With the evolution of SAP HANA, HANA used column-based data storage in Information views and presented the real benefits of columnar tables over Row based tables.Column StoreIn a Column store table, Data is stored vertically. So, similar data types come together as shown in the example above. It provides faster memory read and writes operations with help ... Read More