April 19, 2014 at 8:03 am
Lynn Pettis (4/19/2014)
Jagadeesh Chowdary (4/19/2014)
If the Database is in Suspect mode then follow the below steps to recover ur DB>Stop the SQL Service
>>Copy the MDF and LDF file and place in other safe location
>>>Then Start SQL service
>>>>Now also the Database will be in suspect mode only
>>>>>Drop are Detach the Database
>>>>>>Then Replace the MDF and LDF Files where it was Previously
>>>>>>>And Attach DB by Selecting the MDF File....
First, bad advice if you haven't determined why the database is suspect in the first place.
Second, it may simply be better to restore from a known good backup (full + t-logs).
Third, this is a 6 year old thread.
Agreed
Bad bad bad advice. Why not just fix the root cause instead of jumping to such extreme measures?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 19, 2014 at 11:52 am
Jagadeesh Chowdary (4/19/2014)
If the Database is in Suspect mode then follow the below steps to recover ur DB>Stop the SQL Service
>>Copy the MDF and LDF file and place in other safe location
>>>Then Start SQL service
>>>>Now also the Database will be in suspect mode only
>>>>>Drop are Detach the Database
>>>>>>Then Replace the MDF and LDF Files where it was Previously
>>>>>>>And Attach DB by Selecting the MDF File....
That's not going to fix a damn thing.
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
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply