loading

Msdb no longer exists?

I have a problem with the hard drive on which was Windows 2008 SBS server. Drive is faulty and no longer works. I was able to restore Windows 2008 SBS server but the SBSMONITORING msdb no longer exists. Backup no. What you can do in this case?

sort by: active | newest | oldest

Try install
a new SQL instance called "Junk" and then copy the msdb files over to
the SQL data directory for SBSMonitoring and then restart SBSMonitoring.
Then run the script detailed in the
article on Technet which will recreate the SBSMonitoring database.

The key to
fixing this problem is to restore the msdb mdf and ldf files from a new SQL
instance.

If so you
cannot restore a database then you can try to make sql mdf file repair. For
this you can try to use the MDF Repair
Kit
. On the website you can read more on how to do it. Sometimes this way
helps me when there is no backup or no
serious damage. http://www.mdf.repair/

ArturKis (author) 5 months ago

Thank you guys for your feedback and help. Thank you!

In these cases data loss is normally inevitable, but as this is only the SBSMONITORING SQL instance it really won't matter. You do have some options as the msdb can be rebuilt, you can also take another SQL server instance's msdb as long as it's the same version and build. Alternatively you can just create a new SQL instance and copy the msdb from it.

I'd try following this Microsoft TechNet article on how to recreate the SBSMONITORING database first:

https://blogs.technet.microsoft.com/sbs/2011/08/22...

ArturKis (author)  ThirdEarthDesign5 months ago

I am very glad and grateful that you gave me advice, but unfortunately problem I have left. can anything else be done?

Download the following package and extract it to c:\windows\temp

https://onedrive.live.com/?id=D5FE25AFB6C3615F%211...

Open PowerShell as an administrator, then run the following script:

C:\windows\temp\Create-SBSMonitoringDb.ps1

After the script completes, verify that the monitoring service is running.

If for any reason the above doesn't work, as I previously suggested you can create a new SQL instance, copy the msdb from it then remove the new instance.

If neither of the above works, you may have more problems than just a missing msdb.