Welcome to EMC Consulting Blogs

What does this sort of loop do to CPU utilization? Although this is a simpler approach I would have thought a script task may have been better if you want to sleep for any significant amount of time where other processes might be running on the server.

I would use a script task with only one line:

System.Threading.Thread.Sleep( 10000 )

It is 10 seconds (parameter is in milliseconds), it does not use CPU and it is simpler to read (but I born as a programmer...).

Marco

Hoi,

Probably the easiest way to do this is an 'Execute Sql Task' with a direct input query:

waitfor delay '000:01:10'

or use a  WAITFOR TIME '22:20' to start at a specific time.

Gr. Ronald

Why not a SQL Agent that invokes the SSIS package on the whole?

I mean, since the Sql agent is meant for scheduling, wont it be better suited to do this job?

If a package is dependent on an existence of a file, which is deposited on an FTP server on an 'indeterminante' time line, the above waitfor might come in handy. Can anyone think of other, more elegant way of doing what I described?

Hi Guys,

DATEADD( "ss", 5, @[System::ContainerStartTime]  ) >  GETDATE()

I put the above sleep function into a for loop within another for loop.

You run this for a while and it actually causes a memorly leak.

I wanted to automate the processing of some AS cubes, basically the sleep was used within the for loop to wait until Data Warehouse had been loaded.

This seems to happen on both 32bit and 64bit SP2 versions of SSIS.  

I watched this run on 64bit server, used up to 7Gb or memory before I killed it.

Thanks

Mick

I have a file watcher task.  How can I create an infinite loop around the whole package?

Basically I want to watch for a file dropped by SSRS and then send it to an FTP.  I want it ALWAYS running instead of scheduling it to run every minute in the SQL Agent.  Any ideas?

Jamie and others,

A big standing O for your post on this.  We googled " 0xc002F304 after vmware migration" and found 1 post at http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2816544&SiteID=17

which led us to your blog.

I used the waitfor delay logic in an EXEC SQL Task  and my pkg now runs fine, although I tuned it down to a 1 second wait.

For anyone else who encounters this, here's why our SSIS pkg choked. We migrated to a VM ESX  2 proc quad core machine. The SQL Server was partitioned with 30 GB , GB RAM and 2 virtual processors.  During my pkg, I fill a variable with a specific record count I'm looking for and if the count was > 0 I triggered 2 file tasks back to back to generate an alert.  I believe that the ESX and SQL Server together were too fast for the package to run these tasks side by side.  The first File Task kept failing when run in batch, but I could execute it successfully with a right click-execute.  Wierd.   After adding the delay immediately after the filling of the variable count and before the first file task, the job now works fine in batch run mode.  Thanks for the idea and this post.  I hope others see this in the future and it helps.

Nice help...thank u

Hi all ROnalds soultion is the most elegant