October 1, 2009 at 9:09 am
I have two instances of SQL Server [2005] on my box. The second one was created post-Install of MSSQL, when I installed SharePoint MOSS 2007.
<MachineName>\VM_DC\VM_DC_SQLSERVER
<MachineName>\VM_DC\OFFICESERVERS
When I installed MSSQL 2005 SP3 (disk-based install) the dialog box with
desired updates would not allow me to check OFFICESERVERS. Hence, only
the VM_DC_SQLSERVER (originally MSSQL installed instance) was updated to 9.00.4035 (SP3 1st rel.).
This is particularly important as I need to upate to 9.00.4026 (Jun 16 09) on
both instances ASAP.
Thanks,
Zee
General Dynamics I.T. - SS DBA
Atlanta, GA
October 1, 2009 at 9:23 am
Is the other instance running and not set to disabled start up mode when running the SP3 installer?
October 1, 2009 at 11:51 am
I have set the secondary instance to Manual in OS Services (Startup mode) and Stopped the instance when I run the .EXE to install SP3.
Only <Machinename>\OFFICESERVERS is active and running as SS instance.
When the Feature Selection dialog comes up for SP3, it still disallows
selection of OFFICESERVERS (checkbox) and only allows selection of the
originally installed instance <machineName>_SQLSERVER for installing SP to.
Is there an MSSQL configuration for startup? Maybe I can just delete the original MSSQL instance entirely and keep the one that I want active.
Thanks,
Zee
Atlanta, GA
October 1, 2009 at 12:02 pm
I deleted the second (original) SS instance using ARPWrapper /Remove from DOS shell (Administrator priveledges).
If you want to reply it may help me down the road as I might have mutliple SS instances on a single machine I need to patch and update in tandem.
Thanks for replying to my post.
😛 Zee
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply