October 8, 2014 at 12:42 pm
We have an active/active two-node QA cluster with four instances of sql. I need to add a fifth. In the past I always moved existing instances to the other node while installing a new instance.
Other than impacts to users from install reboots, is that a hard requirement?
QA is reluctant to have me put the four existing instances on one node for most of a day, fearing big performance slowdowns. Each node has 250GB of memory and each instance is allowed 50GB. Netapp disk backend.
October 10, 2014 at 6:29 am
Indianrock (10/8/2014)
We have an active/active two-node QA cluster with four instances of sql. I need to add a fifth. In the past I always moved existing instances to the other node while installing a new instance.Other than impacts to users from install reboots, is that a hard requirement?
QA is reluctant to have me put the four existing instances on one node for most of a day, fearing big performance slowdowns. Each node has 250GB of memory and each instance is allowed 50GB. Netapp disk backend.
I've never done this, you can install a new instance without affecting running instances. A reboot shouldnt be required for the new install of an instance. Even the attaching of the shared storage shouldnt affect the currently running instances
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 10, 2014 at 7:37 am
Thanks. I'll give it a shot. Worst that can happen is a needed reboot which we could let wait until after hours.
October 10, 2014 at 7:38 am
If you're just adding a new instance of sql server thats alreaqdy installed you shouldnt need a rebot, should be fine
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply