An .sdi  file used in an import operation must be generated on a server with the same data dictionary version and sdi version as the import server. The version information of the generating server is found in the .sdi  file: 

{ "mysqld_version_id":80019, "dd_version":80017, "sdi_version":80016, ... } 

To determine the data dictionary and sdi version of the import server, you can check the .sdi  file of a recently created table on the import server. 

The table data and index files must be placed in the schema directory for the import server prior to the import operation, unless the table as defined on the export server uses the DATA DIRECTORY  or INDEX DIRECTORY  table options. In that case, modify the import procedure using one of these alternatives before executing the IMPORT TABLE  statement: 

•Put the data and index files into the same directory on the import server host as on the export server host, and create symlinks in the import server schema directory to those files. 

•Put the data and index files into an import server host directory different from that on the export server host, and create symlinks in the import server schema directory to those files. In addition, modify the .sdi  file to reflect the different file locations. 

•Put the data and index files into the schema directory on the import server host, and modify the .sdi  file to remove the data and index directory table options. 

Any collation IDs stored in the .sdi  file must refer to the same collations on the export and import servers. 

Trigger information for a table is not serialized into the table .sdi  file, so triggers are not restored by the import operation. 

Some edits to an .sdi  file are permissible prior to executing the IMPORT TABLE  statement, whereas others are problematic or may even cause the import operation to fail: 

•Changing the data directory and index directory table options is required if the locations of the data and index files differ between the export and import servers. 

•Changing the schema name is required to import the table into a different schema on the import server than on the export server. 

•Changing schema and table names may be required to accommodate differences between file system case-sensitivity semantics on the export and import servers or differences in lower_case_table_names  settings. Changing the table names in the .sdi  file may require renaming the table files as well. 

•In some cases, changes to column definitions are permitted. Changing data types is likely to cause problems. 

## 13.2.6 INSERT Statement 

INSERT [LOW_PRIORITY | DELAYED | HIGH_PRIORITY] [IGNORE] [INTO] tbl_name [PARTITION ( partition_name  [, partition_name ] ...)] [( col_name  [, col_name ] ...)] { {VALUES | VALUE} ( value_list ) [, ( value_list )] ... 

