August 12, 2014 at 2:58 am
I have a ssis package that reads data in flat files into a sql 2008 r2 database. The flat files are expected to be uploaded by users to a web server.
I have a couple of questions:
1. how can I be sure to only kick off the package when the files are completely uploaded to the server? I suspect that even testing for the existence of a particular file in the depositing folder may result in the package starting before the files have finished writing to disk. Is this a problem that others have encountered?
2. Since I have to work with separate web server and db server should I transfer the files to the db server (where ssis resides), or should I install ssis on the web server (at the cost of a sql licence), or should I persuade network admin to allow me to map a drive to the web server from the db server and have ssis read the files remotely?
Is there a 'best practice' solution - I certainly can't find one documented on the web?
Thanks in advance
August 12, 2014 at 5:55 am
I also faced this type of problem from ssis packages.
we have two possibilities do this work
1) schedule the package for there interval timings.
2) what data is getting for web services, first u can load that data into one temp table then u can test the data .
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply