I am having a problem with uncommitted SQL transactions, as a
precaution I am executing SQL as transactions, then checking the
number of rows affected matches my expectations. It also might have
something to do with the fact that the data I am dealing with is worth
more than my life (hehehe). The past few days I have had uncommitted
SQL transactions from the previous evening's work.
Now I know the easy answer to my question is donot run Transactions
orcheck that night that you have committed them all. But is there a
Stored Procedure or an SQL statement that would allow a DBA to look at
all the uncommited SQL Transactions.
Chris aka *Boo