Abu Dina (3/27/2013)
I wouldn't advise restarting SQL Server as you could end up with a corrupted database after the restart.
You could end up with a database in recovery for a while, you can not end up with a corrupt database. You could end up with a database in the recovery_pending state if you delete the log file after stopping SQL.
Corrupt database means that something outside of SQL, typically the IO subsystem has mangled the data file and damaged the contents. If a restart results in the IO subsystem writing garbage into the files, then the problem is the IO subsystem, not the restart.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass