← All use cases

OPC UA to SQL Database

Turn selected OPC UA values into trustworthy, query-ready SQL records—without placing database logic inside the control network.

Industrial data, structured for the systems that use it.

OTDataMule reads only the nodes you select, applies a consistent data model and writes timestamped records to an approved SQL destination. Local buffering and controlled retries keep the flow dependable when networks or databases are unavailable.

OPC UA ServerPLC · SCADA · Machine
OTDataMuleRead · Normalize · Buffer
SQL DatabaseHistorian · MES · Analytics

A controlled path from tag to table.

01 — Select

Choose OPC UA nodes

Collect only the process values, status fields and timestamps required by the use case.

02 — Normalize

Shape each record

Map source values to consistent names, types, units and quality metadata.

03 — Protect

Buffer and retry

Queue records locally during interruptions and resume delivery without losing sequence.

04 — Store

Write to SQL

Insert structured data into the approved schema for reporting and downstream applications.

Built for operational reality.

Quality-aware records

Preserve source timestamps and OPC UA quality information so consumers can interpret every value correctly.

Database isolation

Keep SQL credentials and write behavior controlled at the integration layer instead of distributing them across machines.

Predictable load

Use deliberate sampling, deadbands and batching to avoid noisy polling and unnecessary database growth.

Resilient delivery

Store-and-forward behavior reduces gaps when the IT destination is temporarily unreachable.

Reusable schema

Give BI, MES and analytics teams a stable structure instead of source-specific tag conventions.

Observable flow

Monitor connection state, queue depth and write outcomes to make data delivery measurable.

Typical deployment boundary

OT side

  • Read-only OPC UA access where possible
  • Explicit node allowlist and sampling policy
  • Local queue sized for expected outages

IT / application side

  • Least-privilege SQL service account
  • Approved schema, retention and indexing
  • Monitoring for latency and failed writes

Validate the flow with your own tags.

Start with one machine, one dataset and one measurable outcome.

Discuss your OPC UA to SQL use case