May 3, 2010 at 12:13 pm
Hi,
We have 3 node active/active/passive cluster setup for SQL Server 2005 EE x64 with SP3. On node1, SSIS and Reporting services(Disables & NOT using) has installed, but NOT on node2 & node3.
Maintenance plans were created on node1 (having SSIS) & node2 (NOT having SSIS) and they are running fine on both nodes.
Now I want to upgrade to SQL Server 2008 using in-place upgrade for the instances on node1 & node2.
1. Do I need to Uninstall both SSIS & Reporting services from Node1 before I starting the inplace upgrade to SQL Server 2008 (according to the KB article 955949, FIX: Cluster upgrade to SQL Server 2008 fails when SQL Server 2005 cluster nodes have different installed features
http://support.microsoft.com/kb/955949
)
2. Does maintenance plans require to have SSIS installed on node1?
3. I know that on node3, without SSIS, maintenance plans running fine. But want to make sure to find this information in BOL. I appreciate if you provide me the link where it says " SSIS is not required to create & run the Maintenance plans?
3. we do have management studio on both the active nodes but NOT on passive node. So does it require to install Management studio on passive node and apply SP3 for that before performing the in-place upgrade to SQL Server 2008? please see the attachment.
Thank you
May 3, 2010 at 4:33 pm
I wouldn't mess with the in place upgrade if I were you...
May 3, 2010 at 6:06 pm
I wouldn't mess with the in place upgrade if I were you...
I know its better to go for side-by-side upgrade method. But our servers are only 1 year old. So donot have other option. I must need to go wit hin-place upgrade method.
June 16, 2010 at 12:57 am
hi,
Do we require SSIS to be installed in order to create Maintenance plans? or just Database engine installation is enough to create Maintenance plans?
thanks
June 21, 2010 at 3:42 am
our servers are only 1 year old. So donot have other option.
You always have an option.
At the very minimum, you should do a risk assessment of an in-place upgrade. Include in your assessment the possibility you may even need to re-install Windows during the upgrade to overcome some problems. Present this to your management, and if they insist on doing an in-place upgrade then your back is at least partially covered if things go wrong. If uptime is critical to your business, then management should see the cost of new servers is far smaller than the cost of outage if your upgrade has problems.
By far the best option is to use what is called 'swing kit'. Most installations have spare servers available so they can be used for an upgrade. When the upgrade is over, the original servers get put into the swing kit pool for someone else to use.
You also need to test your upgrade plan. This means doing an upgrade on a non-production cluster and seeing what works and what problems you may have for your production upgrade.
One problem I have seen when upgrading to SQL 2008 is that the install of .Net 3.5 SP1 sometimes fails. Sometimes the tools from Microsoft designed to get over this problem work, sometimes they do not. If you cannot get a successful .Net install, then you have to reinstall Windows to get past this problem. This situation does not often happen, but you should not ignore the possibility it might.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply