We are working on a project related to migrating a legacy system from an old SQL server to the latest version . Along with that , the Factory SQL , Old Ignition transaction groups also we are migrating on a new server.
There is a challenge we face related to this migration is that Legacy system extensively used stored procedures to get the data from the PLC and directly stored in to the legacy system DB. As per the new suggestion given by the PLC /SCADA team , They would prefer to store the row data in a Ignition DB and then suggesting us to take the data from the DB via any ETL tool.
As per the technical team , The suggestion given by the PLC team will increase the workload only because Ignition itself is having a built in mechanism to call the stored procedure directly from Ignition itself. However , the challenge here is , Incase if a failure happens in the stored procedure logic , the data will be lost coming from the PLC… What is the best way to migrate the legacy system from an old version to a new version.
Is Igntition capable for storing the data in a temporary location incase if a failure happens while calling the stored procedure directly from the Ignition ? Please share your thoughts as we are nearing to the project deadline
Thanks in advance