Need to create a "done" file step.

Question

Need to create a "done" file step.

BI_Developer

SSC Eights!

Points: 908
More actions
September 14, 2017 at 9:11 am

#339229

Hi,
I've created a package that copies two flat files from a remote location to a standard ssis flat file network share. I need to push this package on a daily schedule, so I need to create a simple flat file probably titled "done" So that another process checks for this file's existence so when it does exists, it triggers the process to run. It doesn't need much content. What would be the most optimal way to realize this?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Thom A SSC Guru Points: 99130 More actions · Answer 1

Why have a schedule another process to check for the existence of something, and then run the package? You can run SSIS packages from Agent, then there is no need for an external application. if you then want to log the completin, you could use a table on your SQL server.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

BI_Developer SSC Eights! Points: 908 More actions · Answer 2

Without diving deep into my need. The job I need to create the "done" file for, has to run in a prod environment, while the job that needs to check for the "done" file has to run in a dev environment, thus, I need the job in dev to check a file share for the existence of the file.

Lowell SSC Guru Points: 323518 More actions · Answer 3

I've seen this as a cross check that the big file is not still currently being written to; ie the file exists, and would be open but potentially if read would return partial information. bog gig-size files might still be hammering away for several minutes, and still be open/being written to.

checkign for the "done" file is the step to assume the critical file is not still open.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Chris Harshman SSC-Forever Points: 42192 More actions · Answer 4

A workaround I've used for the situation Lowell describes is to create the file in a "working" folder, then once done, move it to a "ready" folder.

On the receiving side, if all it is doing is checking if a file exists on a network share, then copy it, you may not even need SSI. That could easily be a PowerShell or Windows CMD batch file scheduled in Windows task scheduler.

ZZartin SSC-Dedicated Points: 30920 More actions · Answer 5

I have this requirement alot. I use a pretty straight forward powershell script for it, you specify a file to wait for, the minimum age of the file(prevents picking up old files), how long to wait for a file(after which it fails if nothing has shown up) and a location to copy or move the file to, and it checks for file locks before doing anything with the file. If you want to go with the done file you would just set up your job to look for the done file when it arrives do whatever you were going to do with the other files. Upload doesn't seem to be working but if you want the code i can post it.