Thanks John and Lynn. I am bundling my tasks into sequence containers appropriately and things appear to be working fine now that I understand the underlying issue.

Feedback most appreciated!

Gary

Thanks folks. I am now finding some details that indicate I can change the precedence constraint to include the OR ... expression. In small tests this seems to...

Did some more testing and have a simple example of the issue I am seeing:

Create a package. Add a SQL task that performs "Select 1" and stores the 1...

My apologies. The example I used is bogus and I somehow reversed my logic. The problem I encountered appeared once I had created views from queries I had...

Understood. I wish tSql had a native IsInteger...

But either way, a value like 'NG123' would fail the ISNUMERIC test, so I expected it to be filtered before the CAST...

The WHERE criteria (current iteration) attempts to limit the result set to values that match this pattern:

A999A

Where "A" is an alpha, and "9" is a numeric. The actual length...

Well, thanks, but as I mentioned, this is greatly simplified and the real WHERE clause is significantly more involved. I picked this one simply to illustrate what I think...