A remote subscription is a database object in SAP HANA used specifically for real-time data replication. Its primary purpose is to define the relationship between a remote source table (represented by a virtual table) and a local target table. Once activated, the subscription monitors the remote source for data changes (INSERT, UPDATE, DELETE) and automatically applies these changes to the local target table, ensuring the data remains synchronized.

A. To establish a connection to the replication service: A REMOTE SOURCE object, not a remote subscription, is used to define and establish the connection to a remote system and its associated replication service (Data Provisioning Agent).

B. To be notified when remote data has changed: While a subscription acts on data changes, its function is active data replication, not merely passive notification. The goal is to update a local table, not just to be informed of a change.

D. To assign a virtual table to a remote source: A virtual table is created and mapped to a remote object using the CREATE VIRTUAL TABLE statement. A remote subscription is created after the virtual table exists to replicate its data.

1. SAP HANA Cloud

SAP HANA Database SQL Reference Guide for SAP HANA Platform:

Section: CREATE REMOTE SUBSCRIPTION Statement (Data Lake)

Content: "Creates a remote subscription to specify how to replicate data from a remote source object into a target table." This statement directly confirms that the subscription's purpose is to replicate data from a remote source to a local target.

2. SAP HANA Smart Data Integration and SAP HANA Smart Data Quality Guide:

Section: Replicating Data in Real Time

Content: The guide outlines the process for real-time replication which involves creating a remote source

creating virtual tables

and then creating a remote subscription. It states

"A remote subscription defines the replication process from one source virtual table to one target table." This explicitly supports the function described in option C.

The DEPRECATED setting in the properties of an SAP HANA calculation view serves as a lifecycle management flag. When enabled, it signals to developers that the view is outdated and planned for removal in a future version. The modeling tool will then issue a warning message to anyone opening the view, stating it is no longer supported. Furthermore, if a developer attempts to use this deprecated view as a data source in another, newer calculation view, a specific warning will be displayed, discouraging its continued use and preventing dependencies on obsolete objects.

C. The DEPRECATED setting is a status indicator that generates warnings; it does not function as a lock or prevent authorized developers from making further modifications.

D. This setting does not automatically redirect queries. Query redirection would require a different mechanism, such as a synonym or specific application logic, not the deprecation flag.

1. SAP HANA Cloud

SAP HANA Database Modeling Guide for SAP Business Application Studio: In the section "Model Calculation Views

" under the subsection "General Properties of Calculation Views

" the guide states: "Deprecated: If you select this checkbox

the tool displays a warning message that the calculation view is deprecated and is no longer supported. Also

if you use this calculation view as a data source in other calculation views

the tool displays a warning message that the data source is deprecated." (SAP Help Portal

SAP HANA Cloud)

2. SAP HANA Modeling Guide for SAP Web IDE: In the section "Creating and Editing Calculation Views

" under "Calculation View Properties

" the "Deprecated" property is described with the same functionality: to warn users that the view is no longer supported and to issue a warning if it's used as a data source in other views. (SAP Help Portal

SAP HANA Platform)

The .hdiconfig file is a container-level configuration file for the SAP HANA Deployment Infrastructure (HDI). Its purpose is to specify which HDI plug-ins are active for a given HDI container. This file contains a JSON-formatted list that maps specific file extensions (e.g., .hdbtable, .hdbprocedure) to the corresponding plug-in responsible for processing and deploying those artifact types. By editing this file, developers can enable or disable the processing of certain database object types within their project.

A. Deployment space is a runtime target specified during the deployment command (e.g., using the Cloud Foundry CLI), not within the .hdiconfig file.

B. Access to external schemas is configured using user-provided services (UPS) and grant files (e.g., .hdbgrants), not the .hdiconfig file.

D. Namespace rules, which allow for object name prefixing and aliasing, are defined in a separate configuration file named .hdinamespace.

1. SAP HANA Developer Guide for SAP HANA XS Advanced Model: In the section "The SAP HDI Container Configuration File (.hdiconfig)"

it states

"The plug-ins to use for the deployment to an HDI container are defined in a configuration file (.hdiconfig)... The .hdiconfig file contains a JSON-formatted list of plug-ins that map a file extension to the plug-in that is responsible for handling files with the specified extension." (SAP Help Portal

SAP HANA Platform 2.0 SPS 07).

2. SAP HANA Deployment Infrastructure (HDI) Reference: The section "Container-Level Configuration (.hdiconfig)" explains

"The .hdiconfig file is a JSON file that lists the file suffixes and corresponding HDI plug-ins that are recognized by the HDI deployer... By default

an HDI container is configured to use all available HDI plug-ins. However

you can use the .hdiconfig file to specify a list of plug-ins to use for deployment." (SAP Help Portal

SAP HANA Platform 2.0 SPS 07).

In SAP HANA Calculation Views, a temporal join is a specific property that allows for joining time-dependent data. This is typically used when a transactional table with a specific date needs to be joined with a master data table that has a validity period (e.g., VALIDFROM and VALIDTO columns). This temporal condition feature is explicitly supported for both Inner joins and Left Outer joins. The modeler can specify a temporal column from one table and a temporal interval from the other, and the engine will evaluate the join based on whether the date falls within the interval.

A. Text join: This is a specialized left outer join used specifically for retrieving language-dependent text descriptions. It does not support the temporal join property.

B. Referential join: This is an optimized inner join that relies on pre-existing referential integrity. While it is a type of inner join, it does not have the specific temporal property setting available.

1. SAP HANA Cloud

SAP HANA Database Modeling Guide for SAP Web IDE for SAP HANA: In the section "Defining Temporal Joins

" the documentation explicitly states

"You can define temporal joins for inner joins and left outer joins. A temporal join is used to join a transaction table with a master data table that has time-dependent attributes."

2. SAP HANA Cloud

SAP HANA Database Modeling Guide: In the section "Create Joins in Calculation Views

" under the subsection for join properties

it is detailed that the "Temporal" property can be configured for join types "Inner" and "Left Outer".

CREATE REMOTE SOURCE validates the syntax of the CREDENTIAL clause and the existence of the referenced adapter.

A. When CREDENTIAL TYPE 'PASSWORD' is chosen, USER and PASSWORD must be supplied. Omitting the technical user raises SQL-100055 “Invalid credential specification,” so the statement fails.

D. The adapter name given in the statement must already be registered in SYS.REMOTEADAPTERS (either natively or via the DP-Agent). If it is not found, SQL-100057 “Adapter not found” is returned and the statement fails.

B. Connectivity to the target system is not checked at creation time; the remote source is created and only shows “ERROR” status later when accessed.

C. The CREATE REMOTE SOURCE privilege is required on the local SAP HANA instance, not on the remote system; remote-side privileges do not influence statement execution.

1. SAP HANA SQL Reference Guide 2.0 SPS05

“CREATE REMOTE SOURCE

” Syntax Rules

p. 2835

para. 5 – requirement for USER/PASSWORD with CREDENTIAL TYPE PASSWORD.

2. SAP HANA Smart Data Integration and Quality Admin Guide 2.0 SPS05

“Registering and Managing Adapters

” p. 47 – necessity of adapter entry in SYS.REMOTEADAPTERS.

3. SAP HANA Smart Data Integration and Quality Admin Guide 2.0 SPS05

“Remote Source Status

” p. 60 – network issues reported after creation

not during DDL.

4. SAP HANA Security Guide 2.0 SPS05

“System Privileges

” p. 128 – CREATE REMOTE SOURCE privilege applies to SAP HANA user

no requirement on remote system.