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 ««12

sysobjects corruption Expand / Collapse
Author
Message
Posted Thursday, June 27, 2013 2:12 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:54 AM
Points: 42,466, Visits: 35,530
psingla (6/26/2013)
BTW sysobjects view exists in 2005+ versions also.


The view does, but it's a view and not a table and since a view does not store data, sysobjects cannot become corrupt. Its underlying tables can, but not the view.

So if somebody is trying to select data from sysobjects in later 2005+ then he can get the same error that is listed here.


No he can't.

He cannot get this exact error for a number of reasons, not least because the errors were rewritten in SQL 2005 and no longer have the form that was posted here. Also because sysobjects is not a table in SQL 2005+, it's a view, and any corruption that affects the underlying tables will be reported as being in the underlying tables, not sysobjects.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1468000
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse