I have run into several applications that were written for a one dbms and then ported to SQL Server, and many use implicit transactions--which oftentimes really make it difficult to manage on the SQL side of things.
I came across Kendra Little's website and post here, and she seems to see the same thing:
- Implicit transactions Implicit transactions are a bit weird, and I typically only run into them when applications have been written for a different relational database and then ported to SQL Server.
My question is why? What benefit do implicit transactions provide to the application? It seems like extra work and makes things more difficult all around.