Logging to Local MSSQL Database

Hi all, I am wanting to get some community knowledge on the best way to log from Opto22 to an MS SQL Server. Currently we are doing it through OPC UA and having an OPC UA client on a system on the local network that is archiving the data to an MS SQL Server which is also on the local network.

Is there a more direct way of storing this data? We do not want to use the Opto22 system as storage, we just want to find a fast way to pass the data on from Opto22 into a database system. We have used Node-RED previously in the past however OPC UA seems to be more reliable.

The goal is to log sensor data in the most direct/efficient way possible to an MS SQL Server hosted on the local network.

I assume you are using groov EPIC with PAC Control.

Node-RED might still be the best approach for this. Perhaps you have already searched the forums for it:

All I/O and PAC Control tags are also exposed via the RESTful API, if that is an option for you to access them from MSSQL database via API calls.

2 Likes

Node-RED is a great way to go. We have many systems using it and it has been very reliable.

2 Likes

That’s really interesting… Can you expand on this a bit?
We’ve found that OPCUA is pretty heavy on the CPU vs Node-RED.
I have a personal project that is moving 300 to 500 tags per minute into SQLITE with Node-RED and had zero issues for years. (Node-RED also drives the select statements on that db which holds around 1.5 million records and returns the data in about 2 seconds).

1 Like