Re: Log Question
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Sun, 13 Jan 2008 11:47:11 -0500
Truncate away, you will not affect anything especially not any transactions.
For immediate updating the transaction is applied on the publisher first and
then the subscriber. For queued updating triggers will log the transaction
in a queue, not the log.
--
http://www.zetainteractive.com - Shift Happens!
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
"CLM" <CLM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B27535D0-1036-463F-92E2-96556F32F53D@xxxxxxxxxxxxxxxx
We've got 2000 SP4 servers with transactional immediate replication. One
of
the subscribing databases is in simple mode with a log that is about 70G
and
all of that is used. This is strange but we don't back up that database -
it's not worth it to management right now - so how can I shrink that log
file? If I truncate the log, could I possibly blow away transactions that
contain replicated data? Again, keep in mind that this subscribing
database
is in simple mode and is not backed up now. Thx.
.
- Follow-Ups:
- Re: Log Question
- From: Hilary Cotter
- Re: Log Question
- From: Rubén Garrigós
- Re: Log Question
- Prev by Date: Re: Transaction Log Shipping setup
- Next by Date: Re: Log Question
- Previous by thread: Re: Log Shipping Question
- Next by thread: Re: Log Question
- Index(es):
Relevant Pages
|