Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-11-07 : 08:16:28
|
| Taryn-Vee writes "Hi all,I have a situation where our client application sometimes holds locks due to not issueing a commit when leaving a window and only finally commiting when one exits the application. we are currently in the process of determining where this occurs... however the problem we have is that the system tables remain 'locked' with an IX lock. Is there any way for us to 'commit' this errant connection (open_Tran in sysprocesses?)?ThanksTaryn-Vee" |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-11-07 : 10:16:25
|
| Kill the SPID?Is all of your code dynamic or in stored procedures?Brett8-) |
 |
|
|
tinks
Starting Member
34 Posts |
Posted - 2003-11-12 : 04:43:03
|
quote:
Originally posted by X002548
Kill the SPID?Is all of your code dynamic or in stored procedures?Brett8-)
the code is called via a powerbuilder gui which seems to dynamically wrap a transaction around only certain stored procedure calls (ie any stored procedure that creates and utilises temp tables). Basically what i want to do is check the @@trancount of a spid on the window close event and 'commit' the transaction if there is one still left which should theoretically remove the locks on thes sys tables.I would also like to add that although this doesnt lock our client application out it DOES cause perception problems re locking for our products as these locks remain till either another commit is reached or the person closes the application.Taryn-VeeTaryn-Vee@>-'-,--- |
|
|
|
|
|
|
Locks remaining on system