Show TOC

SAP HANALocate this document in the navigation structure

To create a PDM with support for features specific to the SAP HANA® DBMS family, select the appropriate version in the DBMS field of the New Model dialog. To view these extensions to the PowerDesigner metamodel in the Resource Editor, select Start of the navigation path Database Next navigation step Edit Current DBMS End of the navigation path and expand the Profile node.

PowerDesigner supports round trip reverse-engineering and generation of SAP HANA® v1.0 tables and analytic and attribute views, and limited support for reversing and generating calculation views.

The following tools are available in the SAP HANA Database 1.0 toolbox:

Tool

Description

 Can Create In

Virtual Table - [model root only] See Smart Data Access (HANA).

 Model Root

Calculation View - [HANA package only] See Calculation Views (HANA).

 HANA Package

HANA Package - See HANA Packages (HANA).

 Anywhere

The following sections list the extensions provided for SAP HANA.

Model

The following extensions are available on the General tab:

Name

Description

HDI Namespace

Specifies the namespace for use when generating files for HDI (see Exporting Objects to the HANA Repository).

Scripting name: Namespace

Extended storage

Specifies the extended storage for the HANA database (see Dynamic Tiering (HANA)). Use the tools to the right of the field to create, delete, or open the property sheet of the external storage.

Scripting name: ExtendedStorage
Tables

The following extensions are available on the General tab:

Name

Description

Type
Specifies the table type. You can choose between:
  • Row - [default] If the majority of table access involves selecting a few records, with all attributes selected, ROW-based storage is preferable.
  • Column - If the majority of table access will be through a large number of tuples, with only a few selected attributes, COLUMN-based storage should be used.
  • History column - Creates a table with a session type HISTORY, to support time travel queries, which are queries against historical states of the database.
  • Global temporary - The table definition is globally available while data is visible only to the current session. The table is truncated at the end of the session.
  • Local temporary - The table definition and data is visible only to the current session. The table is truncated at the end of the session.

Scripting name: FullType

The following extensions are available on the HANA tab:

Name

Description

Logging
Specifies whether table logging is activated. You can choose between:
  • logging - [default]
  • nologging - specifies that logging is deactivated. As a result, the definition of the table is persistent and globally available and data is temporary and global. The resource manager should therefore explicitly drop a NOLOGGING table.

Scripting name: LoggingType

Retention period

[if nologging] Specifies the retention time in seconds of the table created as nologging.

Scripting name: Retention
Auto-Merge

Specifies that automatic delta merge is triggered.

Scripting name: AutoMerge
Unload priority

Specifies the unload priority for the table from 0 to 9, where 0 means the table cannot be unloaded and 9 means earliest unload.

Scripting name: UnloadPriority
Schema flexibility

Specifies that the table schema is flexible.

Scripting name: WithSchemaFlexibility
Location

Specifies that partitions will be created on the listed instances using round robin scheme.

Scripting name: PartitionLocation
Multiple

Specifies that the location targets multiple HANA instances.

Scripting name: HasMultipleLocations
Using extended storage

Creates an extended table (see Dynamic Tiering (HANA)). When selected, you can additionally enable support for Row-level versioning.

Scripting name: UseExtendedStorage, EnableDelta
Group options

Specifies the group options.

Scripting name: GroupOptionClause
Options text

Specifies the SQL text of the table options. Options entered here will be set in their relevant fields, and changes to the fields are reflected here.

Scripting name: FullTableOptions

The following extensions are available on the Partitions tab:

Name

Description
Type
Specifies the partition scheme type:
  • Hash - Distributes rows to partitions equally for load balancing and to overcome the 2 billion row limitation. Specify an Expression listing the columns to partition on and the Quantity of partitions to create. You may specify a second scheme of type Hash or Range.
  • Range - Creates partitions for specific values or value ranges. Specify an Expression and Range specifier.
  • RoundRobin - Distributes rows to partitions equally without specifying partitioning columns. Specify the Quantity of partitions to create. You may specify a second scheme of type Range.

