So previously we were using Data Set tags to store are user specific data but we ran into a problem where is we wanted to add a new setting for are users we ether needed to go back and edit all of are scripts that looked at the Data set tag to included what ever new row was added so ive found that t…

At this point in time ive decided and been give the go ahead to learn enough about SQL to use it so I will be move on in that direction and at this point in time it seems like the next big step is just getting a layout for the data base and start messing around with it thanks for all the ideas and s…

Hmm ok so you recommended to save that data to like are SQL data base and pull it in from there Not a bad idea but im not vary familiar with that type of data manipulation and how I would store it and call it to be used so its probably better i stick with just using something that is on a tag.

Don’t let an unfamiliar topic scare you off. This is actually a perfect application to learn the way the DB works and how it is applicable here. For beginners I would recommend using Named Queries to insert data into and get data out of a DB. If you are already using a dataset for your scripts, y…

Consider setting up a SQLite DB: Connecting to SQLite | Ignition User Manual Connect Ignition to the PostreSQL Database It's basically a file that is typically stored on the same filesystem as the Ignition gateway. Very easy to set up, very easy to interface…

[image] Chris_Bingham: first step in migrating This. Do not leave anything production-related in SQLite. Use it to learn SQL, but for production, learn to install and use a real database. I recommend PostgreSQL and its derivatives, but even MS SQL Server (boooo! hissss!) is better than SQL…

Well we are currently using MySQL for are history so I assume I would just make a folder on are MySQL server to store this all to. I can spend a bit of time messing around with it to see if I can get an idea of how to get that working and stored properly/ where to even start with trying to use SQL. …

[image] William_Howard: ... so I assume I would just make a folder on are MySQL server to store this all to. No, you would create a database and in that database you would create the required tables. There are endless articles and video tutorials on the web.

A version of this..yes. Except, 'folders' do not exist in the context of the DB. Instead... As @Transistor alluded to, it would be beneficial to separate "user-entered data" from other "Ignition Historian-entered data". You could do this by creating a separate database on the same server, where you…

Alright thanks im still trying to figure out how I would even layout the Schema to be able to hold the data for each of are users without needing multiple schemas per user well leaving it open to add more columns later when needed.

If you share a bit more of what you are wanting to store and what you do with it in ignition you may get some more specific help here. I do not believe you would need separate schema(s) for each user, but rather probably just one and then create a few tables within that schema, you may only need a …

Storing User Specific Data

Ignition

ryan.white February 6, 2025, 6:18pm 2

Save to/Load from DB and stuff the data in a perspective session custom property. Load on session startup or login. Write on change, or maybe on session shutdown.