Ghost records still exits

  • I am deleting a table which is having 20k records

    i used

    DBCC TRACEON(3604)

    DBCC IND(<DBname>, <Table_name>, -1)

    DBCC page(<DBName>, 1, 234, 3)

    After i deleted the record in the table i am still able to see the records if i ran DBCC page(<DBName>, 1, 234, 3)

    why it is so?

    when it will be vanished?

    what is the purpose of sql server to make it as ghost record?

    Is SQL Server 2000 not cleaning up page space after a data modification operation?

    Will it slow my performance when i insert new record to the table?

    Thanks!

  • It'll be removed when ghost cleanup runs. It's done this way as an optimisation, SQL is cleaning up space properly, no it will not slow down inserts.

    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
  • If millions of record are there and if delete is done on this , will the pages remain in db and occupy space?

  • Until the ghost cleanup runs (which will be almost immediately, in the background)

    If you're impatient, rebuild the clustered index

    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
  • If i ran this query after deleting records i am able to see the transaction information

    DBCC PAGE (RH_USER700, 1, 274, 3) WITH TABLERESULTS

    checked after 4 hour still the same.

    what does it mean? is the tables has been cleaned and the same pages is been used for other record information.

    but i am getting the same record every time when i ran this query no difference in the record.

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

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