Migration Utility¶

Select Workspace¶

Displays the Select Workspace dialog box, which lists the available Visual DataFlex (VDF) workspaces for the selected VDF Version.

The Flex2SQL workspace manager allows you to work with any version of Visual DataFlex starting with version 4. In environments that have more than one VDF version installed, the workspaces for each version are available.

Select a Filelist¶

Files without Filelist Entry¶

Displays a Windows Open DAT/INT Files dialog box so you can browse to select individual data files (.dat) for conversion.

This option is useful when migration consists of one data file.

Open Last Filelist¶

Opens the most recent filelist used by Flex2SQL.

• See Also: Filelist dialog

Clear List¶

Clears all history from the recently used fileset list.

Icons¶

Icons at the top of the Browse Data dialog box can be used to navigate through the selected file(s). Choose the first icon to hide or show the selected filenames in the left panel of the dialog box. Use other icons to position in the list. Hover the mouse over an icon to learn its function.

Index¶

Controls how the displayed data is sorted. The default is by RECNUM but you can choose another index from the pulldown list to modify the sort order.

Data tab¶

Displays records retrieved from the selected file. Only columns checked in the Columns tab are visible.

Columns tab¶

Displays the column number, name, DataFlex type, index segment, and length in bytes, for each column and allows a column to be shown or hidden. Check the Display option to show a column in the Data tab. When you select a column in the top panel, column attributes are shown in the bottom panel.

You can also right-click the grid in the Columns tab to display a short-cut menu that allows you to select all columns, deselect the currently selected columns, or rebuild the Data tab grid to show the selected columns.

Attributes tab¶

Displays DataFlex table attributes for the selected file.

Extended Attributes tab¶

Displays extended attributes that you can use with Mertech drivers. These are explained in detail in the Flex2SQL Programmer’s Guide.

Intermediate File¶

Displays the contents of the .INT file.

TableSpace Selection Lists¶

The tablespace selection lists at the top of the Analyze Storage Requirements dialog box are used to select the default Oracle tablespaces for the migrated data and index tables.

DataFlex Files¶

The DataFlex files grid displays information for the selected DataFlex files.

TableSpace Info¶

Displays size information for all the tablespaces the current user can access.

Export Options tab¶

Settings in the Export Options tab determine the format and location of the output data.

Oracle SQL*Loader Options tab¶

The SQL Load Options tab contains server-specific settings that determine how the data is loaded.

PostgreSQL Load Options tab¶

If the loader scripts will be run from the client, select the Client Execution option. If the loader scripts will be run from the server, uncheck the Client Execution option.

MySQL/MariaDB Load Options tab¶

If the loader scripts will be run from the client, select the Client Execution option. If the loader scripts will be run from the server, uncheck the Client Execution option.

Enable Trigger to Handle Inverse Key¶

Enables a trigger to automatically manage inverse keys whenever an insert, update, or deletion of a record takes place.

Inverse key fields are additional fields created during data migration to handle indexes with descending index segments. These additional fields allow the driver to scan a set of data in descending order without issuing an order by clause. Inverse keys are also used to support upper case indexes.

Disable Trigger to Handle Inverse Key¶

Disables the trigger to handle inverse keys.

Check Inverse Key Columns¶

Examines the selected table(s) and determines if inverse key columns need to be created.

Remove Inverse Key Columns¶

Removes any existing inverse key columns.

MDF file¶

Browse to select an existing master database file. This is the name of the primary database file. The name must include the full path. Any associated LDFs (log files) and NDFs (secondary data files) must be in the same folder.

Database Name¶

Enter a database name (optional). If no database name is entered, the name given when the database was created is used. The MDF file name is typically the same as the database name.

Select File > Logout from the menu bar to detach the database.

Copy Data from .DAT File to Table¶

Copies data from a DataFlex file to an existing table. Typically, this option is used to copy data to an empty table created using Flex2SQL.

Copy Data from Table to .DAT file¶

Copies data into a DataFlex file from a table on the server. This is normally done on a blank data file.

Erase a DataFlex file¶

Uses the DataFlex zerofile command on the DataFlex file to remove all records from the file.

Erase a Table¶

Deletes all records from the selected table.

Maintenance Menu¶

The Maintenance menu contains commands that are useful in maintaining your file structure after migration. Options are available that make it easy for you to modify your table structure while still maintaining compatibility with your DataFlex application.

Restructure Fields Tab¶

Allows you to add modify or delete fields in the table.

Restructure Index Tab¶

Allows you to add modify or delete indexes for the table.

Restructure Table Tab¶

Allows you to select database settings, enter the table’s root, logical, and display names, and determine whether connection information is stored in the INT file.

Script Tab¶

Shows the script that can be submitted to the SQL Server to propagate the updates to customer sites. Click Save to save the script for the currently selected table. Click Save All in one script to save all the scripts in one file.

INT File Tab¶

Displays the new INT file for the selected table. Click Save to save this INT file. The new INT file can be copied directly from the saved location or it can be copied from the development drive once the changes are committed and the new INT file is generated. If more than one table was updated be sure to save all the INT files.

Log Tab¶

Lists the operations you performed. Click Save to save the log file.

Source Code Tab¶

Lists the DataFlex restructure code for the operations you performed. Click Settings to update the content for the restructure code.

• Generate Source For: Select the radio button that corresponds to the desired VDF version.

• Generate Comments in the source: Select to include comments in the restructure code

• Program Skeleton: Pathname for the starting source file (.src). A Use statement that references the saved INC file is added to this skeleton program. Click Open Source in Studio to open this file in Visual DataFlex studio.

• Add Restructuring code to skeleton program: Select to save the code that performs the restructuring. The restructure code is saved in an INC file.

• Add Login details to source: Select to include a login statement with the server type, server name, user name, and password in the skeleton program.

Click Save to save this source code in an INC file.

Segments¶

Displays all the fields in the currently selected index.

Primary Key¶

Checked if the selected index is a primary key.

PCTFREE¶

Specifies the space reserved in each of the cluster’s data blocks for future expansion. The value of the parameter is expressed as a whole number and interpreted as a percentage. (Oracle only)

Initial¶

The initial size in kilobytes allocated for the newly created Oracle index on the Oracle server.

Next¶

The size the Oracle index will be increased by when it is full.

Tablespaces¶

The tablespace where the indexes were created.

• See Also Restructure Index Tab

INT File Relationships¶

Creates a foreign key on the SQL server.

Deletes a relationship in the .INT file.

Synchronizes the SQL foreign key with the INT relationship (can result in relationships being deleted on the SQL server)

Lines up the right tree with the left key.

Collapse the tree. Only the top level is visible.

Expands the tree so all levels are visible.

SQL Table Foreign Keys¶

Creates a relationship in the .INT file.

Deletes a foreign key from the SQL table.

Synchronize the SQL foreign key with the INT relationship (can result in relationships being deleted in the INT file).

Collapse the tree. Only the top level is visible.

Expands the tree so all levels are visible.

Note: If a relationship is missing the corresponding entry in the tree is labeled Missing and marked with a red X.

SQL Script for Creating Tables¶

Generates scripts to create tables, indexes, primary key constraints, and sequence objects (where applicable).

SQL Script for Post Loader steps¶

Generates scripts for post loader steps. Enter the SQL script file name and path to start. This includes estimating statistics, adjusting sequences, and updating text columns to restore stripped out CRLF pairs and restarting Identity column values.

SQL Script for Adjusting Sequence Definitions¶

Generates scripts to initialize auto increment columns (in PostgreSQL) or sequences (in Oracle) to be the highest number in the table plus one.

SQL Script for Enabling Inverse Key Triggers¶

Generates scripts for enabling inverse key triggers. Enter the SQL script file name and path to start.

SQL Script for Disabling Inverse Key Triggers¶

Generates scripts for disabling inverse key triggers. Enter the SQL script file name and path to start.

SQL Script for Dropping objects¶

Generates scripts for dropping indexes, tables, and other objects such as sequence definition on Oracle or a table in any SQL database engine. Enter the SQL script file name and path to start.

Generate .INT File from .DAT¶

This option is used when you want to generate the .INT file from your DataFlex DAT file. Based on the DAT file structure, Flex2SQL generates an .INT file respecting the current settings defined in Flex2SQL.

Generate .INT File from Table/View/Synonym¶

This option is used when you write a DataFlex program that accesses a table that was created or modified on the target DBMS. Before you can access the table from a DataFlex application, you must bring the table into the DataFlex environment by generating the .INT file, adding an entry for it in the filelist and generating .FD files for compilation.

When the dialog box is first displayed, the previously selected Fetch objects are retrieved from the target database and displayed in a grid on the left side of the dialog box.

Overwrite Existing File¶

If this option is selected, a table with the same name is overwritten during migration. By default, the option is turned off, and you are prompted before a table is overwritten.

Erase Table before Data Migration from DAT¶

If this option is selected, the contents of the target table are erased before the contents of the DataFlex data file are copied. By default, this option is turned off.

Save current settings for the future¶

If this option is selected, preferences are saved for future use.

Disable Status Panel¶

If this option is selected, the progress panel is disabled during migration.

SQL Script Generator¶

SQL Scripts for creating tables, indexes, sequences, and other database objects can be terminated with just a line feed (LF) or with a carriage return (CR) and LF. The SQL generator creates an ASCII file. By selecting the appropriate end of line character, the file can be viewed in the UNIX or Windows environment. For UNIX, select the LF character as a terminator. For Windows, select the CR and LF characters.

File Casing¶

You can control whether existing file casing is used or upper or lower case conversion takes place. This option is used in conjunction with MySQL, MariaDB and PostgreSQL conversions to determine if the objects (tables, columns, indexes, etc) are created with upper or lower case letters.

Error Handling During Data Migration¶

Set options to handle errors during migration.

Language Support¶

If your computer is configured with multiple languages, you can choose the display language from this pulldown list.

Put Server Name into INT File¶

If this option is selected, the SERVER_NAME token is placed in the .INT file. The server name provided in the login command is used. By default, this option is turned off (unchecked box).

Put Schema Name into INT File¶

If this option is selected, the SCHEMA_NAME token is placed in the .INT file. The Schema displayed in the Filelist dialog box is used as the schema name. By default this option is turned off (unchecked box).

Put Database Name into INT File (For MS SQL Server only)¶

If this option is selected, the DATABASE_SPACE_NAME token is placed in the .INT file. By default this option is turned off (unchecked box).

DFPath To Use Sub-tab¶

Check boxes¶

When you check one of these boxes, the contents of the associated sub-tab are included in the DFPath that Flex2SQL searches to locate DAT or INT files. Check boxes are listed in priority order, so when User Defined is checked, files in the User Defined sub tab are searched first.

• User Defined: Check this option to include additional paths you enter in the User Defined sub-tab.

• Use DFENV.cfg: Check this option to include paths listed in the DFENV.cfg sub-tab.

• Workspace: Selected by default if the Open type is Workspace. When this option is checked the DFPath includes the paths listed in the Workspace sub-tab.

• Registry: When this option is checked, the DFPath includes the paths listed in the Registry sub-tab.√

• Path: Check this option to include paths listed in the PATH sub-tab.

User Defined Sub-Tab¶

Paths you enter in this sub-tab are searched first when the User Defined option is selected in the DFPath To Use sub-tab.

DFENV.cfg Sub-Tab¶

This sub-tab is populated using the dfenv.cfg file and has an entry like: DFPATH=df31dusrdata;df31dwasa.

Browse to select the location for the dfenv.cfg file. This option is usually only used by console mode DataFlex.

Workspace Sub-Tab¶

This sub-tab is populated using the filelist path (without the filelist name) and the data path from the current workspace.

Registry Tab¶

This sub-tab is populated from the SystemDFPath in the Windows Registry [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeData Access WorldwideVisual DataFlex17.0Workspaces]

Path Sub-Tab¶

This sub-tab is populated using the PATH environment variable.

Main DataDir¶

All auxiliary files created by Flex2SQL during data migration will be created in this directory. This is usually the data file directory. This directory is the first path in the DFPath. If you want to change this directory, add this path first in the User Defined sub-tab.

Filelist¶

Shows the currently selected filelist.

Enable Migration Logging¶

This feature is useful in identifying bad data in the DataFlex database, which might result in incomplete migration. Mertech’s drivers have various levels to define tracing granularity.

The Errors Only option is especially useful during migration as it logs only the errors rather than all driver calls to the server. If bad data is encountered during migration, the target back-end raises an error. On receiving this error, the driver logs the contents of the record buffer to the log file, stops migrating that file, and moves on to the next file.

The user can look at the trace file, correct the data in the DataFlex file, and then run the migration process on the file again. The most common problems are in data fields.

Enable Application Logging¶

This option sets the registry key to turn on the driver traces to allow you to generate driver level traces while you are running your application.

Note: This option severely affects performance if left on and generates very large trace files. Remember to turn this off once you have generated the trace you need.

Detail Level¶

Allows you to control how detailed a trace you want the driver to generate. For most data related problems, Error Only is the best option.

In order to determine which trace level is most appropriate for you, here is a description of the available options. Notice that the trace levels build on the previous one:

1. Errors Only logs only native SQL error related information and driver identification. No other detailed information is included in the log file. The message(s) are preceded by ‘ERROR’ or ‘WARNING’. This option also minimizes the size of the trace file.

2. Debug is the default trace level. It includes the previous level’s information in addition to logging all the database calls issued by the application, like FINDs, SAVEs and DELETEs, LOGIN, LOGOUT and the embedded SQL calls. Besides logging these commands, the call parameters are also logged.

3. Detailed 1 includes the previous level information and adds information about the MOVE commands from/to File field buffers and the calls to the Get_Attribute and Set_Attribute commands.

4. Detailed 2 includes the previous level information and adds text file generation through the driver.

5. Detailed 3 includes all the information from the previous level, this option contains the most comprehensive level of trace information. It logs all calls to the driver and when they start and when they finish.

• See Also: Driver Trace Report

Enable Migration Report¶

This option turns on the report that displays any errors that may have occurred during the migration(s), the license and version of the migration tool, a table creation report, an index creation report, and a data migration report.

• See Also: Migration Report

ASCII Nr.¶

Enter the ASCII number (between 0 and 255) for characters in the OEM character set that should not be translated.

OEM To ANSI¶

Select this option to convert the OEM character set (used by DataFlex) to the ANSI character set.

Use Epoch Year¶

The Use Epoch Year setting is used when the DataFlex database contains 2-digit years. All dates are saved as 4-digit dates on the target database and any year on or before the epoch year value is treated as a new year in the millennium 2000.

Program Displays 2-Digit Year¶

If your program displays 2-digit years and you want a 4-digit year extracted from the table on the target server displayed, uncheck the Program Displays 2-Digit Year option. After retrieving the data field, the driver converts the date to 2-digit year and returns just the last two digits to the runtime for display.

Filelist Options¶

Convert Database¶

Displays the Convert DAT to Table dialog box, where migration options are selected and the file conversion is initiated.

Add Driver Prefix¶

