The speed of data exporting depends on several factors:
- Speed of the data extraction from the source database.
- Network bandwidth (if the source or target database is accessed through the network).
- Speed of the data importing by the target database.
Of course, you can make improvements by proper administration of those things. For example, you can define database indexes, optimize the server(s) operating memory etc. But there are some other important things you should consider when configuring your export and data migration processes, and this is where the Database Tour export tuning can help.
Database Tour has a set of tools to improve your data export performance. Some of the tools are applied on the source database side, some on the target side, and some affect both sides. Using the tools properly can speed up the exporting process in hundred times! Here are some recommendations on how to use them:
- Export only needed table columns. Pay attention to BLOB and long text columns. Check this at Field Mappings export step. These settings affect both sides of the exporting process.
- Use calculated fields at Field Mappings step only when it is really necessary. Try do to all needed data transformations in your source SQL code if possible. These settings affect the source side.
- Try to play with Fetch size environment option to find the optimal performance. Usually, the number of records allocated in one data window equals to 2 * fetch size. This setting affects the source side.
- Try different combinations of Memory saving and Commit interval export options (if you export data to a database). Use Batch mode option whenever possible. These settings work on the target side.
- If Use raw data option is available, and if you sure the data conform to the target format, apply it. The option works on the source side.
When you are exporting data from the command line or action file, bear in mind the following:
- If you are not using the command line parameters for field mappings (/columns, /FieldMappings, /FieldMappingsFile), all fields will be exported. If not all fields are needed, use field mappings parameters explicitly.
- Command line parameters /FetchSize, /MemorySaving, /UseSQLParameters, /UseBatchMode, /CommitInterval, /UseRawData are equivalents of above mentioned interface options.
See also
