I setup a Gateway Network and Remote History Provider. On the Remote Gateway the security for that database is Query and Storage.
I can see the connection works because I’m able to use Tag History/Historian.
Even though it wasn’t in the database I wanted. It’s using the SQL Lite of Remote Gateway.
So I went to Transaction Groups to see if I can pick the database there but it’s not an option in my Data source.
Anyone knows what I am missing? Could it be the firewall blocking the connection?
There is a difference between a history “Provider” and a “Data Source”.
A history provider is only available to the Tag Historian, even if that history provider is configured to use the same database that you want to connect to. You first have to configure a connection to that Database as a Data Source.
Ok, I missed that one. So why it’s only logging the SQL Lite instead of the SQL Express? I’m not connected to the Remote Gateway right now so I can’t double check.
I guess that means I have to connect my Local Gateway to the remote database.
Config → Database → Database Connections
When I setup this connection then its a matter of firewall or something like that.
Maybe I’m wrong, but now I’m thinking that the real benefit of Remote History Provider is the query part and not the storage. If I had setup an explicit connection from the beginning I should have been able to use the database for Tag Historian and Transaction Groups.
By default there is a connection to Sample_SQLite_Database. SQL Express is not, and an installation of SQL Express would have to be provided by the end user and a connection added to the gateway to be used.
Yes a connection must be set up for the Remote Database on the Local Gateway in order for there to be a data source available for Transaction Groups.
For the connection to work there must be network connectivity from the Gateway to the Database. That can be on a LAN or through a Firewall.
Remote History Providers are different than Data sources. A Remote History Provider gives a remote gateway access to a History Provider configured on a Remote Gateway over the GAN. By default it will create a store and forward pipeline for sending data to a remote gateway, but can be configured for Read Only access allowing only querying historical data.
You can add a database connection to the Gateway and also add a Datasource History Provider which will allow you to use the same database for both the Tag Historian and Transaction Groups.
You are right. SQL Lite comes with the installation for quick temporal storage.
Now that I’m back at the server I can see I made a mistake.
I just created that new newDatabase to see that its empty. The table above was the one from yesterday used for testing. I would assume that those tables were made when I set the Local Gateway to start storing remotely using Tag Historian.
It is common to do it that way?
Now that I’m clear that Remote History Provider is only for Tag Historian, I would pick a separate database for Transaction Groups.
I would say it is uncommon not to do it that way.
Just want to make sure you also understand that you can have a Database Connection configured on the gateway to the same database. There is no need for multiple databases unless you are looking for that kind of segregation.
Thank you again @lrose
Hopefully, this post will be helpful to anyone starting out with connecting gateways.