All replies

How did you remove replication? If you do exec sp_dboption inside the database, is one of the rows returned equal to "published"? If so, the database is still published for transactional replication, which is the reason your log is still growing.

Since you removed replication altogether for the database, you can try sp_removedbreplication, although i don't think it will make a difference at this point.

Did you back up the transaction log? If the database recovery model is set to FULL, you can't reduce the size of the file until you back up the transaction log. If the databse recovery model is set to SIMPLE, but the log size continues to grow, then can you verify you don't have any large transactions running in the background?

Hi All,I have a problem similar to this one. I can't run my regularly scheduled maintenance backup for this db. The message is log_reuse_wait column =6 (REPLICATION).

This db is technically no longer in replication - the old replication job was deleted, the subcription was removed from the subscriber db, but when I try to delete the subscription and the publication from the publisher db, I get the error:

"The transaction log for db 'mydb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases."

So - I can't delete the old replication or alter the dboptions since the trans log is full, and I can't shrink the trans log because the db is still listed as being in replcation.