Transactional Replication issue - Tlog file is huge and completely filled

Question

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

MVDBA (Mike Vessey) SSC-Insane Points: 21797 More actions · Answer 1

you'll need to provide more information than that if you want people to be able to help you

first though - have you checked that SQL agent is running an that the LOG READER agent is running?

MVDBA

Steve Jones - SSC Editor SSC Guru Points: 738733 More actions · Answer 2

Are you backing up the t-log? Are your subscribers all getting data?

Is this the publisher or distributor log?

Grant Fritchey SSC Guru Points: 399289 More actions · Answer 3

If you're in transactional replication, did replication fail? Is the distributor down?

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt