Environment:
SQL Server Editions:
SQL Server 2000, SP 4
SQL Server 2005, SP 2 with Cummulations Hotfix (kb918222)
O.S.
Windows 2003 Server R2, SP 2

Clustered Production Environment

Node 1
Tools not installed
Node 2
Tools Installed

Summary:
I logged onto the virtual server with an admin account and was unable to
create a maintenance plan and tools did not display. Research at the
following site seems to point to the culprit.

https://connect.microsoft.com/SQLSer...&wa=wsignin1.0

Node 1
Start | programs | Microsoft SQL Server 2005
SQL Server Business Intelligence Development studio is not displayed

Node 2
Start | programs | Microsoft SQL Server 2005
SQL Server Business Intelligence Development studio is displayed

Install tools:
Node 1
Settings | Control Panel | Add or Remove Programs | SQL Server 2005 | Change

Walk through the wizard
The Component Checker states that there are different versions of the tool
installed.
Install components dialog
Select "install all tools", Next

The dialog window states that the tools are already installed and the
installed components are an older version.
close all windows.

Check Start Menu:

Start | all Programs | Microsoft SQL Server 2005 | SQL Server Business
Intelligence Development studio
Rt. Click | Properties | "C:\Program files\crosoft Visual Studio
8\Common7\IDE\Devenv.exe"

A Search for the executible failed on all drives.


Any ideas?

MJS

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote

By Design.

Tools are not installed via the cluster install mechanism. Only
cluster-aware components (SQl Server Engine and SSAS) are installed
cluster-wide on SQL 2005. SQL 2000 does install tools cluster wide. SQL
2008 does everything local and then lets you add the installed node to an
existing cluster.

The behavior you document is normal and expected.

Patching clusters gets even more complicated.

http://weblogs.sqlteam.com/geoffh/ar...n-Patches.aspx


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"mj" <mj (AT) discussions (DOT) microsoft.com> wrote