Overview
The client had an engineering or operational system backed by Oracle data that needed to be integrated into Azure Data Lake Gen2. The source environment was on-premises and required secure access through a controlled network path.
Challenge
- Source was on-prem with Oracle backend — not a simple cloud API.
- Required coordination across application, database, SHIR, network, and ADLS layers.
- Needed a reliable read-only extraction method that wouldn't disrupt the source app.
Solution
MSPowerhouse designed the integration using Azure Data Factory and Self-hosted Integration Runtime. The preferred approach was to extract from approved Oracle reporting views or read-only database structures where available. Where direct database extraction was not the right option, REST/OData-style access could be considered as an alternative.
The data was copied into Azure Data Lake Gen2 using controlled pipelines and stored in a structured lake pattern for downstream analytics.
Technical Execution
- Self-hosted Integration Runtime for on-premises connectivity.
- Oracle database connection through the internal network.
- Read-only service account access.
- Azure Data Factory Copy Activity.
- Extraction from approved tables, views, or queries.
- Raw landing into ADLS Gen2.
- Optional incremental logic using modified-date fields.
- Monitoring and troubleshooting of runtime, firewall, proxy, and TLS issues.
- Separation of source extraction from downstream reporting transformations.
Outcome
The client gained a secure method to bring Oracle-backed operational data into Azure without exposing internal systems publicly.
Impact
This project helped modernize access to engineering/operational data while respecting the security and stability needs of an on-premises source system.
