Post reply

Dirty pages in memory

  • February 11, 2006 at 12:11 am

    #168236

    Dear all,

     

    How can i know dirty data pages that contain changes that have not yet been flushed to disk?

    Thanks for ur time and help.

    from

    Killer

     

  • February 13, 2006 at 9:18 am

    #620468

    Out of curiosity why would you want to know ? I ask that because SQL Server writes 'dirty' pages out to disk quite frequently. The 'lazy writer' performs this task (and others) automatically in the background constantly. Some of the things that 'trigger' this are:

    • a 'commit' is issued in a database
    • the internal 'threshhold' for recovery interval is reached
    • the data cache manager needs to reuse 'dirty' pages for other data

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • February 14, 2006 at 1:16 am

    #620595

    Dear Rudy,

     

    U are write one the point but also wrong.

    First the checkpoint is issued and then the lazy writter writes the data from buffer cache to the disk.

    The reason i asked the question that i need to know is that ,is there any dirty pages left unwritten to disk before issuing  DBCC DROPCLEANBUFFERS.

     

    As i had solved the problem :

    We can check the status of dirty pages from command

    dbcc memorystatus

    the dirty index shows how many pages are still there not written to disk.

    to writte these point just issue checkpoint command.and then we can clean the buffer easly.

    HTH

     

    from

    Killer

     

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

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