Re: Replication maintenance jobs
- From: NC3 <ncoleman3@xxxxxxxxx>
- Date: Tue, 09 Oct 2007 10:13:03 -0700
On Oct 9, 12:46 pm, "Hilary Cotter" <hilary.cot...@xxxxxxxxx> wrote:
Yes, you can. Something is very wrong here.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com"NC3"; <ncolem...@xxxxxxxxx> wrote in message
news:1191942570.546783.323560@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Oct 9, 7:47 am, "Hilary Cotter" <hilary.cot...@xxxxxxxxx> wrote:
These jobs will be present on the remote distributor. Did you look on
the
remote distributor in the miscellaneous jobs folder on SQL 2000 and in
the
other jobs will show up in the jobs folder in SQL 2005.
Can you check to make sure they are not in those locations?
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
Looking for a SQL Server replication
book?http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL
FTShttp://www.indexserverfaq.com"NC3"; <ncolem...@xxxxxxxxx> wrote in
message
news:1191441595.530216.233700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We've just migrated to a new firm wide application that uses
transactional replication for reporting purposes. I've configured
replication 2 or 3 different times while in test/development without
many issues. On cutover Monday replication became a show stopper due
to configuration issues mainly properly securing each component of the
topology.
I have a remote distributor configured to manage the maintenance jobs
for the replication process. After verifying the proces is actually
replicating data I noticed that the only jobs created are the Snapshot
agent, Log Reader agent and the distribution agent jobs.
During development I also noticed additional jobs that have not been
created.
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
I reviewed the Publisher and Subscriber and located the Expired
subscription clean up oon the publication server.
How can I get the additional maintenance jobs created and equally
important why wouldn't the jobs be created by the wizard during
configuration.- Hide quoted text -
- Show quoted text -
That's the problem they do not show in the jobs folder in SQL 2005 as
expected. I have reconfigured twice and both times they fail to be
created. Can I script the jobs from a development installation which
created the jobs as expected and change the relevant parameters and
have them work successfully?
It seems to me if the additional jobs are not created the over all
health of the repllcation environment can become negatively effected.
Thanks for all the repsonses!- Hide quoted text -
- Show quoted text -
Thanks for the response, And I agree something is very wrong here!!
I'll script the jobs and keep everyone posted.
.
- References:
- Replication maintenance jobs
- From: NC3
- Re: Replication maintenance jobs
- From: Hilary Cotter
- Re: Replication maintenance jobs
- From: NC3
- Re: Replication maintenance jobs
- From: Hilary Cotter
- Replication maintenance jobs
- Prev by Date: Re: Merge Performance
- Next by Date: Replication left the database in a weird state
- Previous by thread: Re: Replication maintenance jobs
- Next by thread: HELP - Error adding an article to a merge replication - Any ideas?
- Index(es):
Relevant Pages
|
