How to Improve The Conversion Speed

As for our approach to database migration, we follow a structured methodology, which is shown in the screenshot below:

Our process involves migrating the schema first, followed by the data.
You can find more detailed information about this approach in the following article: How to Optimize Migration of Schema and Data.

This article explains how to configure schema-only migration to avoid including data conversion in the same step, as this can significantly impact the migration time.
Once all database objects have been migrated, you can perform a data-only migration, excluding the schema, as described here: Data Extraction.

To optimize large-scale migrations, the following combination of strategies should be used to reduce downtime and increase efficiency:

Enable parallelism:

Using the parallel mode in Ispirer Toolkit allows the migration process to use multiple sessions, significantly improving data transfer speed.

This approach splits the data into smaller chunks that can be processed concurrently.

You can find more details in the documentation here: Using Parallel Mode.

Optimize data segmentation:

For large tables, consider segmenting the data using the Data Cut feature or Query Mode.

This allows transferring data in smaller, more manageable portions, reducing overall load times.

More details are available here: Large Tables Migration.

Schema and data migration tuning:

Adjusting the migration settings and configurations tailored to your specific schema can help speed up the process.

Additional recommendations are outlined here: Schema and Data Migration.

Optimized network throughput:

Using a high-speed network connection and optimizing database settings can significantly improve performance.

To optimize migration speed, we recommend performing a schema-only conversion with trace mode enabled.

Instructions for disabling data migration are provided in the first article linked above.

After completing this step, please share the following files for detailed analysis:

• sqlways.log
• sqlways_imp.log
• sqlways.trc

If you have already conducted such a conversion, please forward the existing files.

Subsequently, perform a data-only conversion as per the instructions in the following article: Migration to Existing Database.

Once complete, kindly share the generated files:

• sqlways.log
• sqlways_imp.log
• sqlways.trc

We would like to draw your attention to several factors that can influence the speed of data export during the migration process.

These include:

• performance of the ODBC driver,
• network capabilities (local or cloud-based),
• the performance of source and target databases,
• hardware resources of the machines involved.

Additionally, antivirus software and networking equipment can limit data transfer speeds.
We could assist you with troubleshooting and optimization for this purpose, our technical specialists require the following information:

Information about source and target databases:

1. Source Environment: Operating System (OS), CPU, RAM, and network bandwidth (Mbps).
   
2. Database Environment: Database version, the number of tables, row count per table, and table definitions (column types and sizes).

Ispirer Toolkit environment:

1. Toolkit Environment: OS, CPU, RAM, and network bandwidth (Mbps).

Recommendations for speed optimization:
To enhance conversion speed, we suggest the following approaches:

• Using Multiple Sessions: Run multiple instances of the tool to parallelize the conversion process.
• Optimizing Large Object Conversion: For large objects, consider using the Data Cut option, query mode, or configure data volume limits.

For further details, please refer to:

Schema and Data Migration
Large Tables Migration

If you have any questions or face any difficulties, please contact our support team at support@ispirer.com