Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Torn Page in table with unloved content Expand / Collapse
Author
Message
Posted Wednesday, May 1, 2013 8:37 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, January 17, 2014 4:42 AM
Points: 62, Visits: 277
Hi
We have a SQL 2008 database with a torn page.
The table with the issue contains data which we don't really care about.

We do have good backups however, restoring will be a pain as results in a prolonged outage due to size of db.

It has been suggested that we can truncate the table, however, I googled and someone had a problem with this in sql2k.

Like I say, we don't care about the data but we would like to stop the errors occuring continuously in our errorlog. Does anyone know whether a truncate will work in SQL2008?



Post #1448442
Posted Wednesday, May 1, 2013 8:52 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:42 AM
Points: 5,436, Visits: 10,116
I don't know the answer to your question, but I can tell you what I'd do. I'd restore a copy of the corrupted database on to a test server, and truncate the table there. You'll soon see whether the errors keep occurring. My guess is that dropping and recreating the table is more likely to work than just truncating it.

John
Post #1448449
Posted Wednesday, May 1, 2013 9:05 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 5:35 PM
Points: 866, Visits: 7,470
Truncate will probably work, but if you have a torn page you need to do a thorough check on your I/O system to see what might have caused it. If the base problem isn't remedied, you could get hit with this again on a table with data you need.



And then again, I might be wrong ...
David Webb
Post #1448458
Posted Wednesday, May 1, 2013 9:08 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, January 17, 2014 4:42 AM
Points: 62, Visits: 277
Thanks.
I have requested a restore of the db to another server. We have known issues with our storage subsystem which are making life "interesting" and have been restoring up to know.
The business situation with this particular database is a little more complicated though.



Post #1448464
Posted Wednesday, May 1, 2013 2:09 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, January 17, 2014 4:42 AM
Points: 62, Visits: 277
Just to let you know that the truncation worked and subsequent checkdb came back clean.

However when I check the suspect_pages table in msdb, I still see the corrupt page with status 3 (torn), although the last_update_date is no longer changing.

I'll likely remove this record from suspect_pages in a couple of weeks.



Post #1448605
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse