> Hi,
>
> I have a replication environment with SQL Server 2005 SP2, where I work
> with
> 358 subscribers in a publisher called SQLDB3. They are distributed in four
> publications with diferent schedules between each others, the subscribers
> run
> every two minutes.
>
> When it starts delivering the commands, frequently the job sends the
> commands, the replication finishes the process but the job doesn't stop,
> It
> keeps running and the replication stalls.
>
> How can i solve it so my job finishes together with my replication
> process?
> Is it a known issue with SQL Server 2005? Is there some way to correct it?
>
> Fernando Lascala

>
> Hello Hilary
>
> The JOB doesn't turn itself idle, before cancel, the JOB message seems
> like
> this:
>
> Message
> ****** STATISTICS SINCE AGENT STARTED *******
> 07-20-2007 08:02:56
>
> Total Run Time (ms) : 149125 Total Work Time : 139000
> Total Num Trans : 449 Num Trans/Sec : 3.23
> Total Num Cmds : 9151 Num Cmds/Sec : 65.83
> Total Idle Time : 0
> ...
>
> But on the Replication Monitor reports this: "A total of 2 transaction(s)
> with 2 command(s) were delivered."
> I don't know if this happens becouse 100 subscribers are started
> simultaneously and the msrepl_commands table receives a strong
> concurrence.
>
> Fernando Lascala
>
>
> "Hilary Cotter" wrote:
>
>> Does the final message say no replicated transaction available, with a
>> status of idle?
>>
>> If so this is harmless. You can schedule the agent so that it will stop
>> if
>> you wish.
>>
>> If you are getting any other message or an error message, please post the
>> message you receive back here.
>>
>> --
>> 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
>> "Fernando Lascala" <Fernando Lascala@discussions.microsoft.com> wrote in
>> message news:C17D11FC-483E-410E-B4F9-FA17584E5BBE@microsoft.com...
>> > Hi,
>> >
>> > I have a replication environment with SQL Server 2005 SP2, where I work
>> > with
>> > 358 subscribers in a publisher called SQLDB3. They are distributed in
>> > four
>> > publications with diferent schedules between each others, the
>> > subscribers
>> > run
>> > every two minutes.
>> >
>> > When it starts delivering the commands, frequently the job sends the
>> > commands, the replication finishes the process but the job doesn't
>> > stop,
>> > It
>> > keeps running and the replication stalls.
>> >
>> > How can i solve it so my job finishes together with my replication
>> > process?
>> > Is it a known issue with SQL Server 2005? Is there some way to correct
>> > it?
>> >
>> > Fernando Lascala
>>
>>
>>

"Hilary Cotter" wrote:

> Are you running the binary from the command line? This looks like the
> message you get when you do this.
>
> --
> 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
> "Fernando Lascala" <FernandoLascala@discussions.microsoft.com> wrote in
> message news:3526918B-1E31-4A6D-ACA1-8E0986E00DD3@microsoft.com...
> >
> > Hello Hilary
> >
> > The JOB doesn't turn itself idle, before cancel, the JOB message seems
> > like
> > this:
> >
> > Message
> > ****** STATISTICS SINCE AGENT STARTED *******
> > 07-20-2007 08:02:56
> >
> > Total Run Time (ms) : 149125 Total Work Time : 139000
> > Total Num Trans : 449 Num Trans/Sec : 3.23
> > Total Num Cmds : 9151 Num Cmds/Sec : 65.83
> > Total Idle Time : 0
> > ...
> >
> > But on the Replication Monitor reports this: "A total of 2 transaction(s)
> > with 2 command(s) were delivered."
> > I don't know if this happens becouse 100 subscribers are started
> > simultaneously and the msrepl_commands table receives a strong
> > concurrence.
> >
> > Fernando Lascala
> >
> >
> > "Hilary Cotter" wrote:
> >
> >> Does the final message say no replicated transaction available, with a
> >> status of idle?
> >>
> >> If so this is harmless. You can schedule the agent so that it will stop
> >> if
> >> you wish.
> >>
> >> If you are getting any other message or an error message, please post the
> >> message you receive back here.
> >>
> >> --
> >> 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
> >> "Fernando Lascala" <Fernando Lascala@discussions.microsoft.com> wrote in
> >> message news:C17D11FC-483E-410E-B4F9-FA17584E5BBE@microsoft.com...
> >> > Hi,
> >> >
> >> > I have a replication environment with SQL Server 2005 SP2, where I work
> >> > with
> >> > 358 subscribers in a publisher called SQLDB3. They are distributed in
> >> > four
> >> > publications with diferent schedules between each others, the
> >> > subscribers
> >> > run
> >> > every two minutes.
> >> >
> >> > When it starts delivering the commands, frequently the job sends the
> >> > commands, the replication finishes the process but the job doesn't
> >> > stop,
> >> > It
> >> > keeps running and the replication stalls.
> >> >
> >> > How can i solve it so my job finishes together with my replication
> >> > process?
> >> > Is it a known issue with SQL Server 2005? Is there some way to correct
> >> > it?
> >> >
> >> > Fernando Lascala
> >>
> >>
> >>
>
>