April 17, 2007 at 2:29 am
Hi all
We are using a pull publication what works well. After a time, maybe next day, the publication must be reinitialized again.
The properties of the publication does not define a final date. I could not find other properties controlling the activation state.
Is this a security issue why a publication falls to inactive? Is there a time range to controll that?
Thanks for help, Jan
May 3, 2007 at 4:55 pm
should not be necessary [and doubtless a pain in the bu44]
- If you are not already on latest SP I suggest you upgrade first if feasible
suggest you wire up repl alerts [define operator and check all the boxes for email notification] so you can see if coincides with other activity [resource starvation perhaps]. Understand that the DA's are normal Windows processes [not SPID threads] so compete with other consumers, so as well to use taskmgr/perfmon to set appropriate dynamic memory limits for your SQLinstance(s).
Ensure that the AutoGrow settings are decent for distribution, and that you do normal reindex+shrink optimisation.
You can alo change to agent profile for verbose mode [instead of default] via ReplMonitor or programatically. May shed light on root causes.
Let us know what you find
May 4, 2007 at 4:10 am
Hi Dick
We are on SP2 with hotfix.
The retention time of the distributor was limited to 72 hours, so we put it much higher. It seems to work but we are not shure its the ony reason.
Regards, Jan
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply