The Use Regular Save During Migration (SQL Server only) means that when it is checked, SQL puts recnum in sequence on backend which meaning they won’t match the sequence from DataFlex. If the option is on, then the recnum will follow the DataFlex sequence on the backend. When this option is on, the migration takes longer. Flex2SQL contains facilities for high-speed data migration, including generating SQL*Loader scripts and text files for Oracle and bulk copying of data to MS SQL Server, making it easier to transfer very large databases with both drivers. The SQL scripts enable you to create tables and indexes outside the tool. The high-speed data migration is the default option.
Posts Tagged ‘Migration’
Preserving Recnum During Migration
Monday, February 25th, 2008Creating a Migration Trace from Within Flex2SQL
Sunday, February 24th, 2008In this article we will explain how to create a migration trace to troubleshot problems:
Cannot Open Flex2SQL at the Second Time
Tuesday, February 19th, 2008After downloading the setup and installing it, you can open and migrate tables properly using Flex2SQL. But if closing it and trying to open it again you receive the message below and can’t more open the Flex2SQL:
can't open table TABLE=flexerrs(247) erro number: 75 line number: 113789
This issue is due you don’t have the flexerrs.dat in the new filelist.cfg you selected to convert the tables neither have it in the PATH. To fix it, just copy the flexerrs.dat to the folder from the filelist.cfg you selected or add one folder that has the file in your PATH.
Flex2SQL Conversion Stops
Tuesday, February 19th, 2008In using Flex2SQL for record transfer, it stops without any apparent errors before completion. The problem was due to the DATE_ACQ field, more specifically the value of a leap year (for example, 2-29-1900). DataFlex does not care about leap years, but other databases do. The problem is solved by modifying the errant dates.