November 15, 2004 at 2:01 pm
We recently installed the October security updates (MS04-029 through MS04-038). Since installing these patches, whenever we remove, install or patch a new instance the server requires a reboot. For example if I install a new SQL 2000 instance, I can not load SQL SP3 without rebooting the box first. Prior to this we could add new instances during production time without any issues. We are mandated to have these patches on the server so I can not remove them. Also we are an International company so scheduling time for reboots is very difficult. We are in the middle of a huge SQL server consolidation project. If anyone had ran into this and has a way to get the old functionality back, I would appreciate the advice.
November 15, 2004 at 4:53 pm
Marsha,
are your SQL servers running on NT 4.0? if so i'm not hugely surprised! i have had no problem with this on 2003 server, or 2000 (from what i can remember).
lloyd
November 16, 2004 at 7:59 am
No, we are running on 2003 Enterprise Edition. Our SQL version is 2000. Like I said, we never had this problem until the laterst server patches were applied.
November 16, 2004 at 12:57 pm
Hi,
I am not sure about patches but I do have this task (not a problem) whenever I install SQL Server on Windows 2000 and Windows 2003 servers. As well as installing other SW on servers and workstations. In most cases it would let me NOT to reboot after the original install for example when SQL Server is installed. But I can not install anything else before I reboot with the message saying 'You have to reboot, the previous installation is pending" I am absolutely positive that it is going on not since October but at least for a year or two.
Anyway, this is a good practice to reboot the server after the SW or Service Packs are installed as well as having a scheduled maintenance window of opportunity once in a while.
Yelena
Regards,Yelena Varsha
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply