SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Overview of SQL/MX Migration

HP NonStop SQL/MX Database and Application Migration Guide—540435-005

1-7

Migrating From Enscribe to NonStop SQL/MX

If you are still using legacy Enscribe databases and applications, consider migrating

them to NonStop SQL/MX, which is an industry-standard relational database.

Currently, there is no automated tool to convert Enscribe databases and applications

directly to NonStop SQL/MX. If you want to migrate from Enscribe to NonStop

SQL/MX, follow these steps:

1. Use the Escort SQL product from Carr Scott Software Inc. to convert your Enscribe

database and applications to NonStop SQL/MP.

2. Write SQL/MX applications to take advantage of new SQL/MX functionality.

3. Convert SQL/MP tables to SQL/MX tables as a future project.

For information about the Escort SQL product, see the ESCORT SQL™ User’s Guide,

which you can obtain from Carr Scott Software Inc. at this Web site:

http://www.carrscott.com/evaluation_prog.shtml

Migrating From Another Database Vendor to NonStop SQL/MX

If you are using another database vendor, you might consider migrating to NonStop

SQL/MX because of these advantages of NonStop SQL/MX and the NonStop platform:

•

Scalability

•

24 x 7 database availability

•

Data integrity

•

Mixed workload support (OLTP and business intelligence applications)

•

Total cost of ownership (TCO)

To migrate from another database vendor to NonStop SQL/MX, contact your service

provider for assistance. For more information, see Assistance With Migration on

page 1-20.

Risks of Different Migration Paths

Each migration path has a different level of risk. Migration risks include downtime of

the application or database and difficulty falling back to a previous version. Use

Table 1-2 to help you choose a migration path that will have the least risk and impact

on your production environment.

Note. If there is sufficient market demand, Carr Scott Software Inc. might consider modifying

Escort SQL to support direct Enscribe-to-SQL/MX migrations. If you or your customer deems

this functionality to be critical to your project, please send a note and background on the

project to harry.scott@carrscott.com.