The driver supports migrating schema maps and internal files created with the 6.0 version of the driver so that they can be used by the 6.1 driver. By migrating these files, you can continue to execute the same SQL statements that you did with the 6.0 driver, while leveraging the advantages of the 6.1 driver. Note that new objects discovered by the driver are mapped using the behavior of the 6.1 driver by default. See "Mapping objects to tables" for details.

Note: You can configure the driver to generate legacy virtual keys for new objects by setting LegacyVirtualKeys to true. See "LegacyVirtualKeys" for details.
To migrate an existing 6.0 schema map and internal files, using the SchemaMap property, specify the location of your configuration file used for the 6.0 driver and set SchemaFormat to NormalizeAll. At connection, the driver modifies your configuration and internal files so that they are compatible with the 6.1 driver. In addition, the driver creates copies of the original files in the same directory, if you want to continue using the 6.0 driver while you complete your upgrade. The copies of the original files take the following form: 
<existing_file>-<file_version>.<extension>
For example, version 2 of a file named myserver.config would be renamed: 
myserver-2.config
Note: The versions of the configuration files and internal files are not synched. Therefore, the files will likely have different numbers appended to the them for the 6.0 versions of the files.
Using migrated schema maps and internal files have the following limitation:
  • The driver supports only normalized relational views (SchemaFormat=NormalizeAll) for migrated schema maps and internal files.