Storing Wide Table Data Advice

I have been wondering if storing data to a wide database table over a gateway network is a good idea. In my current architecture, I have several Ignition Edge devices in the field that transmit data to a cloud Ignition Gateway in the cloud via MQTT.

Now I know the historian will take into account the store and forward capabilities and that's great but for the wide tables that I store to every so many seconds, if the Edge device loses connection for an hour, that's an hour of data lossed in the wide table.

I'm wondering if that logging to a wide table is best done at the edge using the SFUpdate script to a database in the cloud through the gateway network so that hour of data is buffered in the edge store and forward and then when it connects all those records are inserted in the database with the timestamp of when the data is collected, not stored.

I don't know if that's too much load on the connection between Edge device and the central gateway or not.

Can anyone speak on this?

Edge cannot use database calls. Full stop.

If you need wide table storage, Edge is not the answer.

Consider installing standard Ignition at your remote sites. Then you can script all of the wide database operations you need. Consider also using a local database in each site, and then using database-native replication to push the content to one or more central databases.