I was wondering about the best approach to pulling data in from csv files with Ignition…
I have multiple different CSV files that need to end up in SQL Server Data Tables. Some files are just simple Data tables and can be accessed with OleDB csv driver and pulled in as data. Some of the others have to be interpreted as they have header sections and a strange format to how the data is stored.
I would like to contain all of this in Ignition but I think this might be a bi beyond it’s functionality…?
How would I do it with Ignition using the SQL Bridge Module?
Other ways that this can be done:
- Write a custom app to do this
- Use Sql Server Integration services
- Use Sql .Net Stored Proc
- Write a Ignition module for CSV file data source using the API. (This is possible isn’t it?)
- Does Ignition have server side scripting that can be called to handle reading in csv files?
So in your oppinion what would be the best design and most robust approach. I would like to contain all my data collection code in the same product and not have it scattered around all over the place fo support reasons.
I hope to hear some other intereresting approaches for this!