The logs probably won't tell you what caused this. It would generally
require that you were running a third party software that is recording what
is going on(Like In-Depth for SQL server or profiler) to find out the issue.
Maybe there would be something in the logs if the issue caused a stack dump.
A rollback generally takes close to the same amount of time to complete as
the time the transaction ran that caused it. If a rollback happens during
the normal process of the daily work then it will roll back and the database
is still accessible. If however, you reboot the server(or cycle the SQL
service) while a rollback is taking place, when the SQL comes back up the
database will go into recovery mode until the rollback is complete and it
cannot be accessed during that time.
Thanks,
Ralph W. Davis
*********************************************************
*** CORPORATE DBA group - Houston ***
*********************************************************
-----Original Message-----
From: Paris Inman
[mailto:mssqldba-ezmlmshield-x70208502.[Email address protected]
Sent: Wednesday, June 29, 2005 10:23 AM
To: LazyDBA Discussion
Subject: Recovery?
Yesterday one of my clients SQL servers went into a recovery mode and it
lasted almost the entire day. We could not access the serve database to see
the server logs for monitors process locks or anything. After the recovery
completed itself our database was back up and with no data loss and the log
indicated the following.
Recovery of database 'DTT5' (7) is 100% complete (approximately 0 more
seconds) (Phase 3 of 3).
1 transactions rolled back in database 'DTT5' (7).
Recovery is checkpointing database 'DTT5' (7)
I am researching the find out what caused this. The server logs are
incomplete and begin at the point of recovery.
Please advise.
Thanks
Paris
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
Confidentiality Note: The information contained in this message, and any
attachments, may contain confidential and/or privileged material. It is intended
solely for the person or entity to which it is addressed. Any review,
retransmission, dissemination, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and delete
the material from any computer.
MS Sql Server LazyDBA home page