Prior to updating sysdatabases entry for database Horny chat 1to1

by  |  26-Nov-2015 07:46

This setting takes effect immediately (without a server stop and restart). sp_configure 'allow updates', 1 GO RECONFIGURE WITH OVERRIDE GO Thanks, It worked fine. I have copied all the user tables and it s data from the query analyzer.

But I have some stored procedures in the DB can i get the text of the stored procedures. SO you have reset the status and can't get to it from EM. If so, select everything from syscomments and see if you can salvage the procs from there. Tomsp_attach_db will not work if the db is in Suspect mode. Rename the existing log device to something else 3.

You will be looking at the ctext column for the most part. Suspect results from data or log device corruption. in QA type the following: exec sp_attach_single_file_db 'your_db', 'complete_path_for_mdf_file' 4.

prior to updating sysdatabases entry for database-23prior to updating sysdatabases entry for database-61

If the problem is with the data device I hope someone else may have a solution, but from what I've seen so far, - only MS PSS tool of recovering db pages did the trick.

i tried to reset the status database by "sp_resetstatus abc".

It is giving the message "Prior to updating sysdatabases entry for database 'cr2db', mode = 0 and status = 260 (status suspect_bit = 256).

WHen i run EXEC sp_resetstatus 'dbname' i got the below message.

Prior to updating sysdatabases entry for database 'ihatespamdb', mode = 0 and status = 4194333 (status suspect_bit = 0).

Community Discussion