At 04:20 PM 16/08/2005 +0530, you wrote:

>Thanks Helen,
>
>I knew that on issuing a commit statement explicitly in isql the changes
>would be reflected, however our client expects that if the client
>application has already executed a commit then what is the need of issuing
>it again…
>
>What exact reason can I provide them??

Why not just explain to them how transaction isolation at snapshot level
works? i.e. that each transaction has its own view of the state of the
database. In snapshot isolation, this view lasts until the transaction
ends. So TxA does not see work that was committed by other transactions
until TxA itself completes. A transaction is not complete until it is
committed or rolled back.

./heLen