Failover cluster server that is subscriber in trans. replication, possible to failover apps to server B in...
(Sorry for shotty title, max characters FTL.)
Once in a while, I'll run into issues with my transactional replication when my publisher's schema changes. For example, sometimes we'll add new fields to one of the publisher tables, and then transactional replication will stop syncing (without warning) to the correlating subscriber table.
The fix for this in the past has been to force the publisher database to take a new snapshot and let it sync everything over again, which unfortunately takes a long time, and locks the subscriber tables causing major downage for applications that depend on the subscriber database. (The publisher database is from a vendor application - Dynamics AX - so I don't have a lot of flexibility here.)
We're planning on setting up a failover cluster via Always On AGs for our subscriber server (for other reasons) but I was curious if this could help mitigate the issue we experience with our replication.
For example, could the applications that depend on the subscriber database failover to the server B in the cluster while server A is locked up as my publisher (server C) is taking a new snapshot and syncing back down to server A?
(Note: We're currently running our servers on SQL Server 2008 R2 but will be upgrading to 2019 when we setup our failover cluster, so I tagged this accordingly.)
sql-server availability-groups transactional-replication failover sql-server-2019
asked 7 mins ago
J.D.J.D.
462311
add a comment |
(Sorry for shotty title, max characters FTL.)
Once in a while, I'll run into issues with my transactional replication when my publisher's schema changes. For example, sometimes we'll add new fields to one of the publisher tables, and then transactional replication will stop syncing (without warning) to the correlating subscriber table.
The fix for this in the past has been to force the publisher database to take a new snapshot and let it sync everything over again, which unfortunately takes a long time, and locks the subscriber tables causing major downage for applications that depend on the subscriber database. (The publisher database is from a vendor application - Dynamics AX - so I don't have a lot of flexibility here.)
We're planning on setting up a failover cluster via Always On AGs for our subscriber server (for other reasons) but I was curious if this could help mitigate the issue we experience with our replication.
For example, could the applications that depend on the subscriber database failover to the server B in the cluster while server A is locked up as my publisher (server C) is taking a new snapshot and syncing back down to server A?
(Note: We're currently running our servers on SQL Server 2008 R2 but will be upgrading to 2019 when we setup our failover cluster, so I tagged this accordingly.)
sql-server availability-groups transactional-replication failover sql-server-2019
asked 7 mins ago
J.D.J.D.
462311
add a comment |
(Sorry for shotty title, max characters FTL.)
Once in a while, I'll run into issues with my transactional replication when my publisher's schema changes. For example, sometimes we'll add new fields to one of the publisher tables, and then transactional replication will stop syncing (without warning) to the correlating subscriber table.
The fix for this in the past has been to force the publisher database to take a new snapshot and let it sync everything over again, which unfortunately takes a long time, and locks the subscriber tables causing major downage for applications that depend on the subscriber database. (The publisher database is from a vendor application - Dynamics AX - so I don't have a lot of flexibility here.)
We're planning on setting up a failover cluster via Always On AGs for our subscriber server (for other reasons) but I was curious if this could help mitigate the issue we experience with our replication.
For example, could the applications that depend on the subscriber database failover to the server B in the cluster while server A is locked up as my publisher (server C) is taking a new snapshot and syncing back down to server A?
(Note: We're currently running our servers on SQL Server 2008 R2 but will be upgrading to 2019 when we setup our failover cluster, so I tagged this accordingly.)
sql-server availability-groups transactional-replication failover sql-server-2019
asked 7 mins ago
J.D.J.D.
462311
(Sorry for shotty title, max characters FTL.)
Once in a while, I'll run into issues with my transactional replication when my publisher's schema changes. For example, sometimes we'll add new fields to one of the publisher tables, and then transactional replication will stop syncing (without warning) to the correlating subscriber table.
The fix for this in the past has been to force the publisher database to take a new snapshot and let it sync everything over again, which unfortunately takes a long time, and locks the subscriber tables causing major downage for applications that depend on the subscriber database. (The publisher database is from a vendor application - Dynamics AX - so I don't have a lot of flexibility here.)
We're planning on setting up a failover cluster via Always On AGs for our subscriber server (for other reasons) but I was curious if this could help mitigate the issue we experience with our replication.
For example, could the applications that depend on the subscriber database failover to the server B in the cluster while server A is locked up as my publisher (server C) is taking a new snapshot and syncing back down to server A?
(Note: We're currently running our servers on SQL Server 2008 R2 but will be upgrading to 2019 when we setup our failover cluster, so I tagged this accordingly.)
sql-server availability-groups transactional-replication failover sql-server-2019
sql-server availability-groups transactional-replication failover sql-server-2019
asked 7 mins ago
J.D.J.D.
462311
asked 7 mins ago
J.D.J.D.
462311
asked 7 mins ago
J.D.J.D.
462311
asked 7 mins ago
J.D.J.D.
462311
asked 7 mins ago
J.D.J.D.
462311
462311
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231618%2ffailover-cluster-server-that-is-subscriber-in-trans-replication-possible-to-fa%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f231618%2ffailover-cluster-server-that-is-subscriber-in-trans-replication-possible-to-fa%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
