DataMasque Portal

SAP HANA connections

DataMasque masks SAP HANA tables in place.

Required privileges

A DataMasque connection for SAP HANA requires at least the following privileges:

  • CREATE ANY on the schema DataMasque operates on (or the connection user owning that schema, which is the usual case). DataMasque uses this to create the mapping and staging tables and the sequences it requires during masking (CREATE TABLE and CREATE SEQUENCE).
  • SELECT and UPDATE on each table to be masked.
  • ALTER on each table to be masked. DataMasque uses this to add and drop columns (for surrogate keys) and to manage constraints during masking.
  • INDEX on each table to be masked. DataMasque uses this to drop and recreate indexes during masking.
  • DELETE on each table targeted by a truncate_table task, where truncation tasks are used.
  • INSERT on each table that is a target of a from_blob mask, which stages file data in a temporary table.
GRANT CREATE ANY ON SCHEMA <schema> TO <user>;

GRANT SELECT, UPDATE, ALTER, INDEX ON <schema>.<table> TO <user>;

-- Required only where truncation tasks are used
GRANT DELETE ON <schema>.<table> TO <user>;

Notes:

  1. The system views DataMasque reads during discovery (SYS.TABLES, SYS.TABLE_COLUMNS, SYS.CONSTRAINTS, SYS.REFERENTIAL_CONSTRAINTS, SYS.INDEXES, and SYS.INDEX_COLUMNS) are readable by any authenticated user; no explicit grants are required.

  2. If a schema is not explicitly specified in the connection settings, DataMasque operates on the connection user's CURRENT_SCHEMA (their own default schema).

  3. Repeat the table-level grants for each table to be masked.

Connection parameters

For SAP HANA databases, the following field is optional:
Schema The name of the schema that DataMasque will operate on. If not specified, the connection user's CURRENT_SCHEMA (their own default schema) will be used.

Notes:

  1. The default port for SAP HANA connections is 30015 (used if no port is specified).

  2. SAP HANA folds unquoted identifiers to upper case. Specify schema, table, and column names in upper case unless they were created as quoted (delimited) identifiers.

  3. A SAP HANA connection operates within a single schema (the connecting user's CURRENT_SCHEMA). Masking across multiple schemas in a single connection is not supported.

Limitations

  • mask_unique_key tasks are not supported. Use the imitate_unique mask instead.

  • Subsetting is not supported.

  • SAP HANA has no filtered or partial indexes.

  • SAP HANA has no equivalent of an Oracle ROWID pseudo-column; rows are identified by declared or generated keys.

Unsupported key columns

Data Type Unsupported Format
clob All
nclob All
blob All
text All
bintext All
st_geometry All
st_point All
real_vector All
real All
double All
float All
decimal Precision >= 39

Notes:

  • Fixed-point decimal is supported as a key column up to SAP HANA's maximum precision of 38.