Scripting name: FirstPartitionElement, Hash1Expression, Hash1Quantity, Range1Expression, Range1Spec, Round1Quantity, SecondPartitionElement, Hash2Expression, Hash2Quantity, Range2Expression, Range2Spec
Columns

The following extensions are available on the Detail tab:

Name

Description

Column stored data type

Specifies the stored data type.

Scripting name: StoreDataType

DDIC data type

Specifies the application data type.

Scripting name: DDICDataType
Indexes

The following extensions are available on the General tab:

Name

Description

Type
Specifies the type of the index, which can be:
  • <none> - [default] The server will choose the appropriate index type.
  • Cpbtree - Compressed Prefix B+-Tree, which can show better performance for larger keys for character, string, binary string, or decimal column types, or when the constraint is a composite key, or a non-unique constraint.
  • Btree - Maintains sorted data that performs efficient insertion, deletion and search of records.
  • Fulltext - Creates an additional data structure to enable text search features on a specific column in a table. Enables the Full-Text tab (see below).

Scripting name: DescIndex

Descending

[btree only] Specifies that the index should be created in descending order.

Scripting name: DescIndex
The Full-Text tab is displayed when you select Fulltext in the Type list on the General tab:

Name

Description

Phrase index ratio

Specifies the percentage of the phrase index between 0.0 and 1.0.

Scripting Name: FTPhraseIndexRatio

Search only

Specifies whether the original document should be stored or only the search results. When selected, the original document content is not stored.

Scripting Name: FTSearchOnly

Text analysis

Enables text analysis capabilities on the indexed column. Text analysis can extract entities such as persons, products, or places from documents, which are stored in a new table.

Scripting Name: FTTextAnalysis

Configuration

Specifies the path to a custom configuration file for text analysis.

Scripting Name: FTConfiguration

Fast pre-process

Specifies that fast preprocessing is used, and that linguistic searches are not possible.

Scripting Name: FTFastPreprocess

Fuzzy search index

Specifies that a fuzzy search is performed with an additional index (faster search, but higher memory consumption).

Scripting Name: FTFuzzySearchIndex

Change tracking

Specifies whether the index should be built in an asynchronous or synchronous manner.

Scripting Name: FTChangeTrackingElement

Flush every (minutes) / Flush after (documents)

Specify how frequently an asynchronous index should be update.

Scripting Name: FTFlushEvery, FTFlushAfter

Language detection / Language column

Specify the set of languages to be considered during language detection and the column where the language of a document is specified.

Scripting name: FTLanguageDetection, FTLanguageColumn

MIME type / Mime-type column

