Re: Log Reader Last Action

• Previous message: larry: "Log Reader Last Action"
• In reply to: larry: "Log Reader Last Action"
• Messages sorted by: [ date ] [ thread ]

Date: Mon, 30 Aug 2004 16:07:16 -0400

First question - are you running DataMirror? I have seen cases where
DataMirror does cause this error message.
Second question - did you set up your database with the sync with backup
option?

Do this in your publication and distribution databases

sp_replicationdboption 'PublicationDatabaseName','sync with backup', 'false'
go
sp_replicationdboption 'distribution','sync with backup', 'false'
go

to answer your questions it means you have the sync with backup option
configured probably so you can log ship your replication databases to a
standby server, or you have DataMirror running on your SQL Server.

You should be concerned as it means that your latency is the same internval
as you are dumping your transaction logs at.

Your transactions are not getting replication until you dump your
transaction log.

To fix it run the statements above.

-- 
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry" <anonymous@discussions.microsoft.com> wrote in message
news:2f5301c48ecb$32299df0$a601280a@phx.gbl...
> Running SQL 2k & Win 2k
>
> Two of my four log readers have the following message....
>
> 'replicated transactions are waiting for next log backup'
>
> What does this mean??  Is this a problem I should be
> concerned about??  Are transactions getting replicated??
> If this is a problem, how do I fix it?
>
> TIA,
> Larry...

• Previous message: larry: "Log Reader Last Action"
• In reply to: larry: "Log Reader Last Action"
• Messages sorted by: [ date ] [ thread ]