June 25, 2008 at 8:34 am
crever (6/25/2008)
That's almost exactly what I said... whatever...
Sorry, I wasn't seeing the forest for the trees when I read your initial post. I was focused on keeping everything inside the data flow task. My disconnect was that I couldn't find how to put an expression inside the data flow task.
June 25, 2008 at 9:57 am
One final question and I think I have this thing done. I have it working for one of our three banks as follows:
1. Does the record count in an Execute SQL task and stores it in a package variable (WFRecordCount).
2. Linked the Execute SQL task to a Data Flow task which will export the actual data. Changed the link to an expression and entered @WFRecordCount > 0 for the expression.
3. Linked the same Execute SQL task to another Data Flow task which will write exceptions to a log file when no records are found. Changed the link to an expression and entered @WFRecordCount == 0 for the expression.
In testing I changed the SQL statement in the Execute SQL task so I could get predictable 0 and > 0 results. It does do as expected.
My question: I have to repeat this process for two other banks. Is it legal to link both of the Data Flow tasks into a single Execute SQL task which will count the records of the next bank (and repeat the process)? I would put a screen shot in here but can't figure out how and don't have access to a web server.
June 26, 2008 at 11:43 am
I answered my own question here. With the data flows linked to the next Execute SQL task, nothing ran past the first data flow task. I removed the links from the data flow tasks so essentially all three Execute SQL tasks begin running at the same time and I am now getting the expected results.
Thanks for all of the input!
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply