![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all! I have a scheduled DTS package that transfers data from a table to a flat file every night. The package and job works just fine but I have found something strange in the log file. (At least something that I can't understand...) When the DTS package was first created the file was put on a server , lets call it serverA. That server was changed for a new one some time ago, the new server is server B. At that time I changed my path in the DTS package to use an alias for the new server. The path used to be \\server A\... and I changed it to \\aliasB\... (aliasB is an alias for serverB) The file has been created every night as supposed to and everything has worked just fine. When I now look in the Output file (under the advanced tab in Edit Job step for the scheduled job) the path there is the old path, that is \\serverA\... The file is created at serverB so I was expecting to se the alias in the path in the output. DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: Copy Data from Results to \\serverA\...Step DTSRun OnProgress: Copy Data from Results to \\serverA\... Step; 1000 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 1000 DTSRun OnProgress: Copy Data from Results to \\serverA\... Step; 2000 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 2000 DTSRun OnFinish: Copy Data from Results to \\serverA\...Step DTSRun: Package execution complete. Why is the wrong path still in the output file? ServerA doesn't exist anymore.The file is there every morning on serverB. So why isn't the output file telling what path the DTS job is using? Where is the path in the output file stored? What have I done wrong? Many questions. ;-) I hope that someone can help a confused soul |
![]() |
| Thread Tools | |
| Display Modes | |
| |