← All use cases

Multiple OPC UA to SQL Databases & CSV Files

Use independent DataPaths to route multiple OPC UA sources to different destinations—without mixing schedules, mappings or delivery policies.

One DataMule. Two purpose-built DataPaths.

Each DataPath is an independent data pipeline with its own sources, transformations, destination and reliability settings.

OPC UA 01
OPC UA 02
OPC UA 03
→
→
DataMule
DataPath ATwo OPC UA sources · shared mapping & schedule
DataPath BOne OPC UA source · independent mapping & schedule
→
→
SQL DatabaseExternal destination
CSV FilesExternal destination
MULTI-DESTINATION PIPELINE

One governed data model, multiple independent outputs

OTDataMule collects from multiple OPC UA servers, normalizes different namespaces into one stable record model and routes each approved stream to its own SQL or CSV destination queue.

OPC UA SOURCESIndependent sessions and tag mappings
A
Packaging Linens=2 · speed · count · state
B
Utilitiesns=4 · energy · flow · pressure
C
Quality Systemns=7 · batch · result · recipe
→SUBSCRIBE & MERGE
OTDATAMULE NORMALIZATIONCommon record model
source_idasset_idsignalvaluesource_timequality
RenameType castScaleEnrichFilterRoute
→ROUTING RULES
INDEPENDENT DESTINATIONSSeparate queues, retries and health
Production SQLHealthy
Line and batch records
Queue A0 pending
Energy SQLOffline
Utilities and consumption data
Queue B12,480 buffered
Shift CSVHealthy
Hourly file rotation
Queue CWriting current file
Archive CSVHealthy
Daily governed export
Queue DNext close 00:00
Destination isolationEnergy SQL can remain offline while Production SQL and both CSV outputs continue normally.
Reference routing model. Each destination requires its own schema, file policy, queue capacity, retry strategy and operational owner.
Source isolation

A slow or unavailable OPC UA server does not invalidate healthy source sessions.

Destination isolation

Failures are contained to the affected queue instead of stopping the full pipeline.

Traceability

Source identity, timestamps and quality remain attached through SQL and CSV delivery.

Source freshnessLast valid update per serverQueue depthPending records per destinationRejected recordsMapping and schema failuresDelivery statusSQL writes and CSV rotation

Why separate DataPaths?

Independent destinations

Write two OPC UA datasets into one SQL model while exporting another dataset to CSV.

Independent policies

Set different polling intervals, field mappings, batching and retry behavior for each flow.

Clear operations

Monitor and troubleshoot every pipeline separately without affecting the other destination.

DataPath A: two sources, one database.

OPC UA 01 and OPC UA 02 are normalized into a common structure and delivered to the same SQL destination. DataPath B independently reads OPC UA 03 and produces controlled CSV files for exchange, archival or offline processing.

Design the right DataPaths for your plant.

Start with your real sources, schemas and delivery requirements.

Discuss a multi-DataPath deployment