In database explorer if you expand the database container, you can see a folder
Audit
In SAP Hana Cloud allows monitoring and recording specific actions in the database
It doesn't directly enhance database security but helps identify security vulnerability and potential breaches, Health, detect unauthorized privilege grants attempts to bridge security and protect against data misuse
Audited actions include changes to user authorization, creation or deletion of database objects, system configuration changes and access to sensitive data
The audit trail stores audit entries when an audit policy is triggered by a specific action
Audit entries are written to an internal SAP Hana database table ensuring quick querying and analysis of audit information
Access to audit entries is limited to the public system view AUDIT_LOG and only users with the system privilege AUDIT_OPERATOR and AUDIT_ADMIN can perform select operation on this view
SAP Hana Cloud Central ⇒ Auditing tile ⇒ Create Audit policy
Select Audit Actions like CREATETABLE
Select Users
Audit Level like info, error and warning
Retention period
Enable Policy
Show Data linage
Visualization of all data sources (like tables and views) that are used to build a calculation view.
Right click hdbcalculation view in BAS and select the ? option
It shows the complete flow of data into and within the calculation view, including the processing steps.
Shows how changes to the source data could impact the calculation view.
Manage Users
SAP Hana Cloud Central ⇒ right click and select SAP Hana Cockpit ⇒ Add all the tiles from ⇒ click on user icon ⇒ Select Manage cards
Is different from the SAPBTP users
Only Users created in SAP Hana Cockpit or SQL console shows up here
Manage Roles
SAP Hana Cloud Central ⇒ right click and select SAP Hana Cockpit ⇒ Add all the tiles from ⇒ click on user icon ⇒ Select Manage cards
Is different from the SAPBTP roles
Only Roles created in SAP Hana Cockpit or SQL console shows up here
Column Lineage
when you want to see quickly where a calculated or restricted column originates from
It also helps you to avoid mixing up columns with the same name.
Where-Used
Input Parameters
Calculated Columns
Restricted Columns
Debug Query mode
Button in Graphical calculation view editor
In each node you will get Debug Query tab to examine the runtime SQL of a node
You can execute at each node to display the interim results
One of the most useful things that you can discover when using Debug Query mode is to see how each node is pruned of columns and even complete data sources under various query conditions
Remember that the Debug Query mode calls the active version of the calculation view. This means that if you have made changes to the calculation view but not yet rebuilt it, then you switch on Debug Query mode, the debug results will not reflect those latest changes.
Previewing the Output of Intermediate Nodes
To troubleshoot problems in view design, preview the data of an intermediate node rather than the whole calculation view.
Replacing a Data Source
For the top node, it's also possible to switch to a Star Join node.
It's possible to convert a Projection node into an Aggregation node and the other way around without losing the reference to the data sources of the node.
SAPHANA Performance Tools
To enable this view, when creating your SAP Business Application Studio development space, or later on, you must add the extension to this space.
This is a set of views, tables, graphs that you can use to analyze any SQL Query. You can drill-down in a graph execution, analyze the timeline of query compilation and execution, visualize how many tables, and which tables, were used, and so on.
In addition to analysing the SQL generated by the calculation views (either the standard query or a modified query), it can be used wherever SQL is defined, for example in table functions.
You must first locate the plan file in the folder where you uploaded it.
Add the plan file to ?.
SYSTEM privileges:
TRACE_ADMIN
INIFILE_ADMIN
SQL Analyzer Plan File
If you have generated the SQL plan file from an SQL Console opened from the SAPHANA Database Explorer view of SAP Business Application Studio, the plan file opens immediately in the HANASQL Analyzer view.
To get started, you generate a file that collects the run-time information of your SQL query. Use the menu option Analyze ⇒ ?. Choose a file name prefix for the plan file, and choose Save. The location is already set for you and you cannot change it at this stage.
If you have generated the SQL plan file from another tool, such as the Data Preview of SAP Business Application Studio, or from the external SAPHANA Database Explorer (outside of SAP Business Application Studio), you need to download the SQL plan file to your computer. Choose Download, and this is then handled by your web browser. Choose a convenient location to store the SQL plan file.
You access these plan files from the External SAPHANA DB Explorer, within the HDI container, in the section Catalog ⇒ Database Diagnostic Files ⇒ <DB Instance ID> ⇒ other. They must be downloaded, and then uploaded to SAP Business Application Studio.
The next stage is to upload the plan file to the Explorer view of SAP Business Application Studio. Upload the plan file to any project folder by using the context menu Upload.
