You can use the command mode to run the Migration Wizard. You can use either DSNs (Data Source Names), or MDBs (Microsoft Jet database files). In either case, you must specify both the Repository 1.0 database (source) and the Repository 2.0 database (target). The following are the parameters to qualify the source:
/SN
Source DSN/SO
Source Owner/SU
Source Username/SP
Source Password/SD
Source Database
and these are the parameters to qualify the target:
/TN
Target DSN/TO
Target Owner/TU
Target Username/TP
Target Password/TD
Target Database
Note The parameters /SD, SO, /TD, and TO are needed only with SQL server.
Example (using DSNs)
MigRepV2 /SN=DSN=MyV1DSN /SO=Owner /SU=MyName /SP=MyPassword /SD=MyV1db /TN=DSN=MyV2DSN /TO=Owner /TU=MyName /TP=MyPassword /TD=MyV2db
Example (using MDBs)
MigRepV2 /SN=C:\V1Repostry.mdb /TN=D:\V2Repostry.mdb
The following are additional parameters that you can use as indicated:
/TF
to force the creation of the target Repository 2.0 file if it does not exist./R
to rename the Repository 2.0 database using the same name of the Repository 1.0 database, and modify the Repository 1.0 database name with the "_old" string, for example, MyV1.mdb becomes MyV1_old.mdb.
Note If you don't supply any parameters MigRepV2.exe will run in the interactive mode.
A log file, MigRepV2.log, is generated. This may be checked for any errors. All error messages that would be reported to the user in both Interactive and Command Mode are written to this log file.