Database can't be recovered? Any help would be appreciated!!!

Question

Database can't be recovered? Any help would be appreciated!!!

July 22, 2011 at 12:48 am

This was removed by the editor as SPAM

Viewing 11 posts - 121 through 130 (of 130 total)

You must be logged in to reply to this topic. Login to reply

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 1

halifaxdal (7/21/2011)
Ninja's_RGR'us (7/21/2011)
halifaxdal (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Halifax, could you please answer the question, made by Gail and Ninja? Thanks in advance!
Sorry I thought I already posted.
I ran
DBCC CHECKDB('CheckListDB') WITH NO_INFOMSGS, ALL_ERRORMSGS
I got:
the Server: Msg 942, Level 14, State 4, Line 1
Database 'CheckListDB' cannot be opened because it is offline.
I'll shut up now let Gail take <back> over. Too many chiefs and too much noise going on at the moment.
C'mon guys, you all rocks

That's not the point, what's were doing is not workign and should have been done 2-3 times over by now.

And Yes I know I rock :smooooth: :hehe:

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

I'm going to stand by earlier conclusion. Unrepairable, no more that can be done (we're past what's detailed in Paul's blog posts)

If you want to risk buying one of the data recovery tools, that's your choice. My experience with them has not been good, maybe yours will be different.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Ignacio A. Salom Rangel (7/21/2011)
Halifax, You can try to follow the steps 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, instead of using Set Emergency, use the step Gail gave you to change the database state.

We've already done that, it failed.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 4

GilaMonster (7/21/2011)
Ignacio A. Salom Rangel (7/21/2011)
Halifax, You can try to follow the steps 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, instead of using Set Emergency, use the step Gail gave you to change the database state.
We've already done that, it failed.

Sorry gail, but in Paul's post he mention

DBCC CHECKDB (databasename, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS I don't recall that in any of the recommendations, Again that should be applied only in cases where nothing else works. Maybe I missed it.

My blog

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

If CheckDB fails (which is has) there is no point in trying CheckDB with repair, it'll fail too.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 6

GilaMonster (7/21/2011)
If CheckDB fails (which is has) there is no point in trying CheckDB with repair, it'll fail too.

Valid point! I just have a hard time accepting that the database was visible and then it is not visible anymore. You are the expert in that area, but I'm sure you are also wondering if all the steps have been executed in the proper order, if something was missing there. Anyway I hope you don't take any of my comments as criticism, I'm a big fan, two years ago I meet you at Pass.

My blog

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

Ignacio A. Salom Rangel (7/21/2011)
GilaMonster (7/21/2011)
If CheckDB fails (which is has) there is no point in trying CheckDB with repair, it'll fail too.
Valid point! I just have a hard time accepting that the database was visible and then it is not visible anymore.

As I said earlier, I don't believe that it was. There is no way that, at the same point in time, a query of the system tables works and a query of a user table fails with 'the database cannot be opened'. I suspect that the earlier queries that 'worked' were been run in the wrong database. It's an easy mistake to make especially if the USE statement fails.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 8

I can see my DB with status 1073742352

what about halifax being able to see the database with status 1073742352?

My blog

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 9

That's just querying sysdatabases, doesn't mean that the DB can be opened (and setting it to emergency mode failed, as did opening it)

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

homebrew01 SSC Guru Points: 55548 More actions · Answer 10

GilaMonster (7/21/2011)
halifaxdal (7/21/2011)
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
When you swapped the files you didn't delete the new DB's log file. You can't mix and match files from different databases.

Was there a response to Gail's comment about the log file?? (Maybe I missed it) Could that be the current problem, and swapping correctly might give a better result ?