Why Dual-Engine SQL Matters (MSSQL + PostgreSQL) addresses a problem most SAP landscapes know too well: Stale warehouses and failed night jobs undermine dashboards the C-suite already promoted.
Millions of rows leave SAP nightly through the same engine you test with First Row Test — no separate ETL product to license and wire up.
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.
Capabilities you use in iDataEngine
- Methods I, A, U, D, L with delta parameters
- Masking on SAP → SQL direction
- Connection test from the maintenance screen
- SQL Job Monitor with cron schedules
- Project clone and monitoring KPIs
- Delta days configuration (L method)
Recommended workflow
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
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
Dashboards built on stale SAP extracts destroy trust faster than no dashboard at all. Reliable nightly SQL Transfer is the foundation for pricing, stock, and finance analytics that executives actually act on.
The competitive edge is not more developers; it is removing wait states between idea, data, and delivery.