"loki" <loki5100-> wrote in message
news:638E3E37-4D40-4CC3-8700-...
> yea i thing of it, but the automatique update is not so bad if their is no
> reboot !
>
> stephane
Stephanie.. the point here is that until you do the reboot.. the update is
not actually installed.
Furthermore, if only *some* of the files in a multi-file update get
installed, you may cause instabilities in applications/services that
subsequently try to use the new files in combination with the old (not yet
updated) files, which can (in rare cases) cause behavior as severe as a full
system crash. I doubt you want a database server crashing as a result of
maintenance choices.
If you're not going to reboot the server, there's no point in doing the
installation(s).
Do the installations WHEN you can safely restart the server immediately
afterward.
>>> their is no user logged in, it's a database server ... i want simply
>>> that when a user will next log on the computer, a dialog box will alarm
>>> it to restart the computer
And on a *database server*, you absolutely do not want to install updates
and defer the installation -- and certainly not until the next time a user
happens to log onto the server. As a DBA, I could go for weeks without ever
actually logging onto a SQL Server console because *everything* was done via
a remote session of SSMS.
In fact, the *only* time I did log onto the console of a SQL Server was,
actually, to install updates! Those updates were installed during a
scheduled maintenance window we had defined in our SLA, and if the
installation required a reboot, then the reboot happened during that same
2-hour window.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin
Similar Threads
Linear Mode
