Why Dual-Engine SQL Matters (MSSQL + PostgreSQL) — Field Guide addresses a problem most SAP landscapes know too well: Stale warehouses and failed night jobs undermine dashboards the C-suite already promoted.
The SQL Project Cockpit defines source objects, target tables, field mapping, delta parameters, and schedules — monitored in SQL Job Monitor with package-level error detail.
SQL Transfer moves SAP data to MSSQL or PostgreSQL using project-based jobs with methods I (full refresh), A (append), U (upsert), D/L (delta), package sizing, and parallel processing.
Capabilities you use in iDataEngine
- Package size and parallel processing
- SQL Job Monitor with cron schedules
- Masking on SAP → SQL direction
- MSSQL and PostgreSQL dual-engine parity
- Methods I, A, U, D, L with delta parameters
- Project clone and monitoring KPIs
Recommended workflow
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
Real-world scenario (2025)
E-commerce stock sync every ten minutes via upsert into PostgreSQL — website stays fast when SAP is slow because SQL Transfer owns the cache layer.
Why it matters
Delta methods save SAP and SQL load; upsert keeps master data current without full-table deletes that frighten operations.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.