Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
CHECKDB
13 posts, Page 2 of 2
««
1
2
CHECKDB
Rate Topic
Display Mode
Topic Options
Author
Message
SQLRNNR
SQLRNNR
Posted Saturday, January 16, 2010 12:26 PM
SSCoach
Group: General Forum Members
Last Login: 2 days ago @ 1:07 PM
Points: 18,733,
Visits: 12,332
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 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #848773
rspskumar-704119
rspskumar-704119
Posted Sunday, January 17, 2010 1:25 PM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, February 07, 2013 12:22 AM
Points: 27,
Visits: 83
plese set db status to emerngy mode and export data and run repair
Post #848897
GilaMonster
GilaMonster
Posted Sunday, January 17, 2010 2:04 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 37,722,
Visits: 29,977
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 2008, MVP
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
Post #848907
« Prev Topic
|
Next Topic »
13 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.