January 15, 2015 at 10:59 am
I have a two node SQL Server 2012 cluster running on Server 2012. On those two nodes are 4 instances, all at the following SQL patch level, SP1 CU13. I want to move 1 of them to SP2 to fix a bug in SSRS when exporting >20,000 rows to Excel.
My question is this, is having one instance ahead of the others in SP level a bad idea? I ask because during the SP install I remember there being some "shared items" that get updated. Those shared items on both nodes would be up to SP2 while 3 of the 4 instances would be on SP1. The reason to not move them all to SP2 is due to current vendor requirements.
I can't find any thing in the Googles that says if this this is bad or good, so I have come to you folks. Thank you for your time.
January 21, 2015 at 12:08 pm
One bump for fun, if no one else chimes in this will drop to the bottom. I'm half tempted to just run the instance in need to SP2 and roll with it, but I'd like to not live all dangerous without at least one internet stranger chiming in on their experiences. Thanks
January 21, 2015 at 1:51 pm
its perfectly valid to have instances with different patch levels, this is one of the main reasons why you would ring fence a particular apps database to a separate instance
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply