The best would have been if you would have the latest backup of MSDB. So a lesson learnt from here would be always take the backups of system databases.(i.e. Master model and MSDB atleast) In you're scenario you need to rebuild the msdb since you dont have any latest backup. As a result you might be loosing any jobs, SSIS/DTS packages or any history sitting out there on earlier MSDB. Now since MSDB can't be set to emergency mode so you cannot run repair command here, so most probably you would need to recreate the MSDB. I would highlight below points on how to do it from Paul's blog: 1. Detach the damaged msdb. You can't just detach msdb because you're not allowed to detach system databases. However, you can if you start the server with trace flag 3608. Do this by shutting down the server, navigating to the directory 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn' and doing the following: start sqlservr.exe -c -T3608 2. Move or rename the damaged msdb files (msdbdata.mdf and msdblog.ldf in the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data' directory) 3. Run the instmsdb.sql script in the 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install' directory 4. shutdown and restart the server without the 3608 trace flag Hope above helps!