|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 7:36 AM
Points: 5,201,
Visits: 11,153
|
|
Thanks for your feedback, please don't forget to rate the article to.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 8:24 AM
Points: 1,610,
Visits: 590
|
|
Five stars for me as I find this type of article almost a "reverse engineering" concept, sometimes this can help with the understanding.
Good stuff.
qh
SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 7:36 AM
Points: 5,201,
Visits: 11,153
|
|
hi thanks for your comments, hope you found it useful Regards Pez
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 3:18 AM
Points: 154,
Visits: 544
|
|
mY database will be corrupted [font="Arial"][/font].so how to recovery the corrupt database??????( i have little bit confusing.because of iam using below script reocvery the database :
DBCC CHECKDB ('Corrupt2K8') WITH NO_INFOMSGS, ALL_ERRORMSGS exec sp_resetstatus 'Corrupt2K8' alter database Corrupt2K8 set emergency dbcc checkdb('Corrupt2K8') alter database Corrupt2K8 set single_user with rollback immediate dbcc checkdb('Corrupt2K8', REPAIR_ALLOW_DATA_LOSS) alter database Corrupt2K8 set multi_user ))
NOTE: some points for consideration:
Then restore My database from a backup - but make sure to run DBCC CHECKDB on that very backup to ensure it's not corrupt itself.
DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS is the very last resort . Before that, you should restore a valid backup. Once you do use REPAIR_ALLOW_DATA_LOSS, don't expect your database to magically come back to life again - most likely, irreparable damage has occurred - especially in this case since it complains about system table corruption.
Thank you in advance
SQL server DBA
|
|
|
|