SQL Server 2014 Failover cluster - Nodes on different patch levels
As part of trouble shooting a performance issue with a SQL Server cluster I found out that the nodes haven't been patched properly to the same level. It is a 2 node active / passive cluster. SQL Server performance was much better on node with higher patch level.
The nodes have been patched to the same level now.
Just trying to understand how SQL Server and the would have behaved in this sort of a scenario?
Would this patch level miss match have caused other issue with the cluster?
sql-server clustering
add a comment |
As part of trouble shooting a performance issue with a SQL Server cluster I found out that the nodes haven't been patched properly to the same level. It is a 2 node active / passive cluster. SQL Server performance was much better on node with higher patch level.
The nodes have been patched to the same level now.
Just trying to understand how SQL Server and the would have behaved in this sort of a scenario?
Would this patch level miss match have caused other issue with the cluster?
sql-server clustering
add a comment |
As part of trouble shooting a performance issue with a SQL Server cluster I found out that the nodes haven't been patched properly to the same level. It is a 2 node active / passive cluster. SQL Server performance was much better on node with higher patch level.
The nodes have been patched to the same level now.
Just trying to understand how SQL Server and the would have behaved in this sort of a scenario?
Would this patch level miss match have caused other issue with the cluster?
sql-server clustering
As part of trouble shooting a performance issue with a SQL Server cluster I found out that the nodes haven't been patched properly to the same level. It is a 2 node active / passive cluster. SQL Server performance was much better on node with higher patch level.
The nodes have been patched to the same level now.
Just trying to understand how SQL Server and the would have behaved in this sort of a scenario?
Would this patch level miss match have caused other issue with the cluster?
sql-server clustering
sql-server clustering
edited 18 mins ago
a_horse_with_no_name
39.1k775112
39.1k775112
asked 2 days ago
Halt_And_Catch_FireHalt_And_Catch_Fire
678
678
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Well that can be possible depending upon which patch you applied. If you refer to Microsoft documentation for the versions, you will see the description of what's different between those 2 patch builds . For example 2014 SP3 have some performance gains compared to SP2. Again it might be possible because of different patch but performance gain include various other factors as well. If you share more details like what improvements you see might help further.
To check whats new in patch that has been introduced please refer sqlserverbuilds
Also, as a good practice you should have both the nodes on same patch versions.
Moreover There is 2014SP3
latest , so you can test that SP in lower env and decide to push in prod once all looks GREEN across both the nodes
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
add a comment |
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%2f227589%2fsql-server-2014-failover-cluster-nodes-on-different-patch-levels%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well that can be possible depending upon which patch you applied. If you refer to Microsoft documentation for the versions, you will see the description of what's different between those 2 patch builds . For example 2014 SP3 have some performance gains compared to SP2. Again it might be possible because of different patch but performance gain include various other factors as well. If you share more details like what improvements you see might help further.
To check whats new in patch that has been introduced please refer sqlserverbuilds
Also, as a good practice you should have both the nodes on same patch versions.
Moreover There is 2014SP3
latest , so you can test that SP in lower env and decide to push in prod once all looks GREEN across both the nodes
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
add a comment |
Well that can be possible depending upon which patch you applied. If you refer to Microsoft documentation for the versions, you will see the description of what's different between those 2 patch builds . For example 2014 SP3 have some performance gains compared to SP2. Again it might be possible because of different patch but performance gain include various other factors as well. If you share more details like what improvements you see might help further.
To check whats new in patch that has been introduced please refer sqlserverbuilds
Also, as a good practice you should have both the nodes on same patch versions.
Moreover There is 2014SP3
latest , so you can test that SP in lower env and decide to push in prod once all looks GREEN across both the nodes
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
add a comment |
Well that can be possible depending upon which patch you applied. If you refer to Microsoft documentation for the versions, you will see the description of what's different between those 2 patch builds . For example 2014 SP3 have some performance gains compared to SP2. Again it might be possible because of different patch but performance gain include various other factors as well. If you share more details like what improvements you see might help further.
To check whats new in patch that has been introduced please refer sqlserverbuilds
Also, as a good practice you should have both the nodes on same patch versions.
Moreover There is 2014SP3
latest , so you can test that SP in lower env and decide to push in prod once all looks GREEN across both the nodes
Well that can be possible depending upon which patch you applied. If you refer to Microsoft documentation for the versions, you will see the description of what's different between those 2 patch builds . For example 2014 SP3 have some performance gains compared to SP2. Again it might be possible because of different patch but performance gain include various other factors as well. If you share more details like what improvements you see might help further.
To check whats new in patch that has been introduced please refer sqlserverbuilds
Also, as a good practice you should have both the nodes on same patch versions.
Moreover There is 2014SP3
latest , so you can test that SP in lower env and decide to push in prod once all looks GREEN across both the nodes
edited 10 hours ago
answered 2 days ago
KASQLDBAKASQLDBA
5,19361943
5,19361943
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
add a comment |
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
10 hours ago
add a comment |
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%2f227589%2fsql-server-2014-failover-cluster-nodes-on-different-patch-levels%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