Guides

What Is an OPC UA Data Logger and How Does It Work?

By Timuçin Çelik, Founder November 19, 2026 6 min reading
RBS Report logo and the question 'What is an OPC UA data logger?' above a simple flow from OPC UA server to data logger to SQL Server.

An OPC UA data logger is a program that reads values from an OPC UA server on a schedule and stores them with a timestamp, usually in a database. The server holds the live values of your machines. The logger keeps the history. This guide explains how that works and what to expect from RBS Data Logger. Where we describe what the product does, we use our product pages and our own demo, and we say so.

The short answer

OPC UA is a standard way for industrial systems to publish data. A data logger is an OPC UA client that connects to the server, reads the tags you choose and writes each reading as a row with a time. RBS Data Logger does this and writes to SQL Server, so the rows can go into scheduled Excel reports.

What OPC UA gives you

An OPC UA server sits in front of a PLC, a gateway or a machine and exposes its values as tags. Each tag has an address inside the server, and the server itself has an endpoint URL that starts with opc.tcp://. A client needs two things to read a value: the endpoint of the server and the address of the tag.

The server only shows what is true now. If nobody records the values, yesterday's temperature is gone. That is the gap a data logger fills.

What a data logger adds

  • A connection. The logger connects to the endpoint as an OPC UA client, with the security settings your server requires.
  • A tag list. You choose which tags to keep. Browsing the server and ticking tags is easier than typing addresses by hand.
  • Storage. Each reading is written with a timestamp to a database table. One column per tag is a common layout.
  • A way to use the history. Once the values sit in a database, you can query them with SQL or build reports from them.

How RBS Data Logger does it

RBS Data Logger collects data from your OPC UA servers and logs it to SQL Server. RBS Report then builds Excel reports from the logged rows, using your own Excel templates, and can send them by email on a schedule. It runs on Windows or in the cloud.

The setup follows the same order as the list above. In our step-by-step guide we did it on one Windows PC with a test OPC UA server:

  1. We added an OPC connection with the server's endpoint URL, a display name and a connection id.
  2. We opened the OPC browser, ticked three tags and added them as columns of one SQL Server table.
  3. We started the data logger. The management page reported that the data collection engine was READY and showed when the last SQL write happened ("1 s ago" in our demo).
  4. We queried the table and got eight rows for the time window we picked.

Every value in that demo was a simulated signal from a test server, so it shows the workflow, not real plant data.

What a logged row looks like

In our demo the table had an ID column, one float column per tag, and two datetime columns. RealDate is the local time of the PC that wrote the row. OPCTimeStamp is UTC, so in our demo, at UTC+01:00, it was one hour earlier. Keep both in mind when you build reports across time zones or around a daylight saving change.

Security settings

An OPC UA connection has a security policy and a security mode. In our demo we chose None for both, because the test server ran on the same PC and was reachable only from localhost. That is fine for an isolated test and not a recommendation. For a real server, use the policy and mode your server and your site require. Our product pages do not describe the available policies, so we do not list them here. Ask us in a demo if this matters for your setup.

Two ways to run it

In our Data Logger Management page, the data logger can run as a desktop application or as a Windows service. Only one mode collects data at a time, so do not start both. We used the desktop application in our demo.

What to check before you rely on a logger

  • The tag list. Confirm the logged tags are the ones your reports need.
  • The timestamp. Decide whether you report in local time or UTC and use the matching column.
  • The gap behavior. A logger can only record what the server provides. If the OPC UA server or the network is down, there are no values for that period. Ask any vendor how their logger behaves after a connection loss, and test it with your own server.
  • The database. Make sure SQL Server is the right place for your history. For very long histories analysed with SQL, read SQL Server or ClickHouse: which RBS Report logger do you need.

To try it with your own server and tags, see the OPC UA Data Logger page, which also has the demo request.

Frequently asked questions

What is an OPC UA data logger?

A program that connects to an OPC UA server as a client, reads the tags you choose and stores each value with a timestamp, usually in a database.

What does RBS Data Logger store the data in?

SQL Server. RBS Report can then build Excel reports from the logged rows and send them by email on a schedule.

Which timestamps does a logged row have?

In our demo, RealDate is the local time of the PC that wrote the row and OPCTimeStamp is UTC.

Can the desktop application and the Windows service log at the same time?

No. Only one mode collects data at a time, so do not run both.

Is security policy None a good choice?

Only for an isolated test. We used it because our test server ran on the same PC and was reachable from localhost only. For a real server, use what your server and your site require.

What happens to values while the OPC UA server is down?

A logger can only record what the server provides, so there are no values for that period. Ask any vendor how their logger behaves after a connection loss and test it with your own server.

Schedule a 30-minute discovery meeting

Talk to our team about the right solution for your business. The demo and consultancy are free.