Posted by Holyman on 09/07/05 18:08

Hi group

I have an application running on a couple of pc's all connecting to
the same SQL-serve databaser. The other day one of my applications
started a transaction which it never committed (programming error) .
The application continiued running for a couple og hours filling every
insert and update statement to the sql-server log-file, where they
remain rigt now. The applications on all the other machines
deadlocket because they waited for the first application to commit. I
eventually shot down the ms sql service and restarted it. Now all the
transactions which were not commited are not to bee seen in the
database, because they remain in the log file (ldf-file) waiting for
af commit I cannot perform. Are there a way to browse an ms-server
..ldf file to see which uncommitted records are in it

Thanks if anyone can helo

Regards
jsa

• Next in forum: Problem with uncommited transactions in log-file
• Prev in forum: Problem with uncommited transactions in log-file
• Thread view: Problem with uncommited transactions in log-file

[Reply to this message]