If I have 100 machines, the Microsoft SQL database cpu is spiking 75%, and I have multiple projects using both the same database, tag provider, and historian- Then, would I benefit from having a second SQL database for some of the queries? Would it be possible to split my tables in this manner to …

Would help, but would also be a nightmare to maintain. Throw more cores at your current DB.

Scaling vertically is far, far, far easier than scaling horizontally. Get familiar with profiling SQL server and the diagnostic tools you have available, also. It’s very likely you’re leaving performance on the table in some way(s).

When you say scaling vertical, you mean adding cores? I want to better understand the options and tradeoffs. What is the nightmare part for more than one database? I thought it was typical to have more than one database.

Have you checked out the server sizing guide? Search the main IA site or this forum, should be a link to it. Multiple databases are common, but they are generally designed for architectural reasons, net performance issues. Say you have two sites, both have Ignition both have their own DB. Site A D…

Thanks What is an example of a nightmare situation that people want to avoid with having a second database? Locations having different databases makes sense to me. I am wondering about situations where someone wants to use a database in a more traditional way. Another person wants to stretch the…

Stupid question but are you using SQL Server Express? Some things you should be doing now: Don’t use star queries (SELECT * FROM table;) Don’t let your tables grow excessively; separate active tables from historical tables. Call queries from the gateway; not the clients.

I appreciate the help. For the purpose of this thread, I want to learn about having more databases.

More work. With one, you have the default DB, and only have to specify the DB connection based on what scope you’re working in. Potential for error. Writing to the wrong DB, dropping a table on the wrong DB, deleting data on the wrong table. More management, your DB should be backed up and or repl…

Thanks, yes. Goal Have one database to really push the limits of. Have one database to use more conservatively. Avoid the two impacting their separate performance. Concerns If I understand correctly, potential errors in designating the proper database are the primary concern, deleting and drop…

Sure, one tag provider, just select on a per tag basis in the history option, which DB it is going to. If you use transaction groups, the same thing, you can only select one. Note that, to my knowledge, a named query etc can only select from one DB. If you have data A in DB A and data B in DB B, …

Inductive Automation Forum

Multiple databases

Ignition

Matrix_Engineering August 8, 2022, 4:51pm 14

Using more than one database connection in a project Ignition

Hi, I am working in a project where I need to consult data from more than one database (Postgres and MySQL). I am not using tags because I need to change the text of the queries dinamically, so I am writing the queries as text in some invisible labels, and making my charts execute those texts as SQL queries. I have several connections defined in the gateway configuration (and they really work). The problem is that in the “Projects” menu I can choose the default database for the project, but I c…

Restricting access to specific projects Ignition

Hi, I have a couple of different projects on our gateway. Is it possible to make the projects visible depending on the user who is logging in both on the gateway and in the designer? The motivation behind this is to have the client log in to our gateway and open their project from there in order to preview it and we can present it to them like that. I am obviously not interested in showing the client the other projects we are working on. Is such an restriction possible in Ignition? I have pl…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled