Tried running sp_removedbreplication with the database in simple mode,
however it produced a transaction log of over 22Gb (all our disk space
available) and crashed out. This table is 16Gb at the moment.
Been on the original server that was the Publisher and there is no
subscription, so still don't understand where the data is coming from !
What are the implications of doing a "truncate table msreplication_queue" ?
I'm assuming this would not create any logging and simply move the HWM ?
Does anyone have any further suggestions with our limited disk space ?
Cheers
[quoted text, click to view] "Luci Charming" wrote:
> Thanks again Paul
>
> Plan to do this tonight out of hours tonight, going with your second
> suggestion by
> putting db in simple mode and trying sp_removedbreplication on the
> subscriber first.
>
> Cheers
> Luci
>
> PS Glad you answered as I found this forum through your replicationanswers
> website Thank you again !
>
> "Paul Ibison" wrote:
>
> > Hi Luci,
> > I was suggesting sp_removedbreplication for the case where the publisher was
> > not available, but this should still be ok. If you run sp_dropesubscription
> > on the publisher we should be back to normal. The balooning of the
> > transaction log on the subscriber is normal when you are deleting so much
> > data. You might want to backup the log and then shrink it, or if the log is
> > not required for the backup strategy, you could use simple recovery mode and
> > then shring the log file.
> > HTH,
> > Paul Ibison
> >
Hi
Just to let you know we got there in the end.
Ended up truncating the msreplication_queue_table, then tried
sp_removedbreplication again which failed as it couldn't drop tables and the
tempdb couldn't extend. So, manually dropped the tables in question, after
which
the sp_removedbreplication did work. Thank you for your help. Cheers Luci
[quoted text, click to view] "Paul Ibison" wrote:
> What I'd probably try is to delete the queue records in batches. The batch
> size could be 10000 and each time round the loop you backup the log with
> truncate_only set. this way the records will get removed without balooning
> the log, and you can drop the subscription at the end...
> HTH,
> Paul Ibison
>
Don't see what you're looking for? Try a search.
