Problem with job

Hi there,

Actually I'm trying to replicate a production database to a development server using merge publication. (I'm using Microsoft SQL Server 2005 - 9.00.2047.00).

When I created the publication job (automatically when creating the publication) I specified to get executed every 15 minutes, and later I created a subscription (push subscription) I specified it to execute continously. So I made some chenges on the data on the production server, and they get replicated every minute aprox. , and not in 15 min intervals as I defined before.... When I go to the server agent I can see the job for publication and It is supposed to be executing the publication every 15 min as I defined but this doesn't happen !!!

Is this a Bug ? Is there any fix ?

Thanks !

The subscription job, which you set to run continuously, is what's moving changes between publisher and subscriber. This runs/polls every 60 sec, which is why you're seeing changes replicated every minute. THis behavior you're seeing is by design and expected. If you want it to replicate every 15 minutes, then change the schedule for this subscription job.

I'm not sure what a "publication" job is, maybe you're referring to the snapshot agent job? For merge replication, its typical to schedule the snapshot agent to run maybe once a day, but not every 15 minutes. You may want to change it.

So no it's not a bug

|||

I've got my problem solved !!! Thank you so much !

Greg Y wrote:

The subscription job, which you set to run continuously, is what's moving changes between publisher and subscriber. This runs/polls every 60 sec, which is why you're seeing changes replicated every minute. THis behavior you're seeing is by design and expected. If you want it to replicate every 15 minutes, then change the schedule for this subscription job.

I'm not sure what a "publication" job is, maybe you're referring to the snapshot agent job? For merge replication, its typical to schedule the snapshot agent to run maybe once a day, but not every 15 minutes. You may want to change it.

So no it's not a bug

sql