Timeline for Best practice bring MS SQL database to remote sites
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2017 at 16:16 | answer | added | Kevin3NF | timeline score: 2 | |
| Jul 9, 2017 at 6:14 | history | edited | roberth | CC BY-SA 3.0 |
Added more info about the use case (and corrected typo)
|
| Jul 9, 2017 at 6:10 | comment | added | roberth | Thanks @DanGuzman and Peter, I edited my question to answer your questions. | |
| Jul 9, 2017 at 6:08 | history | edited | roberth | CC BY-SA 3.0 |
Added more info about the usecase
|
| Jul 8, 2017 at 23:17 | comment | added | Sir Swears-a-lot | Does your application vendor support distibuted db's or availability groups? Is this 3rd party or in house development. | |
| Jul 8, 2017 at 22:42 | comment | added | Sir Swears-a-lot | How much delay can your users/application tolerate between synchronisation? Realtime? Minutes? Hours? | |
| Jul 8, 2017 at 19:05 | comment | added | Dan Guzman | Are data read-only at the remote sites? | |
| Jul 8, 2017 at 18:54 | review | First posts | |||
| Jul 8, 2017 at 18:58 | |||||
| Jul 8, 2017 at 18:50 | history | asked | roberth | CC BY-SA 3.0 |