do I need run dbcc checkdb without using physical only?


  • see error in the log, but run dbcc checkdb with physical only gets no error, do i still need run without physical only?



    Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS


    " failed with the following error: "The operating system returned error stale page (a page read returned a log sequence number (LSN) (607:236532:1) that is older than the last one that was written (0:0:0)) to SQL Server during a read at offset 0x000000581d0000 in file 'g:\\SQLDATA\\tempdb.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Monday, January 30, 2012 2:19 PM


All replies

  • Please see this



    Please mark answered if I've answered your question and vote for it as helpful to help other user's find a solution quicker
    • Marked as answer by George Zhou Wednesday, February 01, 2012 2:20 PM
    Monday, January 30, 2012 2:30 PM
  • I would restart the SQL Server and refresh tempdb as it will be recreated. Then do the DBCC checkdb on the database that has the error.

    Although if the db in question is very broken, then if you restart the server the db may not recover and so not mount, so take that into consideration. 



    Kind Regards Nick Kemp.
    Tuesday, January 31, 2012 5:23 AM


    be aware that using PHYSICAL_ONLY turns DBCC CHECKDB from a CPU-bound process into an I/O-bound process, and makes it run (potentially) magnitudes faster. It will still evaluate page checksums and torn-page protection, just skipping the higher-level logical checks.


    Best Regards, Uri Dimant SQL Server MVP
    • Marked as answer by George Zhou Wednesday, February 01, 2012 2:20 PM
    Tuesday, January 31, 2012 6:49 AM