J
John Lee
Hi,
I developed a scheduler as service and kick off another console application
"DTSRUN.exe" to run a dts package
ProcessStartInfo psInfo = new ProcessStartInfo(command);
Process process = Process.Start(psInfo);
I have two questions need your help:
1. When I stop my scheduler service, if the dtsrun.exe are still running,
the process will be terminated, how could I kick off a detached process that
will run dtsrun.exe in different process and will not be terminated even the
launching process is terminated?
2. Another strange issue we have here is when the dtsrun.exe is launched,
the following command will be started:
DTSRUN.EXE /S DBServerName /E /W True /N DTSPackageName /A
FileName:8=FileTobeProcessed.txt
This works fine for small files but the DTSPackage hangs there around 28600
records if the filetobeprocessed.txt contains lots of data and the problem
is consistent and reproduceable; Even stranger thing is if I manually issue
the above dtsrun.exe command and it works fine; it seems only if that
command is issued from my service (running under a domain service account
with full permission to database server) with big files will will this
problem - hanging there never finish...
Could anyone shed some light on this?
Thanks very much!
John
I developed a scheduler as service and kick off another console application
"DTSRUN.exe" to run a dts package
ProcessStartInfo psInfo = new ProcessStartInfo(command);
Process process = Process.Start(psInfo);
I have two questions need your help:
1. When I stop my scheduler service, if the dtsrun.exe are still running,
the process will be terminated, how could I kick off a detached process that
will run dtsrun.exe in different process and will not be terminated even the
launching process is terminated?
2. Another strange issue we have here is when the dtsrun.exe is launched,
the following command will be started:
DTSRUN.EXE /S DBServerName /E /W True /N DTSPackageName /A
FileName:8=FileTobeProcessed.txt
This works fine for small files but the DTSPackage hangs there around 28600
records if the filetobeprocessed.txt contains lots of data and the problem
is consistent and reproduceable; Even stranger thing is if I manually issue
the above dtsrun.exe command and it works fine; it seems only if that
command is issued from my service (running under a domain service account
with full permission to database server) with big files will will this
problem - hanging there never finish...
Could anyone shed some light on this?
Thanks very much!
John