September 29, 2014 at 8:36 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 mirroring is in use and the mirror is down,
I am looking for an article that covers the basics of detecting mirroring is in use when the DBA did not set it up or was unaware that it is configured. Also, how to disable it so that log space can be reused.
September 29, 2014 at 9:31 am
I would not mind taking this one on, had issue with log files and AlwaysOn last week at a client.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
September 29, 2014 at 10:44 am
Feel free, but I'd like to get it moving. Please don't commit if you can't do it.
September 29, 2014 at 11:07 am
Steve Jones - SSC Editor (9/29/2014)
Feel free, but I'd like to get it moving. Please don't commit if you can't do it.
I will pass on this then, just thought I don't really have resources to setup test environment for this anyway to show examples.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
October 7, 2014 at 12:14 pm
Hi,
What kind of a time frame where you thinking about. I would like to try it out. I am currently working in an environment that uses mirroring, but still fairly new at it. This seems like I could learn a bit while writing up something.
Thanks,
Camille
October 13, 2014 at 9:02 am
No hurry. If you can get in weeks, that would be good. Months, people tend to forget about things.
October 14, 2014 at 7:18 am
OK, I can do it, I'll try to have something in a couple of weeks.
Thanks,
Camille
October 17, 2014 at 1:20 pm
Hello,
Submitted an article.
Thanks,
Camille
October 18, 2014 at 3:51 pm
Thanks, I'll take a look, but it might be a week with travel out of town this coming week.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply