LL Connects to SQL Server with Implicit Transaction On

[b0b555]

We have a number of instances of LiveLink, both in production and development/test. When I look at the connections to the SQL Server database (SQL Server 2005 SP3 Standard Edition is one of our PROD instances for example), I can see SQL connections that have been inactive for weeks, but still have an open transaction and are still holding locks. Looking at the connections in SQL Server Profiler for these connections I can see that the one of the connection parameters is "set implicit_transactions on". I believe this is causing the LL connection to stay open.

This seems to be causing a number of issues, not the least of which is SQL sessions holding large numbers of locks (e.g. over 600,000) for long periods, which in turn causes blocking of other sessions. There are also issues with an ever increasing internal SQL Version Store that SQL maintains because we have Snapshot Isolation turned on.

Has anyone else seen this? Even better, has anyone else overcome this?

LL seems to use ODBC to connect to SQL Server. Does anyone know what ODBC driver LL uses?

Cheers

 

[appnair]

Kindly check the KB for fine tuning aspects of SQLserver.Many of the terms that you use here I seem to have read
in them but I am not a DBA so don't understand them intimately.In most of OT code all the database calls are wrapped in its own transaction so the count should not increase but some code may not do it.I mean you can write code in livelink without using a transaction.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair