SAP HANA to PostgreSQL

BladePipe supports data replication from SAP HANA to PostgreSQL. View supported migration, sync, verification, and connector capabilities.

Target DataSource：

PostgreSQL

Connection

Function	Description
Schema Migration	If the target schema does not exist, BladePipe will automatically generate and execute CREATE statements based on the source metadata and the mapping rule.
Full Data Migration	Migrate data by sequentially scanning data in tables and writing it in batches to the target database.
Incremental Data Sync	Sync of common DML like INSERT, UPDATE, DELETE is supported.
Data Verification and Correction	Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported. For more information, see Create Verification and Correction DataJob.
Subscription Modification	Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.
Table Name Mapping	Support the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase, truncating the name by "_digit" suffix.
Metadata Retrieval	Retrieve the target metadata with filtering conditions from the source table.

Function	Description
Trigger-based Incremental Data Sync	The DataJob automatically creates triggers on tables. These triggers capture INSERT, UPDATE, and DELETE events and write them to the CDC tables.
Handling of Zero Value for Time	Allow setting zero value for time to different data types to prevent errors when writing to the Target.
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.
Setting Update Conditions for Target	Set additional update conditions for UPDATE operations, used to resolve confilcts in bidirectional sync.

Limit	Description
DDL Change Handling	BladePipe captures data changes in a source SAP HANA instance through triggers. DDL synchronization is not supported. If there are DDL changes, follow the steps in Change Schema in a Source SAP HANA Instance.
Hana Data Types in Incremental Sync	In the incremental data sync phase with a source Hana instance, it does not allow capturing changes for TEXT, BIN_TEXT, ST_POINT, and ST_GEOMETRY data types by triggers.
Primary Key Conflict Handling	PostgreSQL <= 9.4 or Greenplum <= 6 does not support conflict skipping or replacement. Performance may be affected when there are a large number of primary key conflicts.

Prerequisite	Description
Permissions for Account	See Permissions Required for Hana

Parameter	Description
sysTriggerDataSchema	The schema name where the trigger writes incremental data.
sysTriggerDataTable	The table name where the trigger writes incremental data.
incrPagingCount	The total amount of data queried each time by the trigger during incremental data synchronization.
incrIdleSleepSecond	The interval between queries for the trigger during idle period of incremental data synchronization (in seconds).
incrScanIntervalMs	The interval between data queries for the trigger during incremental data synchronization (in milliseconds).
autoCheckTriggerAndReInstall	Check the trigger status and reinstall it when the DataJob starts.
triggerDataCleanEnabled	Enable scheduled cleanup of trigger incremental data.
triggerDataCleanIntervalMin	The cleanup interval for trigger incremental data (in minutes).
triggerDataRetentionMin	The retention time for trigger incremental data (in minutes).
dbHeartbeatEnable	Configure whether to enable heartbeat for the source database.
needTriggerDataJsonEscape	Whether to escape characters (\) in the trigger incremental JSON.
triggerDataJsonQuotation	Custom quotation marks for trigger incremental JSON.
triggerParamBathSize	Set the number of columns involved per variable in the trigger template.
fullBeforeImageEnabled	Enable the trigger to record the complete data before all column changes.

Tips: To modify the general parameters, see General Parameters and Functions.

Prerequisite	Description
Permissions for Account	Required permissions include SELECT, INSERT, DELETE, UPDATE, and common DDL permissions. For Aliyun AnalyticDB for PostgreSQL, initial accounts or those with SELECT, INSERT, DELETE, UPDATE, and common DDL permissions are needed.
Port Preparation	Allow the migration and sync node (sidecar) to connect to PostgreSQL / Greenplum / AnalyticDB for PostgreSQL / PolarDB for PostgreSQL standard interactive interface (e.g., 5432).

Parameter	Description
keyConflictStrategy	Strategy for handling primary key conflicts during write in Incremental DataTask: IGNORE: Ignore conflicts (default) REPLACE: Replace conflicts (optional)
dstWholeReplace	Convert INSERT and UPDATE operations into full row replacement in the Target.
enableTimeZoneProcess	Enable time zone conversion to datetime fields.
timezone	Target time zone, e.g., +08:00, Asia/Shanghai, America/New_York.
defaultZeroDate	Default value for replacing '0000-00-00 00:00:00' / '0000-00-00' values. Optional values include: null (empty) Time (14:23:33) Date (1970-01-01) DateTime (1970-01-01 00:00:00), TimeZone Time (14:23:33+08:00 or 1970-01-01 00:00:00+08:00)
caseSensitive	Case sensitivity strategy for SQL statements, including: UpperCase: Convert to uppercase LowerCase: Convert to lowercase Sensitive: Add qualifiers NoSpecified: No conversion/No qualifiers
writeStrategy	Strategy of writing data to the Target, including: ROW (single row) MULTI_SQL (multiple statements) BATCH (write data in batches, default option) COPY (PostgreSQL COPY command)
defaultGisSRID	Set the SRID for GIS data types.

Tips: To modify the general parameters, see General Parameters and Functions.