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

Old records in suspect_pages Expand / Collapse
Author
Message
Posted Wednesday, February 19, 2014 3:09 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 22, 2014 10:27 AM
Points: 137, Visits: 590
Hi All,

I have some rows in suspect_pages where the last_update_date is in 2011, these are all before I was working as the DBA at my company.

The vast majority of these are showing in tempdb; as the server has been restarted several times since then, I'm assuming I don't really need to worry about these as tempdb is recreated on restart? Can I simply delete these rows from the table?

In addition, there are two user databases that have five rows each, both with page_id 1-3 and 6-7 listed.

I run CHECKDB weekly against every database, and this is not showing any errors for these databases. Do I need to worry?

At this point, I don't know whether to spend any more time investigating this or whether there's work that needs to be carried out to fix this? My biggest concern is that it's unlikely that a backup going back to 2011 is still available.

Please let me know if more info is required and I'll happily post it.

Regards,

Matthew

Post #1542904
Posted Monday, March 10, 2014 8:17 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, July 14, 2014 2:06 PM
Points: 3,860, Visits: 7,130
If all that's in there is old records from 2011, you're good to go. These can and should be removed. In fact, by default the size of the table is limited (capped) so if the table is full and you've not deleted the old data, SQL Server will not logged new errors should they occur (giving you a warm sense of security, when in fact things could be very wrong!).

In your database integrity jobs, you may want to include a final select from this table to check to see if anything got written there during your maintenance, and if it did, send an email to let you know.

For more information, check out http://technet.microsoft.com/en-us/library/ms191301(v=sql.100).aspx


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1549249
Posted Monday, March 10, 2014 8:53 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 22, 2014 10:27 AM
Points: 137, Visits: 590
OK cool; well there was only a handful of rows in the table, so the cap won't have been hit. The check at the end of the maintenance task is a good idea though, will definitely be implementing that!
Post #1549284
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse