April 11, 2005 at 5:39 am
Hello,
I've some strange problems with the SQL Server and I hope you can help me a little.
The story so far:
At first there was a power cut causing the system to hold. Aftr rebooting them the work of a whole day was lost. The administrator of the server told me that there was a rollback. This rollback affected 5 databases. Can it be that there is a rollback for a whole day? Can a whole day be marked as uncommited? unfortunately i can't get the logs of the server because they where deleted (not our server :-().
Have you heard something like this in the past?
regards
Andreas
April 11, 2005 at 8:16 am
Are they using SET IMPLICIT_TRANSACTION ON ??? This could explain that so much has been rolled back.
See BOL: Transactions that are automatically opened as the result of this setting being ON must be explicitly committed or rolled back by the user at the end of the transaction. Otherwise, the transaction and all the data changes it contains are rolled back when the user disconnects.
M
[font="Verdana"]Markus Bohse[/font]
April 11, 2005 at 8:37 am
On reboot, there should be a normal rollback/rollforward. Are you sure that there was a whole day of rollback?
If there was, then Markus' idea might be the best one to check. You can check iwth profiler and see the settings of a connection if you grab the session data.
April 11, 2005 at 8:48 am
Hello Markus,
I read in the BOL that implicit transactions are not standard. They have to be turned on and are only valid for one connection.
The Server rolled back the data for all users. The Software is connected through ODBC (BOL says implicit transactions are turnd off when you use ODBC).
How do I know implicit transactions are used?
regards
andreas
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply