Windows service design loading data into database

[John Samson]

I am building a windows services scheduler that shall fetch file and
import the data into a SQL Server according to the predefined schedule.

My idea is to create two application
1) App 1 - Windows Services schduler - that will run component two
according to the schedule
2) App 2 - fetch data file using FTP, process and load the data file
into SQL Server using bulk copy. This process could take very long

Which are the following design will suit best for this tasks and what
are the pro and cons?
1) Build App 2 as an console executable with parameter input. The
windows services will execute this exe use shell command
2) Build App 2 as DLL and App1 use this DLL part of its application
3) Build App 2 as Service Component

Thanks.


*** Sent via Developersdex http://www.developersdex.com ***