May 9, 2007 at 8:55 am
Hi all:
So far every question that I posted here, It was able to solve my problems, Thanks you to all, now the following question:
We have a Cluster 2 node SQL Server 2005, and 2 Instances, one Prod and the other QA, When I logon onto the node one and start SQL Server management Studio, I can set up both instances and access the databases, create new "maintenance plans" on the first node (Prod), but when I get into the second Instance (QA) and I want to create a new "Maintenance plan" I get the following message:
" ITLE: Microsoft SQL Server Management Studio
------------------------------
The action you attempted to perform on a remote instance of SQL Server has failed because the action requires
a SQL Server component that is not installed on the remote computer.
To proceed, install SQL Server 2005 Management Tools on the remote computer,
and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)"
in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 .
(ObjectExplorer)"
Do I need to install the Mangement Tools on the second Instance, How do I do that?.
Please help.
Thanks
Pablo Campanini
May 9, 2007 at 12:10 pm
Pablo,
SQL 2005 maintenance plans make use of SSIS. SSIS is not installed as a cluster resource. You need to maually install it on both nodes in order to se it. The same can be sad about the client tools, notification services and reporting services. Only the database engine and analysis services are capable of clustering and only these two will be automatically installed on both nodes.
So I assume that SSIS is not installed on node 2 and you have to install it. Also keep this in mind when installing service packs.
Markus
[font="Verdana"]Markus Bohse[/font]
May 9, 2007 at 2:53 pm
May 10, 2007 at 10:53 am
in my paranoid mind whenever I do anything like install SQL on a cluster or a service pack i like to do the following.
fail everything over to node A and install
fail everything over to node B and run the install again
fail back one of the groups to it's original node and run your stuff
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply