Multiple authorized reboots and the effects on SQL Server service

Is their a detrimental affect on SQL Server if the server is rebooted again
shortly after a previous reboot, this may occur several times in succession?
Scenario:
Multiple patches have to be applied. Several patches necessitate reboot of
server. Administrator applies the first round of patches, reboots and as
soon as the admin can login again and apply the next round of patches the
server is rebooted again.
My question is this; Does SQL service do any initialization stuff on boot up
that could cause problems if it was interrupted before completing tasks
before next reboot occurs?
Is this is a potential problem is their a standard operating procedure for
this scenario?
Thanks,
John DolinkaHi,
The best method is to "Make the MSSQL Server service to manual". This will
ensure that SQL Server will not be started on each reboot.
Once you are donw with every thing, you could change the service to
Automatic and start the service.
Thanks
Hari
SQL Server MVP
"John Dolinka" <jrd7_nospam@.cdc.gov> wrote in message
news:%234Br$39WFHA.2692@.TK2MSFTNGP15.phx.gbl...
> Is their a detrimental affect on SQL Server if the server is rebooted
> again shortly after a previous reboot, this may occur several times in
> succession?
>
> Scenario:
> Multiple patches have to be applied. Several patches necessitate reboot
> of server. Administrator applies the first round of patches, reboots and
> as soon as the admin can login again and apply the next round of patches
> the server is rebooted again.
>
> My question is this; Does SQL service do any initialization stuff on boot
> up that could cause problems if it was interrupted before completing tasks
> before next reboot occurs?
>
> Is this is a potential problem is their a standard operating procedure for
> this scenario?
>
> Thanks,
>
> John Dolinka
>|||>> Does SQL service do any initialization stuff on boot up that could cause
Yes, it does some initialization. Look in the SQL Server log and you might
see entries like:
Starting up database <x>
<x> transactions rolled forward in database <y>
<x> transactions rolled back in database <y>
Recovery is checkpointing database <x>
Analysis of database <x> is 20% complete
Usually this initialization and loading does not take too much time. I
guess that it might be posible to reboot, patch, and reboot before SQL
Server had a chance to fully recover a database. You should keep in mind
that SQL Server is an enterprise level application and it is designed to
store data. Part of the features that are built into it should allow it to
handle the multiple quick reboot situation. I will say that I have never
tried to break SQL Server by rebooting it but I hae experienced multiple
machine reboots in fast succession and I have never observed an error due to
the reboots.
Keith
"John Dolinka" <jrd7_nospam@.cdc.gov> wrote in message
news:%234Br$39WFHA.2692@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Is their a detrimental affect on SQL Server if the server is rebooted
> again shortly after a previous reboot, this may occur several times in
> succession?
>
> Scenario:
> Multiple patches have to be applied. Several patches necessitate reboot
> of server. Administrator applies the first round of patches, reboots and
> as soon as the admin can login again and apply the next round of patches
> the server is rebooted again.
>
> My question is this; Does SQL service do any initialization stuff on boot
> up that could cause problems if it was interrupted before completing tasks
> before next reboot occurs?
>
> Is this is a potential problem is their a standard operating procedure for
> this scenario?
>
> Thanks,
>
> John Dolinka
>