471,336 Members | 1,409 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,336 software developers and data experts.

Windows service design loading data into database

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


*** Sent via Developersdex http://www.developersdex.com ***
Feb 13 '06 #1
0 1164

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Mark | last post: by
4 posts views Thread by Gordon | last post: by
6 posts views Thread by Chris Marsh | last post: by
3 posts views Thread by Mika M | last post: by
3 posts views Thread by mohithmohith | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.