Specify the default MIME type used for preprocessing (for example cf M_TEXT_ANALYSIS_MIME_TYPES and the column where the MIME type of a document is specified.

Scripting name: FTMimeType, FTMimeTypeColumn

Token separators

Specifies the set of ASCII characters used for token separation.

Scripting name: FTTokenSeparators
Keys

The following extensions are available on the General tab:

Name

Description

Key type

Specifies the key type.

Scripting name: KeyType
Roles

The following extensions are available on the General tab:

Name

Description

Global visibility

Specifies that the role is available globally.

Scripting name: GlobalVisibility

Global ID

[if global visibility] Specifies the external role name for the global user.

Scripting name: GlobalID
References
The following extensions are available on the HANA tab:

Name

Description

Cardinality

Specifies the type of cardinality.

Scripting name: HANACardinality

Join type

Specifies the join type.

Scripting name: HANAJoinType

Language Column

Specifies the language column.

Scripting name: HANALanguageColumn
Users

The following extensions are available on the General tab:

Name

Description

Identification

Specifies the type of identification (global, local or external).

Scripting name: Identification

Distinguished name

Specifies the user's distinguished name (DN) in the directory or certificate.

Scripting name: DistinguishedName

Password

Specifies the clear copy of the password.

Scripting name: CopyPassword

Implicit Schema

Specifies that the database generation will use the stored procedure sp_grantdbaccess instead of a create user statement.

Scripting name: ImplicitSchema

Default Schema

Specifies the first schema searched to resolve the names of objects for this user.

Scripting name: DefaultSchema
Packages

The following extensions are available on the HANA tab of HANA packages:

Name

Description

Structure package

Specifies that the package is a structural package

Scripting name: Structural

Package

Specifies the HANA object name.

Scripting name: _ObjectName_
Facts (Analytic Views) and Dimensions (Attribute Views)

The following extensions are available on the HANA tab:

Name

Description

Default Client / Member

Specify the HANA default client, and (dimension only) member.

Scripting name: DefaultClient, DefaultMember

Multidimensional reporting

[facts] Specifies that multidimensional reporting is enabled.

Scripting name: MultidimensionalReporting

Package / Name / Version

Specifies the HANA package, object name, and version.

Scripting name: _ObjectPackage_, _ObjectName_, _ObjectVersion_

Last Updated Date / at

Specifies when the dimension or fact was last edited.

Scripting name: _LastUpdatedDate_, _LastUpdatedTime_
Dimension Attributes and Fact Attributes

The following extensions are available on the HANA tab:

Name

Description

Default Member / Info Object

Specify the HANA default member and info object.

Scripting Name: DefaultMember, InfoObject

Drill Down Enabled

Specifies the drill down is enabled for the attribute.

Scripting Name: DrillDownEnabled

Hidden

Specifies that the attribute is hidden.

Scripting Name: IsHidden

Key Attribute / Attribute Hierarchy Active

[Dimension attribute only] Specify that the attribute is a key attribute and that the attribute hierarchy is active.

Scripting Name: KeyAttribute, AttributeHierarchyActive

Data Type / Length / Scale

Specify the data type, length and scale of the attribute.

Scripting Name: AttributeDataType, Length, AttributeScale
Fact Measures

The following extensions are available on the HANA tab:

Name

Description
Measure type Specifies the type of the measure:
  • simple - a measurable analytical element that is derived from the data foundation.
  • amount - based on a combination of data from OLAP cubes, arithmetic operators, constants, and functions.
  • quantity - count the recurrence of an attribute.

Calculated measure

Specify the data type, length and scale of the measure.

Scripting Name: MeasureDataType, MeasureLength, MeasureScale

In this section:
    HANA Packages (HANA)
    HANA packages group together related information objects in a structured way. While tables are stored in the catalog (represented by the model root), analytic, attribute, and calculation views must be created in a HANA package.
    Smart Data Access (HANA)
    With SAP HANA Smart Data Access, data can be merged in heterogeneous EDW landscapes (data federation), making it possible to access data in remote sources without having to replicate it to the SAP HANA database beforehand. PowerDesigner models virtual tables as tables with a stereotype of VirtualTable and remote sources as extended objects with a stereotype of RemoteSource.
    Dynamic Tiering (HANA)
    You can define an extended storage for your HANA database, which is an external SAP IQ database automatically used to transparently archive and query data stored in extended tables. Extended tables are physically located in the SAP IQ server, but logically sit in HANA and can be used as if they were regular HANA tables.
    Calculation Views (HANA)
    A calculation view can perform complex calculations and can have tables, standard views, and other calculation views as sources.
    Exporting Objects to the HANA Repository
    While HANA tables are generated directly to the catalog, analytic, attribute, and calculation views are exported to the HANA repository from where they will be deployed. PowerDesigner provides a wizard to allow you to export your objects to the HANA repository and catalog as appropriate in a single action.
    Importing Objects from the HANA Repository
    PowerDesigner provides a wizard to allow you to import analytic, attribute, and calculation views from the HANA repository, along with their supporting catalog objects.