Here’s an overview of the steps i take when working with historian but note that i’m not an ignition expert or anything so there may be a few things that i get wrong, but theses steps work for me:
I set up my database connection within Ignition gateway(This step may vary depending on the database, but ignition’s documentation is enough to get you there).
Go to my project and change it’s default database to my new database.
Look for all my tags that i want to have an history of and enable the history property.
Don’t forget that Ignition won’t save any data until you choose a storage provider on the tag property;
You don’t need to configure one by one, you can choose a bunch of tags and then enable history for all of them while they’re selected;
Take a good look at the deadband settings on the tag history settings, it’ll make sure you’re only saving what you actually need and not clog up your database with useless data;(check documentation and/or Inductive university)
From this point onwards, your data will start to be logged in the database BUT your data will be saved in a manner that is not human readable, if i understand it correctly, it’s saved that way because of efficiency but you won’t be able to understand raw data looking directly at the database table.
Fortunately, inside Ignition this data is very easy to access and understand, ignition takes care of the processs of making it readable. So, whenever possible, work with your data inside ignition, use the efficient way it saves and queries data to your advantage and if you need to view this data outside ignition, there are simple ways of doing it, like using a report or a script like system.tag.queryTagHistory() that will retrieve the data for you and it’s quite easy to export data.
To be clear you can query this data directly and make it readable outside ignition, but you’re just making things harder for yourself this way.
Sometimes you still have to make this data easily available and readable outside ignition, like when you have to use a reporting software that is not ignition’s own reporting module, then, i would recomend you save the data you need to show using transaction groups.
Now, how do you show the tag history data you’ve saved? That depends on the kind of data that you want to display but you’ll mostly work with Tag History bindings and, as always, the documentation is pretty good on explaining this part, and i find the setup screen very intuitive anyway:
About the datatypes, you should just keep in mind that you can’t plot strings on graphs, otherwise just show data in a way that makes sense for the user and remember that data is not information.
On the first project i worked on 99% of my tags that had history could be renamed and could have different units, so every table and every graph had to be dynamic, dynamic pen name, dynamic unit, dynamic table column name etc… And Ignition is very capable and it gives you all the tools you need, but if you want to do anything more complex, get very familiar with datasets, scripts, indirect bindings, python for loops, SQL queries, custom properties on objects, templates and udts and how to work with them.
I hope my english is clear enough, and Boa Sorte!