Of course you can install any of the client tools and applications on either
node. The data server is all that fails over. If you are actively using a
client tool or application on a node that fails, your use of the application
does not fail over -it just aborts.
Generally speaking, the client tools are installed on the dba's and/or
developer's desktops and then remotely access the SQL Server cluster. It
takes a fair amount of resources from the cluster node in order to service
desktop applications. SQL Client tools are desktop applications. I would
rather have that memory, CPU time, etc., dedicated to handling the data
server's needs -not the client applications.
And since you are using one of the cluster nodes as a development server,
you will want to make sure that developers do NOT have sa (sysadmin)
privileges in the server.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
[quoted text, click to view] "Loren Z" <anonymous@discussions.microsoft.com> wrote in message
news:%23uZU$DUzGHA.2196@TK2MSFTNGP03.phx.gbl...
> Thanks for all your help Arnie. I would like to continue the thread in
> this group in that my question is more about clusters now then SQL server
> setup.
>
> As I mentioned the following products get installed on the primary node
> but not the secondary node:
>
> - Microsoft SQL Server 2005 Integration Services
> - Microsoft SQL Server 2005 Notification Services
> - Microsoft SQL Server 2005 Reporting Services
> - Microsoft SQL Server 2005 Tools
>
> Following your recommendation, we manually installed the SQL Server 2005
> Tools on the secondary node. The server is a development server and in the
> event of a failover, the above tools would still be needed. Is it possible
> to install them on the secondary server or is the cluster striclty for
> data redundancy and not application redundancy?
>
>
> "Arnie Rowland" <arnie@1568.com> wrote in message
> news:%23orqSJTzGHA.4816@TK2MSFTNGP06.phx.gbl...
>> Hi Loren,
>>
>> It is usually a good idea to either deliberately 'cross-post', or to NOT
>> post the same question to several groups. You get better assistance here
>> if we are able to bounce ideas off of each other.
>>
>> See the response to your question in microsoft.public.sqlserver.setup.
>>
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>>
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>>
>> "Loren Z" <anonymous@discussions.microsoft.com> wrote in message
>> news:%23IeP5$SzGHA.3584@TK2MSFTNGP02.phx.gbl...
>>>I am doing an SQL Server 2005 Cluster install. The install appeared to go
>>>okay. On the active node everything installed fine. However, when we
>>>looked at the other node only the configuration tools got installed. SQL
>>>Server Management Studio did not get installed. Would anyone know what
>>>caused this and how to install the SQL Server 2005 on a cluser correctly?
>>>I understand that that the management tools only get installed on the
>>>primary node. Should I run setup on the secondary node to install the
>>>tools?
>>>
>>> I also went through the summary log for the install and noticed that
>>> almost everything that was installed on the active node was also
>>> installed on the passive node. The products that did not get installed
>>> on the passive node were:
>>>
>>> - Microsoft SQL Server 2005 Integration Services
>>> - Microsoft SQL Server 2005 Notification Services
>>> - Microsoft SQL Server 2005 Reporting Services
>>> - Microsoft SQL Server 2005 Tools
>>>
>>> Should not these have been installed on the passive node as well?
>>>
>>>
>>
>>
>
>