Skip to main content

How to recover msdb database from suspect mode

 It was Monday 9th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server.
“MSDB is in suspected mode”
At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..

Suddenly faced Error….



The situation I faced  "It was really boil-able  in summer " in  48 degree @ 12 PM bcz automation tasks and backup was failed .. I started digging inside server. I Attempted 4 tests to Resolve the issue but no one helped me:-
EXEC sp_resetstatus 'MSDB'
Warning: You must recover this database prior to access.

Command(s) completed successfully.

Msg 5058, Level 16, State 6, Line 1
Option 'EMERGENCY' cannot be set in database 'MSDB'.

Restoring Test

Then finally I shut down sql server services and copy the msdbdata and msdblog file from template folder and pasted into data folder where system files locating.

Then errors goes out when I restarted back the server. But msdb was showing in single user mode.

Then I  bring back msdb in multiuser from single user mode through alter database msdb set multi_user . After that I restore msdb from last previous days backup.It brings my server in previous and actual state..

Now I am happy but the temperature is still on same state growing hopefully this month end will come monsoon. 


  1. This is amazing, this worked for me after so many failed.

  2. Each of these Changes is communicated to the database. The change is first made on the "read/write" database and then replicated to the remote database copy. create mysql dashboard


Post a comment

Plz dont forget to like Facebook Page..

Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription