InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 17:06:01 GMT20http://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxyou can useCHECKPOINT commandMon, 12 Nov 2012 23:49:56 GMTESAT ERKEChttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxDatabase corruption is notn something that SQL can or will do itself. It's something that's caused by misbehaving components, usually in the IO subsystem.Mon, 12 Nov 2012 13:21:36 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxOk got it. I was just worried for database corruption. Then I may not stop SQL Service; I think there is no harm in rebooting machine 3-4 times in 30-40 mins time frame.Mon, 12 Nov 2012 13:20:04 GMTapathttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspx[quote][b]apat (11/12/2012)[/b][hr]Does the recovery just get aborted and start again after server is up?[/quote]Yup.The last thing done in a recovery is a checkpoint. If the checkpoint does not complete (for whatever reason), recovery just starts over from the beginning after SQL restarts.Mon, 12 Nov 2012 13:09:31 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxThanks for the reply GilaMonster.Question, so what happens if a 600 GB database is halfway recovering and the machine is rebooted? How does SQL Server treat that database? Does the recovery just get aborted and start again after server is up?Mon, 12 Nov 2012 12:57:20 GMTapathttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspx[quote][b]apat (11/12/2012)[/b][hr]That is what I am planning to do, but was just curious to know if not then this can real cause any corruption etc...[/quote]Not unless the reboots or updates mess up the IO subsystem, and if they do it won't make much difference if SQL is running or not.Mon, 12 Nov 2012 12:50:42 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxThanks capnhector. That is what I am planning to do, but was just curious to know if not then this can real cause any corruption etc...Mon, 12 Nov 2012 12:49:15 GMTapathttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxwhat i might do is manually shut down the service then disable the SQL Server service while they do their multiple reboots then once they are done restart and re-enable the service. Since im not sure as to whether the multiple restarts would do any harm but i know not starting SQL Server durring the reboots will prevent any issues that may be possible i would probably go that route.Mon, 12 Nov 2012 12:45:35 GMTCapnHectorhttp://www.sqlservercentral.com/Forums/Topic1383805-391-1.aspxHi Experts,Our network team needs to upgrade firmware and other things on the server which has SQL Server 2008 on it. For this upgrade they will need to reboot machine at least 3-4 times in about 30 mins window. This server has about 20 databases on it and most of them are over 100 GB with the biggest one being 600 GB. Once the machine is rebooted, of course SQL Databases take some time to recover. If we restart machine 3-4 times in this small time window, Can there be any problem with the databases? What happens if they are not recovered during the first reboot and we reboot it again? Any suggestions will help. Thanks in advance...Mon, 12 Nov 2012 11:52:04 GMTapat