Adds the driver prefix (e.g., Sql_drv) to the root file name entry in the filelist. This effectively tells the DataFlex runtime to treat the file as a non-DataFlex file. When an open command is issued, the DataFlex runtime passes the open operation to the driver associated with the file.

Remove Driver Prefix¶

When you remove the driver prefix, DataFlex runtime treats the file as a native DataFlex file. Using driver prefixes is a good way to switch between your DataFlex and newly migrated tables on the server.

Select DF Files¶

Highlights all the files in the filelist that do not contain the driver prefix and for which the DAT file can be physically located by searching directories in DFPATH.

• See Also: Preferences - DFPATH Tab

Select Tables¶

Selects all entries in the filelist that have a valid corresponding table on the target server. The command may take a few seconds, depending on the number of files in the filelist, because the target server’s data dictionaries are used to verify the existence of these tables.

Select All¶

Selects all DF files and tables.

De-Select All¶

Deselects all highlighted entries.

Invert Select¶

Toggles the marked and unmarked entries. All marked entries are unmarked and all unmarked entries are marked.

Show Only Unique Root Names¶

Since DataFlex works with file numbers and not file names, two entries with the same name at a different filelist slot are considered two separate files. It is quite common to have files of the same name at different locations as alias files. If this option if checked, duplicate names are hidden. If the file has already been migrated it is not necessary to check this option.

Schema¶

Select the owner for the converted files from the pulldown list.

Migrate Non-DataFlex File¶

When this option is checked, Flex2SQL uses the appropriate driver to read data from the source file and perform the data migration.

The most common usage is when you are migrating Pervasive.SQL files. You must have the driver for Pervasive installed in the Flex2SQL bin directory with the proper license registration.

.INT File Directory¶

Specify the location of the .INT files generated by the driver for Pervasive.SQL.

Note: Care must be taken not to over write these .INT files with the ones generated by Flex2SQL; otherwise, you cannot open the Btrieve files again. You must generate the Flex2SQL .INT files in a separate directory.

Creation Options¶

Radio buttons at the bottom of the dialog box determine which files are created on the server and whether data is migrated.

Conversion Options¶

Buttons at the bottom of the dialog box are used to set preferences, save the fileset and associated settings, and perform the conversion.

File Statistics¶

Statistical information for the table name shown at the top of the dialog box displays in the status bar at the bottom of the dialog box.

Table and File Name¶

Table Style¶

Determines whether the SQL table uses DataFlex Recnum Table or RowId Table style processing.

Multi-Directory File Handling¶

Used to handle creation of files with the same names in the current database.

It is common in the DataFlex and Pervasive environments to create files with the same name residing in different directories. For example each directory might be dedicated to a specific company, for example CompanyA/customer.dat and CompanyB/customer.dat. The DataFlex program knows based on the directory path, which file to access.

Mertech introduced the concept of “Table Suffix” or “Table Prefix” to support multi-company files. Each file name can now be assigned a custom prefix or postfix value to be prepended or appended to the file name. The table is created as “<prefix>RootName” or alternatively “RootName<postfix>” on the server. This approach allows different files to reside in the same database without conflict.

To specify a prefix, select the Prefix radio button and enter the prefix value. To specify a suffix, select the Suffix radio button and enter the suffix value.

Create All Fields as NOT NULL¶

You can set NOT NULL attributes for a given field type that persists for all tables during migration. When a field is created as NOT NULL, SQL databases expect a default value. You can specify the default values or let the driver assign it.

Checking this option automatically selects the Create all ASCII Fields as NOT NULL, the Create All Numeric Fields as NOT NULL, and the Create all Date and Datetime Fields as NOT NULL options. You can also select each of these options individually.

Use System Defaults¶

This option allows you to select the system default or to enter your own default value for NOT NULL fields.

Inverse Key and Overlap Handling¶

Name¶

Field/column name (read-only).

Type¶

Structural type assigned to the field by DataFlex.

