October 11, 2015 at 9:41 pm
Experts,
Database went into suspect mode because of disk offline,bring is disk online and the DB still in suspect mode. Is it advisable to restart SQL Server?
October 12, 2015 at 2:13 am
I wouldn't restart SQL. Do you have backups?
October 12, 2015 at 2:13 am
I would suggest that you do NOT reboot SQL Server.
First, take the database to EMERGENCY mode using ALTER DATABASE
ALTER DATABASE dbname SET EMERGENCY;
then, immediately take a COPY_ONLY backup and store it on the side (do not overwrite any existing backups). Assuming that works, run DBCC against the database. If that passes, then you can set the database back to ONLINE using the ALTER command again.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 12, 2015 at 2:34 am
Before you do anything, you need to identify why the database went suspect. Check the error log. Look for ALL messages relating to the database from when the disks went offline.
Emergency mode repair is a LAST resort for when no backups exist and all other options have failed. It should not be the first thing tried. Please don't try that before identifying what went wrong.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 24, 2015 at 11:05 pm
Thanks everyone for the reply and sorry for the delayed response. DB went to suspect because of disk went offline. Another DBA went and rebooted the server and many other DB went suspect but all came to normal after another reboot. Is it advisable to do reboot when DB goes suspect because of disk issue?
TIA
October 25, 2015 at 5:39 am
No.
Better to identify why it's suspect and attempt to bring it online through normal means. Rebooting over and over again is not a standard recovery method.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 25, 2015 at 10:35 pm
Thanks Grant.
October 26, 2015 at 10:30 am
Ratheesh.K.Nair (10/24/2015)
DB went to suspect because of disk went offline. Another DBA went and rebooted the server and many other DB went suspect but all came to normal after another reboot. Is it advisable to do reboot when DB goes suspect because of disk issue?TIA
Doesn't make sense, during a planned shutdown sql server will be stopped and buffers flushed to disk before the disks are unmounted! :ermm:
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply