This article describes the course of actions you should take
- if your database somehow got "suspect mode" or "emergency mode";
- if you receive the error 1813 on attaching database
The History Behind
I've been developing under SQL 7 for a while. Sometimes transaction log grew too large. My usual fix for that problem was:
- stop the server (on the development machine we do not need any logs),
- delete transaction log
- start the server again
- after that the server was creating empty 1MB transaction log from scratch
I had been using this technique a lot of times under SQL 7, until sometime I have migrated to MSSQL 2000...
After my transaction log grew too large, I stopped the server, deleted the log file and started the server once again. However this time it did not worked: my database got "suspect". I was not able to read or write from the database. A week of work seemed to be lost... Ouch!...
