Lets take a look at SAP HANA Studio– The tool itself that we can use to define queries on HANA database to make models and data for Analysis.

Once you open the SAP HANA Studio, you are greeted with the workspace Launcher where you can define your work folder for saving all your data and related configuration files


Once you select your workspace, you are greeted with the welcome screen

Here you cane see that you are given several high level options to begin with.

We will be dealing with the Modeler perspective to model our queries for later featuring in analysis application.

Let’s try moving to the Modeler Perspective for now.

You can notice here that the selected perspective can be identified from here in right corner

Now we need to connect to a system to access the database for query.

You will see the below Systems pane. Right click on the blank area inside this pane to add a new system by choosing “Add System” from the context menu as shown below.

Fill in the Host Name and Instance number as provided by your system administrator and description as something relevant.  The other settings may also be different depending on the database you connect to – Please check with your administrator for details. Press “Next” when done.

The next step would be to enter in your username and password which also would be provided to you by your administrator. Press finish after you are done to add the systems.

You will see that the system has been added and the green square on the system icon indicates that all services are working fine.

Also, there are 4 sections or folder like icons that you see here. Let’s discuss their relevance.

  1. Catalog: This is where all the source metadata (Tables, views etc) is grouped under. Here you can do data previews on source system tables that have been replicated or available as virtual tables in case of SDA.
  2. Content: This is where all your HANA development takes place. The HANA models that you create go under here.
  3. Provisioning: This is mostly used for Smart data access. All the source systems connected via SDA will have their tables displayed here like a “Menu Card” in a restaurant. You can choose which one you want and build a virtual table for it in the “Catalog” section we discussed just now.
  4. Security: This is mostly for security consultants to maintain users and roles according to your role in the project – Developers, administrators, testers and so on.

We will dive deeper into the system in later tutorials.