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...

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...

Try restarting the SQL server again.

Good point Lynn, but I still will restart the server first!

[quote-0True, but in general I would still recommend checkDB first then decide on the resolution. Not all corruptions require a restore from backup to fix.[/quote-0]

I agree with Gail on that....

Glad to know that everything its ok now, I also will like to thank you for let us know how you resolve the problem.

I thought that the server was already restarted and that after the restart the database was still unaccessible. That is why I recommended a restore. In case the server has...

If you don't have SCOM this may also be helpful http://www.howtogeek.com/howto/database/sending-automated-job-email-notifications-in-sql-server-with-smtp/ and of couse Books OnLine.

Do you have SCOM?

Check this link out http://technet.microsoft.com/en-gb/library/ms143506(SQL.90).aspx.

I think you must restore the latest backup. If you were using Full recovery and you still have the backup files, then you can try what Lynn advices you.

Could you please share what did exactly helped you to resolve the problem.

That is why I was asking him what he wanted to do, but still no reply.

I agree with homebrew you should be more specific with your question. When you are going to upgrade you can always use the upgrade advisor.

you can try to connect by making are rdp connection to the server and then going to the command line and using SQLCMD -Sservername. It wil use the windows login...