Update sysdatabases set status

Please do let us know in case if there are any other suggestions for the same, any approach which can be more effective and useful. Like us on FaceBook Follow us on Twitter.

May 4, May 4, April 27, April 27, April 22, April 22, Thanks satnam singh for sharing. I had an experience with this kind of problem. Thanks for this great write up. I followed the steps and we were able to recovery the database. Thanks again. If you are using SQL , drop that database and restore again from scratch to ensure there are no lingering side-effects. They should not be touched unless you're completely happy with the possibility of having to restore the DB that you worked on.

In either case, the DB will restore and be left in the recovering state so that you can restore diff or log backups. I've already the command and database stays in the same state.

You must be logged in to reply to this topic. Login to reply. Solution of this error is little long and it involves restart of the server.

I recommend following all the steps below in order without skipping any of them. SQL Server logs are corrupted and they need to be rebuilt to make the database operational. Follow all the steps in order. Replace the yourdatabasename name with real name of your database. Create a new database with same name which you are trying to recover or restore. In our error message it is yourdatabasename. Stop SQL Server. Delete the LDF file of new server just created.

Start SQL Server. Database will be marked as suspect, which is expected. Make sure system tables of Master database allows to update the values. Change database mode to emergency mode. Make sure the path is physical, if you put logical file name it will return an error. Reset the database status using following command. Turn off the update to system tables of Master database running following script. I always check consistence of the database as well as I reset the status of the database to original status.

Set the database to status single user. Make sure that you have done all the steps in order and restarted SQL Server where it is mentioned. Thank you so much for this fix it tip, my client could not work for over a week because of the database crash, six months of data loss was at at stake.