469,148 Members | 1,433 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,148 developers. It's quick & easy.

inconsistent behaviour linked server?

Jan
Hi,

1.
my server configurations:
remote network: sql server 2000 (srvrR1)
local netwerk: server1 - sql server 2000 (srvrL1)
server2 - sql server 2000 (srvrL2)
- linked server to srvrR1
- linked server to srvrL1
I do al my work on server2 - srvrL2

2.
What I do:
I synchronise data between srvrR1 and srvrL1.
In order to do so I use the wizard. But this is not satisfying. So I
created some scripts. See below.

======
update tbl2
set tbl2.fld1=tbl1.fld1
from srvrR1.database.owner.table1 as tbl1
join srvrR1.database.owner.table2 as tbl2
on (tbl2.id_fld = tbl1.id_fld);

update tbl3
set tbl3.fld1=tbl1.fld1
from srvrR1.database.owner.table1 as tbl1
join srvrL1.database.owner.table3 as tbl3
on (tbl3.id_fld=tbl1.id_fld);
======

3.
executing the first script causes the following messages:
Server: Msg 8180, Level 16, State 1, Line 1
Statement(s) could not be prepared.
Server: Msg 209, Level 16, State 1, Line 1
Ambiguous column name fld1.
executing the second script causes the following messages:
(8 row(s) affected)
So, in my point of view, I run two almost the same scripts - both on
linked servers - and yet they have completely different outcome !!

4.
This seems to me inconsequent behaviour.
Can someone explain this to me and, if possible, give guidelines to
solve the problem?

tav,
Jan Willems
Jul 20 '05 #1
0 1331

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by Igor Raytsin | last post: by
2 posts views Thread by David | last post: by
2 posts views Thread by mike b | last post: by
1 post views Thread by Frosty Madness | last post: by
8 posts views Thread by Daniel Kraft | last post: by
reply views Thread by zhoujie | last post: by
1 post views Thread by Mortomer39 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.