The answer is that SQL services share some common components. Plus, the
installer has some generic setup logic. Finally, are you using the same
service account for both services? If so, then permissions can get hosed
during a broken update.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
[quoted text, click to view] "dp" <dp@discussions.microsoft.com> wrote in message
news:90BAC728-916F-4497-B293-55920962EDE8@microsoft.com...
> Hi,
> We have a default clusterd SQL server 2005 with sp2 installed in one
> cluster
> group and then I have installed a default SSAS clustered instance in
> another
> cluster group and it works fine (can failover and user can connect).
> However,
> when I applying the sp2 to SSAS instance (with SSAS checked only) and it
> failed; it not noly just failed but also take down my default clustered
> sql
> server! We have to call MS to get our server up. It seems that, somehow,
> registry for default sql server got messed up by SSAS sp2. My question
> are:
> 1. Is it possible or supported to install a default SQL server and a
> default
> Analysis server on a cluster (each one in its own cluster group) with sp2;
> 2. why applying sp2 on a default AD instance in one cluster group affect a
> default sql instance in another cluster group.
>
> thanks much in advance.
>
> Zack.
>