Post your new code. Include details on which code is in which task and tell us which of the tasks is failing.

Remove your variable declarations. Remove the "Set @cmd1 = ' " bits and the trailing single quotes after the T-SQL. Remove the Execute statements.

Then run the code.

As Koen said, there's...

Koen (da-zero) (2/9/2011)

---

Furthermore, it is possible that the statement within the EXEC is executed under a different scope, so your temp table is likely already destroyed before the next statement...

Gus's suggestion has me wondering if a book like that would actually sell.

Between @Cmd2 and @Cmd3, how are you populating the temp table?

Is it a separate task after executing @Cmd2 and before executing @Cmd3? Or are you doing it all in...

And we've done it several times before. And will likely do...

Diagram

Actually, I refer to CASE as a statement all the time. Call me lazy. I think I picked up the habit from the programming languages I learned in HS and...

Jan Van der Eecken (2/9/2011)

---

You know, I read through that whole thread, and somewhere mid-way I started wondering whether nadabadan himself wasn't actually the interviewer. I guess I am certainly...

An additional note about SSIS, you can multicast the same data to do different destinations at the same time. That's one of the reasons why I like it for situations...

What is the error message? Please post it.

Actually, that's just the wind blowing up your kilt. @=)

Seriously, though, are you just moving on...

I'm betting it's a QD problem. I've seen similar problems before and the query you presented us with looks exactly like it was "written" by Query Designer. QD just doesn't...

Are you seeing performance issues with any other processes, views, or queries?

EDIT: Are you using Query Designer?

Nevermind! It's my bad.

I failed to notice that the ClientIDs are different as well as the ClientNumbers and that some of those IDs are filtered out of the Fact table...