Yes Please follow the steps given by EdVassie. By restoring the SQL Server 2000 Master DB you are inviting the problem and this may also lead you to rebuild the...

I have found these links hope this helps you

http://support.microsoft.com/kb/318605/en-us

http://support.microsoft.com/kb/913372/en-us

http://support.microsoft.com/kb/247931/en-us

http://support.microsoft.com/kb/917409/en-us

http://support.microsoft.com/kb/912412/en-us

Minaz Amin

I mean without the System database.

You have messed up .

Please go ahead and rebuild the Server, then restore the SQL 2000 Database with the system databases.

Regards,

Minaz Amin

Even I agree with Jezemine. It is better to have separate data and log files.

Minaz Amin

Cool article Steve. I had been shooted with this question so many times and it was the same issue with me to answer.

Now I know what to asnwer !!!

Why ?

I do'nt think you need a job to do this. If the Database is suspect then it will shown in the SEM.

Minaz

Is this happens with only msdb database or other too?

If this issue is also with the other DB then, I think you need to check the hardware of the backup server.

Minaz...

Please check this link:

http://support.microsoft.com/kb/271509/en-us

How to resolve blocking problems that are caused by lock escalation in SQL Server

Minaz Amin

Use RESTORE HEADERONLY option and check the backup file.

Is there any error message you receive during the restore process?

Minaz Amin 

Hi, 

This links will help:

http://support.microsoft.com/kb/230785/en-us

Hi,

Apart from you can also get the information in the SQL Server error log: You can check this line in the error log.

2007-04-15 17:35:28.92 Server      Server is listening...

SQL Server automatically creates a unique index to enforce the uniqueness requirement of the PRIMARY KEY constraint. If a clustered index does not already exist on the table, or a...

Hi,

This is a very usefull link where all SQL 2005 connectivity related issue has been discussed.