Anyway to find the row based on the page number

  • DBCC PAGE might give some more information...  You'll need to pass in the database ID, the fileID & page ID, and a formatting option (0-3):

    DBCC PAGE (DB_ID(), 1, 2910904, 0)

    along with this post: https://blogs.msdn.microsoft.com/sqlserverstorageengine/2006/06/10/how-to-use-dbcc-page/ should give you a starting point.

    Good luck!

    Thomas Rushton
    blog: https://thelonedba.wordpress.com

  • In this case it's an orphaned text blob.

    The off-row data node  is not referenced

    As such, the row that the text blob belongs to is gone somehow and hence there's nothing you can delete.

    If this is the only error you have, a repair with allow_data_loss will remove just the orphaned text blob with no actual data loss (the data loss has already happened sometime in the past)

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Thanks Thomas, yes been trying to use DBCC PAGE to try and work my way back to the offending row with no luck.

    Thanks also Gail, yes that is the only error now remaining after fixing the other errors DBCC CHECKDB gave.  I will get backups and recovery procedures in places and then crack on with the repairs.

Viewing 3 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply