Ignition Explained SQL Bridge Module
Welcome to Ignition Explained. We’re going through the Ignition Modules one by one and talking about what you get with each of them, and how Corso uses them to build a project.
There always seems to be questions about what each module does, and doesn’t do. So we’re going through them one by one. If you missed the first video on Vision Module, then check it out here. This time we’re talking about the SQL Bridge Module. For those who don’t know SQL stands for Structured Query Language. Learn more of the basics in the Acronyms Are Hard: SQL Edition.
We need to make a note: Most of the SQL Bridge information below is part of the core functionality of Ignition. The major addition for the SQL Bridge Module is for Transaction Groups.
SQL Bridge Module
SQL Bridge is going to allow you to connect to your SQL database. Inductive Automation calls it a “Swiss Army Knife” and we like that so it’s making it in the blog. Technically it uses transaction groups to move data bi-directionally between OPC Servers and SQL databases.
The Second Part
We talk about this a lot in the videos. Ignition is a platform and allows you to pick and choose the items that you need for your solution. SQL Bridge is an amazing edition to the Vision Module. Now we can both see the data with Vision Module as well as having a bi-directional data transfer between OPC Server and SQL Databases. SQL Bridge is going to allow us to communicate with your ERP, your inventory data, and more. Typically if you’re working on a computer software made in to 2000’s (that’s not Oracle), you’re probably going to be using this to integrate it.
Or comments? Or something else? Please feel free to reach out and ask. We’re here for everyone to talk about all the great ecosystems that we work. You can reach Dave Dave@CorsoSystems.com or call/text him at (773)241.0004.