There are two scenarios in DataFlex where the overlap field type is used. One is to concatenate several fields and consider them as one field. The other is to create a field from a subset of a field.

The driver treats the first scenario logically and it functions similarly to how native DataFlex treats an overlap. When an overlap field is selected as part of an index to an SQL Table, it may not be created due to the number of segments the index is composed of. These are SQL limitations.

Partial overlap (underlaps) fields are created as a native column only if the field is part of an index, otherwise it is treated the same as the first scenario.

Length¶

Field length in bytes. Position the cursor on a field length, then click the Length column header to display the Field Changes Pop-up.

Native Type¶

This is the data type that will be used for this field on the SQL back-end. Choose the desired type using the drop-down list or click the column header and choose the type from the Native Type Pop-up.

Note: Default field mappings can be made in the Tools > Preferences > Field Mappings tab.

AutoInc.¶

Used to select the auto-increment field. RECNUM is the default auto-increment field.

Index¶

Main index associated to a field. Position the cursor on a field index, then click the Index column header to display the Field Changes Pop-up.

not NULL¶

Indicates whether or a null value is allowed in this field. Leave this option unchecked if null values are allowed. SQL databases require that fields specified as NOT NULL are given a value during an insert. The driver automatically inserts a default value if a value is not specified. Fields that are part of an index are always created as not NULL, and Flex2SQL does not allow you to change this because it directly affects FIND performance using indexes based on those fields. You can enter a default value in the panel on the right side of the screen, or by positioning the cursor on a not Null value, and clicking the column header to display the Field Changes Pop-up.

The Fields tab also contains a panel on the right side of the screen that allows you to enter additional information for the selected field.

Default¶

The default value that will be assigned to a not NULL field.

Note: Global settings for the default values for not NULLL field types are made in the Migration Options Tab.

Relates To¶

The file and field from a parent table that this field is related to.

Mask¶

Special data mask applied to the field.

Check Constraint¶

Allows you to specify the name of a constraint that you may have defined for a particular field in the target/destination server.

Inverse Key¶

Field name used for the Inverse key.

Field Changes Pop-up¶

Click the Length, Index, or not NULL column heading in the Fields tab to display the Field Changes dialog box. Allows the default value for not NULL fields, the check constraint, and mask type to be changed.

Primary Key¶

The Primary Key tab shows the index number in the DataFlex file and the fields that comprise the index and are used to create a primary key on the target server. By default, Index 1 is selected in a DataFlex file to be the primary key in the table, but the user can change this. For fast and efficient access, it is suggested that the primary key be comprised of columns that give maximum selectivity.

Flex2SQL selects the Inverse Key checkbox in the Primary Key tab and Native Index tab if one segment is DESC or C/S.

Primary Index¶

RECNUM is the primary index in a DataFlex file. Whenever you perform any operation using RECNUM, the RECNUM index (Index.0) is used. If you are using only the DataFlex database, there is no choice; RECNUM is the primary index. However, with other databases, you can specify any index as the primary index. In ORAFlex, RECNUM, by default, behaves just like the RECNUM field in DataFlex. However, the user can select another index to be the primary index. This is controlled during migration or can be changed after migration in the intermediate file by changing the PRIMARY_INDEX token to an index number specified in the intermediate file.

For ORAFlex, you can select an index created on a non-numeric field to be the primary index. But to make this work, you have to change the definition of the RECNUM field in your .FD file from a numeric to a string data type. For example, if you have a definition like:

#REPLACE VENDOR.RECNUM |FN21,0

In your .FD file, you will have to change this to:

#REPLACE VENDOR.RECNUM |FS21,0

Native Index¶

The Native Index tab allows you to control which indexes are created on the server. If you do not plan to change your DataFlex program, Mertech recommends that you use the default selections that are presented to you by Flex2SQL. The primary key is not selected because the primary key is always created.

Use Database¶

Select the database where the converted data will be saved on the back-end table.

Filegroups¶

