The following table lists all the key server components in HANA, the corresponding services, and OS process details.

In SAP HANA Modeling, Graphical Information Views are faster as compared to SQLScript in almost every scenario and also Graphical Information Views are easier for others to understand, remodel and change.There are scenarios where you need SQLScript, but it shouldn’t be viewed as a general-purpose solution to modeling problems.Note:It is never recommended that you code a Calculation View with SQL Script and use it inside another Calculation View with CE Functions as it results in a very bad performance.

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.

You can get similar things done in many ways. You can use an internal table usage or a range table.Let me showcase an example with an internal table for your reference.SELECT Id, Name, DOB FROM sEmployee INTO CORRESPONDING FIELDS OF TABLE result_tab FOR ALL ENTRIES IN internal_tab // internal_tab is an internal table defined with columns WHERE Id = internal_tab -Id AND Name = internal_tab –Name

The basic principle for performance is that there should be minimal data transferred between application server and database.For your first question, I would suggest to select only the fields that are required. So, don’t use SELECT * in case you don’t require all the fields. But in specific scenarios, if you have multiple SELECT statements at various parts of your program querying the same table but different columns, it is advisable to use SELECT * as the output is stored in a buffer till your program execute. In that case, when you come to subsequent select, the system uses the ... Read More

You can opt for using regular expressions to remove the duplicate numbers from column c or any other intended column.ExampleSELECT REPLACE_REGEXPR ('([A-Za-z0-9])\1+' in 'BB11222343CC'    WITH '\1'    OCCURRENCE ALL) FROM OutputB12343C

Yes, it is  possible to use a view in Business one client and you can use it too. Please find below a sample format that you should be using to query the view in business one environment −SELECT FROM [dbo].[]I have done the same and it is working for me.

Note that IN statement in SQL doesn’t accept a wild character. You have to use OR/AND to make it work as mentioned below:select * from Test1 t INNER JOIN Test2 s ON t.ID = s.RID where t.sdate >= ?1 AND t.edate

Note that when you perform an insertion using an ABAP program, there is no check on foreign key constraint.  Even when you define checks in data dictionary SE11 still there is no check at database level.When you execute using an ABAP code, this checks consistency at application level and not at database level. Errors you see in SE16 shows record rejected at application level.You need to perform validation by checking record from master table with foreign key of child table and incase sy-subrc is not initial then record shouldn’t be inserted to the child table and shows an error message.Read More