July 21, 2011 at 8:13 am
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.
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:15 am
halifaxdal
you may want to take a look at this.
http://www.sqlrecoverytool.com/sql-data-restore.html
trial version lets you view corrupted DB.
July 21, 2011 at 8:23 am
halifaxdal (7/21/2011)
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
What do you see when you query sysdatabases?
July 21, 2011 at 8:25 am
Ignacio A. Salom Rangel (7/21/2011)
halifaxdal (7/21/2011)
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
What do you see when you query sysdatabases?
I can see my DB with status 1073742352
July 21, 2011 at 8:25 am
AlexSQLForums (7/21/2011)
halifaxdalyou may want to take a look at this.
http://www.sqlrecoverytool.com/sql-data-restore.html
trial version lets you view corrupted DB.
Thanks.
July 21, 2011 at 8:32 am
AlexSQLForums (7/21/2011)
halifaxdalyou may want to take a look at this.
http://www.sqlrecoverytool.com/sql-data-restore.html
trial version lets you view corrupted DB.
Yes, it seems working. I can see all the corrupted tables now. The tables names are not recovered, I am not sure if it contains data or if the data is still in integrity, I can see who created those tables and when.
Trial version doesn't allow me to export. That seems encouraging.
July 21, 2011 at 8:39 am
halifaxdal (7/21/2011)
AlexSQLForums (7/21/2011)
halifaxdalyou may want to take a look at this.
http://www.sqlrecoverytool.com/sql-data-restore.html
trial version lets you view corrupted DB.
Yes, it seems working. I can see all the corrupted tables now. The tables names are not recovered, I am not sure if it contains data or if the data is still in integrity, I can see who created those tables and when.
Trial version doesn't allow me to export. That seems encouraging.
I'm happy for you! As for the status you mentioned I could not find it http://msdn.microsoft.com/en-us/library/aa260406(v=sql.80).aspx.
July 21, 2011 at 8:46 am
Ignacio A. Salom Rangel (7/21/2011)
halifaxdal (7/21/2011)
AlexSQLForums (7/21/2011)
halifaxdalyou may want to take a look at this.
http://www.sqlrecoverytool.com/sql-data-restore.html
trial version lets you view corrupted DB.
Yes, it seems working. I can see all the corrupted tables now. The tables names are not recovered, I am not sure if it contains data or if the data is still in integrity, I can see who created those tables and when.
Trial version doesn't allow me to export. That seems encouraging.
I'm happy for you! As for the status you mentioned I could not find it http://msdn.microsoft.com/en-us/library/aa260406(v=sql.80).aspx.
I will try to convince my boss to purchase this tool, actually the content (or part of it) is also visible.
It's strange why the status is not in Microsoft's list. I will forgive them though. :-D:-D:-D
July 21, 2011 at 8:47 am
Ignacio A. Salom Rangel (7/21/2011)
halifaxdal (7/21/2011)
AlexSQLForums (7/21/2011)
halifaxdalyou may want to take a look at this.
http://www.sqlrecoverytool.com/sql-data-restore.html
trial version lets you view corrupted DB.
Yes, it seems working. I can see all the corrupted tables now. The tables names are not recovered, I am not sure if it contains data or if the data is still in integrity, I can see who created those tables and when.
Trial version doesn't allow me to export. That seems encouraging.
I'm happy for you! As for the status you mentioned I could not find it http://msdn.microsoft.com/en-us/library/aa260406(v=sql.80).aspx.
Best guess : It's cleanly shutdown + offline + torn page detection which adds up perfectly.
July 21, 2011 at 8:51 am
Best guess : It's cleanly shutdown + offline + torn page detection which adds up perfectly.
Thanks for letting us know. Do you think that the database can still be recovered? Maybe try to bring it online? It will be great if Gail could tell us what the next step should be.
July 21, 2011 at 8:53 am
Beside this tool: http://www.sqlrecoverytool.com/sql-data-restore.html
Do any of you have any other recommendations?
This tool's company is doing a very good SEO, it's on the top of the search result
July 21, 2011 at 8:54 am
GilaMonster (7/21/2011)
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:54 am
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.
July 21, 2011 at 8:55 am
Ignacio A. Salom Rangel (7/21/2011)
Best guess : It's cleanly shutdown + offline + torn page detection which adds up perfectly.
Thanks for letting us know. Do yuo thing then that the database can still be recovered? Maybe try to bring it online? It will be great if Gail could tell us what the next step should be.
Now I am definitely confidence that this DB is recoverable, simply because the tool can see the content, right?
July 21, 2011 at 8:55 am
Ignacio A. Salom Rangel (7/21/2011)
Best guess : It's cleanly shutdown + offline + torn page detection which adds up perfectly.
Thanks for letting us know. Do yuo thing then that the database can still be recovered? Maybe try to bring it online? It will be great if Gail could tell us what the next step should be.
I've been out of ideas for a long time. Gail is the real expert here. I just try to tag along and survive the ride.
Viewing 15 posts - 91 through 105 (of 130 total)
You must be logged in to reply to this topic. Login to reply