agents db rights for trans. repl

We are about to deploy transactional replication with queue updating
subscribers. Both the publisher and distributor are on server A and the
publisher is on server B. We have one publication on the publisher which
will PUSH a small database (around 51 articles) to the subscriber. The
MSSQLSERVER service and the SQLSERVERAGENT services run in the context of
a windows domain account. These services are configured with different
domain accounts on the 2 servers.
- Do the domain accounts require specific rights/permissions on both the SQL
servers and the databases?
- In the properties page for the snapshot agent, log reader agent, queue
reader and distribution agent there is an OWNER setting. Does this has to be
set to the domain accounts for the MSSQLSERVER and SQLSERVERAGENT services
so replication across servers can occur?
Sysadmin on the publisher, dbo on the subscriber for push, for pull sysadmin
on the subscriber and in the pal on the publisher.
I make the job owner sa. It works better for me, when I do this as opposed
to using another account.
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
"newsgroupuser" <abraxas1969@.hotmail.com> wrote in message
news:OAQA%23EPRFHA.1564@.TK2MSFTNGP09.phx.gbl...
> We are about to deploy transactional replication with queue updating
> subscribers. Both the publisher and distributor are on server A and the
> publisher is on server B. We have one publication on the publisher which
> will PUSH a small database (around 51 articles) to the subscriber. The
> MSSQLSERVER service and the SQLSERVERAGENT services run in the context
> of
> a windows domain account. These services are configured with different
> domain accounts on the 2 servers.
>
> - Do the domain accounts require specific rights/permissions on both the
> SQL
> servers and the databases?
>
> - In the properties page for the snapshot agent, log reader agent, queue
> reader and distribution agent there is an OWNER setting. Does this has to
> be
> set to the domain accounts for the MSSQLSERVER and SQLSERVERAGENT services
> so replication across servers can occur?
>
>

Agents and thread limits from SQL 2005 Distributor machine

Hi DBA's
We have one machime with 4 core processors and 2 GB of RAM. This machine have
3 sql 2005 instances and It's responsable form many replications. More of
them, have pull distribution agent, so we can controll these number over
project growing, but one instance don't.
All distribution agents were configured like "PUSH" and I don't intend to
use "PULL" with these because probably we'll affect subscribers with many
jobs (and thread distribution agents), that the same way, more difficult to
administrate.
How do we see these limits? If so, we can scale to another instance and
controll them!
Plese, if anyone has any article or "better pratical", we appreciate!
Numbers is the focus. We need numbers resgiters like x distrib.exe y logread.
exe and thus for ahead.
Thanks!
Krisnamourt
Message posted via http://www.droptable.com
select logreader=sum(case when program_name like '%logreader%'then 1 else 0
end),distrib=sum(case when program_name like '%'+rtrim(@.@.servername)+'%-%'
then 1 else 0 end) from sys.sysprocesses
http://www.zetainteractive.com - Shift Happens!
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
"Krisnamourt via droptable.com" <u21487@.uwe> wrote in message
news:7bfea23d5f150@.uwe...
> Hi DBA's
> We have one machime with 4 core processors and 2 GB of RAM. This machine
> have
> 3 sql 2005 instances and It's responsable form many replications. More of
> them, have pull distribution agent, so we can controll these number over
> project growing, but one instance don't.
> All distribution agents were configured like "PUSH" and I don't intend to
> use "PULL" with these because probably we'll affect subscribers with many
> jobs (and thread distribution agents), that the same way, more difficult
> to
> administrate.
> How do we see these limits? If so, we can scale to another instance and
> controll them!
> Plese, if anyone has any article or "better pratical", we appreciate!
> Numbers is the focus. We need numbers resgiters like x distrib.exe y
> logread.
> exe and thus for ahead.
> Thanks!
> Krisnamourt
> --
> Message posted via http://www.droptable.com
>
|||Thanks Hilary,
This article below show us some limitation from sql 2000 about log reader
threads. I did some research and didn't find any limitation about sql 2005.
So, is it true 100 log readers or what is the limitation of this agent?
http://support.microsoft.com/kb/306457/en-us
Hilary Cotter wrote:[vbcol=seagreen]
>select logreader=sum(case when program_name like '%logreader%'then 1 else 0
>end),distrib=sum(case when program_name like '%'+rtrim(@.@.servername)+'%-%'
>then 1 else 0 end) from sys.sysprocesses
>[quoted text clipped - 22 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200712/1
|||I am unaware of any such limitation for Standard and Enterprise Editions.
Note that in the SQL 2000 article it refers to the number of simultaneous
agents which could be simultaneously running, its not necessarily a hard
limit as to the number of log reader agents/distribution agents that can be
on your system.
http://www.zetainteractive.com - Shift Happens!
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
"Krisnamourt via droptable.com" <u21487@.uwe> wrote in message
news:7c2e263b3461b@.uwe...
> Thanks Hilary,
> This article below show us some limitation from sql 2000 about log reader
> threads. I did some research and didn't find any limitation about sql
> 2005.
> So, is it true 100 log readers or what is the limitation of this agent?
> http://support.microsoft.com/kb/306457/en-us
> Hilary Cotter wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-replication/200712/1
>