Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq:migration-toolkit:load-parameterization [2019/06/13 18:00]
127.0.0.1 external edit
— (current)
Line 1: Line 1:
-====== How to Parameterize Login Information After Import Script Generation ====== 
- 
-You can use environment variables to specify the **SERVISE**,​ **PASSWORD** and **USER** for the whole run in //​**sqlways_all.bat**//​. But first you need to specify those environment variables in the SQLWays, so that it used them in all the bat files with the commands, like: 
- 
-{{:​faq:​migration-toolkit/​load-parameterization.png|}} 
- 
-The Password is specified as **%PASSWORD%** here. 
- 
-So, as the result you will have bat files for data and ddl loading with the commands like, e.g. for Oracle: 
-  sqlplus %USER%/​%PASSWORD%@%SERVICE% @calendar_ddl.sql 
- 
-All the bat files are run using the //​**sqlways_all.bat**//​ file with the command like: 
-  sqlways_imp.exe /​bat=sqlways_all.bat 
- 
-So, all that is left to do is to update the //​**sqlways_all.bat**//​ file with the following **SET** commands before the **CALL** statements: 
-  set USER=ora 
-  set PASSWORD=pass 
-  set SERVICE=ora 
- 
-As the result the **SQLPLUS** command will be executed as follows: 
-  sqlplus ora/​pass@ora @calendar_ddl.sql 
- 
-So, changing just three values in the sqlways_all.bat file, you can control which user, password and service name must be used for the whole load. 
- 
-\\ 
----- 
-=== More about Ispirer Systems === 
-[[https://​www.ispirer.com|Ispirer Home Page]] 
-[[https://​www.ispirer.com/​products/​database-migration|Database Migration]] 
-[[https://​www.ispirer.com/​application-conversion|Application Conversion]] 
-[[https://​www.ispirer.com/​download|Downloads]]