Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using SQL Server 2005 and I see the following message in event log (event id 9001)

"The log for database xxxx is not available."

After doing some research I found that it could be a corrupted database or possibly I/O related problem. I tried running DBCC CHECKDB and it did not report any problem. At the end it shows following message:

"CHECKDB found 0 allocation errors and 0 consistency errors"

I just want to know if there could be any damage to the database or log and what other steps I have to perform to verify it?

share|improve this question

migrated from Jan 21 '12 at 19:03

This question came from our site for professional and enthusiast programmers. – Mitch Wheat Jul 25 '11 at 14:35
Can anybody help. Does 0 allocation errors and 0 consistency errors need any attention? – kumar Jul 25 '11 at 17:28

Things to check:

  1. Is your Log file size set to a limit?

  2. Have you run out of disk space on the drive where the log file resides (seems unlikely)?

  3. Is this a physical or virtual server?

  4. What service pack are you running?

  5. What, if any, are the preceding errors in the error log?

share|improve this answer
1. No 2. No, There is enough disk space 3. Physical server 4. Sql Server 2005 (SP2). For time being I am using express edition. 5. There was no preceding error. My database size is not quite big. it is just approx 100MB. I am just wondering that memory pressure on server is not a culprit. DB instance is already using the max limit (1 GB). – kumar Jul 26 '11 at 13:36

Try to detach and reattach the database. If you encounter any problems, check out SQL Server log files. They might contain useful info. Note that each of the instances has it's own error logs. The easiest way to access SQL Server logs is in SSMS:

  1. In Object Explorer, expand a SQL Server instance
  2. Expand Management
  3. Expand SQL Server Logs
  4. Right-click a log and click View SQL Server Log
share|improve this answer
Nooooooooo.... don't do this.… – Jon Seigel Dec 3 '12 at 18:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.