Timeline for Temporarily removing replication from Publisher
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2019 at 23:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 16, 2019 at 2:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 11, 2019 at 6:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Oct 4, 2015 at 8:53 | answer | added | Peter | timeline score: 1 | |
| Sep 24, 2015 at 9:03 | history | edited | Peter | CC BY-SA 3.0 |
added 137 characters in body
|
| Sep 23, 2015 at 1:23 | comment | added | Kin Shah | You should be able to make DDL changes as described in the answer. Make sure your vendor is not doing anything drastic - dropping PK, etc - replication wont allow that. Also, since you are using SQL Server 2014 Enterprise Edition, you can think of using AlwaysON and you can leverage your read requests to secondary server. Just putting it as food for thoughts. | |
| Sep 22, 2015 at 23:10 | history | edited | Peter | CC BY-SA 3.0 |
added 133 characters in body
|
| Sep 22, 2015 at 17:05 | history | edited | Peter | CC BY-SA 3.0 |
added 47 characters in body
|
| Sep 22, 2015 at 16:29 | comment | added | Spörri | Are you replicating schema changes (DDL) ? | |
| Sep 22, 2015 at 16:03 | history | edited | Hannah Vernon♦ |
edited tags
|
|
| Sep 22, 2015 at 15:30 | history | asked | Peter | CC BY-SA 3.0 |