July 6, 2009 at 1:32 pm
Greetings All,
I am attempting to install SQL 2005 SP3 on a multi-instance (Active/Active) cluster. Unfortunately, the C: drive of the 'passive' node has precious little space available (i.e. insufficient to allow the decompression of the files needed) . Is there a way to specify another location for the UpdateTemp folder that is created on the inactive (currently 'passive') node to avoid running out of space?
TIA,
Art
July 6, 2009 at 1:35 pm
what about the other node? in my experience all the updates starting with SP2 you run on one node and that's it
July 6, 2009 at 1:52 pm
SQL Noob (7/6/2009)
what about the other node? in my experience all the updates starting with SP2 you run on one node and that's it
That might be true for the SQL Engine, but you still have to run the SP3 on the passive node to upgrade, among others, the client components.
July 6, 2009 at 1:55 pm
That is correct, it is only executed "from" one node but it actually executes on both. In order to do that it copies all of the files necessary to the other node(s) and executes them from there. That's the rub...
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply