Timeline for Compatibility mode change does not reflect on secondaries
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2020 at 22:14 | history | bounty ended | BeginnerDBA | ||
| Jun 2, 2020 at 20:19 | vote | accept | BeginnerDBA | ||
| Jun 2, 2020 at 18:00 | history | edited | Kin Shah | CC BY-SA 4.0 |
added 115 characters in body
|
| Jun 2, 2020 at 17:58 | comment | added | Kin Shah | Logshipping is physical copy of transaction log, so it will reflect it when the log backup is restored. I will clarify my answer. (I missed the point that you have db in standby mode in LS). | |
| Jun 2, 2020 at 16:29 | comment | added | BeginnerDBA | it looks like you answer seems not valid unless i misunderstood. Log shipping read only database reflects the change once ls backup,copy restores completes with change. Just tested and it does not need dr activity on LS side | |
| Jun 2, 2020 at 0:23 | comment | added | BeginnerDBA | thanks: Mirror failover/failback definitely works. But for LS as that is not a DR, just a read only for primary db, doing reverse log shipping might not be approved case in our scenario. so looks like no easy way for LS | |
| Jun 1, 2020 at 21:02 | comment | added | Kin Shah | @BeginnerDBA updated my answer. | |
| Jun 1, 2020 at 21:02 | history | edited | Kin Shah | CC BY-SA 4.0 |
added 421 characters in body
|
| Jun 1, 2020 at 18:46 | comment | added | BeginnerDBA | excellent, thanks for clarifying because bases on my test it was not reflecting. My major concern here and will appreciate if you can add as input to your answer how can i really get this changed without breaking LS or mirroring if possible. if not possible then we have to break mirroring and LS which seems too tedious for VLDB's in production | |
| Jun 1, 2020 at 18:28 | history | answered | Kin Shah | CC BY-SA 4.0 |