Ah, got you (I think). So the SSIS package is not failing, but you have another job step that kicks off before all the inserted rows have been committed. In that case you want to take a look at some of th FastLoad properties in the Advanced Editor of the OLEDB Destination. Specifically there is a property called FastLoadMaxInsertCommitSize which has a default value of 0. Contrary to what you might think, a value of 0 means the complete opposite of "don't wait for any rows to be inserted before committing them", it actually means "wait until all rows have been inserted before committing them".

If you change the value to 1000, 10000, 50000 or whatever, those number of inserted rows will be committed as a batch.

There are 3rd party monitoring tools such as SQL Sentry's Performance Advisor that offer features like SQL Agent job chaining that is not available within SQL Server natively...unless, as you stated, you use WAIT FOR.

Regards

Lempster