Timeline for What happens when you restore the same transaction log multiple times?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2019 at 14:44 | vote | accept | Brian Lund Larsen | ||
| Aug 9, 2016 at 15:32 | comment | added | Scott Hodgin - Retired | I 'think' you just need a common 'share' that they both can reach. The primary would write logs to the 'share' and the secondary would read from the 'share'. One thing that is worrisome is you are using Enterprise backups and restoring to non-Enterprise servers. That would be a problem if someone decides to start using 'Enterprise-Only' functionality (like data compression) in the source database because the target won't support it. | |
| Aug 9, 2016 at 15:13 | comment | added | Brian Lund Larsen | Thanks. I am not really trying to accomplish something by restoring the same log file again and again, I just noticed that it was possible by accident and wonder if it has any negatives (so that I need to keep closer track of what log files I have restored already). The two servers can't communicate directly, which I believe is needed for log shipping. | |
| Aug 9, 2016 at 15:04 | history | answered | Scott Hodgin - Retired | CC BY-SA 3.0 |