Change replicationAgent that starts SQLSERVERAGENT

Hi,
We are using Push subscription in our transactional replication setup in SQL
2K and I noticed that the SQLSERVERAGENT service is started by a local
account called replicationAgent. Is it a problem for me to change it to a
different local account? If it is ok to change it, do I need to change it
also in the subscriber computer and is it necessary that both account name
and password need to be the same?
Wingman
It is ok to change it to an account in the local administrator group, or an
account which has write permission to the default snapshot share.
Make sure that the job owner is sa otherwise it probably will not start.
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
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:67E05E17-2202-477C-BB62-75695B821516@.microsoft.com...
> Hi,
> We are using Push subscription in our transactional replication setup in
> SQL
> 2K and I noticed that the SQLSERVERAGENT service is started by a local
> account called replicationAgent. Is it a problem for me to change it to
> a
> different local account? If it is ok to change it, do I need to change it
> also in the subscriber computer and is it necessary that both account name
> and password need to be the same?
> Wingman
|||Thanks as always.
Wing
"Wingman" wrote:

> Hi,
> We are using Push subscription in our transactional replication setup in SQL
> 2K and I noticed that the SQLSERVERAGENT service is started by a local
> account called replicationAgent. Is it a problem for me to change it to a
> different local account? If it is ok to change it, do I need to change it
> also in the subscriber computer and is it necessary that both account name
> and password need to be the same?
> Wingman