Truncating transcation log file in SQL server 2008 for a database in replication

Asked Apr 17 '12 at 12:35

Active Apr 17 '12 at 12:35

Viewed 555 times

We have a large SQL server 2008 database (full recovery mode) replicated to another server using transactional replication.

The transactions log file is growing due to the amount of transactions we have. The current size is about 300 GB.

I tried to shrink the log file after full and log backups but the size is still considered too large.

Is there any way I can truncate the log file without affecting the replication?

Thanks

asked Apr 17 '12 at 12:35

PyQL

you don't need to shrink the transaction log - you should do frequent (scheduled) **log backups** – marc_s Apr 17 '12 at 13:53
@marc_s , scheduled log backups will decrease log file size? thanks. – loviji Jun 18 '12 at 09:23

0 Answers0