January 26, 2012 at 1:15 am
sp_lock, gives the details of transactions is running in to server ,
if any transactions is running by the client machine and client forgot to commit or rollback the transaction,
and tables is locked.
how DBA can commit or rollback this transaction? in to the server.
waiting for reply....
January 26, 2012 at 1:29 am
You can kill the client session:
http://msdn.microsoft.com/en-us/library/ms173730.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 26, 2012 at 1:44 am
k. but what will be that trancation state. rollback or commit.
January 26, 2012 at 1:47 am
Dhirju (1/26/2012)
k. but what will be that trancation state. rollback or commit.
If you kill the session, the transaction will be rolled back, as stated explicitly in the link that I provided you with:
Use KILL session ID to terminate regular nondistributed and distributed transactions that are associated with a specified session ID.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 26, 2012 at 2:27 am
or, client already end the session without rollback or commit transaction
January 26, 2012 at 2:33 am
Dhirju (1/26/2012)
or, client already end the session without rollback or commit transaction
That would be surprising, as uncommitted transactions are rolled back when the session is terminated.
Has the behaviour from your question occurred on your server? Do you use implicit transactions?
http://msdn.microsoft.com/en-us/library/ms190230.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply