We had a log file that wouldn't stop growing even though we do backups. Turns out that replication had been turned on for that database. None of us DBAs did that (at least as far as we know). So, two questions.
- Can you tell after the fact who or what turned on replication. (We noticed that when we turned off replication there were no entries in the log.)
- What operations can turn on replication WITHOUT the executioner (there's a better word for that) of the operation to know that they are turning on replication.
Thanks in advance. We have fixed the problem but want to make sure it doesn't repeat itself.