Ags Hana Study Questions

In memory

Statement level isolation

Parallelization

Column Store

Query processor

Less distinct values

Compression,

Write optimized

Read optimized

Many distinct values

Select * (All columns)

Aggregation,

Insert and update

Read optimized

Select * (All columns)

Compression

Insert and update

Write optimized

Less distinct values

Many distinct values

Aggregation

Merge changed data from main memory to disk

Merge at the transaction level

Merge from delta to main memory only for column store tables

Merge at the statement level

A save point is where changed data is pushed from delta memory to main memory for column store tables

A save point takes place at the statement level

A save point takes place at the transaction level

A save point is where changed data is pushed from memory to disk

All statements of a transaction see the same snapshot (Isolation level repeatable read)

Different statements in a transaction may see different snapshots (Isolation level read committed)

Each statement sees the changes that were committed when the execution of the statement started.

Statement level snapshot is the default isolation level (Read Committed)

Transaction level snapshot is the default isolation level (Read Committed)

All statements of a transaction see the same snapshot (Isolation level repeatable read)

Different statements in a transaction may see different snapshots (Isolation level read committed)

Each statement sees the changes that were committed when the execution of the statement started.

Hana Studio (Runtime Tab)

Solution Manager Table Viewer

DBACockpit

M_CS_TABLES view

An attempt by a Query Optimizer to merge data from delta to main memory.

An attempt by a Query Optimizer to merge data from memory to disk

An attempt by a Query Optimizer to compute the most efficient way to fulfill a SQL request.

An attempt by a Query Optimizer to create a save point.

Table statistics are generated for all tables included in the query.

It is parsed, pre-complied and bound before being processed by the optimizer

The Plan is passed to the database object containing required information.

It is processed here (DBI) or native SQL

A column store table is generated.

A row store table is generated.

The index is read.

An Execution plan with a Timestamp is generated

RDL – Relational Data Language Mainly for database users

DDL – Data Definition Language Mainly for developers

TCL – Transaction Control Language Mainly for developers

TDL – Transaction Definition Language Mainly for developers

DML – Data Manipulation Language Mainly for database users

DCL – Data Control Language Mainly for system Administrators

Query processor

Data files

Backup Engine

Config Files

Application Engine

Application Engine

Clients

Additional instructions

Semicolon

Data Files

Object name (Database Table, Field Name)

Configuration Files

Command name

User Store

Analytical Privileges

Power user privileges

Package Privileges

Application Privileges

Privileges on user

Superuser (sudo) privileges

System Privileges

Object/ SQL Privileges

Restricted privileges

Database

Studio

Clients

Sapstartsrv

Agents

Backup Engine

AFL

Application Engine

Automatically

Manually

Through the Solution Manager backup scheduler

By using DBACockpit

Solution Manager Technical Operations Workcenter

Via HANA Studio

HDB start and HDB stop from the OS

DBACockpit

Profile.ini

Daemon.ini

Config.ini

Nameserver.ini

Customer.ini

HANA Studio

DBACockpit

HDB Console

Solution Manager Backup Scheduler

HANA User Store

Client User Store

HDB Admin User Store

HDB User Store

Full backup

Delta backup

Online backup

Incremental backup

Licensed CPU

Licensed CPU Cores

Licensed Memory

Licensed Concurrent Users

SAPSTARTSRV

DBACockpit

HANA Studio

HDB Agent

HDB Monitor

System Monitor

Trace Monitor

HDB Administrative Monitor

Activate the expensive statements trace which is deactivated by default

Use the expensive statements trace which is activated by default