Replication schedule

Here's my problem
I have setup a transactional replication with a push
subscription, I schedule it to run every hour, every think
works good, however when the schedule start synchronizing
it never stops so its not stating at the next hour, I have
to manually click stop synchronizing and then it starts
again.
Please help!!!
Expand Replicaiton Monitor, expand the agents folder, expand the
distribution agents folder, right click on your distribution agent and
select agent properties. then select the steps tab. Click on Run Agent and
then click on the Edit button.
in the command section press the end key, remove the -Continuous statement,
click apply, ok, apply ok, right click on your distribution agent again and
select start agent.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"amw" <amw@.1800wheelchair.com> wrote in message
news:0b7b01c48b80$61dbdc50$a301280a@.phx.gbl...
> Here's my problem
> I have setup a transactional replication with a push
> subscription, I schedule it to run every hour, every think
> works good, however when the schedule start synchronizing
> it never stops so its not stating at the next hour, I have
> to manually click stop synchronizing and then it starts
> again.
> Please help!!!
|||Thanks for your reply
I follow your answer but I don't see the -Continuous
statement on the distribution agent schedule, but I see it
in the log reader agent schedule, should I remove it from
there? I think the log reader should run continuous.

>--Original Message--
>Expand Replicaiton Monitor, expand the agents folder,
expand the
>distribution agents folder, right click on your
distribution agent and
>select agent properties. then select the steps tab. Click
on Run Agent and
>then click on the Edit button.
>in the command section press the end key, remove the -
Continuous statement,
>click apply, ok, apply ok, right click on your
distribution agent again and[vbcol=seagreen]
>select start agent.
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"amw" <amw@.1800wheelchair.com> wrote in message
>news:0b7b01c48b80$61dbdc50$a301280a@.phx.gbl...
think[vbcol=seagreen]
synchronizing[vbcol=seagreen]
have
>
>.
>
|||don't touch the log reader!
If it is not present in your distribution agent, you have a lot of data to
send to your subscriber. In time the job will finish.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"amw" <amw@.1800wheelchair.com> wrote in message
news:0c2801c48b8f$7ad28e20$a501280a@.phx.gbl...[vbcol=seagreen]
> Thanks for your reply
> I follow your answer but I don't see the -Continuous
> statement on the distribution agent schedule, but I see it
> in the log reader agent schedule, should I remove it from
> there? I think the log reader should run continuous.
> expand the
> distribution agent and
> on Run Agent and
> Continuous statement,
> distribution agent again and
> think
> synchronizing
> have

replication problem

Ok I'm going to post this again in another way.
Here's what I have.
2 databases p3e_master and winship.
winship has a merge publication that I use with sqlserverce for pocketpc
users. That works fine.
p3e_master has a transactional updateable publication that includes 3
tables. Those 3 tables are also included in the merge publication for
winship.
here's my problem.
If I update a value in any of the three tables either from winship or
p3e_master (with the sqlquery analyzer for instance) the change propogates
in either direction as it should.
However, when I change data on the pocketpc and the data is synced. The
update shows in winship (as it should), but it does not propogate back to
p3e_master.
Does aybody know if this aproach should work, and if so what do I need to do
to get it working correctly?
Thanks in advance
The various forms of replication don't work well together. You would be best
to use merge all the way for such a scenario as you describe.
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
"mgarner1980" <mgarner@.kbsi.com> wrote in message
news:uk$I%23hYMFHA.688@.TK2MSFTNGP10.phx.gbl...
> Ok I'm going to post this again in another way.
> Here's what I have.
> 2 databases p3e_master and winship.
> winship has a merge publication that I use with sqlserverce for pocketpc
> users. That works fine.
> p3e_master has a transactional updateable publication that includes 3
> tables. Those 3 tables are also included in the merge publication for
> winship.
>
> here's my problem.
> If I update a value in any of the three tables either from winship or
> p3e_master (with the sqlquery analyzer for instance) the change propogates
> in either direction as it should.
> However, when I change data on the pocketpc and the data is synced. The
> update shows in winship (as it should), but it does not propogate back to
> p3e_master.
> Does aybody know if this aproach should work, and if so what do I need to
> do
> to get it working correctly?
> Thanks in advance
>