HELP me please ....
-
Ignacio A. Salom Rangel (1/20/2010)
Good point Lynn, but I still will restart the server first!Depends on what the exact error is. Cases like this, where it's a file that is there but SQL claims not to be able to read, yes. More general corruption (error 823 or 824) then no (majority of the time), because it will not benefit anything and may make the matter worse.
In fact, in an article that I wrote on corruption, two of the things I said not to do were
1) restart SQL
2) restart the server
because doing so can turn an online but corrupt database into a suspect and corrupt database, essentially making the whole fixing process harder
There are very few absolutes when it comes to corruption other than to find exactly what's wrong and then look at resolving the problems based on exactly what is 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 recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
GilaMonster (1/20/2010)
Ignacio A. Salom Rangel (1/20/2010)
Good point Lynn, but I still will restart the server first!Depends on what the exact error is. Cases like this, where it's a file that is there but SQL claims not to be able to read, yes. More general corruption (error 823 or 824) then no (majority of the time), because it will not benefit anything and may make the matter worse.
In fact, in an article that I wrote on corruption, two of the things I said not to do were
1) restart SQL
2) restart the server
because doing so can turn an online but corrupt database into a suspect and corrupt database, essentially making the whole fixing process harder
There are very few absolutes when it comes to corruption other than to find exactly what's wrong and then look at resolving the problems based on exactly what is wrong.
I love, It Depends (and no, I'm not talking about those...). In this instance it was necessary for SQL Server to be able to see the disk again. It really comes down to each individual situation that may arise.
-
I have a feeling that I'm confusing the issue not clarifying it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
No, your not. I understand fully that you shouldn't restart a SQL Server instance or server. All I am saying is it really is an "It depends" thing. It isn't something I would do if a CHECKDB came backup with errors.
I have run into a somewhat similiar issue with our older SAN at one point when the SAN was not quite ready when a production server attempted to connect to its SAN resources. Our SIS system sort a worked, but we were getting a lot of errors in the error logs. Rebooted the server and everything came up normally and worked properly.
-
To me for this particular problem, when a disk can not be read, I will restart the server. If I get a corruption error, I will do a DBCC CheckDB first and try to find out if I can repair the problem.
In general every problem is different, so I must agree with both of you (Gail & Lynn).
It's that ok with everyone? 😀
-
I concur with Gail on not restarting the server to avoid having a Corrupt database in Suspect mode unless I am sure that it is only a hardware issue and would only be corrected with a reboot...
Can we have a Life without reboots :hehe:..MS are you listening..??
The_SQL_DBA
MCTS"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
-
Please, I am not disagreeing with Gail. We need to look at each situation and make the appropriate decisions, after all, isn't that why we make the BIG $$$$?
-
I just wanted to make it clear to anyone that runs across the thread in the future that reboot is not the first thing to try for corruption, that's why I posted earlier.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
GilaMonster (1/20/2010)
I just wanted to make it clear to anyone that runs across the thread in the future that reboot is not the first thing to try for corruption, that's why I posted earlier.I don't think you should worry about that. I think it is very clear that the whole point of this thread is to always check the facts and depending on them decide what will be the best way to proceed.
Viewing 9 posts - 31 through 38 (of 38 total)
You must be logged in to reply to this topic. Login to reply