I think you are over thinking on a potential issue. The size of tables as you said will be rarely over one million records which does not qualify it to be considered a big table. In my application we have tables which are much bigger than that but still work pretty well over time. Also, as you said that data is mainly categorized on a daily basis so, theoretically it makes sense to partition tables on dates.  It should improve the performance to some extent. But it can also lead to good number of partitions which can backfire too from ... Read More

You have identified the correct use case as it is by design as you have navigated back and forth, it renders the last version rendered and OnInit() does not gets called. But if you want to override this behavior, SAP lets you do it.You can delegate to the patternMatched event of router, so that wheever the view is rendered the OnInit() method is invoked.this.getOwnerComponent().getRouter().getRoute("").attachPatternMatched(, this);You need to attach the even handler to the router in the init method of the controller. Hope it helps and sorts out your requirement.

Yes, it can be done but I would request you to go through documentation available on SAP help before asking such questions as such things are well explained in documentation and help you to know the system better. You just need to set the text property to text of your choice.INITIALIZATION %_name_%_app_%-text = Hope it helps.

Projection Node is basically a graphical Calculation view. SAP HANA does not allow usage of regular expression in a graphical calculation view for filtering out data.So if you still need to use graphical calculation view (Projection Node), then you need to filter out the data either by using a table function or equivalent.

You got it partially correct but had something irrelevant present in the connection string. Try with the below connection string, it should work: /H/122.175.43.76/S/3266

The answer to your question is that a lot of formats are supported by process integration for processing. The basic concept is that you need to define a mapping which will parse the incoming file and then converts it to the output format. Since you are getting a file from service as an input, it will be better if it is in CSV or .xls.

I don’t think there exists any way where you can define the column type of a column within a table type as an array. Table type refers to a row structure with predefined number of columns. So you might need to rethink on how to change the incoming data from .NET application to be a usable one for your SAP HANA project.

You can achieve something similar to your requirement. Firstly, you need to fetch the layout key information from the layout object. You can look for disvariant to get the key information if not able to find. Then use the key information to specify different handles for different data types. So basically you are having different layouts for different inputs or data types. As soon as you change the data type, the handle will do its job and display will change accordingly. Hope it helps!

Yes, it is feasible and I have done something similar in one of my previous projects. But you need to be little clear on what you need to export. There are two options regarding the content of export:Raw Data ( it is basically the query)Formatted Data ( it is your report)I will provide you help for both. In case, if you are looking for just exporting the raw data then you can the following call and you should be able to fetch the raw data.http://:6405/biprws/raylight/v1/documents//dataproviders//flows/Also as will require the response in CSV, set the ACCEPT to ‘text/plain’ so that the ... Read More

I am not sure whether someone can get you exact answer, SAP is not open source and implementation details and bits are not known to many except the creators and few others. If I go with the standard definition, for storage you will require the size of length of the data plus number of bytes for header information. So as per your example it will require 9 + 2 (for header) = 11 overall for storage.