SQL Server Performance

Error 7105 fatal error

Discussion in 'General DBA Questions' started by brimba, Dec 16, 2005.

  1. brimba New Member


    We got the error 7105 reported once for a table.

    Page %S_PGID, slot %d for text, ntext, or image node does not exist.

    Someone here knows what we should do?

    The error have not showed up again in a couple of weeks.

    I am thinking of tabking a backup of all the data on the table. Drop the table, Create the table and create all the indexes again and then move the data from the backup. Would that help?

    The most important questions is still left. Why did this happen? How can we prevent this from happening again?

  2. satya Moderator

  3. bobbyliambert New Member

    Try to implement these steps in your database...

    • You can run the query command again to see if that happens.
    • If that is the condition, Run DBCC CHECKDB
    • Update the SQL Server with latest server pack if problem is arising due to the SQL Server Engine
    But remember to take a backup of the data or the items stored in the database.

    Reference: http://www.sqldatabase-recovery.com
  4. Luis Martin Moderator

    Welcome to the forums!.
    Thanks for your help. Always check thread date. This one is 7 years old.
  5. FrankKalis Moderator

    Nice try, mate.
    Next time you advertise your tool without contributing anything useful to a 7 years old thread, I'll flag it as spam.

Share This Page