Corrupt Log in Distribution dB

  • I have a corrupt log file in the distribution dB. I have been able to stop repliation by running sp_removedbreplication but I am still unable to drop the distribution dB. I have tried to restore from a backup with NO RECOVERY and MOVE options. This has not worked. Can anyone help???

    Thanks,

    Christine


    Aurora

  • Think I looked at that once a long time ago. Suggest profiling to see what bits its checking to determine that it cant be dropped. Then override that. Tried switching to simple recovery, adding a second log file, etc?

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

  • The database is marked suspect, yet the status in sysdatabases is 'normal' = 8. I have tried to over write the log file. Ah, the light bulb goes off...

    Here's how I solved it:

    1. EXEC sp_removedbreplication '<databasename>'

    2. EXEC sp_dropdistributor @no_checks =1, @ignore_distributor = 1

    [Setting those parameters (bits)= 1 essentially tells SQL not to connect to the distributor (which in this case was marked suspect and not allowing us to connect anyway)

    3. DROP DATABASE <databasename>

    Voila` it worked. And we are moving forward with restoring the distribution database. Then we disabled Publication and Replication. And finally, we set up replication.

    Thanks for your help Andy and I hope this experience helps someone else.

    Christine


    Aurora

Viewing 3 posts - 1 through 2 (of 2 total)

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