Re: dbcc repair_allow_data_loss
From: skrampe (anonymous_at_discussions.microsoft.com)
Date: 05/03/04
- Next message: mid: "SQL Backup and Log Shipping"
- Previous message: Thomas Scheiderich: "Re: Drop the table or Truncate?"
- In reply to: Paul S Randal [MS]: "Re: dbcc repair_allow_data_loss"
- Next in thread: Tibor Karaszi: "Re: dbcc repair_allow_data_loss"
- Reply: Tibor Karaszi: "Re: dbcc repair_allow_data_loss"
- Reply: Paul S Randal [MS]: "Re: dbcc repair_allow_data_loss"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 May 2004 02:01:05 -0700
...
You should assume that
data was lost if you had to use this option and so your business or
application logic may no longer be correct (constraints etc).
....
Just to be sure: You mean, that it's possible that data is lost and we do not have any information about this in the Log-File of the repair job?
We check our database every night.
So, what would you suggest if we'll find consistency errors again (with the suggestion repair_allow_data_loss)?
Go back to the last complete backup? (lose 24 h work of the users)!
Have a system downtime and try to repair the database?
Thank you very much for your help!
Regards,
Sven Krampe
- Next message: mid: "SQL Backup and Log Shipping"
- Previous message: Thomas Scheiderich: "Re: Drop the table or Truncate?"
- In reply to: Paul S Randal [MS]: "Re: dbcc repair_allow_data_loss"
- Next in thread: Tibor Karaszi: "Re: dbcc repair_allow_data_loss"
- Reply: Tibor Karaszi: "Re: dbcc repair_allow_data_loss"
- Reply: Paul S Randal [MS]: "Re: dbcc repair_allow_data_loss"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|