December 23, 2010 at 6:10 am
Hi,
My production database has corrupted due to H/w problems.
my database recovery model is 'simple'
my Full backup completed @12.00PM today,
My database corrupted @4.00PM.
plz suggest me how to recover my database including all transactions upto 4.00PM today.
Subha.......
December 23, 2010 at 6:22 am
No way, AFAIK.
It should have been in Full recovery.
-- Gianluca Sartori
December 23, 2010 at 6:34 am
it is very imp Database in production.
any alternative way to resolve this problem.
plz help me, what should i do now? PM soughting on me......
Subha
December 23, 2010 at 6:55 am
If your last backup is 12pm, then any transactions past that cannot be recovered via restore. That's what simple recovery means.
As for other options, without seeing the full output of CheckDB, I'm not willing to speculate.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
p.s. What the hell is a very important production database doing in simple recovery? Someone's not doing their job here. If point-in-time recovery and minimal data loss is a requirement, the DB should have been in full recovery with log backups. Absolutely no excuses. Whoever the DBA there is, they messed up on this one.
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
December 23, 2010 at 7:07 am
You've got a "very important" production database and no log backups and an untested recovery process? It's either not actually "very important" or you guys have a long and painful learning curve in front of you.
As others have noted, without log backups, no point in time recovery is possible, period. No options. No alternatives. No recourse.
I'd start hoping that you only have a corrupt index or something and Gail (who is absolutely one of THE best people at this) might be able to help. Otherwise, you're going to have to go with that prior full backup. I'd start setting the stage for that right now, avoid any further downtime to the business.
"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
December 23, 2010 at 8:09 am
Be thankful you only lost 4 hours, and put proper disaster procedures in place for next time.
December 23, 2010 at 8:34 am
Thank you very much for your valuable information, i will take the precautions for all databases now onwards.
Subha...
December 23, 2010 at 8:36 am
Learn about the different recovery models:
http://msdn.microsoft.com/en-us/library/ms189275.aspx
http://msdn.microsoft.com/en-us/library/aa173531(v=sql.80).aspx
December 23, 2010 at 9:52 am
subha.mcts2005 (12/23/2010)
Thank you very much for your valuable information, i will take the precautions for all databases now onwards.
So you don't want any possible alternate resolutions?
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
December 23, 2010 at 10:42 am
Would the default trace files be of use to at least get some information about what heppened between 12:00 and 4:00 ?
December 23, 2010 at 10:49 am
homebrew01 (12/23/2010)
Would the default trace files be of use to at least get some information about what heppened between 12:00 and 4:00 ?
Nope. The default trace does not capture DML events. It's focused on DDL and auditing types of events.
"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 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply