replication set up creates a linked server?

Hello - I recently setup replication here & I have a question. In doing an
audit of the SQL Servers the other DBA & I notice a linked server between a
dev box & a prod box with a read-only login called LinkedServer_RO to prod.
Neither one of us recognize this linked server & it's against the security
policies (understandably tight here at the CDC) to have linked servers unless
absolutely necessary. However when I go to remove the linked server it says
it can't be deleted because it is a subscriber in replication - did the
replication setup process create this? I had not remembered seeing linked
servers get automatically created before - any info is greatly appreciated -
thanks.
John F.
this is not created by replication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John F." <juantana@.newsgroups.microsoft.com> wrote in message
news:0FDBFCE9-1F04-4BEE-A20A-AF6639200F91@.microsoft.com...
> Hello - I recently setup replication here & I have a question. In doing
an
> audit of the SQL Servers the other DBA & I notice a linked server between
a
> dev box & a prod box with a read-only login called LinkedServer_RO to
prod.
> Neither one of us recognize this linked server & it's against the security
> policies (understandably tight here at the CDC) to have linked servers
unless
> absolutely necessary. However when I go to remove the linked server it
says
> it can't be deleted because it is a subscriber in replication - did the
> replication setup process create this? I had not remembered seeing linked
> servers get automatically created before - any info is greatly
appreciated -
> thanks.
> --
> John F.
|||thanks so much for your quick reply - in that case I wonder how I can go
about removing it - it errors saying the linked server is a subscriber in
replication.
"Hilary Cotter" wrote:

> this is not created by replication.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "John F." <juantana@.newsgroups.microsoft.com> wrote in message
> news:0FDBFCE9-1F04-4BEE-A20A-AF6639200F91@.microsoft.com...
> an
> a
> prod.
> unless
> says
> appreciated -
>
>
|||oops - actually replication does not create this linked server but someone
may have created a linked server for a subscriber.
Go to tools, replication, configure distributor, publishers, and subscribers
and click on the subscribers tab. You should see it there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"John F." <juantana@.newsgroups.microsoft.com> wrote in message
news:4F7F8843-1205-4084-9DE0-997660584E04@.microsoft.com...[vbcol=seagreen]
> thanks so much for your quick reply - in that case I wonder how I can go
> about removing it - it errors saying the linked server is a subscriber in
> replication.
> "Hilary Cotter" wrote:
doing[vbcol=seagreen]
between[vbcol=seagreen]
security[vbcol=seagreen]
it[vbcol=seagreen]
the[vbcol=seagreen]
linked[vbcol=seagreen]
|||John,
replication will create a remote server for subscribers needing distributed
transactions, but sometimes you also need a (more versatile) linked server
to the same server for some other purpose. As you can't have both entries in
the sysservers table, the solution is to convert the remote server to a
linked server which is my guess what has happened.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql