March 31, 2015 at 12:06 am
Hi,
I am trying the repair the suspect database.how to repair the database
my database having full recovery model and size of 430GB
I found 2 options repair_rebuild,repair_allow_data_loss.
what is best to use
Can any one suggest
March 31, 2015 at 12:59 am
If you are able to recovery using repair_rebuild than it will be good as it do not have any data loss but possibilities are very thin. While using repair_allow_data_loss may have data loss while it fix the issue. Is your server production server?
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
March 31, 2015 at 2:30 am
Please post the results of DBCC CHECKDB.
Don't repair!!!
You could damage your database and lose data.
If you're not sure what to do, wait for a reply here before taking action.
-- Gianluca Sartori
March 31, 2015 at 3:08 am
Neither. (you can't repair_rebuild a database that's suspect)
Restore from a clean backup. Since the DB is in full recovery model, you should have log backups and be able to restore right up to point of failure.
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
March 31, 2015 at 7:01 am
This is the reason you're taking full backups and log backups. Restore to a point in time prior to the corruption of the database.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply