September 11, 2017 at 11:56 pm
Good Morning Experts,
We have a production database that has gone into suspect state. What are the step-by-step process to fix it without any data loss. Thanks in advance
September 12, 2017 at 1:02 am
First of all: keep calm
- What's registered in the SQLServer errorlog file ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 12, 2017 at 1:03 am
Do you have good backups including transaction logs?
Thanks
September 12, 2017 at 1:17 am
Restore from backups (full + log should get you back up with no data loss)
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
September 12, 2017 at 1:21 am
GilaMonster - Tuesday, September 12, 2017 1:17 AMRestore from backups (full + log should get you back up with no data loss)
Hi Gail,
I am not able to take tail log backup. So , there will be data loss, correct?
September 12, 2017 at 7:40 am
Potentially. If you can't take a tail log backup, any changes not in data files will be lost.
September 12, 2017 at 8:47 am
coolchaitu - Tuesday, September 12, 2017 1:21 AMGilaMonster - Tuesday, September 12, 2017 1:17 AMRestore from backups (full + log should get you back up with no data loss)Hi Gail,
I am not able to take tail log backup. So , there will be data loss, correct?
Why not. What's the problem there?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2017 at 8:56 am
Jeff Moden - Tuesday, September 12, 2017 8:47 AMcoolchaitu - Tuesday, September 12, 2017 1:21 AMGilaMonster - Tuesday, September 12, 2017 1:17 AMRestore from backups (full + log should get you back up with no data loss)Hi Gail,
I am not able to take tail log backup. So , there will be data loss, correct?Why not. What's the problem there?
Hi Jeff,
Can we take tail log backup when the database is in suspect state?
September 12, 2017 at 9:15 am
Have you tried?
Or tried a search? https://www.sqlskills.com/blogs/paul/disaster-recovery-101-backing-up-the-tail-of-the-log/
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
September 12, 2017 at 9:20 am
coolchaitu - Tuesday, September 12, 2017 8:56 AMJeff Moden - Tuesday, September 12, 2017 8:47 AMcoolchaitu - Tuesday, September 12, 2017 1:21 AMGilaMonster - Tuesday, September 12, 2017 1:17 AMRestore from backups (full + log should get you back up with no data loss)Hi Gail,
I am not able to take tail log backup. So , there will be data loss, correct?Why not. What's the problem there?
Hi Jeff,
Can we take tail log backup when the database is in suspect state?
A really old post from Gail Shaw appears to suggest that you can (I've not had and am not looking forward to the opportunity to test it 😀 ). I hope she shows up on this thread to confirm. The thread is 7 years old.
https://www.sqlservercentral.com/Forums/1027027/Tail-log-backup-is-failing
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2017 at 9:21 am
Heh... I posted while Gail was posting. Great minds think alike.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2017 at 10:00 am
GilaMonster - Tuesday, September 12, 2017 9:15 AMHave you tried?Or tried a search? https://www.sqlskills.com/blogs/paul/disaster-recovery-101-backing-up-the-tail-of-the-log/
I read the article you posted. But, I am unable to come to a conclusion. Could you please confirm we can take tail log backup when the database is in suspect state
September 12, 2017 at 11:47 am
We can't confirm anything. We don't have your server.
If you read the link, Case 2 from Paul is likely what you need to do, if you cannot follow Case 1. You'll have to determine if those work for you.
September 12, 2017 at 1:38 pm
coolchaitu - Tuesday, September 12, 2017 10:00 AMI read the article you posted. But, I am unable to come to a conclusion. Could you please confirm we can take tail log backup when the database is in suspect state
Did you try?
What was the result? Did it succeed, or throw an error? If error, which 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
October 13, 2017 at 12:25 pm
GilaMonster - Tuesday, September 12, 2017 1:38 PMcoolchaitu - Tuesday, September 12, 2017 10:00 AMI read the article you posted. But, I am unable to come to a conclusion. Could you please confirm we can take tail log backup when the database is in suspect stateDid you try?
What was the result? Did it succeed, or throw an error? If error, which one?
I dont have an opportunity to try. There are no test databases and I cant even create one, not allowed. So, could you please help me in understanding if we can take tail log backup when the database is in suspect state.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply