Linked server help

[Paul]

I searched the group for 'linked servers and replication' and see one
post back in 2005 about how replication does not create linked
servers. I need verification on that. I have a linked server in
production that is configured as "data access" = false. I now need to
setup a linked server for another process but can't because this one
is already there. I was hoping Hilary or Paul I would chime in and
help me figure out if I can safely change this linked server and not
affect the current replication in production.

I'm running Sql Server 2005 Enterprise Edition. Actually, looking
closer, this looks like a remote server. I probably need to see if I
can convert it to a linked server, but my question still remains:
Does replication actively use this remote/linked server and if so, how
can I tell? Or am I safe to alter it?

Thanks for any help you can provide.

Paul

[Hilary Cotter]

In SQL 2000 no linked server was required for updateable subscribers. This
has changed for SQL 2005 which does require them for updateable subscribers.

You can modify the properties of your linked server for data access=true
without breaking replication.

"Paul" <paulb...@gmail.com> wrote in message
news:27e060b7-702c-405f...@g23g2000vbr.googlegroups.com...

[Paul]

Thanks Hilary! Followup - we are only using Transactional replication
- one way, no updateable subscribers. Am I also ok in making changes
to the security settings such that others can use this linked server
without affecting replication? Also if possible could you point me to
how replication is using this linked server so I can verify that it
works after I make all my changes?

I was thinking that I would just modify the security so that other
users that use this linked server use a remote login on another box.
That doesn't seem like it would affect replication.

Thanks for your help!