SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


CHECKDB


CHECKDB

Author
Message
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)

Group: General Forum Members
Points: 66473 Visits: 18570
GilaMonster (1/16/2010)
CirquedeSQLeil (1/15/2010)
Potentially lost. Data may be lost - it depends on how bad the corruption is.


Will be lost.

If the minimum level to repair is repair_allow_data_loss, it means that there will be data loss if that is run. There's only two cases that I know of (incorrect PFS pages and orphaned LOB pages) where repair allow_data_loss is required but data won't be lost.

In this case, there is a single damaged page in the clustered index. Repair will drop that page and fix the links. Hence, any data on that page will be lost.

http://sqlinthewild.co.za/index.php/2009/06/03/does-repair_allow_data_loss-cause-data-loss/


Thanks for correcting that Gail and explaining more precisely.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

rspskumar-704119
rspskumar-704119
Valued Member
Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)

Group: General Forum Members
Points: 58 Visits: 108
plese set db status to emerngy mode and export data and run repair
GilaMonster
GilaMonster
SSC Guru
SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)SSC Guru (223K reputation)

Group: General Forum Members
Points: 223795 Visits: 46301
rspskumar-704119 (1/17/2010)
plese set db status to emerngy mode and export data and run repair


Absolutely not. Totally unnecessary and frankly in this case stupid things to suggest.

Emergency mode is a last resort for when the database is in suspect or recovery pending mode. Not for when the database is online and usable with minor corruption.
Export (and subsequent re-import) is for when there's irreparable corruption, like damaged allocation pages. This corruption is perfectly repairable (albeit with minor data loss) and hence there is no need whatsoever for something as extreme as export and reimport.

Gail Shaw
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


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search