Database in Recovery mode from last 7 days.

  • In SQL Error Log its show processing,because 2 days back recovery processing show 98% today it show 99%, tomorrow i will post some of error log on post for your reference.

    But cause of databases in recovery mode. SQL Agent has been disabled, other databases backup jobs not performed from last 6 days.

    But Thanks for the support dear. I like your prompt reply too.

    Thanks Dude...

    If i want to direct Chat with you please send the details too on my email ID parminder.parmindersingh@gmail.com.

  • If it's progressing and time's not of the essence (which it apparently isn't), just wait.

    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
  • Hello Sir,

    FYI, Below SQL error log.

    2013-02-12 13:26:51.05 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849570342 ms.

    2013-02-12 13:27:51.14 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849630433 ms.

    2013-02-12 13:28:51.23 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849690524 ms.

    2013-02-12 13:29:51.32 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849750615 ms.

    2013-02-12 13:30:51.41 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849810706 ms.

    2013-02-12 13:31:51.50 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849870796 ms.

    2013-02-12 13:32:51.59 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849930887 ms.

    2013-02-12 13:33:51.68 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 849990978 ms.

    2013-02-12 13:34:51.77 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 850051069 ms.

    2013-02-12 13:35:51.86 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 850111160 ms.

    2013-02-12 13:36:51.95 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 850171251 ms.

    2013-02-12 13:37:52.05 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 850231341 ms.

    2013-02-12 13:38:52.14 Server Process 18:0:0 (0x1598) Worker 0x00000000043B21C0 appears to be non-yielding on Scheduler 3. Thread creation time: 13004279824516. Approx Thread CPU Used: kernel 187 ms, user 12448 ms. Process Utilization 0%. System Idle 98%. Interval: 850291432 ms.

    Please help me out.

  • Hello Gila,

    If you required any other information please let me know will provide for the same relevent for this error.

  • My previous advice stands. If no work is being done (and since you didn't post the recovery messages I can't tell), restart SQL. Otherwise wait. Or open a case with MS support.

    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
  • Manually re restore the database stuck in recovery mode. The status will clear back to normal

  • jwgmpi (2/13/2013)


    Manually re restore the database stuck in recovery mode. The status will clear back to normal

    If you mean running RESTORE DATABASE ... WITH RECOVERY, that's for databases in the RESTORING state, not the RECOVERING state.

    Dropping the DB and restoring a backup from scratch would indeed fix the problem, assuming there is a backup.

    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
  • Shifting gears, once you get the DB's back up and running, seriously consider upgraded to the latest service pack of SQL Server 2005.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 8 posts - 16 through 22 (of 22 total)

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