October 15, 2015 at 2:42 am
Hi,
I wonder if anyone can help.
I have a client with a 4 node SQL 2008R2 SP1 cluster. They now want a new node with SQL 2008R2 SP2, is this going to cause problems for me?
My recommendation is to upgrade them all to SP 2 or 3.
However, they want me to build a virtual environment and test it.
Thanks, Phil
October 15, 2015 at 3:15 am
How many instances are running on that cluster?
Mixing service pack levels is supported.
You can have different instances with different service pack levels.
What is not supported is having the same instance with different servie pack levels on different nodes. This should happen only during rolling upgrade work.
-- Gianluca Sartori
October 15, 2015 at 3:25 am
Thanks for the quick response.
Its currently has 5 instances, 1 of which is Analysis services. It also (don't know why as its 2008 cluster) has MSDTC as a resource.
October 16, 2015 at 4:39 am
phil.layzell (10/15/2015)
Thanks for the quick response.Its currently has 5 instances, 1 of which is Analysis services. It also (don't know why as its 2008 cluster) has MSDTC as a resource.
MSDTC may still be required, 2008 doesn't remove the need for it. What it did do was to allow multiple DTC resources which you could map to multiple cluster roles
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 17, 2015 at 5:10 pm
Firstly, thanks for the response. 🙂
I get that, but I thought that by default MSDTC service is running locally, even with Failover Clustering installed and therefore you didn't need to have it running as a resource?
Whoever created this cluster installed MSDTC as a resource, would they have had a reason why they did it like this?
Thanks, Phil
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply