To expand a bit on point 2, SSIS variables don't have a "null" value. They always have to have an actual value. If your package configuration doesn't specify one, then...

sorry - just re-read your previous post and noticed the comment regarding SQL Server 2008 R2.

Are you trying to copy a data flow task from SSIS 2005 to SSIS 2008?...

Yeah that would probably be the easiest bet - AFAIK you can execute a perl file by just using the Execute Process task and passing the file name of the...

Hi there,

For your first step, you have a few options you can use.

The "easiest" option, IE the one that will require the least time up-front, would be to just make...

I regularly copy-paste objects from SSIS projects, and haven't had any problems with it. Best way is to just test it and see what happens.

Does your full table contain more than just the four serverID's you specified in your example, for the UNION showplan?

This is just a theory, but maybe the reason why it...

Yeah I've gotta say, I'm surprised your second query performs worse than the first - it's basically doing the same thing, except without the UNION's.

I'd like to see the execution...

Thanks for posting all the CREATE TABLE statements, but as a general rule of thumb, you should make sure that your code can run as-is in a standalone environment. I...

Short answer, "yes with a but"

You can copy any task from a package to another package. The problem comes when that task is using variables or connections that exist in...

just out of curiousity Chris, I assume there's no real difference between writing the query like that, or like "with ___ AS (blah) SELECT FROM cte WHERE count = 1"

Correct on both counts.

Easiest solution would be to just do the joins on the database level.

When you're doing a merge join in SSIS, it has to do all the manipulations in memory, which...

That would only be the case if the database was actually located on Server 2.

If I understand the OP correctly, there's a whole bunch of servers and machines which are...

Actually after thinking about it more, I think I have a better idea.

Rather than having the UPDATE trigger actually do all the work in updating the replicated tables, how about...

Could it be that your system doesn't have enough memory to handle the task you're asking of it?

I know that when you're using a standard lookup, it will crash if...