Sunil Padarath (5/15/2010)
in my test instance i have managed to changed the db status to mergency. this i was able to do so by putting the instance into single user mode and running the update command.
That is NOT the way to do emergency mode in SQL 2005. No idea if that's actually done anything, or just set the value in the system catalog. I don't think it's going to help, the error that you got earlier is schema corruption, which means CheckDB (which would be the next thing to run) will probably fail.
As a note, by updating the catalog in master, you've just lost all support for that SQL instance from MS, ever.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass