"Duncan" <duncan.megens@keenetch.nl> wrote in message
news:Ox%23sZEpXEHA.644@TK2MSFTNGP10.phx.gbl...
> Hello,
>
> I am using SQL Server 2000 and have a question about the log reader.
>
> I have read, that you can schedule the log reader to run, for instance
once
> a day. My question is when does the log reader 'know' when to stop?
>
> Thanks in advance,
> Duncan.
>
>
>
>

"Duncan" <Duncan@discussions.microsoft.com> wrote in message
news:7DC36633-D98F-4C6F-ACFC-861FDE56C74C@microsoft.com...
> Hilary,
>
> Thanks for your quick reply.
>
> I think I understand what you are saying, but that would mean the log

>
> Thank you,
> Duncan.
>
> "Hilary Cotter" wrote:
>
> > the log reader can be scheduled. It "knows" to stop after it has read
the
> > transaction log.
> >
> > If you are running it in continuous mode it reads the transaction log
> > starting at the point where it last left off. By default it reads the
> > transaction log every 10 seconds, or whatever the -pollinginterval is
set
> > at.
> >
> > Set it to 1 s.
> >
> > "Duncan" <duncan.megens@keenetch.nl> wrote in message
> > news:Ox%23sZEpXEHA.644@TK2MSFTNGP10.phx.gbl...
> > > Hello,
> > >
> > > I am using SQL Server 2000 and have a question about the log reader.
> > >
> > > I have read, that you can schedule the log reader to run, for instance
> > once
> > > a day. My question is when does the log reader 'know' when to stop?
> > >
> > > Thanks in advance,
> > > Duncan.
> > >
> > >
> > >
> > >
> >
> >
> >

> by default the log reader agent starts up in continuous mode whenever the
> SQL Server agent starts.
>
> To change this (and I don't advise you do this, although there are some
very
> unusual set of circumstances when you do want to do this), expand
> replication monitor, expand the agents folder, expand the log reader
agents
> folder, right click on your log reader agent, select agent properties,
> select the schedules tab, click on the edit button, and then select
> recurring and click on the change button to set a schedule.
>
> Then return to the Steps tab on the log reader agent properties. Click on
> run agent, and select edit. at the end of the command string you will
find
> the token -Continuous.
>
> Remove this token.
> Click on apply, ok, apply ok, right click on your log reader agent, and
stop
> it. then start it up again.
>
> I advise you to think long and hard about scheduling your log reader
agent.
> Scheduling it has important implications on performance and the size of
your
> transaction log. IE performance will go downhill, and your transaction log
> will swell considerably.
>
>
> "Duncan" <Duncan@discussions.microsoft.com> wrote in message
> news:7DC36633-D98F-4C6F-ACFC-861FDE56C74C@microsoft.com...
> > Hilary,
> >
> > Thanks for your quick reply.
> >
> > I think I understand what you are saying, but that would mean the log
> reader can be started in two modes: continuous or non-continuous. Can you
> tell me where I can configure this mode?
> >
> > Thank you,
> > Duncan.
> >
> > "Hilary Cotter" wrote:
> >
> > > the log reader can be scheduled. It "knows" to stop after it has read
> the
> > > transaction log.
> > >
> > > If you are running it in continuous mode it reads the transaction log
> > > starting at the point where it last left off. By default it reads the
> > > transaction log every 10 seconds, or whatever the -pollinginterval is
> set
> > > at.
> > >
> > > Set it to 1 s.
> > >
> > > "Duncan" <duncan.megens@keenetch.nl> wrote in message
> > > news:Ox%23sZEpXEHA.644@TK2MSFTNGP10.phx.gbl...
> > > > Hello,
> > > >
> > > > I am using SQL Server 2000 and have a question about the log reader.
> > > >
> > > > I have read, that you can schedule the log reader to run, for
instance
> > > once
> > > > a day. My question is when does the log reader 'know' when to stop?
> > > >
> > > > Thanks in advance,
> > > > Duncan.
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
>
>