Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How much production downtime will be required to convert to NonStop SQL?

April 26, 2017convert downtime nonstop production sql

0

Posted

How much production downtime will be required to convert to NonStop SQL?

1 Answer

0

Posted

Very little, even if you have 1000s of Enscribe programs and 100s of gigabytes of Enscribe data to convert. The application must be stopped and immediately restarted, one time, in order to execute application object files that are enabled (or prepared) to use Escort SQL. By using the Escort SQL Journaling feature, the NonStop SQL tables can be loaded and synchronized (at low priority) while the production application is still up and executing. When the SQL tables are ready, the application must be shut down and restarted to start using the SQL tables as the production database. You may wish to convert the Enscribe DB in stages, a few files/tables at a time to minimize risk. With Journaling, each stage will require a shutdown and immediate restart of the application processes.