Interview preprations SAP HANA Day 1

Questions :

Q 1 : Difference between Catalog and Content folder in SAP HANA Studio project explorer.

The Catalog View gives a view on the runtime objects of the database artifacts. The first level you see under this view is the schema to which the runtime objects are assigned. In case you create e.g. a table using DDL statement CREATE TABLE you see created runtime object for the table under the schema which was used in the statement (but the table is not visible in the Content view).

The Content View gives a view on the design time objects of e.g. database artifacts (and further static content) stored in the HANA repository (therefore the objects are also called repository objects). Under the Content View the design time objects are organized in packages (1 to n levels). The activation of a design time object for a database object leads to the creation of the runtime object in the specified database schema. So if you create e.g. a table via an hdbtable artifact (e.g. mypackage.test.TestTable.hdbtable) and activate it you can see in the Content view the design time object "TestTable.hdbtable" in package "mypackage.test" and in the Catalog view under the schema you defined in the design object the runtime object "mypackage.test::TestTable".

source : https://archive.sap.com/discussions/thread/3845399

Q2:  Difference Between HANA Modeler and Developer

Modeler perspective 

You can model entities in SAP HANA using the Modeler perspective, which includes graphical data modeling tools that allow you to create and edit data models (content models) and stored procedures. With these tools, you can also create analytic privileges that govern the access to the models, and decision tables to model related business rules in a tabular format for decision automation.

You can create the following types of information views:

● Attribute Views 

● Analytic Views 

● Calculation Views

Task that can be performed using Modeler Perspective 

Task	Meaning
Import metadata	Create tables by importing the table definitions from the source systems using the Data Services infrastructure.
Load data	Load data into the table definitions imported from the source system using the Load Controller, SAP Sybase Replication Server or SAP Landscape Transformation, and from flat files.
Create packages	Logically group objects together in a structured way.
Create information views	Model various slices of the data stored in the SAP HANA database. Information views are often used for analytical use cases, such as operational data mart scenarios or multidimensional reporting on revenue, profitability, and so on.
Create procedures	Create procedures using SQLScript for implementing a complex logic that cannot be achieved using other objects.
Create analytic privileges	Control which data that individual users sharing the same data foundation or view can see.
Import SAP BW objects	Import SAP BW objects into SAP HANA, and expose them as information views.
Create decision tables	Create a tabular representation of related rules using conditions and actions.
Import and export objects	Import and export the content objects from and to the client and server location.

Development Perspective 

Used for programming applications, that is, creating development objects that access or update the data models, such as server-side JavaScript or HTML files.

Provides views and menu options that enable you to perform all the tasks relating to application development on SAP HANA XS, for example: to manage application-development projects, display content of application packages, and browse the SAP HANA repository. You can also define your data-persistence model here by using design-time artifacts to define tables, views, sequences, and schemas.