# Differences

This shows you the differences between two versions of the page.

 guides:migration-toolkit:command-line:sqlways-ini:windows-section [2019/06/11 00:26]127.0.0.1 external edit guides:migration-toolkit:command-line:sqlways-ini:windows-section [2019/11/16 11:07] (current)darya.prikhodkina 2019/11/16 11:07 darya.prikhodkina 2019/06/11 00:26 external edit 2019/11/16 11:07 darya.prikhodkina 2019/06/11 00:26 external edit Line 2: Line 2: ====== Sqlways.ini File - Section [WINDOWS] ====== ====== Sqlways.ini File - Section [WINDOWS] ====== - This article describes sqlways.ini file [WINDOWS] section and the options it contains. ​ + This article describes sqlways.ini file'​s ​[WINDOWS] section and the options it contains. ​ ^  Option name  ^ Description ​ ^ ^  Option name  ^ Description ​ ^ - | **GCMD_AFTER_IMP_CMD** | Specifies a command that will be executed after importing each database object (table, view etc). This command is used in the general command file only. \\ SQLWays creates the general command file to make possible ​the importation of large number of database objects (tables, views etc) at once. See the /GCMD option for more information. \\ The general command file invokes command files for each database object using the CALL command. The GCMD_AFTER_IMP_CMD option allows specifying a command that will be placed after each CALL command. | + | **GCMD_AFTER_IMP_CMD** | Specifies a command that will be executed after importing each database object (table, view etc). This command is used in the general command file only. \\ SQLWays creates the general command file to make it possible ​to import a large number of database objects (tables, views etc) at once. See the /GCMD option for more information. \\ The general command file invokes command files for each database object using the CALL command. The GCMD_AFTER_IMP_CMD option allows specifying a command that will be placed after each CALL command. | **Example:​** **Example:​**