An SQL Server database can be partitioned using files and/or filegroups. A filegroup is simply a named collection of individual files grouped together for administration purposes. A file cannot be a member of more than one filegroup. Tables, indexes, text, ntext, and image data can all be associated with a specific filegroup. This means that all their pages are allocated from the files in the filegroup. Log files are never a part of a filegroup.

Note: Microsoft Windows Azure SQL Database does not support filegroups.

There are three types of filegroups:

Primary: The primary filegroup contains the primary data file and any other files not specifically assigned to another filegroup. All pages for the system tables are allocated in the primary filegroup.

User-defined filegroup: User-defined filegroups are any filegroups specified using the FILEGROUP keyword in a CREATE DATABASE or ALTER DATABASE statement.

Default filegroup: One filegroup in each database operates as the default filegroup. When SQL Server allocates a page to a table or index for which no filegroup was specified when they were created, the pages are allocated from the default filegroup. Only one filegroup at a time can be the default filegroup. Members of the db_owner fixed database role can switch the default filegroup from one filegroup to another.

If no default filegroup is specified, the primary filegroup is the default filegroup.

SQL Server 2000 can work quite effectively without filegroups; so many systems do not need to specify user-defined filegroups. In this case, all files are included in the primary filegroup and SQL Server 2000 can allocate data anywhere in the database. Filegroups are not the only method that can be used to distribute I/O across multiple drives.

Members of the db_owner fixed database role can back up and restore individual files or filegroups instead of backing up or restoring an entire database.

With this new feature in Flex2SQL, you can now select the filegroup where you want to place your tables and index files.

Legacy Index Support¶

This option allows the user to use existing field name formats for inverse keys.

Use Regular Save During Migration¶

This option overrides the default migration mode (bulk insert) that is designed for high-speed migration of data from a DataFlex database SQL Server database. Due to a bug in MS SQL Server, there are some cases where data is not correctly loaded into the table for tables with large number of columns. The bug has been reported to Microsoft.

Select Use Regular Save During Migration to use regular inserts to copy data. This is significantly slower than the default option.

This option is useful if you have problems during the migration. Records are inserted one by one instead of in bulk. This lets you migrate all records that do not have any errors and skip problematic ones. If you are migrating in bulk and one row in a bulk group has problems, the entire bulk will fail to migrate.

Bulk Copy Options¶

To allow the user more flexibility during the data conversion Flex2SQL now includes the capability of customizing the bulk copy settings for the data migration. The user can specify the number of rows per batch or kilobytes per batch.

Note: Only one value can be specified; either rows or kilobytes.

Data Tablespace¶

Allows the user to select the name of the Oracle tablespace where the data will be stored once it is converted. The space available in the selected tablespace is displayed.

Index Tablespace¶

Allows the user to select the name of the Oracle tablespace where the index will be stored once it is converted. The space available in the selected tablespace is displayed.

Legacy Index Support¶

This option allows the user to use existing field name formats for Inverse Keys.

Functional Indexes¶

A functional index is an index defined on the result of a function applied to one or more columns of a single table. Functional indexes can be used to obtain fast access to data based on the result of function calls.

Functional indexes can be used to select a custom sort order. If you select the Custom radio button the associated list box is populated with sort options including e.g., Arabic, ASCII7, Big5, and French.

Use Regular Save During Migration¶

This option overrides the default migration mode that is designed for high-speed migration of data from a DataFlex database SQL Server database.

This option is useful if you have problems during the migration. Records are inserted one by one instead of in bulk. This lets you migrate all records that do not have any errors, and skip problematic ones. If you are migrating in bulk and one row in a bulk group has problems, the entire bulk will fail to migrate.

Use Storage Clause¶

Applies to TEXT and BINARY fields when calculating storage requirements.

Table Extent Information¶

Use Database¶

Select the database where the converted data will be saved on the back-end.

Select Table Handler¶

