some years ago, there was danger in using the command databaseManager.startTransaction() on a SQLServer database:
if one person killed a servoy session while a transaction was open, the entire servoy server freeze and no one could work.
Can anyone tell me if this kind of issue is already fixed?
Hi Marco
We had similar Problems with Transactions on a 2008/R2 Server. We issued
ALTER DATABASE DBName SET READ_COMMITTED_SNAPSHOT ON
ALTER DATABASE DBName SET ALLOW_SNAPSHOT_ISOLATION ON
on each Database and got rid of the problem. Everything works smooth since then.
Maybe it helps on your problem as well.