What are the risks involved in the migration?
No migration is risk-free, but the Escort SQL approach is far simpler and safer than a traditional legacy database migration. Because it requires a small team and simple steps, the entire project will succeed. A traditional migration requires coordination of a far larger collection of people and resources; the complexity of managing the traditional migration is a leading cause of failure. Escort SQL enables the database migration through a series of simple and incremental steps that (1) can be thoroughly tested and (2) have quick fallback scenarios. If production problems arise, you can easily drop back to the Enscribe files. With the Escort SQL Journaling product, you can keep the old Enscribe files synchronized with the new SQL tables to allow a fallback with no loss of data. Once the database has been migrated, any changes to the applications (such as using embedded SQL) can be performed incrementally, changing, testing, and installing one module at a time. A traditional database mi
