Dave/Gail, whetever you guys said is true. SQL Server doesn't record history of tranactions and in second session i can only see the last statementran by 1st sesson.

But what surprises me is tha my open transaction is not history. It still is causing blocking on my table and you always don't keep running a trace.

So imagine a scenario where there are 3 open transation in one of my sesson, then there are some more transactions ran in same session. Now I am not sure whether I should commit or rollback these transction. How can I decide that without looking at transction statement???

I understand that it may not be possible in sql sever as of now, but I believe it is a fairly reasonble requirement which should ave implemned that I am always able to see my open transaction staements.