SQL Server 2014 Failover cluster - Nodes on different patch levelsFailover cluster connection issueComplete...
How to properly claim credit for peer review?
How to mitigate "bandwagon attacking" from players?
Why is working on the same position for more than 15 years not a red flag?
Where is this triangular-shaped space station from?
How to tighten battery clamp?
Book where the good guy lives backwards through time and the bad guy lives forward
How do I construct an nxn matrix?
Non-Italian European mafias in USA?
Hacker Rank: Array left rotation
Waiting for the gravy at a dinner table
You'll find me clean when something is full
Is there a German word for “analytics”?
Why does Starman/Roadster have radial acceleration?
It took me a lot of time to make this, pls like. (YouTube Comments #1)
Compare four integers, return word based on maximum
Should I choose Itemized or Standard deduction?
CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?
Must a tritone substitution use a dominant seventh chord?
Find the next monthly expiration date
What's the difference between a cart and a wagon?
If nine coins are tossed, what is the probability that the number of heads is even?
Is there a frame of reference in which I was born before I was conceived?
How would we write a misogynistic character without offending people?
Closure of presentable objects under finite limits
SQL Server 2014 Failover cluster - Nodes on different patch levels
Failover cluster connection issueComplete Failover Cluster Failure SQL Server 2012SQL Server 2008 R2 Cluster Service pack 3 fail to failover nodeInstalling a SQL Server patch on a node within a 2-Node FCIProblem installing SQL Failover clusterMulti-Instance Failover Cluster SQL ClusterIs it possible to have one Sql-Server cluster node in multiple Sql-Server clusters?SQL Server 2008 Patch on Clustered ServerSQL Server Cluster: There is no SQL Server failover cluster available to joinInstall new SQL Server cluster instance on existing cluster without downtime
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
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
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
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
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
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
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 Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
edited Jan 22 at 7:39
a_horse_with_no_name
40.3k777112
40.3k777112
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
asked Jan 19 at 23:01
Halt_And_Catch_FireHalt_And_Catch_Fire
798
798
add a comment |
add a comment |
2 Answers
2
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
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
add a comment |
SQL Server versions on nodes were different and SQL Server needed to do upgrade or downgrade after failover. This increased failover time.
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
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
2 Answers
2
active
oldest
votes
2 Answers
2
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
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
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
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
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
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
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
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
edited Jan 21 at 21:52
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
answered Jan 19 at 23:56
KASQLDBAKASQLDBA
5,47261944
5,47261944
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
add a comment |
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
Thank you @KASQLDBA .. Node1 is on 12.0.5522 and Node2 is on 12.0.5538.
– Halt_And_Catch_Fire
Jan 21 at 21:44
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
@Halt_And_Catch_Fire -- you can compare the differences by going on each patch here - sqlserverbuilds.blogspot.com/#sql2014
– KASQLDBA
Jan 21 at 21:50
add a comment |
SQL Server versions on nodes were different and SQL Server needed to do upgrade or downgrade after failover. This increased failover time.
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
add a comment |
SQL Server versions on nodes were different and SQL Server needed to do upgrade or downgrade after failover. This increased failover time.
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
add a comment |
SQL Server versions on nodes were different and SQL Server needed to do upgrade or downgrade after failover. This increased failover time.
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
SQL Server versions on nodes were different and SQL Server needed to do upgrade or downgrade after failover. This increased failover time.
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
answered 7 mins ago
Halt_And_Catch_FireHalt_And_Catch_Fire
798
798
add a comment |
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
