MSSQL - Torn pages
Author
Discussion

pdV6

Original Poster:

16,442 posts

291 months

Thursday 5th January 2006
quotequote all
Does anyone have some handy hints on how to recover as much as possible from a SQL2000 database that's showing 'torn page' errors?

Cheers

pdV6

Original Poster:

16,442 posts

291 months

Thursday 5th January 2006
quotequote all
No?

UncleDave

7,155 posts

261 months

Thursday 5th January 2006
quotequote all
As far as I know no info can be recovered.. but you just have to make regular backups, and restore your latest backup...? Which is rather unfortunate..

mattley

3,039 posts

252 months

Thursday 5th January 2006
quotequote all
www.nigelrivett.net/SQLAdmin/RecoverCorruptDatabase.html

Not seen it myself, but this makes sense, and is worth a try if your backups aren't looking like the best option.

pdV6

Original Poster:

16,442 posts

291 months

Friday 6th January 2006
quotequote all
mattley said:
www.nigelrivett.net/SQLAdmin/RecoverCorruptDatabase.html

Not seen it myself, but this makes sense, and is worth a try if your backups aren't looking like the best option.

Cheers - had already seen that one.

[History]
Its a customer's database that went to pot when their server crashed.
Latest backup is over a year old thus no use.
[/History]

By using that and similar articles, I have managed to get the db into emergency mode (after much faffing!) and can read a lot of the data. However, neither DTS or BCP want anything to do with it
As a last resort, I'm going to try manually grabbing any data possible via queries but am not relishing the task...

pdV6

Original Poster:

16,442 posts

291 months

Thursday 19th January 2006
quotequote all
Update:

Couldn't get anything out of the db directly but could construct complicated SELECT statements buried in a cursor loop in order to generate appropriate INSERT statements as output. Copy & paste the output into a new script file and run against a new database to regenerate the data.

Checked with customer and gave an estimate of time/cost to get it all running and of course the customer then decided the data wasn't worth that much after all and they'd live without it