July 21, 2011 at 7:31 am
GilaMonster (7/21/2011)
And that's after setting the status to 32767?
Yes, yesterday I changed the status with success
July 21, 2011 at 7:49 am
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.
Gail, are you on the same page as Ignacio? Ninja specifically asked me to listen to you only, I very much thank Ignacio's help and appreciate his opinion, but I also don't want to screw up with other people like you. Please advise. Thanks.
July 21, 2011 at 7:50 am
Looks like it's unrecoverable. If you still can't access the DB in emergency mode then there's no way to access it at all. That was last chance.
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
July 21, 2011 at 7:52 am
halifaxdal (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.Gail, are you on the same page as Ignacio?
No.
You can do it over if you like, you can do it 10 times if you like. The results aren't going to differ, if it's unrecoverable it's unrecoverable and waiting a day and doing things over is not going to change that.
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
July 21, 2011 at 7:54 am
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.
No I said to not try things on your own without telling us and out of sequence. We can't see your screen and I'm not allowed to read your mind.
July 21, 2011 at 7:56 am
GilaMonster (7/21/2011)
halifaxdal (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.Gail, are you on the same page as Ignacio?
No.
You can do it over if you like, you can do it 10 times if you like. The results aren't going to differ, if it's unrecoverable it's unrecoverable and waiting a day and doing things over is not going to change that.
Gail, I agree with you, that if the database is unrecoverable, there is nothing to do, but on the other hand I find it very weird, that yesterday she was able to see the database and today out of the blue the database is not visible anymore. That is why, I would do all the steps again and see what happends. It will not take that much time to be done anyway.
July 21, 2011 at 8:02 am
halifaxdal (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.Gail, are you on the same page as Ignacio? Ninja specifically asked me to listen to you only, I very much thank Ignacio's help and appreciate his opinion, but I also don't want to screw up with other people like you. Please advise. Thanks.
Halifax,
I indeed agree with what Ninje said, you should only listen to Gail, she is an expert in this area, all I ever heard about recovering a database was in her post. I had something similar on a SQL 2005 SQL Server and I used the steps explained in Paul Randal's post http://www.sqlskills.com/BLOGS/PAUL/post/CHECKDB-From-Every-Angle-EMERGENCY-mode-repair-the-very-very-last-resort.aspx . It worked for me.
I suggested you to do it over again, because as I already told Gail, I find it weird that yesterday the database was visible and today it is gone. I wish good luck and hope you can recover the database.
July 21, 2011 at 8:02 am
I am doing everything again from scratch:
1. stop the server and deleted the old DB
2. start the server and create it again
3. take it off line
4. swap the DB files
5. bring it online ------------------Success!!!!! different than last time, but when I open the tables, I see only system tables
Should I continue?
Hold on: I might swapped the wrong file
July 21, 2011 at 8:02 am
Ignacio A. Salom Rangel (7/21/2011)
but on the other hand I find it very weird, that yesterday she was able to see the database and today out of the blue the database is not visible anymore.
I don't think she could. I think she was querying master instead and not realising it. There's no way that, at the same time, a query of sysobjects and shows nothing other than the system tables and a query of a specific known table fails with 'database can't be opened' unless the query of sysobjects was done against a different database by accident.
The DB is visible in Enterprise manager as Suspect, it's not visible in Query Analyser (because it's not usable)
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
July 21, 2011 at 8:04 am
halifaxdal (7/21/2011)
5. bring it online ------------------Success!!!!! different than last time, but when I open the tables, I see only system tables
Are you absolutely sure that you're querying the correct database, not master or something like that?
What does that CheckDB (with the database name) give you?
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
July 21, 2011 at 8:05 am
Ninja's_RGR'us (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.No I said to not try things on your own without telling us and out of sequence. We can't see your screen and I'm not allowed to read your mind.
I never indicated that she should do things in random order, what I told her was to try the steps indicated by Gail from scratch.
As I see it, the database can't be recovered anymore. Yesterday the database was visible and today it is not visible anymore.
July 21, 2011 at 8:07 am
I got this error message:
Error 5173: Cannot associate files with different databases.
Could not restart database 'CheckListDB', reverting back to old status.
ALTER DATABASE statement failed.
Log file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\CheckListDB_Log.LDF' does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
sp_dboption command failed.
In EM, it shows as Offline
July 21, 2011 at 8:09 am
Ignacio A. Salom Rangel (7/21/2011)
Ninja's_RGR'us (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Try to do it all over again and see if it works this time, something may have happened since yesterday.No I said to not try things on your own without telling us and out of sequence. We can't see your screen and I'm not allowed to read your mind.
I never indicated that she should do things in random order, what I told her was to try the steps indicated by Gail from scratch.
As I see it, the database can't be recovered anymore. Yesterday the database was visible and today it is not visible anymore.
I wasn't referring to you. Yesterday she was trying things out of sequence from Gail's instructions. I was simply pointing it out again.
Viewing 15 posts - 76 through 90 (of 130 total)
You must be logged in to reply to this topic. Login to reply