Just a note, the database connection name in the advanced install for the OEE project is different in the text for item 2 compared to the screenshot using “-” instead of “_” in the text which causes errors (that are probably not entirely obvious errors to the target audience of these projects) in the logs when you go to create tables if you use launchpad-oee instead of the correct launchpad_oee for the database name.
Also, in the OEE project’s Production Summary view it says “Runime (mins.)” instead of “Runtime (mins.)” on the header.
Perhaps you should reports these to Sepasoft?
I don’t think Sepasoft has anything to do with these projects, Just trying to help clear up any confusion on the Launchpad projects that appear to be geared towards people who are first getting started with Ignition.
Ignition only, using Sepasoft, or using any of the number of MES-Lite packages various integrators have developed over the years is a larger discussion entirely 
This is an exchange project, not Sepasoft.
1 Like
Deer Ignition Launchpad Team,
Launchpad OEE uses SQLite by default and is promoted as a plug-and-play solution. For a production deployment, is SQLite generally considered sufficient, or is it recommended to migrate to MySQL/PostgreSQL from the start?
I'm mainly concerned about long-term data retention, performance, scalability, and backup/recovery. Has anyone successfully run Launchpad OEE on SQLite in production, and at what scale?
If an external database is recommended, are there any migration guides or best practices for converting the Launchpad OEE schema and scripts from SQLite to MySQL/PostgreSQL?
I would appreciate any guidance from users who have deployed Launchpad OEE in real-world manufacturing environments.
1 Like
Hello, I wonder whether there are also any steps in order to use MSSQL database instead SQLite. Thanks.