Timeline for Failover strategy for SQL Server 2016 Standard Edition
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14, 2019 at 3:34 | history | became hot network question | |||
| Aug 14, 2019 at 2:43 | comment | added | Jonathan Fite | I would suggest adding another server to the mix and use either FCI or Basic Availability Groups for your actual HA, while keeping the transnational replication for reporting. With FCI/BAG the cold (emphasis on cold) spare is free. But anything you read from (such as your transnational replication recipient has to be licensed. | |
| Aug 13, 2019 at 20:21 | answer | added | BradC | timeline score: 3 | |
| Aug 13, 2019 at 20:10 | answer | added | David Browne - Microsoft | timeline score: 4 | |
| Aug 13, 2019 at 19:54 | comment | added | user9516827 | @LowlyDBA:Added that to question.Thanks for pointing out. | |
| Aug 13, 2019 at 19:54 | history | edited | user9516827 | CC BY-SA 4.0 | added 114 characters in body |
| Aug 13, 2019 at 19:46 | comment | added | user9516827 | @LowlyDBA : Basic Availability Groups won't allow read in the secondary server. | |
| Aug 13, 2019 at 19:43 | history | edited | LowlyDBA - John M | CC BY-SA 4.0 | Typos |
| Aug 13, 2019 at 19:40 | history | edited | MDCCL | CC BY-SA 4.0 | Pronoun capitalization; grammar; punctuation; etc. |
| Aug 13, 2019 at 19:31 | history | asked | user9516827 | CC BY-SA 4.0 |