You need to detach the damaged MSDB before running the instmsdb.sql script. And yes, restoring from your backup would be the best option.

You should restore from your backups. As the output from CHECKDB clearly states, REPAIR_ALLOW_DATA_LOSS is what's needed to repair these errors so its no surprise that none of the other...

Can you post the exact command you issued and the exact error messages that were output?

This is terrible advice. Most suspect databases WILL NOT reattach successfully.

Cristo - did the database/log run out of space? Why did it go suspect in the first place? You may...

Can you run DBCC CHECKDB against master and see if there are any corruptions?

What happens if you manually run 'select * from master..sysdatabases'?

Looks like you've got a controller issue - some of the pages have been wiped out with random garbage and one oset of pages has been overwritten by the next...

"I'm surprised you ran "allow data loss". Paul Randal, Storage Engine Lead for SS2K5 and SS2K spoke at TechEd. He said don't run it. Ever, ever, ever, ever."

Not quite -...

Sounds like your Express instance is not configured to accept remote connections (default setting for an Express instance). To change it, follow the instructions at http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Hope this helps

The extra 14 bytes is only needed for records in heap pages. Here's why - heap records do not have keys, by definition, so the only way to reference them...

And as you can see, geekiness runs in my family!

Here's a reply I'd given Georges in response to a PM.

Hi Georges,

Yes, you probably need to analyze the queries being created to see whether inefficient access paths are being chosen....

This indicates that your backup is corrupt in some way. Can you try the restore command manually and see if there are any more errors? Can you also post the...

The answer is yes. A CHECKDB summary of errors found/fixed is always put into the errorlog and if any errors are found, they will be logged in the Windows event...

Not really. Which version of SQL Server are you running?

ok - so if the table schemas are exactly the same and the data is still readable in the source database then the problem occured during the copy process or...