May 19, 2015 at 4:26 am
Historically, i have always stopped SQL Server before restarting the server it sits on, just in case any long running transactions are taking place and to ensure no users are in the system before hand.
if you just restart a server, or schedule reboots, could this cause a negative impact / cause data corruption?
I would always argue do it manually so that
-Health check can be done when SQL is back up, check integrity checks, sql has actually started, connections can be made
-No long running transactions will be cut short
-no updates will be rolled back
-no extracts to CSV etc. will be corrupt
I am interested to see other peopels thoughts
May 19, 2015 at 4:33 am
initiating an OS shutdown will still stop the sql instance cleanly. I've seen cases in the past where someone is rebooting a sql server and it takes its time to shutdown and they're tempted to hold the power button for 4 secs, once you explain to the user what is happening they then understand.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 19, 2015 at 5:00 am
Yes Restarting The server will stop the SQL server cleanly . as windows always shut down all the application before shutting itself down
and SQL works On write Ahead log basis so after restart consistency is maintain
WINNERS NEVER QUIT AND QUITTERS NEVER WIN
sqlserversdba.wordpress.com
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply