Read up on package configuration. It's intended to be use for situations like this.

You could add a Conditional Split in the data flow to prevent unwanted records from reaching the database.

You can also add a Row Count before your database in order to...

I see we're quickly approaching the 7000 posts count.

Congratulations Roy. I had the pleasure of being the co-founder of our local chapter just a few months ago.

As far as speakers are concerned, I have to agree with...

...and of course....

LMGTFY

SQLROCKS

SPWHO2

You might expect that it should, but don't assume that it will.

Was your package being run as a job? If so I suspect that the SQL Server Agent account lacks the sufficient rights. Try fixing now instead of later.

Jack Corbett (7/23/2009)

---

I haven't been as active on the forums, except this thread, lately because of vacation and catching up at work. I'm working in ASP.NET MVC and having...

M Jones (7/23/2009)

---

Hi Alvin (love the gif!) ,

Thanks for the input. Mind to tell me how to do this stuff though? We would like to be able to...

There's is no easy way to do what you're trying to do, at least not the way you want to do it.

You may want to try another possibility. Create...

Yes, the Conditional Split is what should be using.

Try ISNULL(ProductID) == FALSE to select the rows you want.

Use the Conditional Split in the data flow to filter out the records. Direct the ones you want to your table. Ignore the others.

If you need to monitor the progress of a running package then I recommend that you turn on the package logging and enable at least all the error and warning...

Be careful about trying to develop a package that can handle too many files changes. Such a package might be able to run "successfully" even if the order of...