sturner - Uh....yes you can explain it (but chose not to) or yes it is a collation setting (but you don't want to ellaborate).

Just following-up. Turns out the SSIS package created by the Copy DB wizard didn't like the fact that one of my tables had a column named, "ErrorCode" (the table...

Two updates:

1. Found the actual error from the first attempt:

Description: ERROR : errorCode=-1073451000 description=The package contains two objects with the duplicate name of "output column "ErrorCode" (199)" and "output...

Ah, so the key was to get the local server linked on the remote one. That opens up more options...it was a route I was considering...glad to hear I'm...

Lookup Transformation worked...larger table as input to the Lookup Transform...smaller table configured inside the Lookup Transform.

The only caviat was that by default the Lookup Transformation expects a match and the...

Actually, I do need some fields from both servers...but the results need to be only those records that exist in both when matching by some key fields. Server A...

I may have found an answer....Merge Joins. Sound right?

http://www.sqlservercentral.com/Forums/Topic475238-148-1.aspx

odd...I couldn't find a match for "inner join" using the forum search tools, but then found a link back...

I've been fortunate to only have to use the, "File --> Save Copy of [package name] As..."...then select, "SQL Server" or "SSIS Package Store" as the Package Location.

Hope I'm not asking the obvious here, but did you setup a connection manager (of type SMTP) to connect to your outgoing mail server? If so, what kind of...

That sounds like it'd perform ok. So how would you get the list of account numbers to the remote sproc?

Thanks for the reply.

So large amounts of data over linked servers are simply unusable, largely because the data needs to be copied to the local server in the process? ...

It makes a copy of the remote object in TempDB? Including the data? Wow, that would be bad. My remote database is HUGE!!

PassThrough query suggestion...

FYI: Yeah, a passthrough query seemed to work:

INSERT INTO [dbo].[CodeTable05](

[PKID]

, [Value]

, [Description]

, [StartDate]

...

Makes sense...I was just hoping there was some sort of elegant kludge (is that an oxymoron) to make sense of the data on the SQL05 side.

Hmmm....maybe I could do a...

Yeah, it seems like some kind of mediator is needed. I don't have any control over the SQL08 DB so I need to do something on the SQL05 end....