September 29, 2014 at 8:35 am
One common problem that is posted in the forums is a transaction log that will not clear or re-use space for accidental DBAs. In some cases, this is because replication was set up by someone else (or forgotten about) and the DBA is unaware that it is preventing a log from clearing.
I am looking for a short piece that will help someone detect replication is installed or setup in a database and how to remove replication that is unused, but preventing a log from clearing.
January 22, 2015 at 11:19 am
bump
February 3, 2015 at 4:12 am
I've run into this problem before, it'd be nice to get all the concepts together. If there's no much rush I can do it.
February 10, 2015 at 9:32 am
No rush. Please tackle it if you'd like.
March 23, 2015 at 6:02 am
Published in March 2015 -Needs closing
March 24, 2015 at 4:17 am
eric.notheisen (3/23/2015)
Published in March 2015 -Needs closing
Does it mean the article is no longer required?
I must have skipped this, because I didn't see published anything on that topic this month...
Please let me know as I've done some research and was supposed to write about, although been busy and still far from finishing..
Thanks
March 24, 2015 at 5:07 am
raulggonzalez (3/24/2015)
eric.notheisen (3/23/2015)
Published in March 2015 -Needs closingDoes it mean the article is no longer required?
Hello again, I found this one http://www.sqlservercentral.com/articles/Replication/122402/ by yourself, so I guess is the one you're talking about.
I wanted to focus more on "how to delete replication" and the REPLICATION log_wait_type, which is kinda painful sometimes.
I'm ok either if Steve wants to finish this topic or he wants me to carry on with my idea, as I said I'm far from finishing..
Please Steve let us know.
Thanks.
March 27, 2015 at 9:25 am
Apologies. Closing now.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply