Yes that sound good, Please go ahead and open a case with MS. Update us also .

The problem is you have a composite Primary key in the master table

( emp)--right ?

Emp table : Primary Key is

empno , empname , emp_city --> composite primary key

Again the...

Check that you have enough permission to run the debugger and in my case I applied the SP4 and it worked.

Remove a named instance of SQL Server

=====================================

Beautifully described in the following KB : 🙂

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

May be a new bug..not sure better contact support.

To bring the database to emergency mode

Exec sp_configure 'allow updates',1 reconfigure with override

update sysdatabases set status = 32768 where name ='dbname'

Please check BOL for more info.

Rememeber 823...

[SQLSTATE 42000] (Error 22029) is a generic error

Please try to run this command and you will find the exact error message

select * from msdb.dbo.sysdbmaintplan_history

post that error message !!

I think you have manupulated the mdf file. This should be done in any case that is the reason for DB to be in suspect.

Is there any recent full DB...

Try this ..

Select * from sysdatabases .

The Compatibility level cmptlevel is different for 2000(80) and 2005 (90) sysdatadases.

🙂

Purnell is right follow that. Is it possible to resetup the Log shipping once again. That might help.

It is good you got back ur data. It may happes so the data are commited to the mdf file after chaging the recovery model you were able to run...

Similar bug is there in SQL Server 2000 for SQLMaint.exe.

Check this link :

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

Good info !!:)

I think .. the agent does not have sufficient privileges.. check that

we did the follwings:

======================

1. Take all the user databases backup

2. Script out all windows and sql logins.

This will help.