Selects the table type or storage engine for the migrated files. MySQL & MariaDB support the following storage engines:

Table Creation Parameters¶

Enables and disables access to the parameters below. If this option is not checked the parameters below are not included in the CREATE TABLE statement.

AVG_ROW_LENGTH¶

This option is used to pre-allocate space for large tables with variable size records. If an average row length is not specified Flex2SQL uses the value from the DataFlex file property “DF_FILE_RECORD_LENGTH” as its default.

CHECKSUM¶

This option maintains a checksum for all rows (MyISAM). It also slows the performance when updating but facilitates the search for corrupted tables. This option is turned ON in Flex2SQL by default.

COMMENT¶

A 60-character text string used to better identity the table and its content. Flex2SQL uses the value from the DataFlex file property “DF_FILE_DISPLAY_NAME” as its default.

MAX_ROWS¶

This option is used to pre-allocate disk space. It is the maximum number of rows you plan to store in the table. Flex2SQL uses a calculation (MIN_ROWS * 1.5) as its default.

MIN_ROWS¶

The minimum number of rows stored in the table. Flex2SQL uses the value from the DataFlex file property “DF_FILE_RECORDS_USED” as its default.

PACK_KEYS¶

This option compresses the indexes saving disk space. Due to its compression mechanism it makes updates slower and reads faster (MyISAM & ISAM). Setting it to 0 disables packing of keys. Setting this to DEFAULT (MySQL 4.0) tells the storage engine to only pack long CHAR/VARCHAR columns. This option is turned ON in Flex2SQL by default.

PASSWORD¶

Encrypts the .frm file with a password. This option does not apply to the standard MySQL version.

DELAY_KEY_WRITE¶

This option delays key table updates until the table is closed (MyISAM). This option is turned OFF in Flex2SQL by default.

ROW_FORMAT¶

Defines how the rows should be stored. Currently this option only works with MyISAM tables. Flex2SQL checks if DataFlex has compressed the table. If compressed it defaults to “Dynamic” otherwise it defaults to “Default”.

Use Database¶

Select the database where the converted data will be stored on the back-end.

Use Schema¶

Allows the user to select or enter a new schema (owner) name for the table being converted. If this field is left blank the default schema is used.

Data TableSpace¶

The tablespace name that will contain migrated data tables. It is advisable that index and data tables be created on two separate tablespaces, residing on separate hard drives.

Index TableSpace¶

The tablespace where the index files will be created.

OIDS – Object Identifiers of Rows¶

Object Identifiers of Rows - This optional clause specifies whether rows in the new table should have OIDs (object identifiers) assigned to them. The default is to have OIDs.

Note: If the new table inherits from any tables that have OIDs, then WITH OIDS is forced even if With OIDs is not selected.

Use Regular Save During Migration¶

This option overrides the default migration mode that is designed for rapid migration of data from a DataFlex database to a PostgreSQL database. This setting does a direct save, which is not as fast as the default migration option.

This option is useful if you have problems during the migration. Records are inserted one by one instead of in bulk. This lets you migrate all records that do not have any errors, and skip problematic ones. If you are migrating in bulk and one row in a bulk group has problems, the entire bulk will fail to migrate.

The Problem¶

This problem occurs if VDF17.0 is uninstalled. Required runtime files and Codejock OCX controls, which are used by the Flex2SQL menus, are unregistered when VDF17.0 is uninstalled.

The Solution¶

Re-register the Codejock controls:

Start a command prompt as an administrator

CD C:Program Files (x86)Mertech Data SystemsDB DriversDataFlexbin

Regsvr32 Codejock.CommandBars.v13.4.2.ocx

Regsvr32 Codejock.ReportControl.v13.4.2.ocx

Note: If you are running a 32-bit version of Microsoft Windows, the Mertech Data SystemsDB DriversDataFlexbin directory is in Program Files instead of Program Files (x86).