I'm just a little concerned about this because before we had to do a reset
we were getting a lot of timeout errors from the server...basically nothing
would insert or update... and no locks where open.. no one was logged into
the db besides us and CPU usage was at 1%... when it restarted it in total
checkpointed about 15,000 transactions which feels wierd since no one was in
the DB since last friday... and nothing really happened today in it yet...
i'd of thought those would of been checkpointed a long time ago
"Andrew J. Kelly" wrote in message
> This is normal for a recovery action depending on how many transactions
> there were since the last checkpoint. Anything after the last checkpoint
> must be rolled forward or back to get the database in a consistent state.
> For instance if there were open transactions (not yet committed when the
> server was last shut down) it must roll them back to a known good point.
> It will redo or roll forward any that were committed but may not have yet
> been hardened to the db.
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
>
> "Smokey Grindel" wrote in message
>
>> For some reason on a restart today we had our main database go into "in
>> recovery mode" what would cause this to happen? it seems like it
>> recovered from the logs point of view... but there were tons of entries
>> sayign stuff like 9000 transactions rolled forward for the checkpoint
>> event and stuff like the transaction log wasnt checkpointing or
>> something? any ideas? thanks!
>>
> >> Stay informed about: Database in recovery mode