Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a couple of SQL databases running in merge replication. My publishers HDD is full due to the transaction log of the database being replicated which is causing my snapshot agent to fail (out of disk space).

I want to shrink my transaction logs. If I do, will it break my replication? If it will break my replication, is there a way I can tell my publisher to put its files on a different HDD without having to restart replication.


share|improve this question

migrated from Apr 17 '12 at 14:28

This question came from our site for professional and enthusiast programmers.

up vote 1 down vote accepted

Yes - you can shrink the transaction log without it breaking replication. You can also move the publisher files to a different HDD by using ALTER DATABASE MODIFY FILE syntax, setting the publication database offline, copying the files to the new location, and bringing it back online.

I would start with shrinking the transaction log and see if that helps.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.