![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Bob, I your current scenario, where you are executing the package on server a, you don't need to qualify the table name that exists on server a itself. you |
|
select * from [serverb].Database.owner.tableb b join tablea a on a.primarykey = b.primarykey where b.primarykey >= 10 no? hth, K ----- Bob Frasca wrote: ----- I have a package that lives and executes on ServerA. It is copying data from ServerB to ServerA doing a join on ServerA. ServerB is a linked server. The query looks something like this: select * from [serverb].Database.owner.tableb b join [servera].Database.owner.tablea a on a.primarykey = b.primarykey where b.primarykey >= 10 This query works perfectly in a Query Analyzer window on ServerA. In DTS, when I try and save the Transform Data task containing this query it tells me that ServerA is not a linked server. I've never had to create a server that is linked to itself. Doesn't make any sense. The odd part is that it works fine if the package lives and executes on ServerC. In other words, all I did was copy this package from ServerC to ServerA and change the database references in the fully qualified pathname from ServerC to ServerA and it stopped working. Is there some configuration thing that I need to do on ServerA? |
![]() |
| Thread Tools | |
| Display Modes | |
| |