sql server dts:
First, let me quickly say that, so far, this is the best, most concentrated
site I have found with worthwhile information concerning SSIS. Kudos to all
who have contributed.
My questions: I'm still trying to get up to speed with SSIS. (I liked DTS,
cautious of SSIS) In my situation, I have a folder that I need to monitor
for the deposit of .xls files containing data. Once, all these files are
present during a month, I need to import the data into separate SQL tables
along with some calculated data. In addition, some of the data I need to
cross reference with an existing SQL table to convert a product descr to a
product code...so, there is some data manipulation occurring. Originally, I
had set this up with a ForEach loop and had separate DataFlow tasks to
process each .xls file...this was working sometimes, and sometimes I was
getting security errors which made me uncomfortable with relying totally on
SSIS to accomplish this. So, I put together a quick VB.NET app to not only
monitor the folder for the .xls files, but to also put in some reporting,
and to send daily email notifications on the status of the files. Along
with this, I created separate SSIS packages for the processing of each .xls
file. I now want to launch these packages from my VB.NET app. Currently, I
am launching these via the Public Shell function passing it a string to run
the .dtsx package from a command line (btw, the packages are stored in a
File System). Is this a poor way to do this? Are there any documents with
examples showing how to perform a function like this properly? As a side
question...when I ran this via the ForEach loop, I couldn't figure out how
to make the package stop when execution completed, is this a parameter
setting? I also found an SSIS example on the internet where they had a VS
project contain both the VB code pages and the SSIS packages...is that a
