I have a strange problem, really at a loss for an explanation.

Has anyone here experienced a problem with linked servers whereby a weird
undue dependency is created from one server to the other?

I did sp_addlinkedserver on server A, linking it to five other servers. They
ONLY time the main server talks to another is when I do an ad-hoc query such
as

Set ansi nulls On
set ansi warnings on
select * from LinkedserverB.dbo.db.table

There is no other linkage in production, no ad-hoc queries, etc. I have a
database "B" on a linked server, which when renamed or taken offline, causes
all production work on the main server (which houses only database "A"!) to
stop. I have verified that no dependencies exist in code. Isql works but all
clients with OLE-Db or DSNs fail. I am severely restricted from testing at
this point because of business issues. Any help would be greatly
appreciated. I know this info seems sketchy, I can provide more if needed.

DELL1 DELL1 rpc,rpc out,data access,use remote collation 4 NULL
0 0
DELL2 DELL2 rpc,rpc out,data access,use remote collation 5 NULL
0 0
USN1 USN1 rpc,rpc out,data access,use remote collation 2 NULL
0 0
USN2 USN2 rpc,rpc out,data access,use remote collation 1 NULL
0 0
USN3 USN3 rpc,rpc out,use remote collation 0
NULL 0 0
USN4 USN4 rpc,rpc out,data access,use remote collation 3 NULL
0 0


USN3 is the main server as shown here in sp_helpserver.

Thanks!
Ken
MS Sql Server LazyDBA home page