Re: SQL server and SQL agent services' logon account for Replication



In the context of Pull subscription,
Does this mean the publisher/distributor SQL server and agent can run
in local system account?
And only the subscriber's server and agent needs to be run in an local
administrator account which should be included in PAL?

eg:
Currently my MS_Publication_access table in distribution db has only
BUILTIN\Administrators, sa and distributor_admin ids. And my publisher
and subscriber are running in their own local administrator accounts.
This is working fine.

Can you please say how i narrow this configuration down so that it
works fine still?

Thanks,
Lavanya

Hilary Cotter wrote:
For push have the sql server agent run under the local administrators
account which is in the sys_admin role.

For pull, the sql server agent's on the subscriber must have rights to read
the default snapshot share on the publisher, and the SQL server account you
are using to pull the subscription must be in the PAL on the publication
database and be in the dbo_role on the distribution database.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



"Lavanya" <lavanyah@xxxxxxxxx> wrote in message
news:1150198911.963647.122230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is the following solution ok?
1. Have a local administrator account created on both publisher and
subscriber machines
2. Create an SQL login account for the created account with sysadmin
role.
3. Have my SQL servers and agents run on that account.

Is this the only solution or any other simpler?

Thanks,
Lavanya

Hilary Cotter wrote:
Its critical for pull replication.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



"Lavanya" <lavanyah@xxxxxxxxx> wrote in message
news:1150190434.090710.271550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

When is it necessary for these 2 services to have 'this account' logon
credentials?

I have a simple Transactional setup with local distributor and pull
subscription. Some articles say that these services should not be run
in local system account for replication. However, its working for me
otherwise.

Help needed!

Thanks,
Lavanya



.



Relevant Pages

  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... the repldata share on the publisher because the SQL Server Agent account on ... pass-through accounts to prevent the Windows Domain Account problem. ... What are the steps to setup and verify the pull subscription that I must ... > There are two modes - windows authentication and SQL Server Standard ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... the repldata share on the publisher because the SQL Server Agent account on ... pass-through accounts to prevent the Windows Domain Account problem. ... What are the steps to setup and verify the pull subscription that I must ... > There are two modes - windows authentication and SQL Server Standard ...
    (microsoft.public.sqlserver.connect)
  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... the repldata share on the publisher because the SQL Server Agent account on ... pass-through accounts to prevent the Windows Domain Account problem. ... What are the steps to setup and verify the pull subscription that I must ... > There are two modes - windows authentication and SQL Server Standard ...
    (microsoft.public.sqlserver.security)
  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... >> Publisher, Distributor, and Subscriber talk to each other using RPC ... > the repldata share on the publisher because the SQL Server Agent account ... > What are the steps to setup and verify the pull subscription that I must ... >> the repldata share on the publisher because the SQL Server Agent account ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication for non-trusted domains through VPN can only allow push subscription.
    ... >> Publisher, Distributor, and Subscriber talk to each other using RPC ... > the repldata share on the publisher because the SQL Server Agent account ... > What are the steps to setup and verify the pull subscription that I must ... >> the repldata share on the publisher because the SQL Server Agent account ...
    (microsoft.public.sqlserver.connect)

Quantcast